PFN List Corrupt BSoD

Memtest will run until you stop it, so let it run for 7 passes. Windows Memory Diagnostic tool requires that you set how many times it runs.

Code:

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\020512-16926-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`02e09000 PsLoadedModuleList = 0xfffff800`0304e670
Debug session time: Sun Feb  5 13:10:25.464 2012 (GMT-7)
System Uptime: 0 days 9:41:15.339
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 5cf00, 2, 122aff}

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

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: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000005cf00, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000122aff, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f0ed7c to fffff80002e85c40

STACK_TEXT:  
fffff880`0b0a7368 fffff800`02f0ed7c : 00000000`0000004e 00000000`00000099 00000000`0005cf00 00000000`00000002 : nt!KeBugCheckEx
fffff880`0b0a7370 fffff800`02e2d3ce : 00000000`00000000 fffff680`00183088 00000000`00000000 00000000`30774009 : nt!MiBadShareCount+0x4c
fffff880`0b0a73b0 fffff800`02eb7bb7 : 00000000`00000000 fffff680`00183ff8 fffffa80`0d5cf4d0 fffff8a0`09f73c00 : nt! ?? ::FNODOBFM::`string'+0x33094
fffff880`0b0a7560 fffff800`02e730ff : fffffa80`00000000 00000000`30867fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`0b0a7720 fffff800`02e84ed3 : ffffffff`ffffffff fffff8a0`0e9aa858 fffff8a0`0e9aa880 fffff8a0`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0b0a7820 fffff800`02e81470 : fffff880`0318c4b2 fffff8a0`10318980 fffffa80`0d5cf4d0 fffffa80`0d845f00 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0b0a79b8 fffff880`0318c4b2 : fffff8a0`10318980 fffffa80`0d5cf4d0 fffffa80`0d845f00 fffff8a0`0e9aa850 : nt!KiServiceLinkage
fffff880`0b0a79c0 fffff880`03177b5a : 00000000`00000000 fffff8a0`04d7c520 00000000`00000001 fffff8a0`09e0f560 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`0b0a79f0 fffff880`03172523 : fffffa80`07a5cc10 00000000`00000001 fffff8a0`10318900 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112
fffff880`0b0a7aa0 fffff880`03158ecc : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0b0a7b70 fffff880`0309accc : fffff8a0`09ead3c0 fffff8a0`04a28000 fffff8a0`04a28000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0b0a7ba0 fffff880`0309b3ac : fffffa80`07298680 00000001`00000000 00000000`00000001 fffff8a0`04a28000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0b0a7c90 fffff880`0309a651 : fffff8a0`04a28000 fffff8a0`04a28000 fffffa80`0c3147a0 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyResource+0x84
fffff880`0b0a7cc0 fffff880`0309aa03 : fffff8a0`04a28000 fffff8a0`04a28000 00000000`00000001 fffff8a0`0b0858d0 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x95
fffff880`0b0a7d10 fffff880`0309e3e7 : 00000000`00000000 fffff880`0b0a8160 00000000`00000001 fffff880`030653af : dxgkrnl!DXGDEVICE::TerminateAllocations+0x1db
fffff880`0b0a7d60 fffff880`030a0e57 : fffff8a0`04a28000 fffff880`0b0a7e70 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x93
fffff880`0b0a7df0 fffff960`001ff51a : 00000000`fffdb000 fffffa80`0bff7060 00000000`00000020 00000000`72c46168 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`0b0a80b0 fffff800`02e84ed3 : 00000000`00147cac fffff880`0b0a8160 00000000`fffdd000 00000000`72c46168 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`0b0a80e0 00000000`72c6141a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001ac928 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72c6141a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02f0ed7c 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
---------

Possible causes are Memory problems... Drivers...

Continue with the memory tests.

Well, my memory passed 7 times without error at Memtest. I will use Windows Memory test too.

Well, when I bought that laptop, it only had 1 partition. I used different interface of Paragon that I've never used before and it failed at the first time. Could it be the problem?

It is possible that changing partitions caused problems if it did not fully complete the partitioning commands. Have you made any other changes to the system since you first used the laptop? Registry cleaning?

Well, it failed and I did it again. Second time was a success. Also, I tried to change the drive name after that from E to D etc. I haven't cleaned registry until today.

Well, then, should I check HDD?

Well, it's Turkish but I can say there are no errors at disk according to chkdsk.

Google translate can read Turkish if you want to post the logs. I don't mind translating them through that for a disk check. It isn't the most reliable translation for most things, but disk check logs are fairly simple language in all languages.

If you received the equivalent of: "Windows has checked the file system and found no problems", it should be fine, though.

"Windows has checked the file system and found no problems" for all checks. Only one time flagged empty space found in MFT bitmap.

Other than that, I'm really sick of BSoD when everything looks normal

Continue with the memory tests and let us know how they go. Additionally, an underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

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.