PFN List Corrupt BSoD

[Kurama]

Windows 7:

x64
Original OEM OS

Laptop is 2 months old
I recovered laptop to factory default to see whether BSoD will appear again or not

 

[writhziden]

Are you still having crashes after the recovery?

[list=1]


Loading Dump File [J:\BSODDmpFiles\Kurama\Windows_NT6_BSOD_jcgriff2\011612-32619-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*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 Jan 15 20:11:14.165 2012 (UTC - 7:00)
System Uptime: 0 days 0:09:06.040
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007bd34e0, fffff88005a428b0, ffffffffc0000001, 3}

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+298b0 )

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

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8007bd34e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005a428b0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.

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


FAULTING_IP: 
igdkmd64+298b0
fffff880`05a428b0 48895c2418      mov     qword ptr [rsp+18h],rbx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03761d68 fffff880`10112000 : 00000000`00000116 fffffa80`07bd34e0 fffff880`05a428b0 ffffffff`c0000001 : nt!KeBugCheckEx
fffff880`03761d70 fffff880`100e5569 : fffff880`05a428b0 fffffa80`0c1c7000 00000000`00000000 fffffa80`0c1c1010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03761db0 fffff880`10111dad : fffffa80`07bd34e0 fffffa80`07bd34e0 fffffa80`07bd34e0 fffffa80`0c1c1010 : dxgkrnl!DXGADAPTER::PrepareToReset+0x109
fffff880`03761df0 fffff880`101b8f07 : fffffa80`07bd34e0 00000000`00000000 fffffa80`0c1c2010 fffffa80`0c1c1010 : dxgkrnl!TdrIsRecoveryRequired+0x245
fffff880`03761e20 fffff880`101e6d5a : 00000001`ffffffff 00000000`000087ba fffff880`03761f80 fffffa80`0c1e2270 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03761f00 fffff880`101e2df2 : fffffa80`0c1e1000 ffffffff`feced300 fffffa80`0c1e9230 fffff880`101cd92f : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`03761f40 fffff880`101cc770 : 00000000`ffffda01 00000000`000000d2 fffffa80`0c1e9230 fffffa80`0c1f2f60 : dxgmms1!VidSchiSendToExecutionQueueWithWait+0x106
fffff880`03762040 fffff880`101cede5 : fffffa80`000000b7 fffff8a0`04105a40 00000000`00000000 fffff880`101ca500 : dxgmms1!VIDMM_GLOBAL::FlushPagingBufferInternal+0x40c
fffff880`03762190 fffff880`101dbebb : fffff8a0`030e38a8 fffff8a0`03017678 fffff8a0`03017600 fffffa80`0c1f2f60 : dxgmms1!VIDMM_GLOBAL::PurgeAllocation+0x12d
fffff880`037621e0 fffff880`101c860b : 00000000`00000000 00000000`c0000000 fffff8a0`03f77e50 00000000`00000000 : dxgmms1!VIDMM_SEGMENT::PurgeContent+0x133
fffff880`03762240 fffff880`101c83b3 : fffff880`03762500 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ProcessSystemCommand+0xc7
fffff880`037622d0 fffff880`101e2231 : 00000000`00000000 00000001`00000000 fffffa80`0c1e0d50 fffffa80`0c1e2ec8 : dxgmms1!VidMmiProcessSystemCommand+0x47
fffff880`03762300 fffff880`101e13bc : fffff880`03762460 00000000`00000000 fffffa80`0c1e2ec0 00000000`00000001 : dxgmms1!VidSchiSubmitSystemCommand+0x39
fffff880`03762330 fffff880`101b377a : 00000000`00000000 fffffa80`0c1e0d50 fffffa80`0c1e2ec0 fffffa80`0c1e2ec0 : dxgmms1!VidSchiSubmitQueueCommand+0x74
fffff880`03762360 fffff880`101e3927 : fffffa80`0c1c0660 fffffa80`0c1dd000 fffffa80`0c1e2ec0 00000000`00000000 : dxgmms1!VidSchiSubmitQueueCommandDirect+0x1e6
fffff880`037623f0 fffff880`101c84b9 : fffffa80`00000001 fffffa80`0c1c1010 fffffa80`0c1e9000 fffff880`03762500 : dxgmms1!VidSchiSubmitCommandPacketToQueue+0x15f
fffff880`03762460 fffff880`101aa5c6 : 00000000`00000001 fffff880`100e65de fffffa80`0c1c7000 fffffa80`0aded340 : dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait+0xf9
fffff880`037624d0 fffff880`100e67a1 : fffffa80`0c1c7000 fffffa80`0c1c7000 fffffa80`0aded340 fffffa80`0adf7860 : dxgmms1!VidMmPurgeAllSegments+0xe2
fffff880`03762540 fffff880`100e5f48 : 00000000`ffffeea7 fffffa80`0c1c7000 fffffa80`0aded340 fffffa80`0adf7860 : dxgkrnl!DXGADAPTER::PurgeSegments+0x95
fffff880`03762570 fffff880`1013d79a : fffffa80`0aded490 fffffa80`0aded490 fffffa80`0aded340 fffffa80`0adf7860 : dxgkrnl!DXGADAPTER::Stop+0xa8
fffff880`037625e0 fffff880`1013b272 : fffffa80`0aded340 fffffa80`0aded490 fffffa80`0c962c00 00000000`00000000 : dxgkrnl!DpiFdoStopAdapter+0x12a
fffff880`03762670 fffff880`1013aa58 : fffff8a0`00000000 fffffa80`0c962c00 fffffa80`0c962c00 fffffa80`0aded340 : dxgkrnl!DpiFdoHandleStopDevice+0x4e
fffff880`037626a0 fffff880`101397ad : 00000000`00000002 fffffa80`0c962c00 fffffa80`0aded490 fffff8a0`032c4880 : dxgkrnl!DpiFdoHandleRemoveDevice+0x50
fffff880`037626f0 fffff880`10136eb0 : 00000000`00000000 fffffa80`0aded340 00000000`00000000 fffffa80`0c962c00 : dxgkrnl!DpiFdoDispatchPnp+0x51
fffff880`03762730 fffff800`03141af9 : fffff8a0`032c4880 fffffa80`0aded340 00000000`c00000bb fffff880`03762838 : dxgkrnl!DpiDispatchPnp+0xc8
fffff880`03762780 fffff800`032bff71 : fffffa80`07d28a10 00000000`00000000 fffffa80`080eed90 00000000`00000801 : nt!IopSynchronousCall+0xc5
fffff880`037627f0 fffff800`02fd3133 : fffff8a0`040fb100 fffff8a0`040fb100 00000000`00000015 00000000`00000000 : nt!IopRemoveDevice+0x101
fffff880`037628b0 fffff800`032bfac4 : fffffa80`080eed90 00000000`00000000 00000000`00000002 fffffa80`07d28a10 : nt!PnpRemoveLockedDeviceNode+0x1a3
fffff880`03762900 fffff800`032bfbd0 : 00000000`00000000 fffff8a0`025f7001 fffff8a0`04b7f630 ffffe462`31223fd0 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`03762930 fffff800`03350a34 : 00000000`00000002 00000000`00000000 fffffa80`080eed90 fffff8a0`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`037629a0 fffff800`0335108c : fffff880`00000000 fffffa80`07eb4800 fffffa80`0738d600 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xc34
fffff880`03762ae0 fffff800`0323a34e : 00000000`00000000 fffffa80`07eb48d0 fffff8a0`0b5e4ef0 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`03762b10 fffff800`02ee1001 : fffff800`03140998 fffff8a0`025f7010 fffff800`030772b8 fffffa80`0738d680 : nt! ?? ::NNGAKEGL::`string'+0x5b3cb
fffff880`03762b70 fffff800`03171fee : 00000000`00000000 fffffa80`0738d680 00000000`00000080 fffffa80`07321990 : nt!ExpWorkerThread+0x111
fffff880`03762c00 fffff800`02ec85e6 : fffff880`03589180 fffffa80`0738d680 fffff880`035940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03762c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
igdkmd64+298b0
fffff880`05a428b0 48895c2418      mov     qword ptr [rsp+18h],rbx

