Memory_Management and PFN_LIST_CORRUPT

Hey guys, another BSOD again. I was just surfing the web then chrome suddenly closes, I didn't double click the upper left side or clicked the x button, it didn't say that "Whoa! Google chrome has crashed, restart it?", I just presumed that it closed for some reason but after that, I opened chrome again, it didn't start, I checked task manager, nothing "chrome.exe" and then BSOD, booted to safe mode and here I am. Most of my BSODS are the 2 mentioned in the title, 28 "Memory_Management" and 7 "PFN_LIST_CORRUPT". When I checked Bluescreen view I saw that these 2 things which is "hal.dll" and "ntoskrnl.exe" are common in those two BSODs, however, "ntoskrnel.exe" is always in those two BSODs while "hal.dll" is only appearing in some BSODs. I'm currently on safe mode, checking for stability issues too in safe mode if it will crash or not, current uptime on my PC is 18 minutes. If you say that if I will need to do Memtest86+, I'll do it later, gonna check some things first. One more thing about Memtest86+ is that my results is not consistent, I only do it when I get BSODs, for example, memtest found 500 errors after first 30 seconds, I shutdown my PC and boot again to safe or normal mode, and I turned the PC off again or just restart it (no BSODs, just casual shut down or restart), after that, turn it on and go to memtest, this time, I got no errors in the first 30 seconds. I'm gonna put some few .dmp files first, 2 from memory and 2 from PFN (including one today).

Sorry that no one has been able to reply to your post,

Code:

BugCheck 4E, {99, 1d6ba, 3, 62234}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

Code:

Usual causes:  Device driver, memory

The bugcheck indicates that the Page Frame Number (PFN) is corrupt, the first parameter highlighted in blue indicates this. The Windows Memory Management system organizes all physical pages of memory into a large one dimensional array, which allows the operating system to conveniently access each page (Page Frame database); each page is given referenced with a Page Frame Number entry.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

• RAM - Test with Memtest86+

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Arc said:

No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

Please upload a MSINFO32 too:

1. Start
2. Type: msinfo32
3. File, Save
4. Place the file in a zipped folder, and then upload in your next post using: Screenshots and Files - Upload and Post in Seven Forums

I haven't updated my graphics card driver, I rolled back from 320.18 WHQL to 311, had some issues with the driver but I shall reinstall it if it will stop my BSODs. I just had another BSOD, memory_management, blue screen views tells me that ntskrnl and hal.dll is highlighted. Currently on safe mode, just enabled DV and followed the settings given on the tutorial. Will do Memtest86+ after checking some files.

Thanks for the update, and here's the latest analysis:

Code:

BugCheck 1A, {41790, c08027b2, ffff, 0}

Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+41a )

Code:

Usual causes:  Device driver, memory, kernel

Generally speaking the bugcheck tells us that a serve memory management issue has occurred, but if look into more detail, we can see that a page table page has become corrupted. The page table is another data structure used by the operating system to store mappings between virtual and physical memory.

If the Memory test comes back with no errors, then I believe the best step would be to begin testing the hard-drive.

Your MSINFO32 file seems to be corrupt too:

Attachment 272714

Day 2 with DV still enabled, no problems nor crashes, current up-time is 1 hour and 33 minutes. When I open my saved MSINFO32, it shows me the same thing like yours, when I click "OK" or close it, it gives my own MSINFO32, I ran it as admin yet nothing, used SF Diagnostic Tool (with ran as admin too) yet nothing. However, I just exported as a .txt file and it works, I will not post it here since it caused my page to freeze and I have to start typing again. I've also thought of my drive too when I get BSODs, I haven't ran "chkdsk /f" for a while since my last week and I haven't defragged my drive since reformat (April 17, 2013). Window's built-in defragmenter says it's fragmented to 7%, currently defragging now.

Sitrep guys, just got a BSOD, it's "DRIVER_IRQL_NOT_LESS_OR_EQUAL". I'm currently on safe mode, I already added the .dmp file of this BSOD.

Thanks for the text file, I couldn't see any programs or drivers which are likely to cause problems.

Code:

BugCheck 100000D1, {c, 2, 1, 8f1c8460}

Probably caused by : Rt86win7.sys ( Rt86win7+10460 )

This bugcheck indicates drivers referencing invalid memory addresses, and causing interrupts at IRQL levels which are too high.

Update:

Code:

0: kd> lmvm Rt86win7
start    end        module name
8f1b8000 8f1fd000   Rt86win7 T (no symbols)           
    Loaded symbol image file: Rt86win7.sys
    Image path: Rt86win7.sys
    Image name: Rt86win7.sys
    Timestamp:        Thu Mar 04 13:42:33 2010 (4B8FB8C9)
    CheckSum:         0004DDFA
    ImageSize:        00045000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Realtek network adapter driver seems to be causing a few problems, please update the driver from here: Realtek

I also took a look into the raw stack of the crashing thread, and managed to find another possible driver:

Update:

Code:

0: kd> lmvm nvlddmkm
start    end        module name
8e806000 8f0a9000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jan 18 13:21:40 2013 (50F94C64)
    CheckSum:         0088D0A0
    ImageSize:        008A3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

• Latest NVIDIA ForceWare Video Drivers Windows 7

Version: 320.18
Release Date for Desktops and Notebooks : May 23rd 2013
In Device Manager: 9.18.13.2018

You may now disable Driver Verifier.

x BlueRobot said:

-snip-

Thanks for the help, I'll still wait for 2 days if my PC is stable or not, once it's stable, I'll just mark this thread as solve. I already repped you.

Edit: Forgot to tell, I already installed both drivers.

Welcome, and thanks for the rep :)

Hopefully I'll see this thread as solved