Coolme Posted December 25, 2004 Share Posted December 25, 2004 (edited) Windows XP pro sp2 crashes regularly and unexpectedly on my computer, and I want to find out why. In my C:\WINNT\Minidump file, I have 69 dump files and some of them are back from my sp1 days. So I decided to see what's causing the crashes and downloaded dumpchk.exe from here. So I used dumpchk.exe to open one of the .chk files and this is an example of what I get.... Loading dump file C:\WINNT\Minidump\Mini121504-01.dmp ----- 32 bit Kernel Mini Dump Analysis DUMP_HEADER32: MajorVersion 0000000f MinorVersion 00000a28 DirectoryTableBase 00039000 PfnDataBase 81a13000 PsLoadedModuleList 80561b20 PsActiveProcessHead 80567bd8 MachineImageType 0000014c NumberProcessors 00000001 BugCheckCode 1000000a BugCheckParameter1 00000166 BugCheckParameter2 00000002 BugCheckParameter3 00000000 BugCheckParameter4 804ec9c3 PaeEnabled 00000000 KdDebuggerDataBlock 80553760 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 0000064c DriverListOffset 00003260 DriverCount 00000075 StringPoolOffset 00005520 StringPoolSize 00001000 BrokenDriverOffset 00000000 TriageOptions 00000041 TopOfStack 80557534 DebuggerDataOffset 00002fd0 DebuggerDataSize 00000290 DataBlocksOffset 00006520 DataBlocksCount 00000003 Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Kernel base = 0x804de000 PsLoadedModuleList = 0x80561b20 Debug session time: Wed Dec 15 23:42:08 2004 System Uptime: 0 days 2:38:19 start end module name 804de000 806f2780 nt Checksum: 002160C9 Timestamp: Wed Aug 04 00: 19:48 2004 (41108004) Unloaded modules: f1914000 f193e000 kmixer.sys Timestamp: unavailable (00000000) f19de000 f1a08000 kmixer.sys Timestamp: unavailable (00000000) f1b1e000 f1b48000 kmixer.sys Timestamp: unavailable (00000000) f1b1e000 f1b48000 kmixer.sys Timestamp: unavailable (00000000) f1b1e000 f1b48000 kmixer.sys Timestamp: unavailable (00000000) f1be8000 f1c12000 kmixer.sys Timestamp: unavailable (00000000) f1df2000 f1e1c000 kmixer.sys Timestamp: unavailable (00000000) f28eb000 f2915000 kmixer.sys Timestamp: unavailable (00000000) f7c10000 f7c11000 drmkaud.sys Timestamp: unavailable (00000000) f2c6a000 f2c77000 DMusic.sys Timestamp: unavailable (00000000) f2c7a000 f2c88000 swmidi.sys Timestamp: unavailable (00000000) f2915000 f2938000 aec.sys Timestamp: unavailable (00000000) f7a89000 f7a8b000 splitter.sys Timestamp: unavailable (00000000) f70d6000 f70da000 wADV01nt.sys Timestamp: unavailable (00000000) f70de000 f70e1000 wADV02NT.sys Timestamp: unavailable (00000000) f7a1f000 f7a22000 wADV05NT.sys Timestamp: unavailable (00000000) f7a0b000 f7a0e000 wSiINTxx.sys Timestamp: unavailable (00000000) f7917000 f791c000 wVchNTxx.sys Timestamp: unavailable (00000000) f7907000 f790f000 wATV01nt.sys Timestamp: unavailable (00000000) f78f7000 f78fc000 wATV02NT.sys Timestamp: unavailable (00000000) f770f000 f7718000 wATV04nt.sys Timestamp: unavailable (00000000) f78e7000 f78ed000 wCh7xxNT.sys Timestamp: unavailable (00000000) f78d7000 f78dd000 wATV06nt.sys Timestamp: unavailable (00000000) f7a03000 f7a06000 wADV07nt.sys Timestamp: unavailable (00000000) f79f7000 f79fa000 wADV08nt.sys Timestamp: unavailable (00000000) f79ef000 f79f2000 wADV09nt.sys Timestamp: unavailable (00000000) f78c7000 f78ce000 wATV10nt.sys Timestamp: unavailable (00000000) f7313000 f7316000 wADV11nt.sys Timestamp: unavailable (00000000) f792f000 f7934000 Cdaudio.SYS Timestamp: unavailable (00000000) f70c6000 f70c9000 Sfloppy.SYS Timestamp: unavailable (00000000) Finished dump check :huh: :blink: I don't know if it's just me, but it doesn't look anything like this... So could anyone here please turn that dump file in eneglish and tell me what's causing my system to crash? I can post more dump files if you want. Thanks. Edited December 25, 2004 by Coolme Link to comment Share on other sites More sharing options...
dazsherm Posted December 26, 2004 Share Posted December 26, 2004 i've seen this many times. it's usually bad ram. Link to comment Share on other sites More sharing options...
Coolme Posted December 27, 2004 Author Share Posted December 27, 2004 i've seen this many times. it's usually bad ram. Okay, thanks. Link to comment Share on other sites More sharing options...
k22 Posted December 27, 2004 Share Posted December 27, 2004 check the event viewer (application & system sections) for understandable messages Link to comment Share on other sites More sharing options...
Recommended Posts