I have a very annoying problem I can´t figure out.
I have all service pack from microsoft installed. I have newest Java software from Sun. Latest display drivers from ASUS. Changed my grahic card from ASUS 9800XT to ASUS AX850XT still have problems. Bye the way I also changed to Motherboard to the same model again (ASUS P4C800-E-Deluxe)

After running JAVA it is 100% for sure that the pc running Windows XP pro goes to blue screen and says it has problems with Atiduag.dll. Also other programs ends up in a crash.

I have some dumps (taken from crash dump)

Can anybody help - I belive that cpc2004 maybe can !

I included some crash dumps to help figure out this - what is the real problem.
From the crach dump it points in the direction to sound drivers ??? or what ?

Hope somebody can help

Best regards HKOCH
----------------------------------------
my crash dump
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 129b4000
PfnDataBase 80566e48
PsLoadedModuleList 805624a0
PsActiveProcessHead 80568558
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 1000008e
BugCheckParameter1 c0000005
BugCheckParameter2 bfbb527f
BugCheckParameter3 b0f599a4
BugCheckParameter4 00000000
PaeEnabled 00000000
KdDebuggerDataBlock 805522e0
MiniDumpFields 000004ff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 00002268
ThreadOffset 000024c0
CallStackOffset 00002720
SizeOfCallStack 00004000
DriverListOffset 000069b0
DriverCount 000000b0
StringPoolOffset 00009df0
StringPoolSize 000033b8
BrokenDriverOffset 00000000
TriageOptions ffffffff
TopOfStack b0f59a18
DebuggerDataOffset 00006720
DebuggerDataSize 00000290


Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sat Dec 10 19:31:32 2005
System Uptime: 0 days 7:10:21
start end module name
804d7000 806fe000 nt Checksum: 002190E8 Timestamp: Wed Mar 02 01:57:27 2005 (42250F77)

Unloaded modules:
b03b0000 b03da000 kmixer.sys Timestamp: unavailable (00000000)
b03b0000 b03da000 kmixer.sys Timestamp: unavailable (00000000)
b03b0000 b03da000 kmixer.sys Timestamp: unavailable (00000000)
b03b0000 b03da000 kmixer.sys Timestamp: unavailable (00000000)
b03b0000 b03da000 kmixer.sys Timestamp: unavailable (00000000)
b03b0000 b03da000 kmixer.sys Timestamp: unavailable (00000000)
b03b0000 b03da000 kmixer.sys Timestamp: unavailable (00000000)
b03b0000 b03da000 kmixer.sys Timestamp: unavailable (00000000)
b03b0000 b03da000 kmixer.sys Timestamp: unavailable (00000000)
b03b0000 b03da000 kmixer.sys Timestamp: unavailable (00000000)
b04ca000 b04f4000 kmixer.sys Timestamp: unavailable (00000000)
b04ca000 b04f4000 kmixer.sys Timestamp: unavailable (00000000)
b04ca000 b04f4000 kmixer.sys Timestamp: unavailable (00000000)
b074c000 b0776000 kmixer.sys Timestamp: unavailable (00000000)
b096e000 b097a000 BS_DEF.sys Timestamp: unavailable (00000000)
b07c6000 b07d2000 BS_DEF.sys Timestamp: unavailable (00000000)
b56cb000 b56f5000 kmixer.sys Timestamp: unavailable (00000000)
b750d000 b7537000 kmixer.sys Timestamp: unavailable (00000000)
f7e77000 f7e78000 drmkaud.sys Timestamp: unavailable (00000000)
b7537000 b7566000 MidiSyn.sys Timestamp: unavailable (00000000)
b7566000 b7589000 aec.sys Timestamp: unavailable (00000000)
b77f6000 b7803000 DMusic.sys Timestamp: unavailable (00000000)
b7806000 b7814000 swmidi.sys Timestamp: unavailable (00000000)
f7ce7000 f7ce9000 splitter.sys Timestamp: unavailable (00000000)
f7ac3000 f7acb000 dvdriver.sys Timestamp: unavailable (00000000)
b776d000 b777e000 psched.sys Timestamp: unavailable (00000000)
f7813000 f781d000 intelppm.sys Timestamp: unavailable (00000000)
f7319000 f731d000 kbdhid.sys Timestamp: unavailable (00000000)
f7a5b000 f7a60000 Cdaudio.SYS Timestamp: unavailable (00000000)
f7329000 f732c000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

Attached Files

output.txt (3.7 KB, 0 views)

From a very new crash

