BSOD, error 0x04e, PFN_LIST_CORRUPT, ntoskrnl.exe

JimHalpert · 17 Jan 2015

I've had BSOD errors ever since I put this machine together. Dmp files are beyond my knowledge base, but the deeper I delve, the more this seems like the only way to fix this. My computer crashes for no apparent reason. Sometimes it will work fine for months. Other times I get this dreaded PFN_LIST_CORRUPT. I recently updated my graphics card and installed a new hard drive. I updated the drivers with clean installs, but I had the same error message with my old hardware. Please help, folks. I'd greatly appreciate it.

Arc · 19 Jan 2015

Hi.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

It it does not show any error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
_______________________________________

Code:

BugCheck 4E, {99, 1641ae, 2, 1639ad}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

JimHalpert · 15 Mar 2015

Hi, Arc. Thanks for the thorough response. I really appreciate the help on this one. So here is what happened. My SSD died after a series of blue screens. I had to get a new drive, re-install Windows, drivers, etc. My machine ran flawlessly for a few days when previously I had blue screen crashes multiple times daily. I thought that the problem was over, but alas, it crashed again. I ran MemTest with no errors. Upon exiting the software, I couldn't get back into Windows without a complete re-installation. After finally getting Windows back up, I ran driver verifier. There were no issues for several days, so I couldn't produce a dump file, but the computer eventually crashed again, so here is the dump file and a couple that proceeded the most recent. Thanks so much for the feedback.

Arc · 17 Mar 2015

JimHalpert said:

I ran MemTest with no errors.

And then you got 3 more BSODs all showing this ....

Code:

BugCheck 4E, {99, 9f2f0, 2, 1acaef}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

And verifier also did not catch anything.

OK, run memtest86+ again, for a full 8 passes. When it is complete, take a camera snap of the computer screen with memters86+ running, and then upload the camera snap for us.

JimHalpert · 03 Apr 2015

Ok, so here are the results of memtest86+. 12 passes with 0 errors. Please help. Thanks.

Arc · 04 Apr 2015

Can you make it sure that your RAM is compatible with your motherboard?

JimHalpert · 04 Apr 2015

Yeah, it takes up to 1333 MHz. Is there anything else I can do? Thanks.

Arc · 04 Apr 2015

Check if the vendor and RAM specification matches with Foxconn H67S's support list.

There must be some reason behind those memory corruption errors when the memory is free from errors and no driver is causing any bad info to the memory.