win2k minidump info

[rodent]

My computer (running win2k) resets randomly. In the even viewer, I found this information:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000005, 0x0000001f, 0x00000000, 0x0000001f). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini020102-02.dmp.

How can I analyze the minidump and determine what causes these resets? ANYBODY have any idea?

 

[bsobel]

Unless you have a background in kernel development under Windows you won't be able to. They are mainly of use to MS and other developers when you report a problem. You may have to open a trouble ticket with MS to get it looked at.

Sorry,
Bill

 

[wkapri]

I found this in anandtech's FAQ: why does computer reboot itself
and there's a link from there to more information on microsoft technet site: demystifying the "blue screen of death"

I'm running winxp and would like to figure out what's going on as well..
that site says that there's a DUMPEXAM.EXE in the windows NT CD, is there one on the win2k or winxp CD? cause I can't find it..

this would be easier than to disable the automatic reboot and wait till it does crash and copy it down by hand

anyone got any ideas?

 

[NogginBoink]

bsobel is correct. Unless you know i386 assembly language and the deep inner workings of NT, it's not feasible to develop the skills to do a kernel debug.

In this case, debug skills probably wouldn't take you very far, since the parameters on this STOP 1E indicate to me that there's been some kind of memory corruption.

Dumpexam will only check the integrity of the dump file and ensure it's in the correct format; it won't tell you what caused the crash.