BSOD shortly after starting PC (PFN_LIST_CORRUPT)

[Tosti]

Hi all,

I get similar BSOD's every couple of days (see dump files in attachment). They always seem to occur very shortly after starting the PC; either quickly after entering the windows environment (without starting any programs) or shortly after opening the browser or similar program. Remarkably, I can play Battlefield 4 for hours without any BSOD. In fact, I never had a BSOD while playing intensive games. Because of this, I highly doubt it is faulty RAM and I also did a run of memtest86 without errors.

Things I have tried so far:
- Updated all drivers with DriverMax
- Switched antivirus program after reading online this might help (from Avast to Microsoft Security Essential)
- Memtest86
- Remove all programs from startup list except antivirus
- Uninstalled all programs I do not use regularly

I have tried to use driver verifier, but it crashes when I try to stress all drivers. It does not give a BSOD however, so I do not get any information out of it. This again implies (to me) it is a driver issue, but I have no clue how to find the faulty driver.

Any help would be appreciated!

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 144b91, 0, 1cb611}

*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

Did you uninstall Avast after the BSOD at 7:06 on 11/11/2014?

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000001a3a61, page frame number
Arg3: 0000000000000001, current page state
Arg4: 00000000001a3b61, 0

Debugging Details:
------------------


OVERLAPPED_MODULE: Address regions for 'HIDCLASS' and 'crashdmp.sys' overlap

Is Windows fully updated? Do you have yellow triangles next to any USB entries in Device Manager?

 

[Tosti]

Hi Golden,

Thank you for your time and reply.

I have indeed removed Avast after that BSOD. Windows is fully updated and there are no yellow triangles.

 

[Tosti]

I just had another BSOD, see the dumpfile in the attachment. This one occured after 1-2 minutes in the windows environment. Any ideas?

 

[Tosti]

Anyone? I really have no clue what else I can try...

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, cdc64, 3, cd3e3}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

Im not getting anything uselful from the .dmp.

I agree that its probably a driver, and that you said you tested RAM, but I think its worth running it again. You must run 8 full passes of RAM using MemTest86+ to thoroughly test it. Please do that so we can rule it out conclusvely.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Another question : are all the motherboard drivers up-to-date?

 

[Tosti]

For some reason I can not boot Memtest86+ from USB, but Memtest86 does work. Is there any real difference between the 2? I don't have CD's so I'd prefer to use memtest86, unless memtest86+ is significantly better for some reason. I can run 10 passes overnight to confirm it is not a RAM problem.

I used a program called 'drivermax' to update all drivers automatically. I checked the Asus support site for the Z87-C and downloaded the drivers. Strangely, the installer of those drivers said I have newer ones already installed. How can drivermax install drivers that are newer than the ones on the official website? I am now wondering if these are perhaps beta or in another way not ideal...

 

[Golden]

For some reason I can not boot Memtest86+ from USB, but Memtest86 does work. Is there any real difference between the 2? I don't have CD's so I'd prefer to use memtest86, unless memtest86+ is significantly better for some reason. I can run 10 passes overnight to confirm it is not a RAM problem.

I used a program called 'drivermax' to update all drivers automatically. I checked the Asus support site for the Z87-C and downloaded the drivers. Strangely, the installer of those drivers said I have newer ones already installed. How can drivermax install drivers that are newer than the ones on the official website? I am now wondering if these are perhaps beta or in another way not ideal...

MemTest86+ is far superior, and the only one we recommend - you could try writing it to a CD, and booting from that.

I would not use a program such as DriverMax to install driver updates, I would only get them directly from the manufacturers site.

 

[Tosti]

I have tested the RAM overnight with memtest86+ and found no errors. I'm glad I did though, cause now it is indeed ruled out for sure. As far as I know, all drivers are up to date. I use an old wireless rechargeable mouse by Logitech that is plug-and-play. I cant find new drivers for this, but I guess this is normal?

I have also checked:
- SFC scannow
- HDD

 

[Golden]

I use an old wireless rechargeable mouse by Logitech that is plug-and-play. I cant find new drivers for this, but I guess this is normal?

Yes, I don't see that as a problem.

Lets stress the drivers, and see if we can find anything useful. Please read this then implement, and lets see what we can get:

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Tosti]

Thank you for your help Golden. Sorry for my late reply (I was away last 2 days). I turned on the verifier, but so far (couple of hours) nothing happened. I will continue to use it tomorrow to hopefully find something. Is it also useful if there is no BSOD?

 

[Golden]

Run DV for 24hrs...if it doesn't BSOD then, we could potentially say it's solved but keep the thread open in case.

 

[Tosti]

OK, it did not crash so I guess it is not one of the drivers. I have not had a BSOD for a couple of days now so perhapt it was fixed somewhere along the way. I'll keep you updated.

 

[Golden]