Microsoft Windows (dialog box)
Error Signature:
BCCode : 1000008e BCP1 : C0000005 BCP2 : BFBB527F BCP3 : B44609A4
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

That means that this is also from crash #2

----------------------

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 36fca000
PfnDataBase 80566e48
PsLoadedModuleList 805624a0
PsActiveProcessHead 80568558
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 1000008e
BugCheckParameter1 c0000005
BugCheckParameter2 bfbb527f
BugCheckParameter3 b44609a4
BugCheckParameter4 00000000
PaeEnabled 00000000
KdDebuggerDataBlock 805522e0
MiniDumpFields 000004ff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 00002268
ThreadOffset 000024c0
CallStackOffset 00002720
SizeOfCallStack 00004000
DriverListOffset 000069b0
DriverCount 000000ad
StringPoolOffset 00009d10
StringPoolSize 000032c0
BrokenDriverOffset 00000000
TriageOptions ffffffff
TopOfStack b4460a18
DebuggerDataOffset 00006720
DebuggerDataSize 00000290


Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Dec 11 09:54:44 2005
System Uptime: 0 days 1:04:10
start end module name
804d7000 806fe000 nt Checksum: 002190E8 Timestamp: Wed Mar 02 01:57:27 2005 (42250F77)

Unloaded modules:
b47dd000 b4807000 kmixer.sys Timestamp: unavailable (00000000)
b7201000 b722b000 kmixer.sys Timestamp: unavailable (00000000)
f7e44000 f7e45000 drmkaud.sys Timestamp: unavailable (00000000)
b7282000 b72a5000 aec.sys Timestamp: unavailable (00000000)
b7253000 b7282000 MidiSyn.sys Timestamp: unavailable (00000000)
f79c3000 f79d0000 DMusic.sys Timestamp: unavailable (00000000)
f6c58000 f6c66000 swmidi.sys Timestamp: unavailable (00000000)
f7cdd000 f7cdf000 splitter.sys Timestamp: unavailable (00000000)
f7acb000 f7ad3000 dvdriver.sys Timestamp: unavailable (00000000)
b7489000 b749a000 psched.sys Timestamp: unavailable (00000000)
f7081000 f708b000 intelppm.sys Timestamp: unavailable (00000000)
f7319000 f731d000 kbdhid.sys Timestamp: unavailable (00000000)
f7a5b000 f7a60000 Cdaudio.SYS Timestamp: unavailable (00000000)
f7329000 f732c000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

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


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sat Dec 10 19:31:32.828 2005 (GMT+1)
System Uptime: 0 days 7:10:21.526
Loading Kernel Symbols
........................................................................... ........................................................................... .........................
Loading unloaded module list
..............................
Loading User Symbols
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bfbb527f, b0f599a4, 0}

*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll
Probably caused by : ati3duag.dll ( ati3duag+f927f )

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

1: 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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bfbb527f, The address that the exception occurred at
Arg3: b0f599a4, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruktionen ved "0x%08lx" refererede hukommelse ved "0x%08lx". Hukommelsen kunne ikke "%s".

FAULTING_IP:
ati3duag+f927f
bfbb527f ?? ???

TRAP_FRAME: b0f599a4 -- (.trap ffffffffb0f599a4)
Unable to read trap frame at b0f599a4

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from b0f59a78 to bfbb527f

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b0f59a14 b0f59a78 00000000 e7f9f010 bfbacaba ati3duag+0xf927f
b0f59ac8 804da3ee b0f59b08 bf9e1f40 bfa04508 0xb0f59a78
b0f59b74 bf95f9e7 b0f59bf4 e1f57008 e542a938 nt!ExAcquireResourceExclusiveLite+0x67
b0f59bb0 bf9c2aac b0f59bf4 026001ca 00000001 win32k!WatchdogDdContextDestroy+0x3b
b0f59c04 bf9c5097 026001ca 00000000 00000000 dxg!D3dDeleteHandle+0xe6
b0f59c2c bf8c14de 000004a4 e32988d0 00000000 dxg!DdHmgCloseProcess+0x5f
b0f59c48 bf8bfba8 e32988d0 00000000 00000000 win32k!NtGdiCloseProcess+0x45
b0f59c60 bf820f1c e32988d0 00000000 84a120c0 win32k!GdiProcessCallout+0xea
b0f59c7c 8058c2bf 84b6bc70 00000000 84a120c0 win32k!W32pProcessCallout+0x5c
b0f59d08 805739b4 00000000 84a120c0 00000000 nt!PspExitThread+0x3e4
b0f59d28 8058c631 84a120c0 00000000 b0f59d64 nt!PspTerminateThreadByPointer+0x52
b0f59d54 804dd99f 00000000 00000000 0012fedc nt!NtTerminateProcess+0x118
b0f59d54 7c90eb94 00000000 00000000 0012fedc nt!KiFastCallEntry+0xfc
0012fedc 00000000 00000000 00000000 00000000 0x7c90eb94


