PFN List Corrupt BSoD

[writhziden]

Well, verifier gives BSoD when ESET's real time system protection is active. It gave BSoD when I was trying to install Logitech Setpoint too.

• Disable Verifier.
  
• Use the ESET uninstall tool. Replace ESET with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows Firewall.
  
• Re-enable Verifier as before.

 

[Kurama]

I uninstalled ESET and activated verifier. No problem right now...

 

[writhziden]

Alright, run for a bit and post back after you've had a few crashes so we can find a pattern with any crashes. Best wishes it will be more stable and be a while before you have a few.

 

[Kurama]

Well, I got "Driver Verifier IOMANAGER Violation" when I was trying to create virtual device with Daemon Tools...

P.S: I can't upload any files at the moment...

 

[writhziden]

Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.

 

[Kurama]

Verifier is active but I still get PFN LIST CORRUPT BSoD. Could it be because of HDD? When I bought the laptop, I tried creating another partition with Parago but it had gave error. Maybe this is the cause...

 

[writhziden]

Verifier is active but I still get PFN LIST CORRUPT BSoD. Could it be because of HDD? When I bought the laptop, I tried creating another partition with Parago but it had gave error. Maybe this is the cause...

PFN_LIST_CORRUPT usually means a driver or memory issue. It is not likely a hard drive problem unless it caused a corrupt driver. Can you upload your latest crash reports? If you believe it might be hard drive related, do a http://www.sevenforums.com/tutorials/3413-repair-install.html of Windows 7.

 

[Kurama]

I used Acer's recovery so it can't be driver related.

 

[writhziden]

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\Kingston\BSODDmpFiles\Kurama\Windows_NT6_BSOD_jcgriff2\021912-20545-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0309f670
Debug session time: Sun Feb 19 05:26:53.291 2012 (GMT-7)
System Uptime: 0 days 1:54:45.054
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 2e6b3, 1, 138cb3}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+f33 )

Followup: Pool_corruption
---------

5: 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: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000002e6b3, page frame number
Arg3: 0000000000000001, current page state
Arg4: 0000000000138cb3, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  2

IRP_ADDRESS:  ffffffffffffff88

LAST_CONTROL_TRANSFER:  from fffff80002f5fd7c to fffff80002ed6c40

STACK_TEXT:  
fffff880`04a98298 fffff800`02f5fd7c : 00000000`0000004e 00000000`00000099 00000000`0002e6b3 00000000`00000001 : nt!KeBugCheckEx
fffff880`04a982a0 fffff800`02fd8bfa : 00000000`00000001 fffff6fc`c0110800 00000000`00000000 fffff980`22100f10 : nt!MiBadShareCount+0x4c
fffff880`04a982e0 fffff800`0300493b : fffff800`02e5a000 00000000`20206f49 ffffffff`fffc903c fffffa80`0d43af20 : nt!MmFreeSpecialPool+0x41a
fffff880`04a98430 fffff800`02eec09e : fffffa80`0d1a6060 fffff800`02ed94da 00000000`00000010 00000000`00200082 : nt!ExDeferredFreePool+0xf33
fffff880`04a984e0 fffff800`02eca2f7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopCompleteRequest+0x5ce
fffff880`04a985b0 fffff800`02edc13d : fffffa80`0d1a6060 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
fffff880`04a98630 fffff800`02edb44a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000002 : nt!KiCommitThreadWait+0x3dd
fffff880`04a986c0 fffff960`00159838 : fffff900`00000002 fffffa80`0bd42150 fffff900`00000001 fffff880`0000000d : nt!KeWaitForMultipleObjects+0x272
fffff880`04a98980 fffff960`0015a804 : 00000000`00000000 fffff900`c061cb60 fffff960`003a5560 fffff900`c061c9f0 : win32k!xxxMsgWaitForMultipleObjects+0x108
fffff880`04a98a00 fffff960`00115024 : fffffa80`00000001 fffffa80`0000000c fffffa80`0d1a6060 fffff6fc`400251a8 : win32k!xxxDesktopThread+0x254
fffff880`04a98a80 fffff960`0019529a : fffffa80`00000001 fffff960`003a5560 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x64
fffff880`04a98ab0 fffff800`02ed5ed3 : fffffa80`0d1a6060 00000000`00000004 000007ff`fffae000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`04a98ae0 000007fe`fd7d1eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0165fd28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd7d1eea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+f33
fffff800`0300493b 90              nop

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!ExDeferredFreePool+f33

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_VRF_nt!ExDeferredFreePool+f33

BUCKET_ID:  X64_0x4E_99_VRF_nt!ExDeferredFreePool+f33

Followup: Pool_corruption
---------
[*]
Loading Dump File [F:\Kingston\BSODDmpFiles\Kurama\Windows_NT6_BSOD_jcgriff2\021812-28095-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e4c000 PsLoadedModuleList = 0xfffff800`03091670
Debug session time: Fri Feb 17 17:08:19.198 2012 (GMT-7)
System Uptime: 0 days 7:36:24.072
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 187b2c, 3, 119a7e}

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

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

1: 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: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000187b2c, page frame number
Arg3: 0000000000000003, current page state
Arg4: 0000000000119a7e, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f51d7c to fffff80002ec8c40

