• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Fatal Error from ati3duag.dll

M

Modulus-X

n00b
Joined
Nov 12, 2003
Messages
3
I have recently been getting random restarts while using my computer. It can happen when I use any of my programs. It totally crashes and the computer immediately restarts. No BSD no nothing. I would call ATI but they charge $1.25 USD per minute (!!!). So I am here begging for help. My Computer specs are as follows:

AMD Athlon Xp 3000+ Barton
Asus A7N8X Deluxe
ATI Brand Radeon 9800 Pro
Crucial Brand (2)512 Sticks of DDR 3200 RAM


Here is what I have done so far:

Sent back a memory stick I thought was faulty, turns out it isn't.
Reinstalled my drivers 3+ times using driver cleaner.
Analyzed dump files.

Here is my most recent crash. It must have happend less than a half hour ago (I apologize for the formatting problems in advance, just copied it out of the bug checker.):

Microsoft (R) Windows Debugger Version 6.3.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini021104-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: E:\I386
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 UP Free x86 compatible
Product: WinNt
Kernel base = 0x804d0000 PsLoadedModuleList = 0x8053e0a8
Debug session time: Wed Feb 11 15:10:14 2004
System Uptime: 0 days 2:32:00.906
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................................................................................................
Loading unloaded module list
..............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 0, aa984abc, 0}

Unable to load image ati3duag.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll
Unable to load image win32k.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for win32k.sys
Unable to load image watchdog.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for watchdog.sys
Unable to load image dxg.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxg.sys
Probably caused by : ati3duag.dll ( ati3duag+268b7 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: aa984abc, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
+0
00000000 ?? ???

TRAP_FRAME: aa984abc -- (.trap ffffffffaa984abc)
ErrCode = 00000000
eax=00000018 ebx=e3bc7018 ecx=00000000 edx=00000000 esi=e2c02230 edi=00000000
eip=00000000 esp=aa984b30 ebp=e2a68010 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296
00000000 ?? ???
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000100 to 00000000

STACK_TEXT:
aa984b2c 00000100 00000000 8ca743ff e2c02230 0x0


FOLLOWUP_IP:
ati3duag+268b7
bfa218b7 ?? ???

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: ati3duag+268b7

MODULE_NAME: ati3duag

IMAGE_NAME: ati3duag.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3fd9fc4c

STACK_COMMAND: .trap ffffffffaa984abc ; kb

BUCKET_ID: 0x8E_ati3duag+268b7

Followup: MachineOwner
---------

Now the question is, what do I do to fix this???
If you need more info let me know I am willing to go get it.
 
err , does ATi have a tech support e-mail you can reach 'em at?

feel like a good ol' Reformat?

vid. card not pushed in all the way?

vid. card fan dead = overheating?

are you OCing?
 
You must log in or register to reply here.
Back
Top