- Jul 26, 2010
- 23
- 0
- 18,510
Hello all,
wife's laptop has been getting bluescreens. The first few weeks she had it, only used it an hour or 2 every few days; now she's been using it 3-4 every other day or so and it occurs every session once.
From this weekend, we got 1 on saturday after about 2 hours of use (the next 5 or 6 was fine) and sunday after 3-4 hours of use, it happened once and the following 1 or 2 was ok.
Laptop: Asus Strix
Intel i7-7700HQ
GeForce GTX 1050 Ti
solid state HDD (with extra drive for storage)
I used bluescreenview and windbg. checking forums here, reddit, and microsoft site, 1 of the errors meant to upgrade video drivers, which i did. (From a december version, i found a january version). the ntfs error, i found discussions that this is a hardware issue, and another (forgot which now) being a potential memory issue. wanted to post here to get some guidance. The laptop has the asus warranty but i hear asus isn't always the best with issues.
The 2 log files are pasted below:
dump10b9.tmp (saturday)
Microsoft (R) Windows Debugger Version 10.0.15063.468 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\DUMP10b9.tmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff801`5c816000 PsLoadedModuleList = 0xfffff801`5cb625e0
Debug session time: Sat Jul 15 10:01:49.239 2017 (UTC - 4:00)
System Uptime: 2 days 17:56:00.959
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {ffffd78344f1e4a0, fffff80e812c74d8, ffffffffc000009a, 4}
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9674d8 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffd78344f1e4a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80e812c74d8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.15063.483 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.
SYSTEM_PRODUCT_NAME: GL753VE
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: GL753VE.300
BIOS_DATE: 12/20/2016
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: GL753VE
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: ffffd78344f1e4a0
BUGCHECK_P2: fffff80e812c74d8
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
FAULTING_IP:
nvlddmkm+9674d8
fffff80e`812c74d8 48ff258941e7ff jmp qword ptr [nvlddmkm+0x7db668 (fffff80e`8113b668)]
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CPU_COUNT: 8
CPU_MHZ: af8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 42'00000000 (cache) 42'00000000 (init)
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-USHK41P
ANALYSIS_SESSION_TIME: 07-17-2017 11:21:03.0641
ANALYSIS_VERSION: 10.0.15063.468 x86fre
STACK_TEXT:
ffff9101`6d6ef9a8 fffff80e`7d377d28 : 00000000`00000116 ffffd783`44f1e4a0 fffff80e`812c74d8 ffffffff`c000009a : nt!KeBugCheckEx
ffff9101`6d6ef9b0 fffff80e`7d3581e7 : fffff80e`812c74d8 ffffd783`3c944550 00000000`00002000 ffffd783`3c9445e8 : dxgkrnl!TdrBugcheckOnTimeout+0xec
ffff9101`6d6ef9f0 fffff80e`7d3535f8 : ffffd783`3c943010 00000000`04000000 00000000`00000000 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::Reset+0x153
ffff9101`6d6efa20 fffff80e`7d3774c5 : fffff801`5cc00100 ffffd783`4487a040 00000000`00000000 ffffd783`4487a040 : dxgkrnl!DXGADAPTER::Reset+0x430
ffff9101`6d6efaa0 fffff80e`7d377617 : 00000000`00000000 fffff801`5cc0e380 ffffd783`451c1320 fffff801`5c916db0 : dxgkrnl!TdrResetFromTimeout+0x15
ffff9101`6d6efad0 fffff801`5c853ca8 : ffffd783`4487a040 fffff80e`7d3775f0 ffffd783`36292610 ffffd783`451c1320 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff9101`6d6efb00 fffff801`5c8f2ac7 : ffffd783`447abf90 00000000`00000080 ffffd783`348ad500 ffffd783`4487a040 : nt!ExpWorkerThread+0xd8
ffff9101`6d6efb90 fffff801`5c987946 : ffff9101`631e9180 ffffd783`4487a040 fffff801`5c8f2a80 ffffd783`452a7900 : nt!PspSystemThreadStartup+0x47
ffff9101`6d6efbe0 00000000`00000000 : ffff9101`6d6f0000 ffff9101`6d6e9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 56a150c818aff348d17e35fc9e822916b6c0190b
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2b8e36420ad492fac55ee6ac7de8c9381dcb67f0
THREAD_SHA1_HASH_MOD: 3225689ea8bf23dca00cdfd517975e0703e07271
FOLLOWUP_IP:
nvlddmkm+9674d8
fffff80e`812c74d8 48ff258941e7ff jmp qword ptr [nvlddmkm+0x7db668 (fffff80e`8113b668)]
FAULT_INSTR_CODE: 8925ff48
SYMBOL_NAME: nvlddmkm+9674d8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5865017a
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
PRIMARY_PROBLEM_CLASS: 0x116_IMAGE_nvlddmkm.sys
TARGET_TIME: 2017-07-15T14:01:49.000Z
OSBUILD: 15063
OSSERVICEPACK: 483
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-07-07 02:06:35
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.15063.483
ANALYSIS_SESSION_ELAPSED_TIME: 7c1
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x116_image_nvlddmkm.sys
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
dump180c.tmp (sunday)
Microsoft (R) Windows Debugger Version 10.0.15063.468 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\DUMP180c.tmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff802`17e92000 PsLoadedModuleList = 0xfffff802`181de5e0
Debug session time: Sun Jul 16 16:56:31.138 2017 (UTC - 4:00)
System Uptime: 1 days 6:54:21.243
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80217f3a6d8, ffffbb80a066f3f8, ffffbb80a066ec40}
Probably caused by : ntkrnlmp.exe ( nt!CcUninitializeCacheMap+a8 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80217f3a6d8, The address that the exception occurred at
Arg3: ffffbb80a066f3f8, Exception Record Address
Arg4: ffffbb80a066ec40, Context Record Address
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.15063.483 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.
SYSTEM_PRODUCT_NAME: GL753VE
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: GL753VE.300
BIOS_DATE: 12/20/2016
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: GL753VE
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80217f3a6d8
BUGCHECK_P3: ffffbb80a066f3f8
BUGCHECK_P4: ffffbb80a066ec40
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
FAULTING_IP:
nt!CcUninitializeCacheMap+a8
fffff802`17f3a6d8 48394208 cmp qword ptr [rdx+8],rax
EXCEPTION_RECORD: ffffbb80a066f3f8 -- (.exr 0xffffbb80a066f3f8)
ExceptionAddress: fffff80217f3a6d8 (nt!CcUninitializeCacheMap+0x00000000000000a8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffbb80a066ec40 -- (.cxr 0xffffbb80a066ec40)
rax=ffff868b6d2c8938 rbx=ffff868b6d2c8760 rcx=ffff868b6d2c8840
rdx=00ff868b6d2c8840 rsi=0000000000000000 rdi=ffff868b6d2c88d8
rip=fffff80217f3a6d8 rsp=ffffbb80a066f630 rbp=ffff868b6d280910
r8=0000000000000000 r9=0000000000000000 r10=7ffffffffffffffc
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=ffffa90fb6f4bb00
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!CcUninitializeCacheMap+0xa8:
fffff802`17f3a6d8 48394208 cmp qword ptr [rdx+8],rax ds:002b:00ff868b`6d2c8848=????????????????
Resetting default scope
CPU_COUNT: 8
CPU_MHZ: af8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 42'00000000 (cache) 42'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
FOLLOWUP_IP:
nt!CcUninitializeCacheMap+a8
fffff802`17f3a6d8 48394208 cmp qword ptr [rdx+8],rax
BUGCHECK_STR: AV
READ_ADDRESS: fffff80218273358: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffffffffffffff
ANALYSIS_SESSION_HOST: DESKTOP-USHK41P
ANALYSIS_SESSION_TIME: 07-17-2017 11:22:51.0944
ANALYSIS_VERSION: 10.0.15063.468 x86fre
LAST_CONTROL_TRANSFER: from fffff80a5c80ec26 to fffff80217f3a6d8
STACK_TEXT:
ffffbb80`a066f630 fffff80a`5c80ec26 : 00000000`00000000 ffffa90f`b6f4ba00 ffff868b`6d280910 00000000`00000000 : nt!CcUninitializeCacheMap+0xa8
ffffbb80`a066f6c0 fffff80a`5c821e18 : ffffa90f`b6f4ba00 ffffa90f`b6f4ba00 00000000`00000000 ffffa90f`b6f4bb40 : NTFS!NtfsDeleteInternalAttributeStream+0xde
ffffbb80`a066f700 fffff80a`5c7682b5 : ffffa90f`b6f4ba00 ffffa90f`b6f4bb40 00000000`00000000 ffffa90f`b6f4bb40 : NTFS!NtfsRemoveScb+0x118
ffffbb80`a066f750 fffff80a`5c76880f : ffff868b`76cfadc8 fffff80a`5c86d1d0 ffffbb80`a066f901 ffffa90f`b6f4ba00 : NTFS!NtfsPrepareFcbForRemoval+0x75
ffffbb80`a066f790 fffff80a`5c821b3b : ffff868b`76cfadc8 ffff868b`63c4a180 ffffa90f`b6f7e7d0 ffffa90f`b6f7eca8 : NTFS!NtfsTeardownFromLcb+0x2df
ffffbb80`a066f830 fffff80a`5c7691d3 : ffff868b`76cfadc8 ffffbb80`a066f932 00000000`00000000 ffffa90f`b6f7e7d0 : NTFS!NtfsTeardownStructures+0xdb
ffffbb80`a066f8b0 fffff80a`5c82464c : ffffbb80`a066fa48 ffffa90f`b6f7e7d0 ffff868b`76cfadc8 ffffa90f`b6f7e7d0 : NTFS!NtfsDecrementCloseCounts+0xd3
ffffbb80`a066f8f0 fffff80a`5c86d3ad : ffff868b`76cfadc8 ffffa90f`b6f7e910 ffffa90f`b6f7e7d0 ffff868b`63c4a180 : NTFS!NtfsCommonClose+0x3fc
ffffbb80`a066f9c0 fffff802`17ecfca8 : 00000000`00000d00 ffff868b`72236040 fffff802`182104e0 ffff868b`77e65830 : NTFS!NtfsFspCloseInternal+0x1c9
ffffbb80`a066fb00 fffff802`17f6eac7 : 00000000`00000000 00000000`00000080 ffff868b`63cdc500 ffff868b`72236040 : nt!ExpWorkerThread+0xd8
ffffbb80`a066fb90 fffff802`18003946 : ffffbb80`9acac180 ffff868b`72236040 fffff802`17f6ea80 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffbb80`a066fbe0 00000000`00000000 : ffffbb80`a0670000 ffffbb80`a0669000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
THREAD_SHA1_HASH_MOD_FUNC: e14d4606622fe6d2f12849981be71257adfaa6c0
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3826b10b5261cd62cf04a9569f03079884e64ee8
THREAD_SHA1_HASH_MOD: 9f1091b7bd436ce311b408fee80c3c2f82aa7ac6
FAULT_INSTR_CODE: 8423948
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CcUninitializeCacheMap+a8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 595f24eb
IMAGE_VERSION: 10.0.15063.483
STACK_COMMAND: .cxr 0xffffbb80a066ec40 ; kb
BUCKET_ID_FUNC_OFFSET: a8
FAILURE_BUCKET_ID: AV_nt!CcUninitializeCacheMap
BUCKET_ID: AV_nt!CcUninitializeCacheMap
PRIMARY_PROBLEM_CLASS: AV_nt!CcUninitializeCacheMap
TARGET_TIME: 2017-07-16T20:56:31.000Z
OSBUILD: 15063
OSSERVICEPACK: 483
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-07-07 02:06:35
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.15063.483
ANALYSIS_SESSION_ELAPSED_TIME: 70a
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_nt!ccuninitializecachemap
FAILURE_ID_HASH: {5e333050-db44-aabc-a308-fae0adf1591a}
Followup: MachineOwner
---------
Some images of windbg
https://ibb.co/giZBfF
https://ibb.co/n8qj0F
Thanks for any help
Regards,
Sanjay
wife's laptop has been getting bluescreens. The first few weeks she had it, only used it an hour or 2 every few days; now she's been using it 3-4 every other day or so and it occurs every session once.
From this weekend, we got 1 on saturday after about 2 hours of use (the next 5 or 6 was fine) and sunday after 3-4 hours of use, it happened once and the following 1 or 2 was ok.
Laptop: Asus Strix
Intel i7-7700HQ
GeForce GTX 1050 Ti
solid state HDD (with extra drive for storage)
I used bluescreenview and windbg. checking forums here, reddit, and microsoft site, 1 of the errors meant to upgrade video drivers, which i did. (From a december version, i found a january version). the ntfs error, i found discussions that this is a hardware issue, and another (forgot which now) being a potential memory issue. wanted to post here to get some guidance. The laptop has the asus warranty but i hear asus isn't always the best with issues.
The 2 log files are pasted below:
dump10b9.tmp (saturday)
Microsoft (R) Windows Debugger Version 10.0.15063.468 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\DUMP10b9.tmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff801`5c816000 PsLoadedModuleList = 0xfffff801`5cb625e0
Debug session time: Sat Jul 15 10:01:49.239 2017 (UTC - 4:00)
System Uptime: 2 days 17:56:00.959
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {ffffd78344f1e4a0, fffff80e812c74d8, ffffffffc000009a, 4}
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9674d8 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffd78344f1e4a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80e812c74d8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.15063.483 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.
SYSTEM_PRODUCT_NAME: GL753VE
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: GL753VE.300
BIOS_DATE: 12/20/2016
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: GL753VE
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: ffffd78344f1e4a0
BUGCHECK_P2: fffff80e812c74d8
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
FAULTING_IP:
nvlddmkm+9674d8
fffff80e`812c74d8 48ff258941e7ff jmp qword ptr [nvlddmkm+0x7db668 (fffff80e`8113b668)]
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CPU_COUNT: 8
CPU_MHZ: af8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 42'00000000 (cache) 42'00000000 (init)
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-USHK41P
ANALYSIS_SESSION_TIME: 07-17-2017 11:21:03.0641
ANALYSIS_VERSION: 10.0.15063.468 x86fre
STACK_TEXT:
ffff9101`6d6ef9a8 fffff80e`7d377d28 : 00000000`00000116 ffffd783`44f1e4a0 fffff80e`812c74d8 ffffffff`c000009a : nt!KeBugCheckEx
ffff9101`6d6ef9b0 fffff80e`7d3581e7 : fffff80e`812c74d8 ffffd783`3c944550 00000000`00002000 ffffd783`3c9445e8 : dxgkrnl!TdrBugcheckOnTimeout+0xec
ffff9101`6d6ef9f0 fffff80e`7d3535f8 : ffffd783`3c943010 00000000`04000000 00000000`00000000 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::Reset+0x153
ffff9101`6d6efa20 fffff80e`7d3774c5 : fffff801`5cc00100 ffffd783`4487a040 00000000`00000000 ffffd783`4487a040 : dxgkrnl!DXGADAPTER::Reset+0x430
ffff9101`6d6efaa0 fffff80e`7d377617 : 00000000`00000000 fffff801`5cc0e380 ffffd783`451c1320 fffff801`5c916db0 : dxgkrnl!TdrResetFromTimeout+0x15
ffff9101`6d6efad0 fffff801`5c853ca8 : ffffd783`4487a040 fffff80e`7d3775f0 ffffd783`36292610 ffffd783`451c1320 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff9101`6d6efb00 fffff801`5c8f2ac7 : ffffd783`447abf90 00000000`00000080 ffffd783`348ad500 ffffd783`4487a040 : nt!ExpWorkerThread+0xd8
ffff9101`6d6efb90 fffff801`5c987946 : ffff9101`631e9180 ffffd783`4487a040 fffff801`5c8f2a80 ffffd783`452a7900 : nt!PspSystemThreadStartup+0x47
ffff9101`6d6efbe0 00000000`00000000 : ffff9101`6d6f0000 ffff9101`6d6e9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 56a150c818aff348d17e35fc9e822916b6c0190b
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2b8e36420ad492fac55ee6ac7de8c9381dcb67f0
THREAD_SHA1_HASH_MOD: 3225689ea8bf23dca00cdfd517975e0703e07271
FOLLOWUP_IP:
nvlddmkm+9674d8
fffff80e`812c74d8 48ff258941e7ff jmp qword ptr [nvlddmkm+0x7db668 (fffff80e`8113b668)]
FAULT_INSTR_CODE: 8925ff48
SYMBOL_NAME: nvlddmkm+9674d8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5865017a
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
PRIMARY_PROBLEM_CLASS: 0x116_IMAGE_nvlddmkm.sys
TARGET_TIME: 2017-07-15T14:01:49.000Z
OSBUILD: 15063
OSSERVICEPACK: 483
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-07-07 02:06:35
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.15063.483
ANALYSIS_SESSION_ELAPSED_TIME: 7c1
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x116_image_nvlddmkm.sys
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
dump180c.tmp (sunday)
Microsoft (R) Windows Debugger Version 10.0.15063.468 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\DUMP180c.tmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff802`17e92000 PsLoadedModuleList = 0xfffff802`181de5e0
Debug session time: Sun Jul 16 16:56:31.138 2017 (UTC - 4:00)
System Uptime: 1 days 6:54:21.243
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80217f3a6d8, ffffbb80a066f3f8, ffffbb80a066ec40}
Probably caused by : ntkrnlmp.exe ( nt!CcUninitializeCacheMap+a8 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80217f3a6d8, The address that the exception occurred at
Arg3: ffffbb80a066f3f8, Exception Record Address
Arg4: ffffbb80a066ec40, Context Record Address
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.15063.483 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.
SYSTEM_PRODUCT_NAME: GL753VE
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: GL753VE.300
BIOS_DATE: 12/20/2016
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: GL753VE
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80217f3a6d8
BUGCHECK_P3: ffffbb80a066f3f8
BUGCHECK_P4: ffffbb80a066ec40
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
FAULTING_IP:
nt!CcUninitializeCacheMap+a8
fffff802`17f3a6d8 48394208 cmp qword ptr [rdx+8],rax
EXCEPTION_RECORD: ffffbb80a066f3f8 -- (.exr 0xffffbb80a066f3f8)
ExceptionAddress: fffff80217f3a6d8 (nt!CcUninitializeCacheMap+0x00000000000000a8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffbb80a066ec40 -- (.cxr 0xffffbb80a066ec40)
rax=ffff868b6d2c8938 rbx=ffff868b6d2c8760 rcx=ffff868b6d2c8840
rdx=00ff868b6d2c8840 rsi=0000000000000000 rdi=ffff868b6d2c88d8
rip=fffff80217f3a6d8 rsp=ffffbb80a066f630 rbp=ffff868b6d280910
r8=0000000000000000 r9=0000000000000000 r10=7ffffffffffffffc
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=ffffa90fb6f4bb00
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!CcUninitializeCacheMap+0xa8:
fffff802`17f3a6d8 48394208 cmp qword ptr [rdx+8],rax ds:002b:00ff868b`6d2c8848=????????????????
Resetting default scope
CPU_COUNT: 8
CPU_MHZ: af8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 42'00000000 (cache) 42'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
FOLLOWUP_IP:
nt!CcUninitializeCacheMap+a8
fffff802`17f3a6d8 48394208 cmp qword ptr [rdx+8],rax
BUGCHECK_STR: AV
READ_ADDRESS: fffff80218273358: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffffffffffffff
ANALYSIS_SESSION_HOST: DESKTOP-USHK41P
ANALYSIS_SESSION_TIME: 07-17-2017 11:22:51.0944
ANALYSIS_VERSION: 10.0.15063.468 x86fre
LAST_CONTROL_TRANSFER: from fffff80a5c80ec26 to fffff80217f3a6d8
STACK_TEXT:
ffffbb80`a066f630 fffff80a`5c80ec26 : 00000000`00000000 ffffa90f`b6f4ba00 ffff868b`6d280910 00000000`00000000 : nt!CcUninitializeCacheMap+0xa8
ffffbb80`a066f6c0 fffff80a`5c821e18 : ffffa90f`b6f4ba00 ffffa90f`b6f4ba00 00000000`00000000 ffffa90f`b6f4bb40 : NTFS!NtfsDeleteInternalAttributeStream+0xde
ffffbb80`a066f700 fffff80a`5c7682b5 : ffffa90f`b6f4ba00 ffffa90f`b6f4bb40 00000000`00000000 ffffa90f`b6f4bb40 : NTFS!NtfsRemoveScb+0x118
ffffbb80`a066f750 fffff80a`5c76880f : ffff868b`76cfadc8 fffff80a`5c86d1d0 ffffbb80`a066f901 ffffa90f`b6f4ba00 : NTFS!NtfsPrepareFcbForRemoval+0x75
ffffbb80`a066f790 fffff80a`5c821b3b : ffff868b`76cfadc8 ffff868b`63c4a180 ffffa90f`b6f7e7d0 ffffa90f`b6f7eca8 : NTFS!NtfsTeardownFromLcb+0x2df
ffffbb80`a066f830 fffff80a`5c7691d3 : ffff868b`76cfadc8 ffffbb80`a066f932 00000000`00000000 ffffa90f`b6f7e7d0 : NTFS!NtfsTeardownStructures+0xdb
ffffbb80`a066f8b0 fffff80a`5c82464c : ffffbb80`a066fa48 ffffa90f`b6f7e7d0 ffff868b`76cfadc8 ffffa90f`b6f7e7d0 : NTFS!NtfsDecrementCloseCounts+0xd3
ffffbb80`a066f8f0 fffff80a`5c86d3ad : ffff868b`76cfadc8 ffffa90f`b6f7e910 ffffa90f`b6f7e7d0 ffff868b`63c4a180 : NTFS!NtfsCommonClose+0x3fc
ffffbb80`a066f9c0 fffff802`17ecfca8 : 00000000`00000d00 ffff868b`72236040 fffff802`182104e0 ffff868b`77e65830 : NTFS!NtfsFspCloseInternal+0x1c9
ffffbb80`a066fb00 fffff802`17f6eac7 : 00000000`00000000 00000000`00000080 ffff868b`63cdc500 ffff868b`72236040 : nt!ExpWorkerThread+0xd8
ffffbb80`a066fb90 fffff802`18003946 : ffffbb80`9acac180 ffff868b`72236040 fffff802`17f6ea80 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffbb80`a066fbe0 00000000`00000000 : ffffbb80`a0670000 ffffbb80`a0669000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
THREAD_SHA1_HASH_MOD_FUNC: e14d4606622fe6d2f12849981be71257adfaa6c0
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3826b10b5261cd62cf04a9569f03079884e64ee8
THREAD_SHA1_HASH_MOD: 9f1091b7bd436ce311b408fee80c3c2f82aa7ac6
FAULT_INSTR_CODE: 8423948
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CcUninitializeCacheMap+a8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 595f24eb
IMAGE_VERSION: 10.0.15063.483
STACK_COMMAND: .cxr 0xffffbb80a066ec40 ; kb
BUCKET_ID_FUNC_OFFSET: a8
FAILURE_BUCKET_ID: AV_nt!CcUninitializeCacheMap
BUCKET_ID: AV_nt!CcUninitializeCacheMap
PRIMARY_PROBLEM_CLASS: AV_nt!CcUninitializeCacheMap
TARGET_TIME: 2017-07-16T20:56:31.000Z
OSBUILD: 15063
OSSERVICEPACK: 483
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-07-07 02:06:35
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.15063.483
ANALYSIS_SESSION_ELAPSED_TIME: 70a
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_nt!ccuninitializecachemap
FAILURE_ID_HASH: {5e333050-db44-aabc-a308-fae0adf1591a}
Followup: MachineOwner
---------
Some images of windbg
https://ibb.co/giZBfF
https://ibb.co/n8qj0F
Thanks for any help
Regards,
Sanjay
Facebook
Twitter
Instagram