560 Ti - Display driver nvlddmkm stopped responding and has successfully recovered.

Toggle sidebar Toggle sidebar
M

MisterLeroy

Reputable
Mar 21, 2015
1
0
4,510
This message is my life now.

Hey TH.

For some months now, on and off, this has been an ongoing struggle of mine. I've been through various drivers, with clean installs. As I write they have crapped out a number of times:

Log Name: System
Source: Display
Date: 21/03/2015 22:53:44
Event ID: 4101
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: MisterLeroy
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Display" />
<EventID Qualifiers="0">4101</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-03-21T22:53:44.000000000Z" />
<EventRecordID>63440</EventRecordID>
<Channel>System</Channel>
<Computer>MisterLeroy</Computer>
<Security />
</System>
<EventData>
<Data>nvlddmkm</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: System
Source: Display
Date: 21/03/2015 22:53:44
Event ID: 4101
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: MisterLeroy
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Display" />
<EventID Qualifiers="0">4101</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-03-21T22:53:44.000000000Z" />
<EventRecordID>63441</EventRecordID>
<Channel>System</Channel>
<Computer>MisterLeroy</Computer>
<Security />
</System>
<EventData>
<Data>nvlddmkm</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: System
Source: Display
Date: 21/03/2015 22:49:47
Event ID: 4101
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: MisterLeroy
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Display" />
<EventID Qualifiers="0">4101</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-03-21T22:49:47.000000000Z" />
<EventRecordID>63438</EventRecordID>
<Channel>System</Channel>
<Computer>MisterLeroy</Computer>
<Security />
</System>
<EventData>
<Data>nvlddmkm</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: System
Source: Display
Date: 21/03/2015 22:49:47
Event ID: 4101
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: MisterLeroy
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Display" />
<EventID Qualifiers="0">4101</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-03-21T22:49:47.000000000Z" />
<EventRecordID>63439</EventRecordID>
<Channel>System</Channel>
<Computer>MisterLeroy</Computer>
<Security />
</System>
<EventData>
<Data>nvlddmkm</Data>
<Data>
</Data>
</EventData>
</Event>

The card appears ok and paste has been replaced. Fans spinning up. Last weekend, I went through a collection of driver releases, I had the PC down on it's side as I worked on it through the Saturday. Sunday morning and I wasn't encountering errors, and since then I have had the tower on it's side as kind of a "if it works, don't move it" deal. Today, I returned it to Tower form...

I can't even write a forum post without the screen blacking out and the drivers failing.

Is this simply time to get a new card? Should I resume using the tower on it's side?

It doesn't seem to be anywhere near overheating...

Log Name: System
Source: Display
Date: 21/03/2015 23:07:34
Event ID: 4101
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: MisterLeroy
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Display" />
<EventID Qualifiers="0">4101</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-03-21T23:07:34.000000000Z" />
<EventRecordID>63444</EventRecordID>
<Channel>System</Channel>
<Computer>MisterLeroy</Computer>
<Security />
</System>
<EventData>
<Data>nvlddmkm</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: System
Source: Display
Date: 21/03/2015 23:07:34
Event ID: 4101
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: MisterLeroy
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Display" />
<EventID Qualifiers="0">4101</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-03-21T23:07:34.000000000Z" />
<EventRecordID>63445</EventRecordID>
<Channel>System</Channel>
<Computer>MisterLeroy</Computer>
<Security />
</System>
<EventData>
<Data>nvlddmkm</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: System
Source: Display
Date: 21/03/2015 23:07:22
Event ID: 4101
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: MisterLeroy
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Display" />
<EventID Qualifiers="0">4101</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-03-21T23:07:22.000000000Z" />
<EventRecordID>63442</EventRecordID>
<Channel>System</Channel>
<Computer>MisterLeroy</Computer>
<Security />
</System>
<EventData>
<Data>nvlddmkm</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: System
Source: Display
Date: 21/03/2015 23:07:22
Event ID: 4101
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: MisterLeroy
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Display" />
<EventID Qualifiers="0">4101</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-03-21T23:07:22.000000000Z" />
<EventRecordID>63443</EventRecordID>
<Channel>System</Channel>
<Computer>MisterLeroy</Computer>
<Security />
</System>
<EventData>
<Data>nvlddmkm</Data>
<Data>
</Data>
</EventData>
</Event>

There it goes again. Any advice welcome. I'm losing my mind :(
 
Sort by date Sort by votes
R

Rasklop

Reputable
Mar 13, 2015
32
0
4,540
1) Make sure that you are in High Performance mode(google is your friend)
2) Change the theme
3) Completely uninstall drivers for your GPU, and then install only the newest driver(preferably beta)
4) Try using Windows Update
5) Downclock your video clock speeds and/or ram speeds.
6) Run memory tests overnight.
7) Administrative tools > Task Scheduler > Scroll down till you see TMM. Double click ‘TMM’. Right click it and select disable. - known to work, definetely try
8)
1. Goto registry editor (start -> run -> regedit)
2. Navigate yourself to HKEY_LOCAL_MACHINESystemCurrentControlSetControlGraphicsDrivers (make sure GraphicsDrivers is highlighted)
3. Right click -> New -> DWORD (32-bit) value -> Name it: TdrDelay -> double click it -> Set it to A (hexadecimal) or 10 (decimal).
If that doesn't work, try disabling it, by adding the following DWORD: TdrLevel and setting the value to 0, then rebooting.
9) Try using different RAM
10) Try using better cooling
11) New GPU


Hope I helped!
 
Upvote 0 Downvote
Hokman101

Hokman101

Reputable
Apr 13, 2015
14
0
4,520


 
Upvote 0 Downvote
Hokman101

Hokman101

Reputable
Apr 13, 2015
14
0
4,520
The problem is not in tdr or any outdated drivers...the problem is in your RAM i am 100% sure.to fix it go to bios and if your ram speed is for example 1600mhz deacrese it to 1333mhz ;). I had same problems and tryed 1000 solutions none of them worked util i realized it was RAM,so lower the speed of ram and u will be fine.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom