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 PFN List Corrupt

Greetings and thanks in advance for your help. Our system is experiencing frequent BSOD issues. Attached are the requested files per the posting instructions.

Our system is running Win7 64 Home Premium. We have an EVGA 750i SLI mobo and an EVGA GTX560 video card. Memory is 4GB (2 sticks, 2GB ea) of Kingston HyperX. We have a WD hard drive. The CPU is a Core2Quad Q6600 at 2.4 GHz.

In addition to the BSOD issues we also have constant video card crashes when playing Battlefield3.

Nothing is attached try this method.We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
Please attach the DMP files to your next post not to post one.If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

Quote:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

Quote:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

2. These crashes were caused by memory corruption/exception (Cx05) probably a driver.
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.

Quote:

*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.

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"IRP Logging and Force Pending I/O Requests. 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.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.

* Please provide us with your Event Viewer administrative logs by following these steps:

Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file here.

* I suggest you download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

BSOD PFN List Corrupt

BSOD PFN List CorruptI had some very bad luck after installing Adobe Photo Shop with BSOD's so I uninstalled it but things seemed to turn worse so I did a restore. It seemed good but my Norton 360 was out of date after the restore, During the update I got a BSOD PFN List Corrupt. Here is my DM Log Collector file. ...

BSOD Help and Support

Bsod - pfn list corruptI've had this computer for about 6 months now. I've had BSOD constantly, and whatever I do isn't helping a friend told me to come here. So here I am, if you can please help me.
I've run Prime95 for 24-48 hours and no problems then I can run it a different time and it will crash. I've fixed my...

BSOD Help and Support

PFN List Corrupt BSoDWindows 7:
x64
Original OEM OS
Laptop is 2 months old
I recovered laptop to factory default to see whether BSoD will appear again or not

BSOD Help and Support

Random BSOD PFN List CorruptOver the last week or so i keep getting random BSOD happening for no apparent reason at all.
The computer reboots to quickly for me to gather any information.
All I've had a chance to read at towards the top was
PFN List Corrupt
I googled that and it said test your memory so i ran the...

BSOD Help and Support

BSOD PFN List CorruptI am having random BSOD's with the same PFN list corrupt error message. I have attached the requisite zip files. Any help would be greatly appreciated.
Windows 7 32-bit upgraded from Vista full retain version purchased from retailer in August, 2009; upgrade to Windows performed in December,...