LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys


Joined
Feb 19, 2016
Messages
49
Reaction score
0
So today i checked event viewer and i saw entry: LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys and of course minidump file in Windows/Watchdog...


Log:

Loading Dump File [C:\Users\Me\SysnativeBSODApps\WATCHDOG-20161002-2050.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.206.amd64fre.rs1_release.160915-0644
Machine Name:
Kernel base = 0xfffff802`ca68b000 PsLoadedModuleList = 0xfffff802`ca98f080
Debug session time: Sun Oct 2 19:50:34.805 2016 (UTC + 1:00)
System Uptime: 0 days 0:36:24.487
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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 141, {ffffce0e028194a0, fffff803235e9164, 0, 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+159164 )

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

2: kd> !analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q
*******************************************************************************
* *
* 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: ffffce0e028194a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff803235e9164, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000004, Optional internal context dependent data.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 14393.206.amd64fre.rs1_release.160915-0644

DUMP_TYPE: 2

BUGCHECK_P1: ffffce0e028194a0

BUGCHECK_P2: fffff803235e9164

BUGCHECK_P3: 0

BUGCHECK_P4: 4

FAULTING_IP:
nvlddmkm+159164
fffff803`235e9164 ?? ???

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: BETENOIR

ANALYSIS_SESSION_TIME: 10-08-2016 05:54:36.0644

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:
ffffa681`090cf4f0 fffff803`2058abac : ffffce0e`028194a0 ffffce0e`028194a0 ffffa681`090cf690 ffffce0e`003cf490 : watchdog!WdDbgReportRecreate+0x10c
ffffa681`090cf540 fffff803`232a4c74 : 00000000`00000000 00000000`00000000 ffffce0e`028194a0 ffffce0d`fedaa000 : dxgkrnl!TdrUpdateDbgReport+0xec
ffffa681`090cf590 fffff803`2331ecf9 : ffffce0d`fedaa000 00000000`00000000 00000000`00000001 ffffce0d`fedac001 : dxgmms2!VidSchiResetEngine+0x74c
ffffa681`090cf880 fffff803`233034ea : ffffce0d`fedaa000 00000000`00000002 00000000`00000000 ffffce0d`fedac000 : dxgmms2!VidSchiResetEngines+0x99
ffffa681`090cf8c0 fffff803`232e21f7 : 00000000`00000002 00000000`0002219b 00000000`003bb955 00000000`00000001 : dxgmms2!VidSchiCheckHwProgress+0x20daa
ffffa681`090cf930 fffff803`2328a4b4 : ffffce0e`01e4d010 ffffce0d`fedac000 ffffce0e`01e4d018 00000000`00000002 : dxgmms2!VidSchiWaitForSchedulerEvents+0x337
ffffa681`090cf9f0 fffff803`232ee09f : ffffce0d`feebc200 ffffa681`090cfb50 ffffce0d`feebc200 ffffce0d`00000000 : dxgmms2!VidSchiScheduleCommandToRun+0x3d4
ffffa681`090cfb00 fffff803`232ee060 : ffffce0d`fedac500 ffffce0d`fedac000 00000000`00000080 fffff803`232edfe0 : dxgmms2!VidSchiRun_PriorityTable+0x2f
ffffa681`090cfb50 fffff802`ca75d3f5 : fffff802`ca9cc180 fffff802`ca7da69f 00000000`00f1ff88 ffffce0d`fedd1800 : dxgmms2!VidSchiWorkerThread+0x80
ffffa681`090cfb90 fffff802`ca7da776 : fffff802`ca9cc180 ffffce0d`fedd1800 fffff802`ca75d3b4 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffa681`090cfbe0 00000000`00000000 : ffffa681`090d0000 ffffa681`090c9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 38ff1601a490f5ffd3426ba59d83f8532ab501a0

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e36952b8f9a66efc8372dc3187985c40ea22c2b2

THREAD_SHA1_HASH_MOD: d61bf2826c83f42798f71aa711aa4f2cb3225799

FOLLOWUP_IP:
nvlddmkm+159164
fffff803`235e9164 ?? ???

SYMBOL_NAME: nvlddmkm+159164

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5773fe45

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: 2016-10-02T18:50:34.000Z

OSBUILD: 14393

OSSERVICEPACK: 0

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: 2016-09-15 17:21:59

BUILDDATESTAMP_STR: 160915-0644

BUILDLAB_STR: rs1_release

BUILDOSVER_STR: 10.0.14393.206.amd64fre.rs1_release.160915-0644

ANALYSIS_SESSION_ELAPSED_TIME: 52c

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:lkd_0x141_image_nvlddmkm.sys

FAILURE_ID_HASH: {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc}





That was during DOOM in 02.10.2016 , i realize today about this when i found it.

Game was not crashed, but event viewer report LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys and create minidump in Windows/Watchdog folder.

Question. What part of pc is unstable now? Propably GPU even if it is on stock?

I dont oc my pc,all is stock.

6700K no OC ( good temps 60C )
16GB DDR4
Asus Z170-P
Corsair 750 RM
Gigabyte 1080 Xtreme ( NO OC ,stock clocks )

Currently i am on Windows 10 Anniversary and 368.69 drivers.

Memtest86 pass fine no errors. So if gpu crashed i can rma card now?

So if its my gpu crashed then ( i found minidump in Watchdog folder ) its not unstable on stock clocks and i can rma card,because of that single event?

Beside that all of my games are stable, i can play GTA V no crashes, Heaven, 3dmark 11,13 stable.
 
Ad

Advertisements

Joined
Oct 2, 2014
Messages
1,747
Reaction score
403
nvlddmkm.sys is part of your Nvidia graphics drivers. First, download the latest drivers from Nvidia's website (see my edit first). Then, download and install a program called DDU (display driver uninstaller). Boot in to safe mode and run it. It'll reboot your PC when done. Now install the latest Nvidia drivers. I know it's a pain to do, but sometimes necessary if you have a corrupt driver install. I use it every time I update my drivers. Hopefully that helps.

edit: It wouldn't hurt to check out the DOOM forums and see if others are having the same issue. It could be a certain driver version that's having an issue with that specific game.
 
Joined
Feb 19, 2016
Messages
49
Reaction score
0
I was thinking that TDR is caused by unstable OC or faulty card. So thats why i am asking.
Also my card is on stock so on stock is unstable if crashed once?

image.jpg


Screen, display driver crash.
 
Joined
Oct 2, 2014
Messages
1,747
Reaction score
403
You can see if they'll RMA it. But I've had the same issues, and it always turned out to be drivers. Unstable overclocks usually end up with a freeze or blue screen, and will happen any time the card is pushed. A bad card either will do the same, or just black screen on boot. Try what I said above first. If it's only doing it with Doom, I'll guarantee it's a driver conflict.
 
Ad

Advertisements

Trouble

Noob Whisperer
Moderator
Joined
Nov 19, 2013
Messages
13,409
Reaction score
2,319

Top