BSOD 1-2 times per day PFN_LIST_CORRUPT error 4e

thedriveee · 04 Dec 2014

Hello all!

I'm sometimes (1-2 times per day) getting BSOD. It started happen after installation new OS - Windows 7 Ultimate x86. On last (XP) I did not get BSOD.

My PC:
MB: ASUS P5K
Proc: Core 2 Duo E6550 2.33 GHz
RAM: 2 x 1Gb DDR2 Corsair
Video: GeForce 8600 GTS

Please help! Thanks everybody in advance.

koolkat77 · 05 Dec 2014

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\Compressed\TRAST-PK-04_12_2014_131422,76\120314-22136-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82a49000 PsLoadedModuleList = 0x82b93850
Debug session time: Wed Dec  3 10:13:29.919 2014 (UTC + 6:00)
System Uptime: 0 days 0:07:07.527
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, a20e, 2, 9d8d}

*** 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+24 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 00000099, A PTE or PFN is corrupt
Arg2: 0000a20e, page frame number
Arg3: 00000002, current page state
Arg4: 00009d8d, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82b33513 to 82b27f20

STACK_TEXT:  
95e77690 82b33513 0000004e 00000099 0000a20e nt!KeBugCheckEx+0x1e
95e776a8 82af573b 00000000 841f1260 82a17b48 nt!MiBadShareCount+0x24
95e776ec 82b18c70 00000001 00000000 c0036380 nt!MiRestoreTransitionPte+0x250
95e77728 82ae7101 84e503b8 c0036380 84e50340 nt!MiRemoveLowestPriorityStandbyPage+0x1bc
95e77748 82b19407 0000002f 00000000 00000000 nt!MiGetPage+0x2a0
95e777d0 82adae04 0000000e c0036310 84e5040c nt!MiResolvePageFileFault+0x744
95e77850 82ad98ed 06c62005 00000000 88355c48 nt!MiDispatchFault+0x66d
95e778d8 82b188a7 00000000 06c62005 00000000 nt!MmAccessFault+0x25cc
95e77918 82b18a5e 00000010 85327400 00000000 nt!MiPrefetchVirtualMemory+0x1df
95e77970 82ce30b8 80000a6c 00000010 85327400 nt!MmPrefetchVirtualMemory+0x10a
95e779dc 82ce2889 95e77a08 95e77b64 00000001 nt!PfpPrefetchPrivatePages+0x1c5
95e77a80 82ce2ba4 a8d34000 b6361582 95e77b78 nt!PfpPrefetchRequestPerform+0x216
95e77ad4 82c8dff3 95e77b64 00000001 b63614ce nt!PfpPrefetchRequest+0x16e
95e77b98 82c99cd2 0334fb60 00000014 00000001 nt!PfSetSuperfetchInformation+0x182
95e77cd8 8d45187d 0000004f 00000000 00000014 nt!NtSetSystemInformation+0xbdd
WARNING: Stack unwind information not available. Following frames may be wrong.
95e77d20 82a871ea 0000004f 0334fb60 00000014 aswSnx+0x1887d
95e77d20 770270b4 0000004f 0334fb60 00000014 nt!KiFastCallEntry+0x12a
0334fb78 00000000 00000000 00000000 00000000 0x770270b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+24
82b33513 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+24

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78a09

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x4E_99_nt!MiBadShareCount+24

BUCKET_ID:  0x4E_99_nt!MiBadShareCount+24

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

Caused by Avast! Remove it for testing.

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

Good and Free system security combination.

Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

Click on the
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

SPTD Removal:

Uninstall the software using Add/Remove Programs.
Reboot the system.
Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.
DuplexSecure - Downloads

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Take memtest. 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.

Information

Errors are sometimes found after 8 passes.

Tip

Memtest should be done overnight.

thedriveee · 05 Dec 2014

Thanks for helping.

But It definitely was not about avast. looks like BSoD appeared because of Windows or drivers. ASUS did not write drivers on P5K for Windows 7. I setup Vista drivers on compatibility mode. Also may be I setup bad Windows 7.

I restart it and It work good (for now:)).