Community Area

Dealing with Blue Screens

by
Mitch Tulloch
[Published on 21 April 2005 / Last Updated on 21 April 2005]

Handling a blue screen is more about common sense than being an uber-geek.

Ever got a had a Windows 2000 or later system blue screen? The information displayed in such "STOP messages" can be cryptic to decipher to say the least. Not many of us are geeky enough to use a kernel debugger to analyze a memory.dmp file and figure out what went wrong. If you're not inclined to do that (and don't want to pay Microsoft PSS to do the same) then try out some of the following steps and you may be able to resolve your problem:

Uninstall the last device you installed.

Roll back a device driver you updated recently.

Open up your box and reseat PCI cards and memory.

Run diagnostics on your hard drives.

Uninstall a recently installed hotfix or service pack.

Roll back the configuration of your system using Last Known Good or XP's System Restore.

Featured Links

Online Survey: The Definitive State of Load Balancing and High Availability

MSExchange.org, KEMP Technologies and numerous MSFT and VMware experts worldwide would like to invite you to participate in our confidential 6 question survey on Load Balancing and High Availability. This survey takes about 6 minutes and all participants who wish can leave their email address and register to win a $50 Amazon gift certificate.

The results of this survey will be used to create a white paper on the State of Load Balancing. Everyone who registers will also get a copy of the white paper.