Windows 10: BSOD PFN_List_Corruption

I've been having trouble with BSOD lately on my computer. At first I believed it had to do with a single game, Playerunknowns Battleground, but while it still is far more frequent in this game (never lasts more than 15 minutes), I have had crashes in other games, during login and even 10-15 seconds after windows have apparently successfully killed off a non-responding game.

Often the computer have locked up, not even resulting in a bluescreen, the last bluescreen I got stated "PFN_List_Corrupt". I've tried reinstalling and updating some drivers, also played using only 8 out of 16GB RAM and switch to see if one was faulty and ran a RAM test without faults.

Starting to be at a loss as to what it can be, the PSU should offer sufficient power, but it is worth noting that it is getting old. At some point I had to reseat the RAM in order for the computer to successfully boot, which is why I've been focusing a bit towards the RAM to begin with.

As far as I've been able to observe, there has never been a problem with temperature, few components ever go beyond 40-50C, and nothing have been clocked.

I've added the minidumps I had available if that helps, if anyone has any idea, that would be appreciated.

MSI X99A RAIDER 2011
HyperX Predator DDR4 3200Mhz 16GB
Intel i7-6800K
MSI Geforce GTX 1070
Thermaltake 1200W PSU

:)

 

BSOD error || Error : PFN_LIST_CORRUPT

Original title : PFN_LIST_CORRUPT

Another day, another BSOD. Brand new message I've never seen before while playing CS:GO. Here is the minidump: https://1drv.ms/u/s!Ao0Qrxmadwobgst1HP_6G2fmiw8tLQ

 

pfn_list_corrupt BSOD

Hi!

That's why I asked because a W10 32 bit version can't handle the memory. W10 32 bit will run on a 64 bit system hardware.

 

I have also ran a stress test on the GPU, temperature peaked at 85C, to me it looked as if this was desirable as it was clearly regulating around this point with the fans at about 70%. Also various chkdsk etc. for the SSDs.

 

Please read and follow the instructions here: Blue Screen of Death (BSOD) Posting Instructions

 

Here are the additional files collected by the log tool.

 

Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums







Note MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

 

Analyze v displaying memory.
Thread and dps left few if any clues.

Code: Dump file creation failed due to error during dump creation.[/quote] Code: Start-up Repair failed.[/quote] Code: Crash dump initialization failed![/quote]
Open administrative command prompt and type or copy and paste:


1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)


2) sfc /scannow


3) dism /online /cleanup-image /restorehealth


4) chkdsk /scan


When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread

5) turn off Windows fast startup


Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

6) confirm and or configure settings for minidmp:


Keyboard: win + r keys simultaneously > type or copy and paste: sysdm.cpl > click advanced tab > under startup and recover click settings > under system failure uncheck automatically restart




See this link: BSOD Finding and fixing them - Microsoft Community
BSOD Finding and fixing them - Microsoft Community


This is information about the needed 8 or more runs for Memtest86+ version 5.01 testing:
http://www.memtest.org/https://answe...f-ecc7b7ff6461

 

Windows 10 Version 1703 (OS Build 15063.447)

I had to give up on the memory test after 3 runs due to the time it took. I will start it up again when I know I have more time to let it run. It took more than 10 hours to complete 3 runs, is this usual given the specifications?

Attachment 141914

I also ensured the BIOS is now fully up to date without it helping the issue, is there any clue in the fact that certain games or situations consistently cause the BSOD more often? Best example would be Playerunknowns Battleground, a somewhat poorly optimized game consistantly crashing after 10-20 minutes of game time. While other games or programs can run days without a crash, though it does not crash exclusively to that game. Again, I have monitored temperatures prior to crashes and stress tested the GPU for about half an hour.

I have already run the disk checks without finding errors, but I will try ones more following your steps.

I've disabled automatic restart and Fast startup.

 

The data for the memory is 16GB ram total with 4gb per dimm. That will take many hours so it is best to run it over night. The more runs the less likely there is a false negative.

Please post the results of chkdsk /scan

If the memory test displays errror then ram and dimm have to be checked.
If the memory test displays no errors with at least 8 runs there is a tool that can be used to stimulate the drivers and find misbehaving drivers. This tool is already part of windows 10. Running windows driver verifier will continuously produce bsod unless it is turned off or unless all misbehaving drivers have been fixed. Each bsod should produce minidmp files. These files when evaluated will help us narrow down whether the bsod are coming from drivers, software or hardware. Once there are no more bsod you will use the tool for 36 hours with the computer under typical use. If there are no bsod then troubleshooting and preventative maintenance will be completed.

 

