Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys


  • Please log in to reply
3 replies to this topic

#1 sew333

sew333

  • Members
  • 76 posts
  • OFFLINE
  •  
  • Local time:02:28 PM

Posted 07 October 2016 - 04:34 PM

Hello. So today i checked event viewer and i saw TDR log about display crash. LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys
 
Screen:
Image
 
image.jpg
 
 
That was during DOOM. Game was not crashed, but event viewer report LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys.
Question. What part of pc is unstable now?
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 gpu crashed and rma card now?
 
Beside that all of my games are stable, i can play GTA V no crashes, Heaven, 3dmark 11,13 stable.
 
Here i upload minidump ,can somebody help me and tell what part is failing?
 

Edited by sew333, 07 October 2016 - 04:34 PM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:28 AM

Posted 08 October 2016 - 11:56 AM

These are errors with your video - either the card itself or the drivers.

Please follow these troubleshooting suggestions:  http://www.carrona.org/VideoTDR.html

Also, please monitor your temps with this free utility: 

SpeedFan v. 4.5.1 and later (free from here:  http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:

To make it work you have to do BOTH of the below steps:

1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.

2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.

The log will be located at C:\Program Files (x86)\SpeedFan

Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.

Notes: whenever you change the options related with logging, SpeedFan starts a new log file.

NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.


 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 sew333

sew333
  • Topic Starter

  • Members
  • 76 posts
  • OFFLINE
  •  
  • Local time:02:28 PM

Posted 09 October 2016 - 05:01 AM

It happened once. Its not repeatable i dont know why.
Game didn't crash, everything works as normal, but event viewer report LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys and of course minidump file in Windows/Watchdog..

So its TDR then and its hardware problem?

 

 

Here is 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}


Edited by sew333, 09 October 2016 - 05:02 AM.


#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:28 AM

Posted 11 October 2016 - 06:56 AM

The memory dump doesn't tell us much more other than it being a TDR error.
And the link that I gave you to the TDR page is the best suggestion that I have for your problems: 

Please follow these troubleshooting suggestions:  http://www.carrona.org/VideoTDR.html

Also, please monitor your temps with this free utility: 

SpeedFan v. 4.5.1 and later (free from here:  http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:

To make it work you have to do BOTH of the below steps:

1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.

2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.

The log will be located at C:\Program Files (x86)\SpeedFan

Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.

Notes: whenever you change the options related with logging, SpeedFan starts a new log file.

NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.

 

 

Basically, there are 2 types of TDR errors - those that cause BSOD's (because the driver wasn't able to recover from the TDR event) and those that don't cause BSOD's (because the driver was able to recover from the TDR event).

 

TDR errors can be hardware or software.  Follow the suggestions in the link that I posted.

If all the software tests/installations fail - then it's time to try another video card


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users