Update: If you’re puzzled because you’re getting STOP errors (the Blue Screen of Death) and they scroll off your screen before you can read the details, here’s the solution: Get details about the Blue Screen of Death.
Trying to figure out what’s causing a Windows STOP error (more commonly known as the Blue Screen of Death, or BSOD) can be a challenge. One likely candidate is bad hardware; if the error messages are random and the shutdowns appear unpredictably, you should suspect a faulty power supply or bad RAM.
Another common BSOD cause is a faulty device driver. Typically, you should be suspicious of any installed drivers that are not digitally signed, especially if they were written for an earlier version of Windows.
Windows XP includes a powerful troubleshooting tool called Driver Verifier (Verifier.exe). It’s a terrific way to identify flawed device drivers. It’s also a surefire way to screw up your system if you use it incorrectly. Read on for the details and important cautions.
Driver Verifier works by testing each driver you specify at startup; if it finds a problem, it stops your computer predictably with a BSOD that accurately explains the true problem. Although this doesn’t sound like a huge improvement (your system still won’t work, after all), Driver Verifier performs a critical troubleshooting step: identifying the problem. You can then correct the problem by removing or replacing the offending driver. (If you’re satisfied that the driver really is OK despite Driver Verifier’s warning, you can turn off Driver Verifier for all drivers or for a specific driver. Any driver that Driver Verifier chokes on should be regarded with suspicion, but some legitimate drivers bend the rules without causing problems.)
Driver Verifier works at startup to thoroughly exercise each driver. It performs many of the same tests that are run by the Microsoft Windows Hardware Quality Labs as part of the certification and signing process, such as checking for the way the driver accesses memory.
Beware: If Driver Verifier finds a nonconforming driver – even one that doesn’t seem to be causing any problems – it will prevent your system from starting. If you use the advice in this article and have trouble starting your system, I won’t be able to help you. Use Driver Verifier only if you’re having problems. In other words, if it ain’t broke …
To enable Driver Verifier, click Start, Run. In the Open box, type verifier and press Enter. In the Driver Verifier Manager dialog box (shown here), select Create Standard Settings.

Click Next and select the type of drivers you want to verify. Because unsigned drivers are the most likely cause of problems, I recommend that you choose the default option: Automatically select unsigned drivers.

When you click Next, you get a list of all unsigned drivers on your system. Note that the list will contain some hardware drivers and some file-system filter drivers, such as those used by antivirus programs, CD burning software, and other low-level system utilities.

At this point you have two choices:
- Go through the list and make a note of all drivers identified and then click Cancel. No changes are made to your system configuration; all you’ve done is gather a list of suspicious drivers, which you can then try to remove or disable manually.
- Click Finish to complete the wizard and restart your computer. I DO NOT RECOMMEND THIS OPTION, for reasons that will become obvious with the remainder of this article. If you choose this option, don’t blame me if things get even messier than they already are.
Did you ignore my advice and choose Option #2 anyway? Fine. If your computer stops with a BSOD when you next log on, you’ve identified a problem driver. The error message includes the name of the offending driver and an error code. To resolve the problem, boot into Safe Mode (press F8 during startup) and disable or uninstall the problem driver. You’ll then want to check with the device vendor to get a working driver that you can install.
To disable Driver Verifier so that it no longer performs verification checks at startup, run Driver Verifier Manager again and select Delete Existing Settings in the initial dialog box.
Alternatively, click Start, then Run, and type verifier /reset in the Open box. (If you haven’t yet solved the driver problem, of course, you’ll be stopped at a BSOD, unable to disable Driver Verifier. In that case, boot into Safe Mode and then disable Driver Verifier.)
You can configure Driver Verifier so that it checks only certain drivers. To do that, open Driver Verifier Manager, select Create Standard Settings, click Next, and select the last option, Select driver names from a list. This option lets you exempt a particular driver from Driver Verifier’s scrutiny – such as one that Driver Verifier flags but you are certain is not the cause of your problem.
For much more detailed information about the Verifier utility, including command-line options and error codes, see Microsoft Knowledge Base article 244617, “How to Use Driver Verifier to Troubleshoot Windows Drivers.”
[This material was adapted from Windows XP Inside Out, Second Edition.]

