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.
Who is Participating?
Rob MinersConnect With a Mentor Commented:
Check the Hard drive.
You can either download UBCD and use the Drive tools or go to the Maufacturers site.
Major Hard drive manufacturers :
Hitachi / IBM
Fujitsu / Toshiba
Seagate / Samsung
Western Digital
You can download ImgBurn to burn the ISO to CD/DVD
Rob MinersCommented:
It appears that you have two Antivirus products installed, McAfee and Symantec. Both are running, please use the Antivirus maufacturers removal tools to remove one of them. Then check to see if you have the same symptoms.

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)

Download and run the Norton Removal Tool to uninstall your Norton product

BugCheck 4E, {9a, ca26d, 6, 5}

Probably caused by : memory_corruption ( nt!MiBadRefCount+26 )

ddantesAuthor Commented:
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.
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Seth SimmonsConnect With a Mentor Sr. Systems AdministratorCommented:
memtest86 is a better tool to use for memory

the first parameter is 0x9a which could indicate a driver issue

A driver attempted to free a page that is still locked for IO.

Rob MinersCommented:
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.txt

 Look for any errors...

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.
ddantesAuthor Commented:
Thank you both for comments.  I'll run memtest86 first, then I'll post again...
ddantesAuthor Commented:
Memtest86 has completed one iteration, 8 tests, no errors.  I'll run the verifier test and post again...
ddantesAuthor Commented:
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.
ddantesAuthor Commented:
The system drive is a Western Digital  WD 3200JB.  I attached a screenshot of an error reported by WDC Diagnostics.Diagnostics report
Seth SimmonsSr. Systems AdministratorCommented:
i would backup any data you need to keep and replace that drive
it's obviously failing
Rob MinersCommented:
I have to agree with seth2740.  If it's been running since 2009 you have had a good run with it.
ddantesAuthor Commented:
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.
Rob MinersCommented:
Your welcome :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.