Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Microsoft (R) Windows Debugger Version 10.0.15063.468 AMD64
- Copyright (c) Microsoft Corporation. All rights reserved.
- Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170903-1920.dmp]
- 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
- Machine Name:
- Kernel base = 0xfffff802`fa089000 PsLoadedModuleList = 0xfffff802`fa3d55c0
- Debug session time: Sun Sep 3 19:20:08.616 2017 (UTC - 7:00)
- System Uptime: 0 days 0:08:10.419
- Loading Kernel Symbols
- ...............................................................
- ................................................................
- ...................................................
- Loading User Symbols
- Mini Kernel Dump does not contain unloaded driver list
- *******************************************************************************
- * *
- * Bugcheck Analysis *
- * *
- *******************************************************************************
- Use !analyze -v to get detailed debugging information.
- BugCheck 141, {ffffd083ece583a0, fffff805a9fdfd08, 0, f58}
- 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+15fd08 )
- Followup: MachineOwner
- ---------
- 6: kd> !analyze -v
- *******************************************************************************
- * *
- * Bugcheck Analysis *
- * *
- *******************************************************************************
- VIDEO_ENGINE_TIMEOUT_DETECTED (141)
- One of the the display engines failed to respond in timely fashion.
- (This code can never be used for a real bugcheck.)
- Arguments:
- Arg1: ffffd083ece583a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
- Arg2: fffff805a9fdfd08, The pointer into responsible device driver module (e.g owner tag).
- Arg3: 0000000000000000, The secondary driver specific bucketing key.
- Arg4: 0000000000000f58, Optional internal context dependent data.
- Debugging Details:
- ------------------
- DUMP_CLASS: 1
- DUMP_QUALIFIER: 400
- BUILD_VERSION_STRING: 10.0.15063.540 (WinBuild.160101.0800)
- DUMP_TYPE: 2
- BUGCHECK_P1: ffffd083ece583a0
- BUGCHECK_P2: fffff805a9fdfd08
- BUGCHECK_P3: 0
- BUGCHECK_P4: f58
- FAULTING_IP:
- nvlddmkm+15fd08
- fffff805`a9fdfd08 ?? ???
- DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_ENGINE_TIMEOUT
- TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
- CPU_COUNT: 8
- CPU_MHZ: fa8
- CPU_VENDOR: GenuineIntel
- CPU_FAMILY: 6
- CPU_MODEL: 5e
- CPU_STEPPING: 3
- BUGCHECK_STR: 0x141
- PROCESS_NAME: System
- CURRENT_IRQL: 0
- ANALYSIS_SESSION_HOST: DESKTOP-L1HPRBE
- ANALYSIS_SESSION_TIME: 09-03-2017 20:09:42.0339
- ANALYSIS_VERSION: 10.0.15063.468 amd64fre
- STACK_TEXT:
- ffffbe00`188874e0 fffff805`a73978b7 : ffffd083`ece583a0 ffffd083`ece583a0 ffffbe00`18887680 ffffd083`ebb028e0 : watchdog!WdDbgReportRecreate+0x10c
- ffffbe00`18887530 fffff805`ac077470 : 00000000`00000000 00000000`00000000 ffffd083`e7a5b000 ffffd083`e7a5b000 : dxgkrnl!TdrUpdateDbgReport+0xe7
- ffffbe00`18887580 fffff805`ac0fafdd : ffffd083`e7a5b000 00000000`00000000 00000000`00000001 ffffd083`e7a5d001 : dxgmms2!VidSchiResetEngine+0x74c
- ffffbe00`18887890 fffff805`ac0dd0aa : ffffd083`e7a5b000 ffffd083`e7a5d000 00000000`00000000 ffffd083`e7a5d000 : dxgmms2!VidSchiResetEngines+0x99
- ffffbe00`188878d0 fffff805`ac0ba883 : 00000000`00000002 00000000`00007a0f 00000000`003bb952 00000000`00000001 : dxgmms2!VidSchiCheckHwProgress+0x2234a
- ffffbe00`18887940 fffff805`ac0592b6 : ffffd083`e83d0010 ffffd083`e7a5d000 00000000`ffffffff ffffd083`e7a5b000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x303
- ffffbe00`18887a10 fffff805`ac0c5dff : ffffd083`e7aff000 ffffd083`e7a5d000 ffffd083`00000000 ffffd083`e7a5d000 : dxgmms2!VidSchiScheduleCommandToRun+0x3a6
- ffffbe00`18887b00 fffff805`ac0c5dbe : ffffd083`e7a5d500 ffffd083`e7a5d000 00000000`00000080 fffff805`ac0c5d30 : dxgmms2!VidSchiRun_PriorityTable+0x2f
- ffffbe00`18887b50 fffff802`fa165ac7 : ffffbe00`1768b180 fffff802`fa1fa967 00000000`017ae1cc ffffd083`e7a5e7c0 : dxgmms2!VidSchiWorkerThread+0x8e
- ffffbe00`18887b90 fffff802`fa1fa9e6 : ffffbe00`1768b180 ffffd083`e7a5e7c0 fffff802`fa165a80 00000000`00000000 : nt!PspSystemThreadStartup+0x47
- ffffbe00`18887be0 00000000`00000000 : ffffbe00`18888000 ffffbe00`18881000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
- STACK_COMMAND: kb
- THREAD_SHA1_HASH_MOD_FUNC: 38ff1601a490f5ffd3426ba59d83f8532ab501a0
- THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 014ddff9af1a1cfd04f2ad50f1ab130dfda7332e
- THREAD_SHA1_HASH_MOD: d61bf2826c83f42798f71aa711aa4f2cb3225799
- FOLLOWUP_IP:
- nvlddmkm+15fd08
- fffff805`a9fdfd08 ?? ???
- SYMBOL_NAME: nvlddmkm+15fd08
- FOLLOWUP_NAME: MachineOwner
- MODULE_NAME: nvlddmkm
- IMAGE_NAME: nvlddmkm.sys
- DEBUG_FLR_IMAGE_TIMESTAMP: 5938865d
- FAILURE_BUCKET_ID: LKD_0x141_IMAGE_nvlddmkm.sys
- BUCKET_ID: LKD_0x141_IMAGE_nvlddmkm.sys
- PRIMARY_PROBLEM_CLASS: LKD_0x141_IMAGE_nvlddmkm.sys
- TARGET_TIME: 2017-09-04T02:20:08.000Z
- OSBUILD: 15063
- OSSERVICEPACK: 540
- SERVICEPACK_NUMBER: 0
- OS_REVISION: 0
- SUITE_MASK: 272
- PRODUCT_TYPE: 1
- OSPLATFORM_TYPE: x64
- OSNAME: Windows 10
- OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
- OS_LOCALE:
- USER_LCID: 0
- OSBUILD_TIMESTAMP: 2017-07-31 18:23:25
- BUILDDATESTAMP_STR: 160101.0800
- BUILDLAB_STR: WinBuild
- BUILDOSVER_STR: 10.0.15063.540
- ANALYSIS_SESSION_ELAPSED_TIME: 3a3
- ANALYSIS_SOURCE: KM
- FAILURE_ID_HASH_STRING: km:lkd_0x141_image_nvlddmkm.sys
- FAILURE_ID_HASH: {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc}
- Followup: MachineOwner
- ---------
Add Comment
Please, Sign In to add comment