Ed.
Thanks for this weblog. I’ll try running verifier this weekend to determine the cause of by BSOD problems. My computer boots fine and I am able to run numerous program at the same time. It is when I play dvd that I always get BSOD. Any idea on the cause? I did not take note of the error code but I will tonight. I also observed that only one of the cores (amd X2) appears to be very busy when I run the CPU monitor.
I’ll update you of the results.
Thanks.
as you should know..it is not possible to click “start” “run” or anything once the computer stops at the BSOD…
Uh, Rob? Who are you talking to?
You can also get to safe mode and run verifier from there.
Ed- if I restart and select any of the options…I just get the blue screen again error 0×0000007b…..
Rob, you probably have a hardware problem. Remove as many hardware devices as you can, including all but minimal amount of memory and hard drive, to find the problem.
thanx…
Ed
I have a problem when I open Excel, I go into reboot
Word and Power Point work fine
Could this be a problem Verifier could help resolve
Thank you very much for helping me out with this manual. I had the same problem as RuizdelVizo and it turned out Driver Verifier itself was the problem. No more BSODs for me and again thank you!
i have a bluetooth usb dongle which works fine(laptop) until i plug the power lead in,
i then get bsod usb bugcode,would this be the bluetooth driver even though it runs fine on battery supply.
I experienced the BSOD three times in the past couple of weeks. The last one was an 0xC1 error. I heard about Driver Verifier Manager and checked if any drivers were being monitored. When I displayed information about currently verified drivers, it listed brpar.sys, mpfirewall.sys, scsiport.sys, snapman.sys, tifsfilt.sys, timntr.sys, xmasbus.sys and xmasscsi.sys. I didn’t add any of these drivers to the monitored list. In, fact I never added any drivers ever. How did these drivers get into this list? Can just delete the existing settings?
Thanks,
I get blue screens of death all the time. Ed, I have no idea where to start. I don’t understand what the hell I am doing, is there anyway we could do some live for of chatting to fix my computer? I am considering going to Macs, please save me!
Thanks in advance!
Looks like some folks had trouble disabling Verifier. One way to disable Verifier is to:
1. Boot up in Safe Mode.
2. Run “verifier.exe /reset”.
3. Reboot.
Driver Verifier is disabled in Safe Mode.
If you are curious to learn more about Driver Verifier, its documentation is available at http://www.microsoft.com/whdc/DevTools/tools/DrvVerifier.mspx.
Will any of these driver scan or registery clean up sites really get rid of BSOD? I”m getting an error code of OxOOOOOO9c.
Steve, your blue-screen errors are caused by faulty drivers. You need to find the driver and remove or replace it. A registry cleaner will not help, and I know of no driver-scan sites that will be of any assistance either. Sorry.
Thanks for trying, this BSOD is a problem, maybe i’ll try the Verifier.
Hi i have a laptop and i get frequent bluscreens. the code is something like 0×0000008e and it cant even boot in safe mode. i need help urgently.
Hi Ed.
I found this post very helpful since I had turned on verifier and was in a bsod loop. This post got me out of it. Thank you.
I then went in safe mode, turned verifier on, and found only two unsigned drivers, exifs.sys, which is apparently part of Exchange and shouldn’t be an issue, and filedisk.sys, which was part of winimage which I downloaded yesterday to try and make a seagate boot cd to test the hard drives (it didn’t work). Also, the bsod loop comes back even in safe mode if I leave the server running with verifier on.
So, I don’t think these two drivers are my problem. One is too new and the other is apparently part of the program, although I haven’t been using Exchange. Now what?
This all started because of frequent random crashes. I had the server rebuilt, keeping the cpu, the ram (and adding more) and the hard drives. Since the problems continue, and I reinstalled sbs, and the hard drives passed the Western Digital test I found, I guess I’m left with the original RAM being bad. I’m going to try and test that next, unless I’m missing something with the drivers? Could it be one of the signed ones?
Nat, if you are seeing stop errors in safe mode, the cause is almost certainly hardware. When you’re in safe mode, neither of the suspect drivers is being loaded.
I would recommend either (a) running the most comprehensive memory test you can find or (b) remove half the RAM and restart, and if the errors continue then reinsert the RAM and remove the other half and test.
I’ve seen RAM fail in service before. It’s not unusual or unexpected.
Hi Mr. Bott.
Again, thank you. I did swap out the memory, and it boots with either one in place, and recognizes that there is only 512 present. But I continue to have safe mode crashes, most now with no notation as to cause at all, a couple with irql not less or equal. I found a cpu tester at pc world, but while i was transferring it to cd on my laptop, the server, which was in safe and doing nothing else but waiting, crashed again. What now? Do I give up, replace the cpu and hope that solves it? Your insights appreciated.
update. New ram chip put in last night. Server stayed on all night. Keep your fingers crossed for me!