Solved PFN_LIST_CORRUPT and MEMORY_MANAGEMENT errors

[zqlx]

Currently I can boot into safe mode fine, and booting into normal mode works for a short while before I eventually get a BSOD.

I've already run memtest86+ on the RAM (all four sticks at the same time) for 6 passes with no failures.

Running sfc /scannow usually results in the message "Windows Resource Protection found corrupt files but was unable to fix some of them." or sometimes an early termination with "Windows Resource Protection couldn't perform the requested operation" (or something like that).

My research so far as indicated that this is probably some sort of driver issue? I've updated (I think) my ethernet driver (Rt64win7.sys), and the system seemed more stable, but I still get crashes.

I'm sort of at a loss for what to try next.

Requested information from the diagnostic tool is attached.

 

[Arc]

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If memtest86+ comes to be free from 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.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
________________________________________________________________________________
BSOD ANALYSIS:

[URL="http://www.carrona.org/bsodindx.html#0x0000004E"]BugCheck 4E[/URL], {99, 3549fc, 2, 356dff}

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

Followup: MachineOwner
---------------------------------------------------------------------------------
[URL="http://www.carrona.org/bsodindx.html#0x0000004E"]BugCheck 4E[/URL], {99, 338463, 2, 33675f}

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

Followup: MachineOwner
----------------------------------------------------------------------------------
[URL="http://www.carrona.org/bsodindx.html#0x0000001A"]BugCheck 1A[/URL], {41287, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+454f5 )

Followup: MachineOwner
-----------------------------------------------------------------------------------
[URL="http://www.carrona.org/bsodindx.html#0x0000004E"]BugCheck 4E[/URL], {99, 36ad3a, 2, 36b039}

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

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

 

[zqlx]

Thanks for your reply.

Some more updates:

