BSOD Upon First Booup of the Day

  • Thread starter Thread starter Sam
  • Start date Start date
S

Sam

I have a Dell Dimension 8200 computer with windows XP Pro (SP3) installed.
The computer has been operating without any apparent problems. I have not
installed any software or hardware in the last three months, except for the
monthly MS Security Updates and the daily definitions for ESET NOD 32 (ver
4) and Malwarebytes Anti-Malware programs.

This morning on the first bootup of the day, I experienced the BSOD. If my
memory is correct, the message on the screen said something to the effect
that the computer was being shutdown to prevent damage. I pressed the power
button on the tower and the computer shutdown. I waited for about five
minutes and pressed the power butter again and the bootup was completed
without any problems. I copied the following information from the Event
Viewer (Event ID 1001).

"The computer has rebooted from a bugcheck. The bugcheck was 0x1000008e,
0xc000005, 0x80565114, 0xf39ad990, 0x00000000. A dump was saved in
C:\WINDOWS\Minidump\Mini070809-01.dmp."

So far the computer has been operating for over two hours and I have not
notice any unusual problems. Also information in the DiskCheckup program,
HD Tune, and Event view do not indicate anything abnormal.

I did a quick Google search but did not notice anything that might apply to
my situation. Any help would be very much appreciated, Sam.
 
Sam

In the Stop Error under this line it often refers to a file. What is the
file? This detail does not appear in the Event Viewer version of the
report,

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Right click on
the My Computer icon on the Desktop and select Properties, Advanced,
Start-Up and Recovery, System Failure and uncheck box before
Automatically Restart.Do not re-enable automatic restart on system
failure.

Background information on Stop Error message 0x8E
http://msdn2.microsoft.com/en-us/library/ms794023.aspx

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
A kernel mode program generated an exception which the error handler
didn't catch. These are nearly always hardware compatibility issues
(which sometimes means a driver issue or a need for a BIOS upgrade).
Source: http://aumha.org/a/stop.htm

You may find the degree of diffulty for my next suggestion too much You
can use a Kernel Debugger to examine the 0x0000000A: IRQL Dump Report.
If you succeed in running the debugger post a copy of the Report and
obtain a stack trace.

Install Debugging Tools for Windows 32-bit Version
http://www.microsoft.com/whdc/devtools/debugging/installx86.Mspx


--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Gerry, very much appreciate your reply and information. I checked the
"automatic restart on system failure" and it was disabled as you suggested.
Regarding your first paragraph, "In the Stop Error under this line it often
refers to a file." Would this file be listed somewhere on the BSOD when it
appears on the monitor? I don't remember seeing any file mentioned in the
BSOD but I could have easily missed it.

I planned to shutdown the computer when I finish this email. Then tomorrow
morning, will bootup the computer and be ready with pen and paper in case
the computer decides to do a BSOD again (hope not!!) Will let you know what
happens tomorrow.

Regarding the Debugging Tool, I will read the referred URL information and
see if I can understand enough about using the program.

Thanks, Sam.
 
To Rich and Gerry, before booting up this afternoon, I opened the computer
tower and reset all of the cables and cards on the motherboard. DVD, and
hard drives. Fortunately, the initial bootup was without difficulty. Don't
know if the resetting solved the BSOD that the computer experienced
yesterday or if it was just a random problem. Thanks again for your help,
Sam.
 
You may find that the BSOD was the result of a hardware problem. If so, it
will likely reoccur more and more often,
until there is a hard failure. Cleaning and reseating stuff may have
cleared the problem.
 
Back
Top