So, I updated my NVIDIA driver, because I noticed that my games were significantly dropping in frame-rate. and it immediately stopped working. I need to have it disabled now, otherwise, it blue-screens/freezes my computer with the error "VIDEO_TDR_FAILURE (nvlddmkm.sys)", which makes any game unplayable! So, I have to run things off of my Intel card now, but it can't really handle games! I can get my laptop fixed at Best Buy, but I'd rather not have the people be going through my files, it makes me uncomfortable. I also don't want to have to pay to have them fix something that I can fix myself. I've tried everything. Rolling back the Intel driver, rolling back the NVIDIA driver, disabling the Intel driver, updating the Intel driver, but nothing works! It always blue-screens or freezes! I can't even reset my PC, it always So, I can't play any games anymore! I really need help fixing this. Has says "There was a problem resetting your computer. No changes have been made." So I can't fix it like that, either. Has anybody had the same issue? Is there a way I can fix this myself?
Thanks, in advance.

CPU Specs:
Computer Information:
Manufacturer: Alienware
Model: Alienware 17 R3
Form Factor: Laptop
No Touch Input Detected

Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
CPU Family: 0x6
CPU Model: 0x5e
CPU Stepping: 0x3
CPU Type: 0x0
Speed: 2592 Mhz
8 logical processors
4 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Supported

Network Information:
Network Speed:

Operating System Version:
Windows 10 (64 bit)

