XP's Blue Screen of Death

[Ed]

I feel like Win 95 Blue Screen of death is back except XP
doesn't just hang it automatically reboots! Nice trick!
Anyway twice today my Windows XP Home Edition just did a
total reboot without warning. I checked out the logs and
find there's a system error with a log dump. I've been
trying to locate the answers to the errors through
support to no avail. I'm having no luck finding anything
on the log file using MS support and the dumpchk.exe
fails with the following:
C:\Documents and Settings\Ed>dumpchk.exe Memory.dmp
Loading dump file Memory.dmp
**** DebugClient cannot open DumpFile - error 80070002

This has happened a handful of times in the past couple
of months and it seems to alude me by rebooting when I'm
not around. I have NOT installed SP2, yet, I'm a bit
apprehensive. Any help or guidance much appreciated!


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 8/25/2004
Time: 6:07:31 PM
User: N/A
Computer:
Description:
The computer has rebooted from a bugcheck. The bugcheck
was: 0x100000ce (0xf87797da, 0x00000000, 0xf87797da,
0x00000000). A dump was saved in:
C:\WINDOWS\Minidump\Mini082504-01.dmp.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/25/2004
Time: 6:08:10 PM
User: N/A
Computer:
Description:
Error code 100000ce, parameter1 f87797da, parameter2
00000000, parameter3 f87797da, parameter4 00000000.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 63 100000c
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 66 38 eters f8
0030: 37 37 39 37 64 61 2c 20 7797da,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 66 38 37 37 39 37 , f87797
0048: 64 61 2c 20 30 30 30 30 da, 0000
0050: 30 30 30 30 0000

 

[Thane of Lochaber]

You can turn off the automatic reboot if you wish, and you will get the blue
screen instead. If you want right click My Computer and click the Advanced
tab. In the "Startup and Recovery" section click the Settings button. Now
uncheck the box "Automatically restart". This will not solve the crash
problem of course, but perhaps you'll be able to get more information by
reading the crash screen.

 

[ed]

Thanks for the Tip Thane, good point on stopping the auto
reboot as a way to catch some more info. Any pointers on
deciphering the error logs?

 

[Chad Harris]

Ed--

I couldn't find info on that error message but here's what I'd do. It
doesn't seem to b e a terribly helpful error, more info might be in Event
Viewer--it reminds me of the error "Windows Cannot Find Search." I did
find one thread on the error here:
http://sillydog.org/forum/viewtopic.php?t=6615

I can't do anything with the hex portion of those errors. You might try
googling them,but most of them will probably be non-specific. Hardware or
drivers are always suspect.


I'd run Adaware and Spybot. I'd do a viral scan. I'd definitely run System
File Checker by putting "sfc /purgecache" then "sfc /scannow" in your run
box or at your command prompt. You may be prompted to use the CD unless you
point it to the install files of your latest service pack by doing the
regedit here:

Introduction to using scannow sfc (system file checker)
http://www.updatexp.com/scannow-sfc.html

Description of the Windows File Protection Feature
http://support.microsoft.com/defaul...port/kb/articles/Q222/1/93.ASP&NoWebContent=1

Also humor me because this sometimes helps spontaneous reboots: Run a
"chkdsk /r" because it implies (includes chkdsk /f) from the command prompt.

Try going to Event Viewer by putting "eventvwr.msc" in the run box and at
the time of the error see if you can get additional information in
Application and Systems. It appears you already have some error info from
there.

How To View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q308427

How to Use Dumpchk.exe to Check a Memory Dump File
http://support.microsoft.com/default.aspx?kbid=315271

How to Troubleshoot Hardware and Software Driver Problems in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q322205

To review Shutdown Event Tracker data, Open Event Viewer. Click System Log,
scroll to the Event column, and find entries with the number 1075.

Read Kelly's article here under reboot.

http://www.kellys-korner-xp.com/xp_qr.htm

I don't know whether installing SP2 would help this or not, but you can
always go to Add/Remove and uninstall it.

hth,

Chad Harris
________________________

I feel like Win 95 Blue Screen of death is back except XP
doesn't just hang it automatically reboots! Nice trick!
Anyway twice today my Windows XP Home Edition just did a
total reboot without warning. I checked out the logs and
find there's a system error with a log dump. I've been
trying to locate the answers to the errors through
support to no avail. I'm having no luck finding anything
on the log file using MS support and the dumpchk.exe
fails with the following:
C:\Documents and Settings\Ed>dumpchk.exe Memory.dmp
Loading dump file Memory.dmp
**** DebugClient cannot open DumpFile - error 80070002

