PFN_LIST_CORRUPT while moving my Temp file to other drive

I was moving my temporary folder from my SSD drive to my HDD drive today and after I pushed ok to change the %USERPROFILE%\AppData\Local\Temp that was for TEMP and TMP to D:\TEMP, then closed out Internet Explorer 9, I immediately got a PFN_LIST_CORRUPT 0x4e BSOD.

Id like to know the cause of the BSOD if possible. Was this directly contributed to me having IE9 open while during me changing the TEMP/TMP file location? Could someone please have a look and give me some info if it was a driver or not. Thanks.

Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+






Driver Verifer

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc) It is doubtful that IE had any effect but it was running at the time.

More likely a driver (not named) wrote bad data to the page file.

Thanks for both your responses and feedback. I just installed a new wireless router today. It didnt have a driver so I thought I didnt need one. I even checked the companies site and there was none on there. When i was looking around to find the cause of the BSODs i checked my device manager and saw the exclamation mark with yellow triangle warning on my wireless router device. Then I checked windows updater shortly after and there was an "important" update for microsoft wireless router driver. I installed that and havent had another BSOD so far. Im not sure if this was the cause of them or not (hopefully was) but im still keeping driver verifier on for at least 24 hours, thanks again

Tank997 said:

Thanks for both your responses and feedback. I just installed a new wireless router today. It didnt have a driver so I thought I didnt need one. I even checked the companies site and there was none on there. When i was looking around to find the cause of the BSODs i checked my device manager and saw the exclamation mark with yellow triangle warning on my wireless router device. Then I checked windows updater shortly after and there was an "important" update for microsoft wireless router driver. I installed that and havent had another BSOD so far. Im not sure if this was the cause of them or not (hopefully was) but im still keeping driver verifier on for at least 24 hours, thanks again

Good job so far. If you crash dont forget to upload the DMP files.

I was copying bookmarks from IE9 browser and pasting them in Firefox to import some bookmarks into Firefox (I had just installed Firefox) and when I switched from IE9 browser to Firefox browser window I BSOD'ed to a Memory Management 0x1a error.

My bluescreen viewer says that it was caused by driver tcpip.sys address tcpip.sys+6e8f7


Who Crashed says this:

This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x1A (0x3452, 0x1662E000, 0xFFFFF700010B5988, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe


This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x3452, 0x1662E000, 0xFFFFF700010B5988, 0x0)
Error: MEMORY_MANAGEMENT



Was this crash directly contributed to firefox? I have since uninstalled Firefox to see if the crash happens again. If it doesn't i might reinstall firefox next week and see if the crashes return. I posted the dmp file if anyone would be so kind to give me more info.

Ok. For a solid month straight I was BSOD'ing while playing Battlefield 3 and just surfing the web in general. That whole time I was using Firefox browser. I thought and was told by many people that the reason I was getting BSOD's was because of my video drivers being corrupt some how.

I decided to do a fresh Windows 7 install and only use IE9 since i figured it would be the most stable to run with windows (and not give me crashes). For 5 entire days I used ONLY IE9 and I didnt get one BSOD the whole time! I decided to install Firefox 11 again, sure enough 1 hour into a BF3 session i minimized the game to check something in firefox and immediatly got a BSOD. That was my eureka moment. I was sure that it was Firefox that was causing my problems.

I uninstalled firefox and installed Google Chrome. All seemed well again until I did the same thing that crashed me in firefox. I minimized a BF3 game while the countdown to the next game was going on to check some stuff in the google chrome browser. As i clicked a link i got a PFN_LIST_CORRUPT BSOD. So both Firefox and Google Chrome give me BSOD's while IE9 Gives me no BSOD. What am i to make of this?

The only thing I can think of is to possibly change the Compatibility mode of Firefox and Chrome to something different and hope they stabilize.

Has anyone got a recommendation of what to set Firefox and chrome's compatibility mode setting to to try and resolve them causing BSODs?

The BSOD are always "MEMORY_MANAGMENT" or "PFN_LIST_CORRUPT"

Tank 997,

Most (if not all) BSOD's are caused by a mulitude of events.

Usually it is a combination of files interacting that finally causes the crash.

You can install an application and have it interact with one you installed 6 months ago and have them both cause the crash.

Did you submit any DMP's for analysis by our BSOD group?

Try Opera.

JMH said:

Tank 997,

Most (if not all) BSOD's are caused by a mulitude of events.

Usually it is a combination of files interacting that finally causes the crash.

You can install an application and have it interact with one you installed 6 months ago and have them both cause the crash.

Did you submit any DMP's for analysis by our BSOD group?

Here are the DMP's, the MEMORY_MANAGEMENT was from firefox , the PFN_LIST_CORRUPT was with chrome open