Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

The Blue Screen of Death Blues

Lincoln Spector | Jan. 10, 2011
Pcpchelp has been getting a lot of Blue Screens of Death lately. He asked the Windows forum for help.

FRAMINGHAM, 10 JANUARY 2011 - Pcpchelp has been getting a lot of Blue Screens of Death lately. He asked the Windows forum for help.

Microsoft tried to call them "Stop Errors," but even they have had to accept the name everyone else uses: The Blue Screen of Death (abbreviated as BSoD). One minute you're happily typing or mousing, the next, you're starring at a blue screen filled with white text that tells you absolutely nothing. You have no option except to reboot...if you can reboot.

Almost everyone gets a rare, occasional BSoD. There's not much you can do except curse, reboot, and try to recreate any lost data (which is basically everything that wasn't saved to disk when disaster struck).

But if it happens regularly, you're going to need to do some detective work.

Remember that BSoDs are generally caused by hardware or by drivers--which are, after all, software that controls hardware. Of course, you need to narrow it down considerably from there.

Believe it or not, there may actually be some useful information in the message itself. The next time the BSoD hits, take a pen and piece of paper and write down the parts outlined in yellow on the image below. Pay particular attention to the file name (if there is a file name) and the text in ALL_CAPS_WITH_UNSCORES_BETWEEN_THE_WORDS.

Once you've rebooted, use your favorite search engine to look for bsod and one or two of the terms you've jotted down. Hopefully, you'll find something, and with it, some instructions.

Ask yourself if anything has changed lately. Any new peripherals? Updated drivers? Although software itself rarely causes BSoDs, it's not unheard of, so...any new programs?

If you find something that seems suspicious, see if there's an update. If not, try uninstalling the program, or removing the hardware and uninstalling the driver.

One quick fix that may help is to use System Restore to roll back Windows to a time before the problem developed. This doesn't always work, and is often only a temporary fix, but it's worth a try.

Bad RAM can cause BSoDs. To see if you have any, download Memtest86+ (and yes, despite the 86 in the name, it works with x64 processors). This is not a Windows program; you have to boot it separately. You can download the program as an .iso file--from which you can create a bootable CD--or as an .exe file that will install the program and its bootable operating system onto a flash drive.

 

1  2  Next Page 

Sign up for Computerworld eNewsletters.