Video Screencast Help

How to manage Blue Screen of Death (BSOD)

Created: 18 May 2007 • Updated: 05 May 2008 • 5 comments
riva11's picture
+7 7 Votes
Login to vote

In addiction to my previous post Windows XP Common Stop Messages, I'd like to give more info related to managing the Blue Screen of Death (BSOD).

These errors show up at the worst possible times... usually after midnight. And there's always someone willing to call you in to solve this issue immediately.

A normal solution for is probably shutdown the server and restart, lose all your data and wait to see what happens. Maybe the problem will be resolved. But if you see it again, the same fantastic ( ... ) screen then you need to investigate the cause more thoroughly.

The first operation is identify the error message in the BSOD. This information is in the first part of the blue screen and contains an error code number, the addresses where the error occurred, and text where the type of error is reported.

Using this information, you can start the investigation.

Some resources are reported in my previous post and in some comments. See, for example :

Common XP Stop messages

XP Stop messages

A good suggestion is using the Debugging Tools for Windows 32-bit Version to analyze the dump generated during the crash.

Debugging Tools for Windows 32-bit Version

Other interesting sites that can help to understand what happens during a BSOD:

Introduction to Windows NT Stop Errors

Troubleshooting Windows Stop Messages

And, of course, looking for the error reported in the BSOD on the Microsoft Knowledge Base at this link :
Microsoft Knowledge Base

As you can see, there are many ways that you can come to understand and try to solve a BSOD. Maybe it's not really easy but with the right information, you can analyze the BSOD and try to solve the software issue.

Regards

Comments 5 CommentsJump to latest comment

mb773's picture

About BSOD there's on wikipedia a good description ( http://en.wikipedia.org/wiki/Blue_Screen_of_Death )

Regards

+6
Login to vote
riva11's picture

Thanks for your contribution, this descritpion in a general way is a good one, even if the wikipedia is not a IT tech skilled.
regards
PM

+6
Login to vote
riva11's picture

In case you need to debug drivers, applications, and services for Windows Vista and Windows Server 2008, has been released Debugging Tools also for these OS and available versions for 32-bit x86, native Intel Itanium, and native x64 platforms.

Link: http://www.microsoft.com/whdc/devtools/debugging/i...

Paolo

+6
Login to vote
riva11's picture

In case you need to produce a crash the Windows operating system with a BSOD (of course for some tests), take a look on nirsoft tool (http://www.nirsoft.net/utils/start_blue_screen.html).
It allows to crash with 5 paramenters a computer based on Windows 2000, Windows XP, Windows Server 2003, and Windows Vista (32-bit).

+6
Login to vote
jdulle's picture

There is an easier way to force a memory dump and blue screen without the use of third party tools. I have had to use this method in order to create a memory dump to send to a vendor in the past.

http://www.monblog.ch/blog/?p=200702281201530

+1
Login to vote