Sign in with
Sign up | Sign in
Your question

Blue Screen of Death Help, Please.

Last response: in Windows XP
Share
April 24, 2008 1:28:58 PM

I have a computer that frequently BSoD's on me.

Thier seem to be 2 different codes.

PFN_LIST_CORRUPT (9 out of 10 times)
IRQL_NOT_LESS_OR_EQUAL(1 out of 10 times)

Now I know that PFN bsod is typically RAM related.
And I know the IRQL is hinting a Driver error.

So I figure that the 2 together are probably screaming that bad data is being fed to my RAM by one of my drivers.

The problem is, WHICH driver?

I have loaded several of my minidumps into dumpchk.exe and kd.exe and !analyzed them....

But quite honestly, I really do not know exactly what I am looking for.

More about : blue screen death

April 24, 2008 1:36:49 PM

Run c:\windows\system32\verifier.exe. If it BSODs, write down the name of the file and google it. That is your driver error. You need to go in safe mode to disable verifier, otherwise it will run on every reboot. You need to reset the computer after running verifier for the first time.
April 24, 2008 1:54:06 PM

And running this will tell me which of my drivers is feeding bad data to my RAM?

I thought all that Verifier did was confirm that there was a working driver installed for the device?
Related resources
April 24, 2008 1:56:43 PM

If verifier BSODs, you have a bad driver, like rscan.sys for Zonealarm.
You can disable the bad driver or uninstall the program.
Test your RAM with memtest86+. If you get errors replace the RAM.
April 24, 2008 1:58:03 PM

Already tested the RAM. In tested ok, but to be sure I bought a brand new stick, removed the old RAM, and placed the new RAM in a different slot.

No change at all.

I am 99% sure it is a driver.
April 24, 2008 1:59:32 PM

What I do not know is how to figure out WHICH driver without just reinstalling all of them one by one.
April 24, 2008 2:05:22 PM

Once you have the file name of the bad driver, do a search on your computer. The folder will tell you the name of the program or else google the name of the file.
April 24, 2008 2:07:14 PM

Very good article. Thanks. I will try that when I get home from work this evening.

If I am reading that correctly, the verifier is going to try and stress my driver to the point that it crashes.

And the idea, is that instead of getting a stop message that does not really tell me anything useful, I will get a stop message containing the name of the driver?

Or am I way off and this thing is just going to give me the same stop, but only confirm it is in fact driver related without really giving me any more information than I already have?
April 24, 2008 2:09:00 PM

This sounds like it will be much better than trying to load it into kd.exe and decode that cryptic garble of hex. lol

Thanks a lot. I feel pretty hopeful about this idea.
April 24, 2008 2:11:16 PM

Verifier.exe will give you the name of the driver plus some other hex...
Write down the entire BSOD. Important is the driver name.
April 24, 2008 2:13:48 PM

If you havn't already done so, do this also:

Right click my computer and select properties then the advanced tab. Under startup and recovery, click settings and uncheck the box that says automatically restart. Click ok/apply/ok and reboot the computer. The next time the computer crashes you will see a BSOD that you can read.
April 24, 2008 3:30:58 PM

yea. I do that on install. I hate the auto reboot option.
!