This has happened a handful of times in the past couple
of months and it seems to alude me by rebooting when I'm
not around. I have NOT installed SP2, yet, I'm a bit
apprehensive. Any help or guidance much appreciated!


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 8/25/2004
Time: 6:07:31 PM
User: N/A
Computer:
Description:
The computer has rebooted from a bugcheck. The bugcheck
was: 0x100000ce (0xf87797da, 0x00000000, 0xf87797da,
0x00000000). A dump was saved in:
C:\WINDOWS\Minidump\Mini082504-01.dmp.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/25/2004
Time: 6:08:10 PM
User: N/A
Computer:
Description:
Error code 100000ce, parameter1 f87797da, parameter2
00000000, parameter3 f87797da, parameter4 00000000.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 63 100000c
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 66 38 eters f8
0030: 37 37 39 37 64 61 2c 20 7797da,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 66 38 37 37 39 37 , f87797
0048: 64 61 2c 20 30 30 30 30 da, 0000
0050: 30 30 30 30 0000

 

[Travis King]

You might have bad memory in your computer also. (Or your memory is rated
for a lower speed than the FSB of your processor if you know the more
advanced computers.) I've had two computers that I built that restarted
because of the RAM. One memory module came up with the BSOD then restarted.
The other would just restart without the BSOD. Both computers have not had
new memory modules put in yet, but the fix to the one that had the BSOD was
just to simply drop the FSB on the processor. (A better option of course if
you have the money is to replace the memory.) If you drop the FSB, your
system's speed may go down. (The FSB is the most critical when it comes to
your comptuer's speed.) The other computer that restarted itself will
restart no matter what you do. Good luck...

 

[ed]

Thanks Chad for all the info. the chkdsk -r is where I
suspect, 120GB ATA drive. Great capacity but short on
reliability, already replaced original.

-----Original Message-----
Ed--

I couldn't find info on that error message but here's what I'd do. It
doesn't seem to b e a terribly helpful error, more info might be in Event
Viewer--it reminds me of the error "Windows Cannot Find Search." I did
find one thread on the error here:
http://sillydog.org/forum/viewtopic.php?t=6615

I can't do anything with the hex portion of those errors. You might try
googling them,but most of them will probably be non- specific. Hardware or
drivers are always suspect.


I'd run Adaware and Spybot. I'd do a viral scan. I'd definitely run System
File Checker by putting "sfc /purgecache"

then "sfc /scannow" in your run

 

[Guest]

Hi,

I have same issue with ED, my PC automatically restarts too...randomly.
There are times that I would turn on my PC and use it for 5 hours and I
wouldn't experience it. However, it would happen in some occasion. Im still
in the process of sorting out which driver or hardware could be conflicting.
This is the sample error description I got from Event viewer:

Date: 9/4/2004 Source: System Error
Time: 6:26 AM Category (102)
Type: error Event ID: 1003
user: N/A
computer:

Description:
Error code 000000d1, parameter1 00000000, parameter2 00000002, parameter3
00000000, parameter4 00000000.

0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 64 000000d
0020: 31 20 20 50 61 72 61 6d 1 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 30 2c 20 000000,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000

and this is the errro message the second time i experiecned it

Error code 000000d1, parameter1 00000000, parameter2 00000002, parameter3
00000000, parameter4 00000000.



Error code 000000d1, parameter1 00000000, parameter2 00000002, parameter3
00000000, parameter4 00000000.

0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 64 000000d
0020: 31 20 20 50 61 72 61 6d 1 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 30 2c 20 000000,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000

Now my question is about your suggestion to check on the memory (RAM). I
have 1 Gig of RAM (PC400). Lets say that this is the culprit, would my system
always restart once I open my PC? As I said, there are some instances that
even if i use my PC for hours and even a day it wont restart. However, there
are occasion that it would. If it's a bad memory in my system, should it
always restart since my computer is being used for hours, right? Or are there
occasions (referring to your experience) that even if you have a bad memory
in your system some times it wouldnt restart?

Your response is highly appreciated...