Display driver nvlddmkm stopped responding and has successfully recovered.

Associate
Joined
6 Jun 2013
Posts
1
Hi,

I have recently built a new PC, all components are new apart from the GFX card and Hard Drives/SSD. I never had this issue with my previous build, however whenever I game now the screen goes black and the game will crash (this happens very sporadically), looking in the event log I see the error:

"Display driver nvlddmkm stopped responding and has successfully recovered."

I have tried everything I can think of so far:

New Drivers, Older drivers.
Re-formatting the PC.
Running Memtest, Seatools, Prime95, Furmark - all came back fine
I tried running the recommended windows fix - http://support.microsoft.com/kb/2665946?wa=wsignin1.0

I have tried running on one monitor and both, different display ports, making sure the components are seated correctly.

All temperatures are fine, CPU is around 35 degrees while in BF3 and graphics card is around 45 degrees. Nothing has been overclocked, apart from the GFX which is factory overclocked.

I am at a loss now.... do I have a faulty component or is it driver/firmware related? I would really appreciate any help because at the moment I have a £1000+ machine that was built for gaming which can't game... Any help would be greatly appreciated.

###Specs###

7 4770k 3.5Ghz
Corsair H100i CPU Cooler
16 GB Corsair Vengeance Pro
MSI Z87-GD65 Gaming Motherboard
GTX 670 Gigabyte Windforce x3 GPU
Corsair AX860 Modular PSU
Samsung 840 Pro 256GB SSD
1TB Western Digital Caviar Black HDD

ystem Information
------------------
Time of this report: 6/25/2013, 17:31:56
Machine name:
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
Language: English (Regional Setting: English)
System Manufacturer: MSI
System Model: MS-7845
BIOS: BIOS Date: 05/17/13 11:14:29 Ver: 04.06.05
Processor: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (8 CPUs), ~3.5GHz
Memory: 16384MB RAM
Available OS Memory: 16326MB RAM
Page File: 3717MB used, 37093MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 64bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 670
Manufacturer: NVIDIA
Chip type: GeForce GTX 670
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_1189&SUBSYS_35421458&REV_A1
Display Memory: 4042 MB
Dedicated Memory: 1994 MB
Shared Memory: 2047 MB
Current Mode: 1920 x 1080 (32 bit) (120Hz)
Monitor Name: Acer GD245HQ (Digital)
Monitor Model: Acer GD245HQ
Monitor Id: ACR0125
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.2018 (English)
Driver Version: 9.18.13.2018
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 5/12/2013 22:42:27, 15143904 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-52C9-11CF-0A70-4F151CC2C435}
Vendor ID: 0x10DE
Device ID: 0x1189
SubSys ID: 0x35421458
Revision ID: 0x00A1
Driver Strong Name: oem21.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section066:9.18.13.2018:pci\ven_10de&dev_1189
Rank Of Driver: 00E02001
 
This problem is a real pain; it could be almost anything.

I've had two instances of this happening to me personally, once with GTX 460 in SLI (PSU wasn't up to the job) and once with a 6850. I never managed to solve the 6850 one, and just put it down to a faulty card.

Unfortunately it's a case of long troubleshooting and swapping out parts. You could try downclocking the card too to see if it alleviates the problem at lower clocks (although this usually just indicates a faulty card anyway).

On a fresh install of Windows I'd very much doubt it was a driver/software issue, but stranger things have happened. I'd probably test on the most minimal install you can manage, just in case it's an extremely rare compatibility issue with another driver or something. My money would be on hardware issue though.
 
Back
Top Bottom