STACK_TEXT:  
fffff880`0b518088 fffff800`02f51d7c : 00000000`0000004e 00000000`00000099 00000000`00187b2c 00000000`00000003 : nt!KeBugCheckEx
fffff880`0b518090 fffff800`02e709ef : fffff680`000423f0 00000000`0847e000 fffffa80`0eb243f8 fffff800`02ea1a22 : nt!MiBadShareCount+0x4c
fffff880`0b5180d0 fffff800`02ebe671 : d8600000`00000000 fffff680`000423f0 00000000`00000200 000fffff`00000001 : nt! ?? ::FNODOBFM::`string'+0x336da
fffff880`0b518150 fffff800`02eb5e62 : fffffa80`0cb8a7c0 fffff880`00000000 fffffa80`0eb24060 fffffa80`0eb243f8 : nt!MiDecommitPages+0x1a1
fffff880`0b5189e0 fffff800`02ec7ed3 : ffffffff`ffffffff 00000000`0033df50 00000000`0033df48 00000000`00004000 : nt!NtFreeVirtualMemory+0x382
fffff880`0b518ae0 00000000`77b714fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0033df18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b714fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02f51d7c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_VRF_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_VRF_nt!MiBadShareCount+4c

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


[/list]

1. Fairly inconclusive. Possible causes are Memory problems... Drivers...
2. This one is pointing toward memory. Same as the first one for possible causes.

These were caused by Verifier running, but they do not show which driver is the culprit. Disable Verifier for a time and see if the system runs more stable with the changes made so far.

Also, run memtest86+ again for 7 passes. Sometimes it has to be run for 7 passes a few times before errors are found.

I also note Avira installed. Avira is known to cause blue screen crashes on some systems. Recommend uninstalling using Start Menu -> Control Panel -> Uninstall a program and then running the Avira RegistryCleaner once the program has been uninstalled. Replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall, at least to test.

 

[Kurama]

I uninstalled Avira and 7 pass without errors at memtest.

I will check the temperature of graphic card when I play games.

 

[Kurama]

Well, I don't get BSoDs when antivirus program with firewall is not installed. I will observe the situation. If it is because of antivirus program's firewall, I will only install antivirus.

 

[writhziden]

Alright, keep us posted. Best of luck!

 

[Kurama]

I've got PFN List Corrupt when I tried shut down the computer

 

[writhziden]

Sorry to see the problem is back...

Please post back with the crash reports. They may have more information as to why the crash occurred.

 

[Kurama]

Well, I don't know why but it is decreased. At first month, I got more than 30 BSoDs. Now, it's 3-4 in 2 weeks.

Also, we can be sure that it isn't because of ESET

I will send it to technical service if problem persists.

 

[writhziden]

Problem Devices:

Broadcom 802.11n Network Adapter PCI \ VEN_14E4 & DEV_4358 & SUBSYS_E040105B & REV_00 \ 4 & 124A40C8 & 0 & 00E1 This device is disabled.

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


Loading Dump File [D:\Kingston\BSODDmpFiles\Kurama\Windows_NT6_BSOD_jcgriff2\022612-22822-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e5d000 PsLoadedModuleList = 0xfffff800`030a2670
Debug session time: Sun Feb 26 08:52:08.657 2012 (UTC - 7:00)
System Uptime: 0 days 5:07:59.533
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 18bb0b, 3, 15a305}

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

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

4: 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: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000018bb0b, page frame number
Arg3: 0000000000000003, current page state
Arg4: 000000000015a305, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f62d7c to fffff80002ed9c40

STACK_TEXT:  
fffff880`08311088 fffff800`02f62d7c : 00000000`0000004e 00000000`00000099 00000000`0018bb0b 00000000`00000003 : nt!KeBugCheckEx
fffff880`08311090 fffff800`02e819ef : fffff680`00022a90 00000000`04552000 fffffa80`0c1923f8 fffff800`0305dc80 : nt!MiBadShareCount+0x4c
fffff880`083110d0 fffff800`02ecf671 : cb600001`00000000 fffff680`00022a90 00000000`00000200 000fffff`00000001 : nt! ?? ::FNODOBFM::`string'+0x336da
fffff880`08311150 fffff800`02ec6e62 : fffff800`03062900 fffff880`00000000 fffffa80`0c192060 fffffa80`0c1923f8 : nt!MiDecommitPages+0x1a1
fffff880`083119e0 fffff800`02ed8ed3 : ffffffff`ffffffff 00000000`00efe6e8 00000000`00efe6e0 00000000`00004000 : nt!NtFreeVirtualMemory+0x382
fffff880`08311ae0 00000000`777414fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00efe638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777414fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02f62d7c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

Points to memory problems. Would you mind posting your memory and system setup through CPU-Z? Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

It may be the settings just need to be adjusted.

 

[Kurama]

Who haven't got CPU-Z on their computer?

 

[writhziden]

Have you tried running with just one module at a time and seeing if it is more stable? I am wondering if you have a bad module.

I forgot you had a laptop, so we cannot change any RAM settings, but they all look good anyway.

 

[Kurama]

No, I didn't try because I don't want to open laptop case until I send it to service.

 

[writhziden]

No, I didn't try because I don't want to open laptop case until I send it to service.

Fair enough. In that case, I would keep running Memtest86+ every chance you get to see if it finds any errors. If the problem persists, send it in to be serviced as you said.

How much longer do you have on the warranty?