Random BSoDs ("PFN_LIST_CORRUPT")

There doesn't seem to be any rhyme or reason to them, sometimes I can go a week without a problem, other times it'll be as often as one a day. It doesn't seem to matter what programs I'm running as it's happened while playing Starcraft 2 and also when just browsing the web. Not really sure what other information I can provide.

Hello NightKev and welcome to Sevenforums.

BSOD Analyse

The stack unfortunately, doesn't show as much information as I wanted to. Though, looking at specific crash symbols, it's blaming the system and memory on most of the cases. We're going to troubleshoot the basics, and hopefully draw some conclusions that we'd find useful.

Code:

1: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`009efd68 fffff800`030cc769 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009efd70 fffff800`030cac32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009efeb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2

Memory Troubleshooting

Looking at your bugcheck it's likely that a memory corruption event was triggered. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.

   Warning

Note that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.

To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

i) System (kernel) Troubleshooting

We usually ask people to do this command to check if Windows is corrupted. It's the most common one used to check if the Windows files are corrupted. If it'll find errors, it'll restore them.

   Tip

If you're having a custom customization layer on your Aero, it's likely to get restored to default.

Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

SFC /SCANNOW Command - System File Checker

ii) System (kernel) Troubleshooting

For a trial, try downloading a copy of Ubuntu and see if your system will crash.
By that, we'd have an idea if Windows 7's drivers and system is broken. You can try it out on a
flash drive if you so desire.
Go to Ubuntu.com | Download the image | See how to create a bootable flash drive
Leave it running for some time and report your results.

STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP

Code:

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are.

Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

Best Regards,
Frederik.

Alright. Let's enable driver verifier.

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.

So, 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).

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 "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- 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.

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 locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Best Regards,
Frederik.

Code:

Start Menu\Programs\Paradox Interactive	Public:Start Menu\Programs\Paradox Interactive	Public
Start Menu\Programs\Paradox Interactive\Crusader Kings II	Public:Start Menu\Programs\Paradox Interactive\Crusader Kings II	Public
Start Menu\Programs\Paragon Backup & Recovery™ 10 Home Special Edition	Public:Start Menu\Programs\Paragon Backup & Recovery™ 10 Home Special Edition	Public
Start Menu\Programs\Paragon Drive Copy™ 11 Professional Special Edition (English)	Public:Start Menu\Programs\Paragon Drive Copy™ 11 Professional Special Edition (English)	Public
Start Menu\Programs\Paragon Migrate OS to SSD™	Public:Start Menu\Programs\Paragon Migrate OS to SSD™	Public
Start Menu\Programs\Paragon Partition Manager™ 11 Personal Special Edition	Public:Start Menu\Programs\Paragon Partition Manager™ 11 Personal Special Edition	Public

Your BSOD with Verifier enabled points toward Paragon Image Mounter (UIM) Plugin driver. Suggest you to uninstall everything related to this program to test.

Code:

Debug session time: Wed Nov 28 22:07:30.676 2012 (UTC + 6:00)
System Uptime: 0 days 0:00:27.863
STOP 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION  
Usual causes:  Device driver 
BugCheck C4, {e1, fffff98001420f9c, 0, 0}
*** WARNING: Unable to verify timestamp for uim_vimx64.sys
*** ERROR: Module load completed but symbols could not be loaded for uim_vimx64.sys
Probably caused by : uim_vimx64.sys ( uim_vimx64+1827e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
...........................................................................................
kd> lmvm uim_vimx64
start             end                 module name
fffff880`04434000 fffff880`04491300   uim_vimx64 T (no symbols)           
    Loaded symbol image file: uim_vimx64.sys
    Image path: \SystemRoot\System32\Drivers\uim_vimx64.sys
    Image name: uim_vimx64.sys
    Timestamp:        Thu Jul 05 04:56:06 2012 (4FF4CA06)
    CheckSum:         0006F120
    ImageSize:        0005D300
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Free up the start-up:

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

*How does the PC work in safe mode?

Uninstall SandBox.

Update the video card drivers.
Click on the Start ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; ATI. (Restart the system) Delete remnants of its drivers/older drivers using Driver Fusion/Sweeper

Latest version: AMD Driver Autodetect

Video Card - Stress Test with Furmark

• Video Card - Stress Test with Furmark

Monitor your temps with Speccy during these tests

• Speccy - System Information - Free Download

Take memtest in the following way: Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

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.

Errors are sometimes found after 8 passes.
Do this test overnight, before going to bed.