BSOD PFN_LIST_CORRUPT
I began having BSOD with PFN_LIST_CORRUPT since yesterday. I am constantly making changes to my system, so it's not always easy to identify the cause of new behavior.
Yesterday I installed an application called DirDate, which is used for correcting file timestamp errors, using a backup with correct timestamps. I can't think of another change (new driver, new program) which was made just before these symptoms developed. The DirDate application was not running when the BSOD occurred. It has happened three times in the last few hours. Chkdsk found some index issues and corrected them, but BSOD still occurred. Windows Memory Diagnostics reported no problems.
112313-25272-01.dmp
WER-45567-0.sysdata.xml
Yesterday I installed an application called DirDate, which is used for correcting file timestamp errors, using a backup with correct timestamps. I can't think of another change (new driver, new program) which was made just before these symptoms developed. The DirDate application was not running when the BSOD occurred. It has happened three times in the last few hours. Chkdsk found some index issues and corrected them, but BSOD still occurred. Windows Memory Diagnostics reported no problems.
112313-25272-01.dmp
WER-45567-0.sysdata.xml
ASKER
Thank you for your input. I don't think McAfee is an issue. I tried it, around 2009, and uninstalled it immediately. Apparently it left some folders and registry entries, but I'm not running it. I just removed those folders and registry entries, because I don't want them, but I believe the issue must be elsewhere.
Regarding memory corruption, Windows Memory Diagnostics didn't report any problem.
Regarding memory corruption, Windows Memory Diagnostics didn't report any problem.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can also run Driver Verifier if the memory test is successful.
Ensure that you have the latest Chipset drivers installed from the manufacturers website.
Press the WinKey + r type verifier /standard /all
Restart the machine.
You may or may not Blue screen, if not you can also create a log file by following this proceedure:
Once you're up and running press the WinKey + r type verifier /log drvchk.txt and press Enter.
This will open a blank command window while it is doing the check. Let it run for at least 4 minutes, then close the window, you may get an error message, but you can ignore it.
Press the WinKey + r type verifier /reset and press Enter.
Press the WinKey + r type %userprofile%\drvchk.txt
if it's not there
Press the WinKey + r type %windir%\System32\drvchk.t
Look for any errors...
Note:
If the computer fails to boot because of the verifier.
Restart in Safe Mode by repeatedly pressing the function key F8 during startup.
Click Start, type verifier /reset in the Start Search box, and then press Enter.
Click OK or Yes to the UAC prompt.
Restart the machine.
Ensure that you have the latest Chipset drivers installed from the manufacturers website.
Press the WinKey + r type verifier /standard /all
Restart the machine.
You may or may not Blue screen, if not you can also create a log file by following this proceedure:
Once you're up and running press the WinKey + r type verifier /log drvchk.txt and press Enter.
This will open a blank command window while it is doing the check. Let it run for at least 4 minutes, then close the window, you may get an error message, but you can ignore it.
Press the WinKey + r type verifier /reset and press Enter.
Press the WinKey + r type %userprofile%\drvchk.txt
if it's not there
Press the WinKey + r type %windir%\System32\drvchk.t
Look for any errors...
Note:
If the computer fails to boot because of the verifier.
Restart in Safe Mode by repeatedly pressing the function key F8 during startup.
Click Start, type verifier /reset in the Start Search box, and then press Enter.
Click OK or Yes to the UAC prompt.
Restart the machine.
ASKER
Thank you both for comments. I'll run memtest86 first, then I'll post again...
ASKER
Memtest86 has completed one iteration, 8 tests, no errors. I'll run the verifier test and post again...
ASKER
After running verifier there was a blue screen: IO Manager detected a violation by a driver that is being verified... 0x000000C9
SSCRDCLS.sys Adr 836012E4 Base at 83600000 Datestamp 473df66c
This driver is associated with RamDisk, an application which has been on my system for several years without any adverse effects.
The system failed to restart, so I booted into safe mode and ran verifier /reset.
SSCRDCLS.sys Adr 836012E4 Base at 83600000 Datestamp 473df66c
This driver is associated with RamDisk, an application which has been on my system for several years without any adverse effects.
The system failed to restart, so I booted into safe mode and ran verifier /reset.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The system drive is a Western Digital WD 3200JB. I attached a screenshot of an error reported by WDC Diagnostics.
i would backup any data you need to keep and replace that drive
it's obviously failing
it's obviously failing
I have to agree with seth2740. If it's been running since 2009 you have had a good run with it.
ASKER
Thanks to both Experts. I'll close this question, but I will post it again if replacing the hard drive doesn't eliminate the BSOD.
Your welcome :)
Disable both Antivirus products and then choose which one to uninstall. After you have uninstalled the selected Antivirus Update which ever is left.
How to uninstall or reinstall supported McAfee products using the Consumer Products Removal tool (MCPR)
http://service.mcafee.com/FAQDocument.aspx?id=TS101331
Download and run the Norton Removal Tool to uninstall your Norton product
https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us
BugCheck 4E, {9a, ca26d, 6, 5}
Probably caused by : memory_corruption ( nt!MiBadRefCount+26 )
-=eol=-