Blue Screen Of Death..

[Guest]

Wow, I'm sure we've all heard that title before o.0;; I'm having a serious,
annoying problems with my Windows XP Home Edition system. I like to leave my
computer on at night for a bunch of different reasons (mostly to download
things). Well, just about every morning I wake up and open up my laptop, it's
at the logon screen (where I left it, after hitting Switch User the night
before so my cousins can't get on it). All seems well, but after I type in my
password, it boots up as if it had been shut down. After this happening to me
a good 10 times already, it's really starting to get annoying. Now this is
what's happening. From what I've gathered together, my computer causes a
"serious error" almost every night while I leave it on, and automatically
reboots itself. Well, when I log on, as soon as it's done booting up, it
displays the Microsoft "You're computer has just recovered from a serious
error" box, and everytime I send a report (I have like 10 times already), it
says "Bad dump file submitted." I'm guessing that means, it doesn't know what
the heck went down with my computer? This odd "serious error" has occured
many-a-times while I'm actually on it, too. The blue screen pops up out of
nowhere, and I have to time to read the error or anything, because the second
it comes up, my computer restarts. I don't know what the heck is going on..
I'll be happy to go into more detail (if possible, haha) with someone or
answer some questions about my machine or whatever. I just reaaaally hope
there's some way to find a tool to tell me what's wrong, or SOMETHING-
ANYTHING to help me with this. I would greatly, GREATLY appreciate it!!

~Preston

 

[Guest]

Please submit the exact STOP error message taht the BSOD is showing. Also,
at times there is a file mentioned in the BSOD - please let us know if there
is one mentioned, and it's name if it is mentioned.

- John

 

[Guest]

With Debugging Tools from Microsoft (http://www.microsoft.com/whdc/devtools/debugging/default.mspx) and some information from KB article 315263 you could determine the .sys, or .dll file which is causing the BSOD.

How to read the small memory dump files that Windows creates for debugging
http://support.microsoft.com/default.aspx?scid=kb;en-us;315263

Good luck!

 

[Guest]

Daniel,

Would you mind if maybe you could use Remote Assistance with me or something
to help me out? I'm better than your average computer user, but this kind of
stuff boggles my mind =) And I always love to learn advanced stuff about the
thing that will make my career in the future!

~Preston

 

[Bruce Chambers]

Wow, I'm sure we've all heard that title before o.0;; I'm having a serious,
annoying problems with my Windows XP Home Edition system. I like to leave my
computer on at night for a bunch of different reasons (mostly to download
things). Well, just about every morning I wake up and open up my laptop, it's
at the logon screen (where I left it, after hitting Switch User the night
before so my cousins can't get on it). All seems well, but after I type in my
password, it boots up as if it had been shut down. After this happening to me
a good 10 times already, it's really starting to get annoying. Now this is
what's happening. From what I've gathered together, my computer causes a
"serious error" almost every night while I leave it on, and automatically
reboots itself. Well, when I log on, as soon as it's done booting up, it
displays the Microsoft "You're computer has just recovered from a serious
error" box, and everytime I send a report (I have like 10 times already), it
says "Bad dump file submitted." I'm guessing that means, it doesn't know what
the heck went down with my computer? This odd "serious error" has occured
many-a-times while I'm actually on it, too. The blue screen pops up out of
nowhere, and I have to time to read the error or anything, because the second
it comes up, my computer restarts. I don't know what the heck is going on..
I'll be happy to go into more detail (if possible, haha) with someone or
answer some questions about my machine or whatever. I just reaaaally hope
there's some way to find a tool to tell me what's wrong, or SOMETHING-
ANYTHING to help me with this. I would greatly, GREATLY appreciate it!!

~Preston

It's likely to be a problem with the computer's over-heating. Normal,
consumer-grade laptop computers simply don't have the cooling system to
handle 24/7 operation. You might find something here that helps:
http://www.pccasegear.com/category142_1.htm

Beyond that, to get started troubleshooting the cause of your
problems, we'll need to learn what specific errors are occurring and
being recorded.

To get the error message from the blue screen (a.k.a. the BSOD --
Blue Screen of Death), you'll need to turn off WinXP's automatic
reboot "feature:" Right-click My Computer > Properties > Advanced >
Startup and Recovery > Uncheck "Automatically restart." The next time
your PC crashes, you'll be left with a blue screen full of memory
addresses and other seeming gibberish. The top 2 or 3 lines of this
screen will contain information that can help solve your problem.
Carefully write down these lines and post the exact text back here.
Hopefully, one of us will be able to provide some insight.

Additionally, you should check your Event Logs to see if they can
shed any light on the matter, To do so, Right-click My Computer >
Manage > Event Viewer > System and Application. Record the specifics
of any red-flagged error messages and post the exact text back here.
Again, hopefully, one of us will be able to provide some insight.


--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH

 

[Guest]

First of all, By default, Windows restarts itself if a stop message occurs. You can avoid that, therefore, a BSOD will be shown:

1. Open Start, Run, type (without quotes) 'sysdm.cpl' and press Enter.
2. Click the Advanced tab.
3. Under the Startup and Recovery field, press Settings.
4. Uncheck the 'Automatically restart' box.
5. Click OK.

When the computer shows a blue screen, write down all data it provides, maybe that information is enough and it could even pinpoint a device driver, so the diagnosing process is even easier.

If the blue screen does not show enough information, you could examine the dump file using WinDbg from Debugging Tools:

Open WinDbg and configure the application to download the most current symbols from MS website (the KB article that I mentioned explains this). Then, press Ctrl+D to show the Open Crash Dump dialog box and select the dmp file that XP has created (minidumps are stored by default in 'C:\Windows\Minidump' folder).

Take a look at the output, at the end of the text there may be a line that says something like 'Probably caused by :'. Well, we have a clue about the file which caused the problem, type '!analyze -v' (without quotes) and press Enter to display a more complete debug information. The 'Arguments' section could be interesting especially if it points to an IRP address (use the '!IRP 87e5a490' command if the referenced IRP address is 87e5a490, for example).

This is a general method for debugging Windows crash dump files. Unfortunately, each crash dump is different and there are not any valid steps for all of them, investigation and experimentation do the rest. Windows Debugging Tools help file will assist you to understand better all this stuff and will provide you further information.

 

[Steve N.]

Wow, I'm sure we've all heard that title before o.0;; I'm having a serious,
annoying problems with my Windows XP Home Edition system. I like to leave my
computer on at night for a bunch of different reasons (mostly to download
things). Well, just about every morning I wake up and open up my laptop, it's
at the logon screen (where I left it, after hitting Switch User the night
before so my cousins can't get on it). All seems well, but after I type in my
password, it boots up as if it had been shut down. After this happening to me
a good 10 times already, it's really starting to get annoying. Now this is
what's happening. From what I've gathered together, my computer causes a
"serious error" almost every night while I leave it on, and automatically
reboots itself. Well, when I log on, as soon as it's done booting up, it
displays the Microsoft "You're computer has just recovered from a serious
error" box, and everytime I send a report (I have like 10 times already), it
says "Bad dump file submitted." I'm guessing that means, it doesn't know what
the heck went down with my computer? This odd "serious error" has occured
many-a-times while I'm actually on it, too. The blue screen pops up out of
nowhere, and I have to time to read the error or anything, because the second
it comes up, my computer restarts. I don't know what the heck is going on..
I'll be happy to go into more detail (if possible, haha) with someone or
answer some questions about my machine or whatever. I just reaaaally hope
there's some way to find a tool to tell me what's wrong, or SOMETHING-
ANYTHING to help me with this. I would greatly, GREATLY appreciate it!!

~Preston

Right click My Computer, Properties, Advanced tab, Startup and Recovery,
uncheck Automatically Restart. The next time the BSOD occurs it will
stay on screen until you reset the PC, then you can write it down and
post it here.

Steve

 

[Guest]

Of course, hardware problems such as overheating or bad RAM sticks could also produce unexpected reboots.

 

[Guest]

Bruce,

I appreciate your insight into my problem. As far as cooling goes, it should
be no problem whatsoever. I have an Alienware Area51 laptop, and as far as
those things you showed me go, I have two of those on the bottom of the
laptop that are used to suck in air. I think they work quite effectively. I
can put my hand near the little heat dispertion bays, and all seems only
slightly hot. I know that really doesn't account for the true temperature of
the processor and such, but it's a good idea. Also, if it was due to
overheating, I don't think it would reboot automatically, and cause a
"serious error". It's definitely an error in a dll or sys file, or something
like that. I had found that auto restart command in my Advanced tab in system
right before I saw your message. I have already unchecked it, and I will post
the information it gives me at the next error. Daniel, another replier, was
saying I should use a debugger. I'm not quite that advanced to know how to
use one =/ I read through a few pages, and it's something I'm going to need
some guidance on. But as I said, I shall post the error that occurs on here
next time it happens. I appreciate yours, and everyone elses support!

~Preston

 

[Bruce Chambers]

Bruce,

I appreciate your insight into my problem. As far as cooling goes, it should
be no problem whatsoever. I have an Alienware Area51 laptop, and as far as
those things you showed me go, I have two of those on the bottom of the
laptop that are used to suck in air. I think they work quite effectively. I
can put my hand near the little heat dispertion bays, and all seems only
slightly hot. I know that really doesn't account for the true temperature of
the processor and such, but it's a good idea.

Good enough. I was simply trying to guess the most likely cause, given
what little information you had provided in the original post.

Also, if it was due to
overheating, I don't think it would reboot automatically, and cause a
"serious error".

Actually, that exactly the type of symptom one would see with an
over-heating system that lacks a safety shutdown capability. Thermally
stressed RAM would be the primary suspect.

It's definitely an error in a dll or sys file, or something
like that.

... Which may just happen to be the file active in RAM at the time of
the crash; it's not necessarily the cause of the failure. Of course, it
could also be that the mentioned file is corrupted; the precise Stop
Code should help. FYI, though: With WinXP, I've yet to see a BSOD that
wasn't caused by a hardware failure of some sort. But, yes, I do
realize that damaged device drivers can also cause the problem; I just
haven't run across that situation, yet.

I had found that auto restart command in my Advanced tab in system
right before I saw your message. I have already unchecked it, and I will post
the information it gives me at the next error.

Very good. Keep us posted.


--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH

 

[Guest]

Well Bruce,

I got two different errors today.. here's the first:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Technical Information:
***STOP: 0x000000D1 (0xE20F8FA4, 0x000000FF, 0x00000000, 0x8613FFAA)

 

[Guest]

Daniel,

I got two different errors today. Maybe this will help you decipher my
problem.. here's the first:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Technical Information:
***STOP: 0x000000D1 (0xE20F8FA4, 0x000000FF, 0x00000000, 0x8613FFAA)

 

[Guest]

Steve,

I got two different errors today.. here's the first:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Technical Information:
***STOP: 0x000000D1 (0xE20F8FA4, 0x000000FF, 0x00000000, 0x8613FFAA)

 

[Bruce Chambers]

Well Bruce,

I got two different errors today.. here's the first:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Technical Information:
***STOP: 0x000000D1 (0xE20F8FA4, 0x000000FF, 0x00000000, 0x8613FFAA)
------------------------------------------------------------------------------------------
Here's the second, that happened like 10mins ago:

***STOP: 0x0000008E (0xC0000005, 0x85BBF2D7, 0xF0EC1920, 0x00000000)
------------------------------------------------------------------------------------------
On the second one, there was no information at the top. I really, REALLY
hope you guys can figure it out. I'm going to reply to the other guys too =)

~Preston

That reveals quite a few possibilities. Some of the more "promising"
ones are:

Error Message with RAM Problems or Damaged Virtual Memory Manager
http://support.microsoft.com/default.aspx?scid=kb;en-us;810093

You receive a STOP 0xD1 error message when you start your Windows
XP-based computer
http://support.microsoft.com/default.aspx?scid=kb;en-us;839876

You receive a "STOP 0x000000D1" error message on your Windows XP Service
Pack 2-based portable computer
http://support.microsoft.com/default.aspx?scid=kb;en-us;888399

You receive a "Stop 0x0000008E" error message after you resume your
laptop computer
http://support.microsoft.com/default.aspx?scid=kb;en-us;833837

A "STOP: 0x0000008E" error message occurs when you change the hardware
acceleration setting
http://support.microsoft.com/default.aspx?scid=kb;en-us;330187


--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH

 

[Rock]

Daniel,

I got two different errors today. Maybe this will help you decipher my
problem.. here's the first:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Technical Information:
***STOP: 0x000000D1 (0xE20F8FA4, 0x000000FF, 0x00000000, 0x8613FFAA)
------------------------------------------------------------------------------------------
Here's the second, that happened like 10mins ago:

***STOP: 0x0000008E (0xC0000005, 0x85BBF2D7, 0xF0EC1920, 0x00000000)
------------------------------------------------------------------------------------------
On the second one, there was no information at the top. I really, REALLY
hope you guys can figure it out. I'm going to reply to the other guys too =)

~Preston

<snip>

See these links: http://aumha.org/win5/kbestop.htm

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

 

[David Candy]

Type verifier in Start Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.

If you can't start after enabling verifier
choose Last Known Good Configuration at the Failed Boot menu (which will
start without verifier).


You will be creating a crash dump file in c:\windows\minidump every blue screen. Make sure you are set to record minidumps (Small Memory Dumps) - type it in Help to see how.

Then

If you have the XP SP2 Security Update CD (else see
http://www.microsoft.com/whdc/­devtools/debugging/symbolpkg.m­spx
)


Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS

Download
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

Load the crash dump file into windbg
and read what it says. You may need to tell it where the symbols are. Read it.
Type
!Analyze -v
into Windbg's command line.
(this will hopefully tell you the faulty component)

If the above is too technical then email the crash dump files to davidc @ mvps.org. Don't send me lots of them. Just the one from your last crash after you turn verifier on. And only one per mail.

You can look up specific details here
http://msdn.microsoft.com/library/d..._ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp

If it indicates faulty memory might be the cause you can get a memory tester
here
http://oca.microsoft.com/en/wi­ndiag.asp


If it mentions a core windows system file, meaning it a MS fix is required,
upload a minidump to

http://oca.microsoft.com

Also try typing the main error code in Help while online (ie,
Stop 0x50
and also try in the 8 digit form
stop 0x00000050)
and if there are too many hits use a filename if available. Generally memory
addresses are different for each computer (as each computer has a different
mix of drivers) so parameters that are memory addresses aren't that useful for searching, but NTStatus codes are (plus you can look them up here http://cvs.sourceforge.net/viewcvs.py/mingw/w32api/include/ddk/ntstatus.h?rev=1.2).

 

[Steve N.]

Steve,

I got two different errors today.. here's the first:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Technical Information:
***STOP: 0x000000D1 (0xE20F8FA4, 0x000000FF, 0x00000000, 0x8613FFAA)
------------------------------------------------------------------------------------------
Here's the second, that happened like 10mins ago:

***STOP: 0x0000008E (0xC0000005, 0x85BBF2D7, 0xF0EC1920, 0x00000000)
------------------------------------------------------------------------------------------
On the second one, there was no information at the top. I really, REALLY
hope you guys can figure it out.

~Preston

Test your RAM, do a search for Memtest86 and for Microsoft Memory
Diagnostic, download them, create the boot disks for them and run them
both for serveral passes.

Steve