My computer gave me a "blue screen of death" and then
automatically rebooted (I have since changed it so that it
doesn't automatically reboot after a system failure). I
now have a 64K minidump file in the c:\winnt\minidump
folder, but I can't understand anything in the dump file.
Is there any way to make any sense of the file and see
why my computer crashed? Should I change my settings to
get either a kernel memory dump or a complete memory dump
instead of a small memory dump? I appreciate any help that
anyone can give me.

On Tue, 15 Jul 2003 12:27:24 -0700, Jamie <(E-Mail Removed)> wrote:

> My computer gave me a "blue screen of death" and then automatically
> rebooted (I have since changed it so that it doesn't automatically reboot
> after a system failure). I now have a 64K minidump file in the
> c:\winnt\minidump folder, but I can't understand anything in the dump
> file. Is there any way to make any sense of the file and see why my
> computer crashed? Should I change my settings to get either a kernel
> memory dump or a complete memory dump instead of a small memory dump? I
> appreciate any help that anyone can give me.
>

In order: dumpchk.exe is downloadable from various spots. And no. It isn't
any more help except in the hands of an expert.


1 more suggestion: Dig in the event log. You should see an event from "ssve
dump."
Opening it will reveal a message that says "the system has rebooted from a
bugcheck ... a dump was saved in ... "

Paste the full message here (not the dump file, please).

--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

>-----Original Message-----
>On Tue, 15 Jul 2003 12:27:24 -0700, Jamie
<(E-Mail Removed)> wrote:
>
>> My computer gave me a "blue screen of death" and then
automatically
>> rebooted (I have since changed it so that it doesn't
automatically reboot
>> after a system failure). I now have a 64K minidump file
in the
>> c:\winnt\minidump folder, but I can't understand
anything in the dump
>> file. Is there any way to make any sense of the file
and see why my
>> computer crashed? Should I change my settings to get
either a kernel
>> memory dump or a complete memory dump instead of a
small memory dump? I
>> appreciate any help that anyone can give me.
>>
>
>In order: dumpchk.exe is downloadable from various spots.
And no. It isn't
>any more help except in the hands of an expert.
>
>
>1 more suggestion: Dig in the event log. You should see
an event from "ssve
>dump."
>Opening it will reveal a message that says "the system
has rebooted from a
>bugcheck ... a dump was saved in ... "
>
>Paste the full message here (not the dump file, please).
>
>--
>Using M2, Opera's revolutionary e-mail client:
http://www.opera.com/m2/
>.
>
The computer has rebooted from a bugcheck. The bugcheck
was: 0x0000001e (0xc0000005, 0xbfe2d7c0, 0x00000000,
0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was
saved in: C:\WINNT\Minidump\Mini071403-01.dmp.

On Tue, 15 Jul 2003 18:19:21 -0700, Jamie <(E-Mail Removed)> wrote:

>
>> -----Original Message-----
>> On Tue, 15 Jul 2003 12:27:24 -0700, Jamie
> <(E-Mail Removed)> wrote:
>>
>>> My computer gave me a "blue screen of death" and then
> automatically
>>> rebooted (I have since changed it so that it doesn't
> automatically reboot
>>> after a system failure). I now have a 64K minidump file
> in the
>>> c:\winnt\minidump folder, but I can't understand
> anything in the dump
>>> file. Is there any way to make any sense of the file
> and see why my
>>> computer crashed? Should I change my settings to get
> either a kernel
>>> memory dump or a complete memory dump instead of a
> small memory dump? I
>>> appreciate any help that anyone can give me.
>>>
>>
>> In order: dumpchk.exe is downloadable from various spots.
> And no. It isn't
>> any more help except in the hands of an expert.
>>
>>
>> 1 more suggestion: Dig in the event log. You should see
> an event from "ssve
>> dump."
>> Opening it will reveal a message that says "the system
> has rebooted from a
>> bugcheck ... a dump was saved in ... "
>>
>> Paste the full message here (not the dump file, please).
>>
>> -- Using M2, Opera's revolutionary e-mail client:
> http://www.opera.com/m2/
>> .
>>
> The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e
> (0xc0000005, 0xbfe2d7c0, 0x00000000, 0x00000000). Microsoft Windows 2000
> [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini071403-01.dmp.


First off: monitor to see if this is a one time problem. Now would be a
good time to make a backup.
If it (or any other STOP error) recurrs, then start troubleshooting.

The windows 2000 manual page 89.

Most of the suggestions have to do with bad drivers. Have you installed any
new hardware or drivers recently, or done any BIOS tweaks? Also, are you
runsing low on free disk space?

You could have bad hardware, or a heat isue as well.

--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

On Wed, 16 Jul 2003 07:28:41 -0700, Jamie <(E-Mail Removed)> wrote:

> I have started using my PCMCIA ethernet card again - that's the only new
> hardware that I've installed recently. I may use the other ethernet port
> in the port replicator instead to be safe. Thanks for your help.
>
If this is the only time it's happened, i wouldn't worry too much yet.

Laptop? Definately consider heat to be a potential factor if you're using
it in an unairconditioned enviroment.


--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

I'll have to keep the heat thing in mind. I have air
conditioning here, but it doesn't seem to work too well in
this room.