Solved Random BSODs - pfn list corrupt, memory management, memory_corruption

[wheezyt]

Hello friends. I have been having an issue with BSODs for some months now, they were usually infrequent enough that I just ignored them thinking "I'll fix it eventually", and they have steadily grown in frequency (I've had 4 in the last 24 hours, but sometimes I can go for a couple of days working fine).

I have also been having a problem where I will be using chrome and the page will suddenly flip to the chrome error message stating something went wrong. I have created a new user as their troubleshooting guide says and it still happens, sometimes it will happen 3 or 4 times within a few minutes and other times I can be browsing fine for hours. I can't consistently replicate this, it has happened on everything (facebook, youtube, reddit and so on).

I ran a malwarebytes scan on full and that came back clean

I only replaced the ram in early August, but all the errors seem to be pointing to that as the culprit. I'm hoping someone here can help me =[

 

[Arc]

Welcome aboard.

Your crash dump says:

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 4E[/COLOR], {99, 172d70, 0, 173e70}

[COLOR=Red]Probably caused by : memory_corruption [/COLOR]( nt!MiBadShareCount+4c )

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

According to Carrona.org, STOP 0x0000004E: PFN_LIST_CORRUPT
Usual causes: Device driver, ?memory

So , let us search for any driver which is causing the problem or not. In such a situation, it is better to 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.

Also, the the memory modules needs to be tested.
RAM - Test with Memtest86+
Run it for at least eight passes, preferably overnight.

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

 

[wheezyt]

Hi thanks for trying to help.

Since enabling verifier I've had another 3 crashes, but instead of getting a BSOD my system just locked up and I had to power off and on again to restart it. This hasn't happened before so I'm assuming it's connected to verifier somehow?

I'm about to head to bed so I'll set memtest running and update in the morning.

 

[Arc]

Disable Verifier.

Then enable it properly, following the tutorial. Make it sure that you are not selecting any drivers selected by microsoft.

 

[wheezyt]

Hello sorry for the delayed response, some real life stuff came up.

I disabled verifier and re-enabled it but my machine ran fine for the next couple of days. Last night I set up memtest and left it running for 12 hours, came back to it this morning with just over 44,000 errors.

I'm about to go out, when I get back I'm going to take out the ram and try it one stick at a time with memtest.

 

[Arc]

I wish changing the RAM modues will resolve the problem in this case.

Best of luck mare

 

[wheezyt]

Hi, just a follow up to say I tried the ram in different configurations over the course of a few days and couldn't find a way to make memtest happy. I purchased new ram and everything seems to be running fine now (fingers crossed).

Thanks for the help.