Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD - Random intervals with PFN_LIST_CORRUPT and MEMEORY_MANAGEMENT

29 Dec 2012   #1

Win7 x64

Computer has been BSoDing quit a bit since we built it (even during windows installs at times).
Motherboard: ASUS P8Z68-V Pro
CPU: i7 2600K
RAM: 8gb GSkill RipjawX (F3-12800CL9D-8GBXL)
HDD: Was originally a 128gb OCZ Vertex2, replaced it with a 256gb Samsung 830
OS: Win7 x64
Graphics Card: Was a GTX460, upgraded to a GTX680

Attached file contains a heap of different times the PC has BSoD'd (since I cleared them out that is).

Had run win7 x64 for a while, then got win8 x64 but it would occasionally BSoD as well. After upgrading my BIOS to the latest version (from 1 revsion before it) win8 would crash on every boot, so I formatted and re-installed win7 again.

Have ran memtest86+ for 3 days, have ran prime95 for 20 hours using just about all of the available free RAM after a reboot (left about 400mb to spare, https://fbcdn-sphotos-g-a.akamaihd.n...55417024_n.jpg, ignore the win classic theme :P) and neither of these tests failed.

Unsure if problem is in RAM or memory management module in the CPU... I think all my drivers are up to date. Also have had occasions where chrome would crash one of its tabs and I would not be able to go to that webpage again until after a reboot. Other times with both chrome and firefox they have crashed and corrupted themselves and they would not re-launch until they were re-installed.

Friend had asked what my voltages were set at, so i took these screenshots.




He said to:

Set these

CPU Voltage - 1.25v
DRAM Voltage - 1.6v
VCCIO Voltage - 1.2v

Your CPU PLL voltage may need a slight bump too... normal rated value should be 1.8v, yours is a sneeze under that, it may be fine but try nudging it up to say 1.85v.
So I did that, ran for about 4 days then got a MEMORY_MANAGEMENT BSoD again...

I am running out of ideas. Any and all help is greatly appreciated!

My System SpecsSystem Spec
30 Dec 2012   #2

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

Welcome to SevenForums.

Did you run memtest with all sticks inserted?

Please follow what's asked in this quote:
Quote   Quote: Originally Posted by Dave76 View Post
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages (QPI/DRAM core voltage) are set at.
Then test RAM, in the following manner:

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.

In your case I would suggest running more than 8 passes for all sticks individually if you haven't done this already.

You have a lot of the following errors in eventapp:
  Log Name: Application
  Source: NVIDIA OpenGL Driver
  Date: 2012-12-08T21:48:17.000
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Brad-PC
The NVIDIA OpenGL driver has encountered an out of memory error. This application might behave inconsistently and fail.
Reinstall a last known stable driver for the GPU.

Click on the Start ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to " NVIDIA" and reboot the system. Delete remnants of its drivers/older drivers using Driver Sweeper.

Drivers - Clean Left over Files after Uninstalling

Video Card - Stress Test with FurmarkMonitor your temps with Speccy during these testsVideo memory test for around 20 passesLet us know the results.
My System SpecsSystem Spec
30 Dec 2012   #3

Win7 x64

Have attached the CPU-Z result.

Have removed nVidia drivers and reinstalled latest.
Did burn in test with FurMark, stopped the test once it leveled out the temp (70 degrees), observed no artifacts.
Could not monitor GPU temps with Speccy as Speccy does not monitor GPU temps (at least on the GTX 680). Used MSI Afterburner to monitor temps. Not using MSI Afterburner to OC the GPU, just use it to monitor.

Video memory stress test resulted in
Changing video mode to 640x480x16...OK
[30/12/2012 9:09:09 PM] Test started for "Primary Display Driver (NVIDIA GeForce GTX 680)"...
Trying 16bpp RGB:565 mode...OK
Trying 16bpp RGB:555 mode...OK
Trying 16bpp BGR:565 mode...NOT SUPPORTED (Code: 80004001)
Trying 32bpp RGB:888 mode...OK
Trying 32bpp BGR:888 mode...NOT SUPPORTED (Code: 80004001)
[30/12/2012 9:20:00 PM] Pass completed (0 errors found).

As for testing memory if I am not mistaken (See part1 and part2 RAM Memory Troubleshooting & Diagnosis Part 1 Linus Tech Tips - YouTube) if memory is to fail in a multi-channel environment the test would fail in a multi-channel environment and the stick can still pass in a single channel environment... I have run tests in this multi-channel environment over several days and it did not error. But alas, I will repeat these tests as you have requested. I will try each DIMM slot with each memory stick (so going to do 8 - 8 pass runs) and will update after that is done as that could take quite some time...

It appears that Driver Sweeper has been replaced with Driver Fusion according to We are happy to see you at

EDIT: I also forgot to mention that the memory is on the supported vendors list.
My System SpecsSystem Spec

30 Dec 2012   #4

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

Thanks for the snips, I see they're OK, but I've requested a friend to take a look at them.

I forgot to ask one thing:
Is the firmware for the SSD(s) up to date?
My System SpecsSystem Spec
30 Dec 2012   #5

Win7 x64

I'll check tomorrow when I get up (just got in bed) but it shouldn't matter too much as I had this problem with the OCZ vertex2 SSD.
My System SpecsSystem Spec
30 Dec 2012   #6

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit


When you're back uninstall Avast!.
Start Menu\Programs\avast! Free Antivirus
It seems to be contributing to your crashes.
fffff880`0686b6d8  fffff880`0431bea1Unable to load image \SystemRoot\System32\Drivers\aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Use MSE instead:

Microsoft Security Essentials.
Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-
warning   Warning
Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.
My System SpecsSystem Spec
31 Dec 2012   #7

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64

Those suggested voltage increases are ok, although a bit high for testing purposes, and don't correspond to the voltage pics.
Are the voltages at the suggested level or at the level in the pics?

Leave the CPU voltage on Auto.
DRAM Voltage - 1.550v
VCCIO Voltage - 1.150v

When RAM passes memtest86+ it doesn't mean the RAM is good or won't fail the next test, just the way electronics are.
Run the test on the single RAM cards, as suggested.
Sometimes re-seating the cards will help.

The last two crashes are the same:
Usual causes:  Device driver, memory, kernel
They are blaming Chrome and Steam, not a lot of useful information. 
Which usually indicates a RAM issue
The previous two are the same:
Usual causes:  Device driver, ?memory
Probably caused by : memory_corruption
fffff880`035e76d8 fffff800`033080ec : 00000000`0000004e 00000000`00000099 00000000`000a5282 00000000`00000003 : nt!KeBugCheckEx
fffff880`035e76e0 fffff800`032e252a : fffffa80`02697720 00000000`00000001 00000000`000cdd26 00000000`00000000 : nt!MiBadShareCount+0x4c
fffff880`035e7720 fffff800`03380c9a : fffffa80`0adea7d8 fffff880`035e7930 00000000`00000000 fffffa80`0000000a : nt! ?? ::FNODOBFM::`string'+0x20543
fffff880`035e7910 fffff800`032fa377 : fffffa80`066ed950 fffff880`00000001 00000000`00000000 fffff880`031657f0 : nt!MiEmptyWorkingSet+0x24a
fffff880`035e79c0 fffff800`0326bf46 : 00000000`00006021 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4c632
fffff880`035e7a40 fffff800`0326c360 : 00000000`00000008 fffff880`035e7ad0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`035e7a90 fffff800`03518e5a : fffffa80`066ed950 00000000`00000080 fffffa80`066d7740 00000000`00000001 : nt!KeBalanceSetManager+0x138
fffff880`035e7c00 fffff800`03272d26 : fffff880`009b3180 fffffa80`066ed950 fffff880`009be0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`035e7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
The PFN_LIST_CORRUPT stop code is usually a RAM fault, sometimes (not often) caused by a bad driver.
When the stack starts out with errors (the bottom is the start) it's pointing to hardware.

From your System Event Logs:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2012-12-29T20:38:45.760
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  Computer: Brad-PC
ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated.             
_PSV = 0K             
_TC1 = 0             
_TC2 = 0             
_TSP = 0ms             
_AC0 = 353K             
_AC1 = 328K             
_AC2 = 273K             
_AC3 = 273K             
_AC4 = 273K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
_CRT = 372K             
_HOT = 0K             
_PSL - see event data.
This is indicating your CPU is overheating.
Check that the CPU cooler is firmly attached.
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Intel® Core™ i7-2600K Processor
Your CPU max temp is 77.6°C.

From your Apps Event Logs:
About 40k of these ending around Dec 9.
  Log Name: Application
  Source: NVIDIA OpenGL Driver
  Date: 2012-12-09T09:31:34.000
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Brad-PC
The NVIDIA OpenGL driver has encountered an out of memory error. This application might
behave inconsistently and fail.
This may be the reason for crashes from those dates, graphics driver.
Have you changed it?

Lots of errors from Bonjour Service, ipod related, make sure it's up to date.
My System SpecsSystem Spec
31 Dec 2012   #8

Win7 x64

Uninstalled avast, installed MSE, updated scanned, all clear.

Samsung 830 SSD firmware was up to date.

I went away for New Years and left the computer doing a memtest. This was with 2 sticks in the default position how they were (thought I'd re-test after altering voltage and whatnot). The RAM is in slots A2 and B2 as advised by the manual (, section 2.2.3).
See memtest.jpg

I have since removed the stick from B2 and am running a single stick in A2 also as advised by the manual.

Quote   Quote: Originally Posted by Dave76 View Post
Are the voltages at the suggested level or at the level in the pics?
Those where from before I updated the pictures. See ai-tweaker-3.png for currnet settings.
After this stick has tested I'll change the voltages back to what you suggested. Then will keep testing memory as instructed in the first reply :)

Quote   Quote: Originally Posted by Dave76 View Post
They are blaming Chrome and Steam, not a lot of useful information.
Which usually indicates a RAM issue
Yeah, from the times these happened neither Chrome or Steam were doing anything intensive nor were using a lot of memory. I remember the previous chrome one I had opened a new tab with maybe 3 other tabs open, wrote "" and hit enter and it BSOD'd.
Though it should be noted that chrome would occasionally crash with this screen

As for the temp thing, yeah it was running a little hot. When I ran XMP settings from the mother board it set my CPU clock a lot higher than I'd like, hitting 98 degrees in the few minutes I was running prime95 for before I got worried and changed the settings back. It idles at about 40 degrees as shown in monitor-1.png

Ill make sure the heatsink (stock intel cooler) is in firmly, other than that I will get a friend to help me clean off the old muck and re-seat it.

Removed the drivers for graphics card, did a clean with the driver as instructed in first reply.

As for Bonjour and stuff, I would assume updating iTunes would fix that which is always updated.

EDIT: I also attached other BIOS screens incase something was set blatantly wrong.
My System SpecsSystem Spec
01 Jan 2013   #9

Win7 x64

Finished testing stickA in slot A2, IMG_0454.JPG

I also adjusted the voltages as instructed and took a photo of BIOS after a reboot, IMG_0457.JPG
My System SpecsSystem Spec
01 Jan 2013   #10

Win7 Ultimate X64

1st memtest screen with two sticks shows speed @ 800 Mhz
My System SpecsSystem Spec


Thread Tools

Similar help and support threads
Thread Forum
Random BSOD, last one (PFN_LIST_CORRUPT)
Hi guys, lately I've been getting a lot of BSOD, I never put them much attention but now is getting annoying. They tend to happen randomly. The BSOD are different, the last one I got was PFN_LIST_CORRUPT Hope you can help me, thanks in advance
BSOD Help and Support
Random BSOD PFN_List_Corrupt
Lately I have been finding the computer on bsod occasionally. It has PFN_List_Corrupt at the top and I read a post to run verifier. when I restarted computer it kept going to bsod before it could even load up windows completely and said a driver was causing the problem. But I don't know which one....
BSOD Help and Support
Random BSOD PFN_List_Corrupt
Hi, Getting some random BSOD all of a sudden within the past 2 days, progressively gotten worse tends to be happening every 30 minutes now. I've attached the mini dump Any help would be great Thanks
BSOD Help and Support
Hello, i need help with random BSOD on Windows 7 64 bit. System is updated including all patches and drivers, but i'm getting BSOD PFN_LIST_CORRUPT once per day. Based on my findigs this BSOD is pointing to buggy driver, but i can't identify which one. I executed memtest86 for 12 hours run,...
BSOD Help and Support
caused by driver ntoskrnl.exe, not sure what to do about this. Running Windows 7 64 bit on a fresh build, memory checks out after repeated long term testing. My hardware profile is in my profile.
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 17:20.
Twitter Facebook Google+