SYMBOL_NAME:  igdkmd64+298b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4df25f60

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_igdkmd64.sys

BUCKET_ID:  X64_0x116_IMAGE_igdkmd64.sys

Followup: MachineOwner
---------
[*]
Loading Dump File [J:\BSODDmpFiles\Kurama\Windows_NT6_BSOD_jcgriff2\011612-23571-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*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`02e56000 PsLoadedModuleList = 0xfffff800`0309b670
Debug session time: Sun Jan 15 20:01:46.036 2012 (UTC - 7:00)
System Uptime: 0 days 4:38:56.911
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 113ca4, 2, 113bf9}

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

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

3: 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: 0000000000113ca4, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000113bf9, 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 fffff80002f5bd7c to fffff80002ed2c40

STACK_TEXT:  
fffff880`0b00a4a8 fffff800`02f5bd7c : 00000000`0000004e 00000000`00000099 00000000`00113ca4 00000000`00000002 : nt!KeBugCheckEx
fffff880`0b00a4b0 fffff800`02e7a3ce : 00000000`00000000 fffff680`001a1068 00000000`00000000 00000000`00000000 : nt!MiBadShareCount+0x4c
fffff880`0b00a4f0 fffff800`02f04bb7 : 00000000`00000000 fffff680`001a13f8 fffffa80`0ce52b30 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x33094
fffff880`0b00a6a0 fffff800`02ec00ff : fffffa80`00000000 00000000`3427ffff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`0b00a860 fffff800`02ed1ed3 : ffffffff`ffffffff fffff8a0`0f566538 fffff8a0`0f566560 fffff8a0`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0b00a960 fffff800`02ece470 : fffff880`101e74b2 fffff8a0`0e527360 fffffa80`0ce52b30 fffffa80`0d3e1670 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0b00aaf8 fffff880`101e74b2 : fffff8a0`0e527360 fffffa80`0ce52b30 fffffa80`0d3e1670 fffff8a0`0f566530 : nt!KiServiceLinkage
fffff880`0b00ab00 fffff880`101d2b5a : 00000000`35d00000 fffff8a0`0cd6a7e0 00000000`00000001 fffff8a0`1003d180 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`0b00ab30 fffff880`101cd523 : fffffa80`0d699900 00000000`00000001 fffff8a0`0e527360 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112
fffff880`0b00abe0 fffff880`101b3ecc : fffffa80`00000000 fffff880`00000000 fffffa80`0c25a878 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0b00acb0 fffff880`100f5ccc : fffff8a0`0de2c670 fffff8a0`0cd99000 fffff8a0`0cd99000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0b00ace0 fffff880`100f63ac : fffff8a0`0dca8790 fffff8a0`0dca8790 00000000`00000001 fffff8a0`0cd99000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0b00add0 fffff880`100f5651 : fffff8a0`0cd99000 fffff8a0`0cd99000 fffff8a0`0e297760 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyResource+0x84
fffff880`0b00ae00 fffff880`100f58e1 : fffff8a0`0cd99000 fffff8a0`0cd99000 00000000`00000001 fffff8a0`0fb475d0 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x95
fffff880`0b00ae50 fffff880`100f93e7 : 00000000`00000000 fffff880`0b00b2a0 fffffa80`0c24c000 fffff880`100c03af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`0b00aea0 fffff880`100fbe57 : fffff8a0`0cd99000 fffff880`0b00afb0 00000000`fffdb001 fffff880`100f62c1 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x93
fffff880`0b00af30 fffff960`0024f51a : 00000000`0010c5e0 fffffa80`0d259b60 00000000`00000020 00000000`74d96168 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`0b00b1f0 fffff800`02ed1ed3 : 00000000`0036b650 fffff880`0b00b2a0 00000000`0f253980 00000000`0000027f : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`0b00b220 00000000`74db141a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0010c5d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74db141a


