BSOD PFN_LIST_CORRUPT While Inputing info on a webpage

maretodoric · 22 Jun 2014

First of all, i want to greet all members of the forum and I'm sorry that this is my first post.

As the title says, i was surfing the net, trying to input some info on my homebanking website (and it's possible that PC was doing some background job but can't remember what) and all of a sudden, i got a BSOD - PFN_LIST_CORRUPT
I was doing some searching and found out that it could be driver related. So i ran Driver Verifier using the info found on your forum here and i couldn't boot back up to windows because of other BSOD. Before i get to login screen, the system hangs.
I managed to boot back up using the "Last known good config." in startup menu.

I can't figure out which driver gives me the trouble so i was hoping that you can help me.
In an attachment is a zipped file of DM Log Collector's logs and a screenshot of a BSOD after i ran Driver Verifier.

Thanks in advance.

Boozad · 22 Jun 2014

Paragon Image Mounter is causing issues.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {e1, fffff98002f06f9c, 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+182be )

Followup: MachineOwner

Either uninstall or check for any updates.

Code:

2: kd> lmvm uim_vimx64
start             end                 module name
fffff880`04c77000 fffff880`04cd4380   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 Nov 22 12:08:04 2012 (50AE15A4)
    CheckSum:         00068F05
    ImageSize:        0005D380
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your nVidia driver is also being flagged.

Code:

fffff880`0a95a2f8  fffff880`0faa574eUnable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x21274e

Code:

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f893000 fffff880`104f7000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue May 20 00:08:44 2014 (537A8EFC)
    CheckSum:         00C1EA41
    ImageSize:        00C64000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Download this earlier version from here and follow NVIDIA Drivers - Avoid Problems for the cleanest possible install.

Uninstall Alcohol 120%, a known cause of BSODs.

Code:

C:\Program Files (x86)\Alcohol Soft\Alcohol 120\AxAutoMntSrv.exe

1. Uninstall Alcohol 120%.
2. Download the SPTD standalone installer and follow these steps:
3. Double click the executable to open it
4. Click the button shown below

If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.

Report back after these steps as more action may need to be taken.

maretodoric · 22 Jun 2014

Okay, done everything.
I've removed Paragon HDD Suite (in which package was Paragon Image Mounter)
I've removed alcohol 120% and SPTD Drivers and done a fresh install of nVidia drivers.

If i need to do anything else, please, tell me :)
Btw, offtopic, which software to for virtual drives use if Alcohol is unreliable? Is Daemon tools reliable?

Boozad · 22 Jun 2014

No, do not use DaemonTools as it uses SPTD just like Alcohol120% does. That's a bridge we can cross when the BSODs are eliminated, for now that is our primary objective.

In the meantime, test the system for a few days to see if the BSODs re-occur. Report back with the results of your system stability.