Video Card:
Driver: NVIDIA GeForce GTX 970M
DirectX Driver Name: igdumdim32.dll
Driver Version: 21.21.13.6909
DirectX Driver Version: 20.19.15.4463
Driver Date: 1 Aug 2016
OpenGL Version: 4.4
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 60 Hz
DirectX Card: Intel(R) HD Graphics 530
Number of Monitors: 1
Number of Logical Video Cards: 1
No SLI or Crossfire Detected
Primary Display Resolution: 1600 x 900
Desktop Resolution: 1600 x 900
Primary Display Size: 15.04" x 8.43" (17.20" diag)
38.2cm x 21.4cm (43.7cm diag)
Primary Bus Type Not Detected
Primary VRAM: -1024 MB
Supported MSAA Modes: 2x 4x 8x 16x

Sound card:
Audio device: Speakers (Sound Blaster Recon3D

Memory:
RAM: 8091 Mb

Miscellaneous:
UI Language: English
Microphone: Not set
Steam Controller Cable and Base: Not set
Media Type: Undetermined
Total Hard Disk Space Available: 1062487 Mb
Largest Free Hard Disk Block: 167204 Mb
OS Install Date: Dec 31 1969
Game Controller: None detected
VR Headset: None detected

7 years ago

Comment has been collapsed.

o laptop, probably overheating

7 years ago
Permalink

Comment has been collapsed.

I've got a cooling pad for it, and it's never overheated before, and the fans to get rid of the heat are cool to the touch, and it only does it if I enable my NVIDIA driver. If the driver is disabled, the computer runs fine.

7 years ago
Permalink

Comment has been collapsed.

put an older drivers.

7 years ago
Permalink

Comment has been collapsed.

I tried that. It still does the same thing, now.

7 years ago
Permalink

Comment has been collapsed.

clean install?

7 years ago
Permalink

Comment has been collapsed.

Yep. I did a clean install of it.

7 years ago
Permalink

Comment has been collapsed.

7 years ago
Permalink

Comment has been collapsed.

Okay, thank you. I will try that now.

7 years ago
Permalink

Comment has been collapsed.

No such luck. Now I get frozen at the boot up menu, I don't even get to the login screen. I had to disable the driver again.

7 years ago
Permalink

Comment has been collapsed.

Did you experience any issue (not necessary the same) before installing the new driver? "and it immediately stopped working" - what exactly happened?

7 years ago
Permalink

Comment has been collapsed.

Well, I restarted the PC after the update, and it would blue-screen every time I booted it up, then, after a while, it would let me log in, and then blue-screen once everything loaded. I hadn't experienced issues with it before.

7 years ago
Permalink

Comment has been collapsed.

Hmmm, in this case it's different from the issue I have with mine. Sorry, can't help then.

7 years ago
Permalink

Comment has been collapsed.

In your post, your driver date is Aug. 1 2016. After following Tzaar's advice and wiping your driver installation, are you installing the nVidia drivers with the same date? Because I can't get the site to go older than Aug. 15.

7 years ago
Permalink

Comment has been collapsed.

No, which is strange, because my driver is newer than August 1st. I updated it to the newest available version. Which I believe was November 28, 2016. I'm trying to install the newest driver that was released today, now. After I wiped the installation, of course.

7 years ago
Permalink

Comment has been collapsed.

But you started having issues with the new driver, right? That means that, while the driver is meant for your GPU, there may be another factor, hardware or software, that renders it incompatible. You should roll back to your last known good setup (Aug. 1 drivers by your OP) to restabilize, then start stepping through drivers released since then until you find the last most recent driver that works for you.

Believe it or not, the most recently released drivers aren't always the best.

7 years ago
Permalink

Comment has been collapsed.

There's no way for me to roll back that far, because I can't get the site to go older than August 15th, either.

7 years ago
Permalink

Comment has been collapsed.

Google tells me you need to rename and replace nvlddmkm.sys after reinstalling the drivers.

7 years ago
Permalink

Comment has been collapsed.

With the same thing? How should I do that?

7 years ago
Permalink

Comment has been collapsed.

Google.

7 years ago
Permalink

Comment has been collapsed.

I've seen a couple of people fixing error like those by replacing the nvlddmkm.sys with the one in the driver package... it seems the file get corrupt for some reason.

Search for a file nvlddmkm.sys_ in nvlddmkm c:\nvidia which will probably be found in c:\nvidia\displaydriver\<version>\international\display\

you need to expand files ending with with the expand utility like this : expand.exe nvlddmkm.sy nvlddmkm.sys

Also the full error message from the eventlog could give us more info.

7 years ago*
Permalink

Comment has been collapsed.

Right, I might sound like an idiot, but I have no idea how to do that. I'm okay with technology, just not when it comes to stuff like this. How might I do something like this? And what event log? If it's not the driver event log, I don't know how to access it, and the driver event log doesn't say anything about crashes or errors, it's all about the updates to it.

7 years ago
Permalink

Comment has been collapsed.

The eventlog can be accessed by typing "eventvwr" in the search bar next to the start button in Windows 10. The error (if logged) should be in the Windows journal -> Application Or Windows journal -> System. Search for a red ! at about the time it last crashed.

As for the nvlddmkm.sy file in the c:\nvidia. If you go in that folder use the search bar of that window... it should find it. If multiple files are found... try the oldest one first (in case it's a new bug). Then copy the file in the c:\nvidia folder. Then open a console (type cmd in the search bar of the taskbar). Then in the console type expand c:\nvidia\nvlddmkm.sy c:\nvidia\nvlddmkm.sys. There should now be a new file in the nvidia folder (if no error were returned). Copy that file in the c:\windows\system32 and reboot.

7 years ago
Permalink

Comment has been collapsed.

Event log from when it last crashed (I'm not sure it's the right thing you need, but I haven't edited it at all, and it's the last crash that happened.);

Log Name: System
Source: nvlddmkm
Date: 12/14/2016 2:50:42 PM
Event ID: 14
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-1DUO1OP
Description:
The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\UVMLiteController0x1
120c0(33a4) 00000000 00000000

the message resource is present but the message is not found in the string/message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="nvlddmkm" />
<EventID Qualifiers="49322">14</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-12-14T22:50:42.186121400Z" />
<EventRecordID>63286</EventRecordID>
<Channel>System</Channel>
<Computer>DESKTOP-1DUO1OP</Computer>
<Security />
</System>
<EventData>
<Data>\Device\UVMLiteController0x1</Data>
<Data>120c0(33a4) 00000000 00000000</Data>
<Binary>0000000002003000000000000E00AAC0000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>

As for the nvlddmkm.sy thing, I'm going to try that now.

7 years ago
Permalink

Comment has been collapsed.

Right, I've done the last thing you told me, restarted it, then it came on, bluescreened after a little bit, with the error "DRIVER_POWER_STATE_FAILURE", then restarted, and the PC seems stable now, and I can actually be on it without safe mode being on, but, I tried to launch a game to see if it had fixed this issue, and it gave me the "VIDEO_TDR_FAILURE (nvlddmkm.sys)" error again. Should I try to launch a game again?

7 years ago
Permalink

Comment has been collapsed.

So it's a little bit better... but it still crash. I've just reread my last post and it should had said... copy in c:\windows\system32\drivers. Sorry. Could you try that. I'll do some more research in the meantime.

7 years ago
Permalink

Comment has been collapsed.

7 years ago
Permalink

Comment has been collapsed.

when trying diff drivers, i'd prob use DDU to make sure priors are super clean uninstalled.

7 years ago
Permalink

Comment has been collapsed.

7 years ago
Permalink

Comment has been collapsed.

i am, lol.. just the first thing i thought of after reading thread.. didn't read comments. my bad. xD

7 years ago
Permalink

Comment has been collapsed.

I'm sorry, perhaps these questions were asked from above. But how old is the laptop? When was the last time he cleaned from dust physically :)? And do you have program for monitoring the temperature , and if so then what temperature it shows?

I ask this because such errors occur primarily because of the video card overheating

7 years ago*
Permalink

Comment has been collapsed.

The PC is only around a year old, I got it for Christmas last year. I clean the fans of dust frequently. I would be able to feel how hot the computer is by touching the back, where the fans are, but it's cool to the touch. I also have a cooling pad for the computer, as well. So, I don't think it's overheating.

7 years ago
Permalink

Comment has been collapsed.

I have exactly the same problem the only solution I found is using an old NVIDIA driver

7 years ago
Permalink

Comment has been collapsed.

7 years ago
Permalink

Comment has been collapsed.

"So, I updated my NVIDIA driver, because I noticed that my games were significantly dropping in frame-rate."

It sounds to me like you may have been already having problems with the GPU before you updated the drivers.

Dell's page has a download for your driver package that is dated 09 Mar 2016. I would use these manufacturer drivers before using nVidia's as sometimes there's a proprietary setting that will prevent the regular ones from installing properly.

http://www.dell.com/support/home/us/en/4/product-support/product/alienware-17-r3/drivers

The Intel driver from Dell is also on that page.

7 years ago
Permalink

Comment has been collapsed.

Wonderful, thank you. I will try that now.

7 years ago
Permalink

Comment has been collapsed.

No luck. Even after installing all of that, then cleanly installing the Nvidia driver, it still crashes, with the same error.

7 years ago
Permalink

Comment has been collapsed.

I'm not sure what else you can try but I still think that your statement that I quoted may signify a hardware failure. It seems strange for your FPS to just start dropping from the norm. I would maybe try taking it apart and seeing if there's something built up in the fans that you can't get to by just by blowing air through the vents.

7 years ago
Permalink

Comment has been collapsed.

Alright, I'll try that.

7 years ago
Permalink

Comment has been collapsed.

since you had issues before (which was the reason you installed the new driver), it might be that your graphics card is actually broken. what is the exact blue screen error message? maybe we can find out something about it.

if you want to be sure that the problem is purely software/driver related, make a complete backup of your pc (make an image with Acronis or something), so you can go back later. then wipe your drive and do a clean windows installation. install graphics card drivers and play a game. if you have no issues then, it is really a software/driver problem. if you experience the same or other errors, your hardware may be broken, in which case you should go to best buy and let it repair. if you have a backup image, you can wipe your hdd before that, so nobody can see your files.

7 years ago
Permalink

Comment has been collapsed.

Okay, thank you so much! I will do that.

7 years ago
Permalink

Comment has been collapsed.

good luck :)

7 years ago
Permalink

Comment has been collapsed.

What a blunder trying to fix fps drop with driver update. Frame drop is always heating issue. Cooling pads is not enough.

  1. Go into safe mode, reinstall your old driver and see if that solves it.
  2. Install temperature monitor application(MSI afterburner). Use your computer as you normally do and see, If temp reach 80+ its heat issue, if it reach 95+ that is hardware failure level.
  3. If even after you reinstall your old driver it gives you the same error and bsod but using intel do not gives you error, that means your gpu has already suffered critical hardware failur(gpu fried). Not much you can do other than sending it for motherboard replacement.
7 years ago
Permalink

Comment has been collapsed.

Frame drop is NOT always a heating issue. Hardware decay, poorly tested game updates, game engine updates being incompatible with old drivers, malware, archive fragmentation, and archive corruption are just a few causes that I can name off the top of my head.

Perfect example, earlier this year Guild Wars 2 rolled out an update to its renderer. For many running on older nVidia cards, there was a frame drop on the order of 20-50 FPS depending on configuration. There was nothing wrong with the new renderer, but it was tapping a feature nVidia hadn't fully supported for older cards due to age rather than capability. It took months before new drivers rectified the issue, but it was, in the end, a frame drop requiring updated drivers to rectify.

There is, of course, historical instances of engine devs leaping an new DirectX releases, pushing patches to their licensees, which then caused widespread issues because card manufacturers hadn't rolled out support for the new feature sets (DX9 launch SUCKED the first few months) except in bleeding-edge hardware.

In fact, heat is never an issue; it's a symptom of any number of issues, ranging from dust to corrupted drivers to hardware decay.

7 years ago
Permalink

Comment has been collapsed.

Yeh, when it's about a laptop, people always start screaming "overheating". I have had a quite a few laptops and sure after a while they start getting hotter if the dust clogs up the heatsinks. But when you clean it it is all back to normal. But people don't like to clean I guess :P
In fact, the gaming laptop I have now runs normally extremely cool. Around 40C.

7 years ago
Permalink

Comment has been collapsed.

I have exactly that with a Geforce 430 GT, drivers from 2015 give an exclamation mark (thus not working) in device manager, 2016 drivers give a bsod on that sys file, 2014 drivers give me a sound loop after a few hours my pc being on, but atleast it works and i am not getting a blue screen.
It's not the card because i have tried another exact same card, and all those BSOD fixed about replacing that sys file, didn't work.

And when you google actually alot of people with nvidia cards getting bsod too, Definitely something wrong with nvidia and their drivers.

7 years ago*
Permalink

Comment has been collapsed.

Did some more research, found this.

http://ccm.net/faq/6210-how-to-fix-an-nvlddmkm-sys-error-message

EDIT: Pretty much the same thing, just different directions to accomplish it.

https://www.drivereasy.com/knowledge/nvlddmkm-sys-video_tdr_failure-blue-screen-error-solved-on-windows-10/

7 years ago
Permalink

Comment has been collapsed.

You are late :P

7 years ago
Permalink

Comment has been collapsed.

Well damn it. :X
Oh well, now he has step-by-step instructions. ;_;

7 years ago
Permalink

Comment has been collapsed.

So, unless I miss my guess, the installer isn't correctly expanding the driver archive on Win10? This sounds vaguely familiar...

7 years ago
Permalink

Comment has been collapsed.

That would appear to be the case. I've not come across this problem myself or with client builds.
That's why I was so curious about a possible solution (in case it ever happens).

7 years ago
Permalink

Comment has been collapsed.

This is historically common, thus my sarcastic "familiar" comment (poe's law, I know). nVidia is as bad about pushing malformed installers over the years as AMD has been "fixing" the malfunctioning Catalyst Control Panel.

7 years ago
Permalink

Comment has been collapsed.

Thanks, I'll try it if nothing else works.

7 years ago
Permalink

Comment has been collapsed.

Closed 7 years ago by xXRaiser0fHellXx.