Help with BSOD

[Guest]

I have XP Pro SP2. I've started to get BSOD on cold boot. This sometimes
happens after the desktop appears and sometimes before the desktop appears.
My system was running fine before. After a couple of re-boots I eventually
get into windows. It is then stable until the next cold boot.

The problem is that I don't get chance to read the BSOD as it doesn't stay
on the screen for long. I've tried setting the Start-up and Recovery dialog
so that XP doesn't automatically restart after system failure. This has no
effect. I've also tried looking at the System Event viewer but nothing is
recorded.

What can I do to get more information about the cause of this error?

 

[Guest]

Hi Lee,

For understanding the BSOD you can use the Windows Debugging Tool:

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

All the BSOD reports are stored at : C:\Windows\Minidump

Regards,

Jitesh Biswas

http://jiteshbiswas.tripod.com

 

[Guest]

I've analysed the minidump file using dumpcheck and received the following
output. I see the stop code is 0000009c but this could be related to any
hardware failure. Are there any other clues in the output from dumpcheck
that would lead me to the offending hardware/driver>

C:\Program Files\Support Tools>dumpchk.exe
c:\windows\minidump\Mini073106-01.dmp

Loading dump file c:\windows\minidump\Mini073106-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00725000
PfnDataBase 81000000
PsLoadedModuleList 805531a0
PsActiveProcessHead 80559258
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 0000009c
BugCheckParameter1 00000004
BugCheckParameter2 80545ff0
BugCheckParameter3 b2000000
BugCheckParameter4 00070f0f
PaeEnabled 00000001
KdDebuggerDataBlock 80544ce0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00003fff
DriverListOffset 00006c10
DriverCount 0000008b
StringPoolOffset 00009558
StringPoolSize 00001338
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack b101a000
DebuggerDataOffset 00006980
DebuggerDataSize 00000290
DataBlocksOffset 0000a890
DataBlocksCount 00000004


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Mon Jul 31 08:56:30 2006
System Uptime: 0 days 0:04:49
start end module name
804d7000 806cd280 nt Checksum: 001F632B Timestamp: Wed Mar 02
00:
34:37 2005 (42250A1D)

Unloaded modules:
b501c000 b5046000 kmixer.sys Timestamp: unavailable (00000000)
baec7000 baec8000 drmkaud.sys Timestamp: unavailable (00000000)
b9cdb000 b9ce8000 DMusic.sys Timestamp: unavailable (00000000)
b50be000 b50cc000 swmidi.sys Timestamp: unavailable (00000000)
b5046000 b5069000 aec.sys Timestamp: unavailable (00000000)
bae12000 bae14000 splitter.sys Timestamp: unavailable (00000000)
b509e000 b50ae000 Serial.SYS Timestamp: unavailable (00000000)
b4d2b000 b4d3f000 Parport.SYS Timestamp: unavailable (00000000)
bac68000 bac6d000 Cdaudio.SYS Timestamp: unavailable (00000000)

Finished dump check

C:\Program Files\Support Tools>

 

[Guest]

Hi Lee,

Can you send the dump file to (e-mail address removed)

(Note: Don't change the spelling of ms_assitance : "s" is missing)

I can try to check the same.

Regards,

Jitesh Biswas

 

[Guest]

I've sent my dump file to you. Furthermore, when I tried to run WinDBG I got
errors about missing symbols. I've not sure how to rectify this.

 

[Guest]

Hi Lee,

Update *********************

Your minidump file gives the following error:

Use !analyze -v to get detailed debugging information.
BugCheck 9C, {4, 80545ff0, b2000000, 70f0f}
Probably caused by : ntkrnlpa.exe ( nt!KdPitchDebugger+ef4 )
Followup: MachineOwner

Check the forum : http://forums.amd.com/lofiversion/index.php/t67969.html

*********************
I am looking into the issue, lets see if we can resolve it.