FOLLOWUP_IP:
ati3duag+f927f
bfbb527f ?? ???

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: ati3duag+f927f

MODULE_NAME: ati3duag

IMAGE_NAME: ati3duag.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 43506ef3

STACK_COMMAND: .trap ffffffffb0f599a4 ; kb

FAILURE_BUCKET_ID: 0x8E_ati3duag+f927f

BUCKET_ID: 0x8E_ati3duag+f927f

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

Did not find any problems.



// Henrik

I tried with diffent types of power supplies.

Ny current is a NorthQ 4100 PSU 12-19 DB 500W
So i don´t believe it´s a problem with too little supply

Attached Images

northq.jpg (11.5 KB, 0 views)

My RAM is to pcs. of 512 MB -->

1 GB kit EL DDR PC4200 Dual Channel OZC

http://www.ocztechnology.com/product...EL+DDR+PC-4200

Hi,

You don't have to paste the content of your debug report here. Usually we attach the debug report as the attachment. Would you please zip 5 to 6 minidumps and attach the zip file here (note each attachment cannot exceed 100K).

I here add some more files. One zip containing the last 5 minidumps. The other one containing files from the crash dump.

// Henrik

Attached Files

	Minidump.zip (36.3 KB, 1 views)
	crash_111205.zip (23.6 KB, 2 views)

Hi,

All the minidumps are crashed with the same symptom. Upgrade ATI display card driver and dxg.sys.

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b683aa14 b683aa78 00000000 e8401010 bfbacaba ati3duag+0xf927f
b683aab4 805502fa b683abf4 e554d800 00000000 0xb683aa78
b683ab74 bf95f9e7 b683abf4 e1f37008 e62ef3d0 nt!ExFreePoolWithTag+0x664
b683abb0 bf9c2aac b683abf4 3b600018 00000001 win32k!WatchdogDdContextDestroy+0x3b
b683ac04 bf9c5097 3b600018 00000000 00000000 dxg!D3dDeleteHandle+0xe6
b683ac2c bf8c14de 00000a3c e6078550 00000000 dxg!DdHmgCloseProcess+0x5f
b683ac48 bf8bfba8 e6078550 00000000 00000000 win32k!NtGdiCloseProcess+0x45
b683ac60 bf820f1c e6078550 00000000 84455158 win32k!GdiProcessCallout+0xea
b683ac7c 8058c2bf 84a50020 00000000 84455158 win32k!W32pProcessCallout+0x5c
b683ad08 805739b4 00000000 84455158 00000000 nt!PspExitThread+0x3e4
b683ad28 8058c631 84455158 00000000 b683ad64 nt!PspTerminateThreadByPointer+0x52
b683ad54 804dd99f 00000000 00000000 0012feec nt!NtTerminateProcess+0x118
b683ad54 7c90eb94 00000000 00000000 0012feec nt!KiFastCallEntry+0xfc
0012feec 00000000 00000000 00000000 00000000 0x7c90eb94

Hello and thanks for Your help.

I have been having this problem with the last 5 releases of driver for my previous ASUS 9800XT and now with a couple of releases with my AX850. That´s mysterious to me why they haven´t solved this yet.
Is there any way to put on focus for this problem for ASUS or ATI in fact which I believe are writing the drivers for ASUS.

Best regards
Henrik

From where does the dxg.sys come.

And from where do I get at new (newer ? )

// Henrik

Can It have something to do with this ?

http://support.microsoft.com/?kbid=811009

Sorry about my last post - if I read it they say that this is corrected in service pack 2. I´m desparate to get rid of my problem and is ready to try anything.

Same problem for me after swapping my ati 9600XT for the x850.
It seemed to be running slow and after I ran the tests in dxdiag the third test failed.
Played with that for a month (drivers, rollback, repair directx, reinstall directx, yeah right).
Today for the first time I got the blue screen after seeing the java icon on the taskbar.

I give up, I ordered another hard drive (WD Raptor 10K 36G).
I'll install that as master and re-install XP, scoop my data and dump the whole mess.

new thread created

Hi Stella,

Open a new thread for a new problem.