How to interpret MEMORY DUMPS?!?!?!

[vk7773]

Windows XP - Used dumpchk to create txt files for some memory dumps and now I'm not too sure whether it's a hardware or software (driver) issue...i think i have an idea but just want to verify first...tanx...vk.
Here's one of em:
DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 02b602c0
PfnDataBase 805610a8
PsLoadedModuleList 8055c700
PsActiveProcessHead 805627b8
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 0000000a
BugCheckParameter1 09000055
BugCheckParameter2 0000001c
BugCheckParameter3 00000001
BugCheckParameter4 80501ff4
PaeEnabled 00000001
KdDebuggerDataBlock 8054c2e0
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 0000007d
StringPoolOffset 00008ed0
StringPoolSize 000026a0
BrokenDriverOffset 00000000
TriageOptions ffffffff
TopOfStack f8a94da4
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 = 0x8055c700
Debug session time: Thu Jun 23 12:40:00 2005
System Uptime: 0 days 0:00:45
start end module name
804d7000 806e2000 nt Checksum: 001EE722 Timestamp: Tue Mar 01 19:34:38 2005 (42250A1E)
Unloaded modules:
b88e0000 b890a000 kmixer.sys Timestamp: unavailable (00000000)
f8d4a000 f8d4b000 drmkaud.sys Timestamp: unavailable (00000000)
b890a000 b892d000 aec.sys Timestamp: unavailable (00000000)
b8a82000 b8a8f000 DMusic.sys Timestamp: unavailable (00000000)
b8a92000 b8aa0000 swmidi.sys Timestamp: unavailable (00000000)
f8c09000 f8c0b000 splitter.sys Timestamp: unavailable (00000000)
f8985000 f898a000 Cdaudio.SYS Timestamp: unavailable (00000000)
f8b59000 f8b5c000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

 

[cpc2004]

Bugcheck paramter 2 is IRQL and your value is x'1c' which is a clock level interrupt. Clock level interrupt is a well test routine. My XP has thousands of clock level interrupts within an hours. Clock level interupt routine does not crash unless it is hardware error at CPU, M/B or RAM. I've resovled several case of Bugeck 0A at IRQL x'1c' and they are related to hardware error.

Refer the following urls and it has link to some of my resolved cases of clock level interrupt interrupt at XP
http://www.experts-exchange.com/Operating_Systems/WinNT/Q_21419604.html
http://www.experts-exchange.com/Operating_Systems/WinNT/Q_21361736.html
http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21306911.html
https://www.techspot.com/vb/showthread.php?p=143574#post143574 refer page 8 Kritonas
kritonas install the CPU hot tester and find out this is CPU problem. You can ask him the url of the hot tester link.

https://www.techspot.com/vb/showthread.php?p=144841#post144841 refer the post from Boxer

 

[vk7773]

thanks cpc2004...funny thing is that my mobo, video and ram all had to be replaced b/c they were all faulty...possibly bad psu and so i replaced that too...i also replaced the hdd for good measure...but i kept on getting the bsod's still...only thing left was cpu and so i replaced it and so far so good...ur suspicions were correct once again...tanx for the advice!!!