STACK_COMMAND:  kb

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


[/list]

1. The first crash shows that your display card or display card driver did not respond to the system in a timely manner.
2. Possible causes are Memory problems... Drivers...

Thanks to Dave76 for help understanding possible causes.

We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• If you are overclocking anything, please stop.
  
  
  
• Closely follow the first three posts of http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html and proceed through each step. Let us know if you need further help.
  
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
  
• Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net and |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card.

 

[Kurama]

Yeah, I still having crashes. And today I forgot "verifier" opened and it give BSoD when I tried to install Logitech Setpoint. It appears randomly when verifier isn't active.

 

[writhziden]

Run through the steps I provided, and post back your results with each. We'll help you narrow down the problem.

 

[Kurama]

Well, my parents don't know that I bought a new laptop so I don't know when I will start. But I will do it eventually so I can send results

 

[Kurama]

I use BlueScreenView and it says it is because of ntoskrnl.exe mostly

 

[writhziden]

BlueScreenView often blames system files because they are running all the time. The cause is something else, otherwise Windows would not run at all.

 

[Kurama]

Well it isn't anything to do with INTEL and NVIDIA graphic cards. I used stress tests but nothing happened.

 

[writhziden]

What happened with Memtest86+ and the Windows memory diagnostic tool?

 

[Kurama]

Well, I will rum Memtest before I go to sleep. Do it continue continueously or stop after specific number of passes? Well, I have BSoD again. Here are the files.

 

[writhziden]

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.

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.

 

[Kurama]

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?

 

[writhziden]

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?

 

[Kurama]

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?

 

[writhziden]

Run http://www.sevenforums.com/tutorials/433-disk-check.html with both boxes checked. Post back your logs following http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html



Also, in reference to registry cleaning...

Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.

In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to http://www.sevenforums.com/tutorial...ws-7-a.html?filter[2]=Performance Maintenance.



If you created a backup of the registry prior to cleaning, revert to that. If not, see if you have a restore point you can revert to through http://www.sevenforums.com/tutorials/700-system-restore.html.

 

[Kurama]

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

 

[writhziden]

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.

 

[Kurama]

"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

 

[writhziden]

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 http://www.sevenforums.com/tutorials/700-system-restore.html 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.​

 

[Kurama]

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.