New Bluescreen, new error, this time DPC_WATCHDOG_VIOLATION.

Some searching suggest old SSD driver incompatible with windows 8 or 10. My current OS SSD is somewhat old, currently running on an Kingston HyperX 3K SSD 120GB.

Also in the system there's an Crucial MX300 750GB and an HyperX Savage 240GB.

Since I tend to limit the OS hard drive to very few things I tend to use a small one for it, but could this SSD be an issue? Can I update these drivers or are they locked to factory drivers?

Apologies, I see I forgot the chkdsk, here it is:

 

Anytime you have a new bsod please update the zip file or post a new one in the thread:
BSOD - Posting Instructions - Windows 10 Forums

 

ok, here is the updated log and dump files. There's been one more crash in between the last crash and this upload, I am unsure if that crash managed to create a dump file as it never went over 0% on the Bluescreen, but it did display an error UNEXPECTED_KERNEL_MODE_TRAP

 

Please use Memtest Version 5.01.

 

Code: 20-Jun-17 15:19 Windows Error Reporting Fault bucket 0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiTimerWaitTest, type 0 Event Name: BlueScreen Response: Not available Cab Id: 2bacf5e7-ca04-42e9-8584-1951312c2080 Problem signature: P1: 139 P2: 3 P3: ffffa7818eb6d730 P4: ffffa7818eb6d688 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\061917-11062-01.dmp \\?\C:\Windows\Temp\WER-11671-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER39AD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER39AF.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER39B0.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_d5395dbf72513b3150cc752d60151130b07a8f2f_00000000_cab_14a0757e Analysis symbol: Rechecking for solution: 0 Report ID: 80f736a0-f50c-465b-90f9-a0620cc3ef71 Report Status: 268435456 Hashed bucket:[/quote]
Bug Check 0x139 KERNEL\_SECURITY\_CHECK\_FAILURE | Microsoft Docs

Code: 19-Jun-17 21:12 Windows Error Reporting Fault bucket 0x3B_BEDaisy!unknown_function, type 0 Event Name: BlueScreen Response: Not available Cab Id: 8298d3b8-6977-4fba-a67a-b3d907e348f6 Problem signature: P1: 3b P2: c0000005 P3: fffff80057d83a30 P4: ffffe601a1a13a60 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\061917-11046-01.dmp \\?\C:\Windows\Temp\WER-11593-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER39EC.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER39FB.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A0C.tmp.txt \\?\C:\Windows\Temp\WER469F.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_cda27180da1417ea66d9aa8c17478d8da1c6c12_00000000_cab_16f849bb Analysis symbol: Rechecking for solution: 0 Report ID: edfa3b90-d7fc-4485-9bad-c19d9327a6e2 Report Status: 268435460 Hashed bucket:[/quote] BEDaisy.sys BattleEye anti-cheat driver

Initially released on 8 January 2015 BattlEye – The Anti-Cheat Gold Standard » Downloads

Code: BEDaisy BEDaisy BEDaisy Kernel Manual Stopped OK FALSE FALSE 0 684,032 0 11-Jan-17 04:01:10 \??\C:\Program Files (x86)\Common Files\BattlEye 4,096[/quote] Code: 17-Jun-17 01:49 Windows Error Reporting Fault bucket AV_nvlddmkm!headHandleRgStall_v02_08, type 0 Event Name: BlueScreen Response: Not available Cab Id: 796c8d33-66f6-429d-97f1-dbb177b0e86a Problem signature: P1: d1 P2: ffffe48161c2a880 P3: 6 P4: 1 P5: fffff80435173b5a P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\061717-11171-01.dmp \\?\C:\Windows\Temp\WER-11781-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A69.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A78.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A79.tmp.txt \\?\C:\Windows\Temp\WER3FE9.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_b6915e7c56d84b9c6649b9c33e5318ebb8b6_00000000_cab_3a98560b Analysis symbol: Rechecking for solution: 0 Report ID: 50056e7c-b884-438c-a78d-2a48212f45e7 Report Status: 268435456 Hashed bucket:[/quote] nvlddmkm.sys nVidia Video drivers Download Drivers | NVIDIA
Get from OEM for laptop
1) Uninstall Battle eye
If you must use it then reinstall it.
Otherwise it may be able to be reinstalled after the troubleshooting has been completed

2) Uninstall all Nvidia drivers/softwareThe best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.Display Driver Uninstaller Download version 17.0.6.7: Official Display Driver Uninstaller DDU Download