Driver Verifier question

[Bill W]

A friend of mine is getting the BSOD with a PFN_LIST_CORRUPT error (x4e). My research shows that it could be a bad driver and suggests that we run Driver Verifier. I've never run it before, but it looks pretty straight forward. Instructions I've found say to select drivers from the list and restart. If the driver is the culprit, another blue screen will appear indicating that the selected drive is at fault. I also understand that to disable the verifier, type "verifier /reset" (without parens) with a space after the word verifier. Is it that simple and can someone either recommend for or against using such a tool for this particular problem? I know that other information I've found points to bad memory, but I'd like to verify his drivers before suggesting that he buy new memory for a 2 year old computer. He's getting the error about once a week - sometimes when he's not at the computer at all and it's been idle. He's has a Dell Inspirion E1705 laptop. Thanks for your help.

 

[Gerry]

Bill

Article 793247 suggests using a kernel debugger not Driver Verifier
http://www.microsoft.com/whdc/devtools/debugging/Installx86.mspx

Background information on Stop Error message 0x4E
http://msdn.microsoft.com/en-us/library/ms793247.aspx

This indicates that the memory management Page File Number list is
corrupted. Can be caused by corrupt physical RAM, or by drivers passing
bad memory descriptor lists. Source: http://aumha.org/a/stop.htm

--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~




A friend of mine is getting the BSOD with a PFN_LIST_CORRUPT error
(x4e). My research shows that it could be a bad driver and suggests
that we run Driver Verifier. I've never run it before, but it looks
pretty straight forward. Instructions I've found say to select drivers
from the list and restart. If the driver is the culprit, another blue
screen will appear indicating that the selected drive is at fault. I
also understand that to disable the verifier, type "verifier /reset"
(without parens) with a space after the word verifier. Is it that
simple and can someone either recommend for or against using such a tool
for this particular problem? I know that other information I've found
points to bad memory, but I'd like to verify his drivers before
suggesting that he buy new memory for a 2 year old computer. He's
getting the error about once a week - sometimes when he's not at the
computer at all and it's been idle. He's has a Dell Inspirion E1705
laptop. Thanks for your help.