I had two more crashes (BAD_POOL_CALLER and BAD_POOL_HEADER, respectively; they're attached) last evening.

I should have mentioned this earlier, but I just upgraded from 8GB to 16GB of RAM. I did run memtest on all the sticks earlier, and it came up clean, but I can run it some more.

I enabled Driver Verifier last night (using that exact tutorial).

After those two crashes, I removed the two old sticks of RAM, and the system was much more stable. Ran games for a couple hours, then since it was seeming particularly stable I starting imaging my boot drive with Macrium Reflect (I didn't have an image of it yet) and went to bed. This morning I found the computer on, but all the screens were black and the keyboard was lit but wouldn't respond to numlock / capslock / scroll lock. So something went wrong overnight and I don't know what. It didn't leave a dump log or I would have attached it.
The image seems to have completed successfully? I can't get it to mount but that could be because I'm in Safe mode right now.


I'll run memtest86+ on the two new sticks today.

 

[Arc]

Neither of the crash dumps are driver verifier enabled.

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

With DV enabled, the value would have been "VERIFIER_ENABLER_VISTA_MINIDUMP".

Also you will need to scan the system for possible virus infection with the following programs with these programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

 

[zqlx]

I've run memtest86+ on my two new sticks of ram, and they've gone though 11 passes with no failures. I'll just keep using them for now and worry about the old sticks if we can fix the crashes.

Neither of the crash dumps are driver verifier enabled.

Really? That's odd. They may both have been before I enabled it. I'll check to make sure it's actually on.

Also you will need to scan the system for possible virus infection with the following programs with these programs.

I will do that.

 

[zqlx]

TDSSKiller found no threats. I haven't run Windows Defender Offline yet but I will tomorrow.

I had two more crashes that left logs. I checked and Driver Verifier says it's enabled, so the attached dumps should be with that, whatever that means.

I have disabled all auto-starting programs except for MSE.

I've discovered that my ATI graphics card drivers have a big impact on stability. With them uninstalled I can boot into normal mode (although Windows then automatically installs drivers for the card, and I have to uninstall them again if I want to reboot without them). If they are installed, when I try to boot up I get approximately to the welcome screen (sometimes I can manage to log in) before the screen messes up and the computer becomes unresponsive.
It doesn't actually BSOD though, so I don't have any logs from it. It just sits there looking like this https://dl.dropboxusercontent.com/u/14015968/2013-05-22%2012.36.03.jpg, is completely unresponsive and I have to do a hard shutdown.
I think I have the latest version of the drivers. I'm not sure what version Windows tries to install automatically, but when I install the drivers I've downloaded over those, this happens.

If there's any other information I can provide that would help, please let me know and I'll do my best.

 

[Arc]

Verifier is still not running.

Open an http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html and use the command verifier /query

It willdisplays a summary of Driver Verifier's current activity. So you will be able to know if it is running actually or not.

 

[zqlx]

I ran verifier /query in Safe mode and it output

5/23/2013, 1:17:51 PM
No drivers are currently verified.

I followed the Driver Verifier tutorial again to try to enable it. Not sure why it wasn't working before.

Booted into normal mode and quickly ran verifier /query and it output a long list of drivers, so it should be working now. Sorry about that, I was sure that I had enabled it before but I guess I messed it up somehow.

EDIT: My system is running unusually well right now; the AMD drivers are installed, my computer hasn't crashed and Firefox isn't even crashing constantly. (I have hundreds of tabs, so Firefox is like the canary in a coal mine for my system; when it starts crashing once every few minutes something is usually very wrong.) This is weird. I'll try to get a BSOD now that Driver Verifier is actually enabled.

EDIT 2: According to the AMD website the latest version of my graphics card driver is 12.104, which is the version I have installed. So there's that. I could try the beta driver if the crashes resume.

 

[zqlx]

After around four hours of normal operation today I experienced the crash I mentioned yesterday, where the screen messes up but the computer doesn't BSOD. Also, this might just be my imagination but I think that towards the end of the four hours, Firefox crashes became more frequent.

I tried booting up again a couple times and was met with immediate crashes of the same type. So I let the computer stay off for around ten minutes, then booted up again and it took around 5-10 minutes for it to crash that time. So it seems like letting the computer stay off for a while increases the time it takes to get a crash (since it was off all last night and lasted for four hours today). This makes me really suspect something hardware-related as the culprit.

I pulled out my current video card and installed an old Nvidia GeForce 9500 GT that I had lying around. I booted into Safe mode and used DriverSweeper to wipe all the ATI drivers (I've heard that Nvidia and ATI drivers don't play well together), and rebooted into normal mode. Upon reaching the login screen I got an actual BSOD.

I was suspicious of my ATI graphics card, but getting a BSOD with a different card it sort of rules that out, doesn't it? So now I'm not sure anymore.

I tried booting two more times to make sure it wasn't just a fluke. Both times I got BSODs.

 

[Northernsoul55]

Hi,

Your logs do not show anything definitive, Arc is quite correct, you need to somehow enable Driver verifier
in order for us to acurately analyse your issue.


Which slot did you try the cards in? PCIe x16 slot i assume?
If so try both cards in a different PCIe slot? It could be possible you have a bad PCIe slot.

Try updating your Chipset drivers first, as they (Northbridge) are responsible for PCIe functions:

:ar: GIGABYTE - Motherboard - Socket 1155 - GA-Z68XP-UD3 (rev. 1.0)


cheers

Dave

 

[zqlx]

Not even the logs I posted earlier tonight have Driver Verifier enabled? That's very strange. It says it's enabled, and lists whether drivers have been loaded or not when I use the display options. verifier /query also spits out a giant list of drivers.
I didn't enable it for Microsoft-provided drivers, as instructed in the tutorial. Is that related?


Also I feel really silly now. I realized earlier that I hadn't actually just tried using my old RAM sticks in their old slots. I thought I had tried this at the very beginning, but I never actually did. So I swapped them back in, and now I'm sitting here with no crash after 6 hours. It seems like something might actually be wrong with the new RAM (or the slots it was in) despite them passing memtest.

I'll leave the computer running overnight and see if it crashes. Then I'll swap back in my ATI graphics card and see if it still runs fine, and then start testing all my ram in different slots to see if I can pin down the faulty stick / slot. I'll keep the PCIe slot tip in mind too.

Thanks for the help; I'll post back if I figure it out or if everything goes wrong.

 

[Northernsoul55]

Thanks for the feedback.

Good spot on the RAM, hopefully all will go well now

Look forward to the result

cheers

Dave

 

[zqlx]

In case it comes up later: When I was switching video cards this time, I dropped a screw into my power supply (*facepalm*) and had to disconnect it and carefully shake it upside down to get the screw out. The computer still boots and turns on so I don't think anything was damaged.

I uninstalled the Nvidia drivers, then swapped my ATI card back in. On the first boot with the ATI card, I got a BSOD I'd never seen before (0x000000C4 DRIVER_VERIFIER_DETECTED_VIOLATION) before I got to the login screen, I think. I definitely didn't log in but it may have gotten to the login screen before it crashed without me noticing.

So I booted into Safe mode, uninstalled the ATI drivers (which somehow got installed before I even logged in? Pretty sure I uninstalled them before swapping the cards the first time), and rebooted into normal mode to let the drivers install again. Then I rebooted a third time and nothing crashed, so here I am. Going to see if this stays stable for a while before moving on to testing my RAM.

I attached all the new minidumps I had since the last zip I uploaded. All but the most recent are from before I switched back to my old RAM sticks, but they're there for completeness' sake.

 

[zqlx]

I was able to narrow the crashes down to one of the new sticks of RAM! I've been running with the other three for over a day now and everything works perfectly. Seems like that stick is bad even though it didn't fail memtest.

Thanks for the help, guys!

 

[Northernsoul55]

Good news Glad its sorted.

cheers

Dave