Issues with Nvidia GTX 770 Card (Event ID 14 nvlddmkm stopped responding)

1Exhd281

Honorable
Jul 4, 2013
1
0
10,510
Good day,

I recently put together a new PC with the following components:

ASUS Z87-Pro BIOS Revision 1007
Intel i7-4770k at 3500Mhz
32GB Corsair Vengance (4 x 8GB) DDR3 1866 Desktop Memory
EVGA SuperClocked w/ACX Cooling 02G-P4-2774-KR Geforce GTX 770
2 x WD 3TB WD3001FAEX HDDs (RAID 1 using MB Intel RST)
SeaSonic Platinum 1000 1000W ATX12V Power Supply
Windows 8 Pro x64

After settling in, I noticed that after an uptime of over 36 hours or so, the Nvidia driver would stop responding reporting Event ID 14 and most of the time it was able to recover without freezing my PC. I have already RMAed the video card once and just installed the replacement a few days ago and it froze up this morning (about 36 hours or so after installation).

I initially had Nvidia drivers 320.18, then upgraded to the 320.49 beta drivers, then the WHQL drivers after they were released and I have even dabbled in the 326.01 Windows 8.1 drivers as well. Regardless of drivers used and/or video card it seems to freeze up.

Currently I am running with the integrated Intel video to see if it too freezes up after a day or so of uptime. It is just I think there must be something afoot on my PC because if this was widespread I don't think Nvidia could be so indifferent in their approach to this.

I have ran HWMonitor, tested my CPU and RAM, even ran some of the video stress tests and my PC never shows issues during any of them.

When the issues arise, I usually have a few browsers up over two displays, maybe a video playing and World of Warcraft in a window. I just don't get it.

Any thoughts?

==

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\Video3
CMDre 00000003 0000011c bad0011f 00000000 00d0011f
 
Solution
Unfortunately I have no answer for you and am only posting so that I can monitor the thread. I'm having the same issues you are on a somewhat similar setup.

Intel core i7 3770k
32GB Kingston HyperX Blu RAM
OCZ Vertex 120GB SSD - (OS drive)
Seagate Momentus XT Hybrid Drive 750GB (Programs, storage)
Nvidia GTX 560 ti 2GB running in SLI
Gigabyte Intel Z77 LGA 1155 (GA-Z77X-UD3H)

Maybe we can find some similarity. I've gone back to reading posts over four years old with the same problems reported but have yet to find a solution. I'm at a loss because I did just make some hardware changes, I added the second video card and upgraded to that motherboard and reinstalled windows. I did not have any issues prior to making the changes...

hellofrommycubicle

Honorable
Aug 6, 2013
12
0
10,520
Unfortunately I have no answer for you and am only posting so that I can monitor the thread. I'm having the same issues you are on a somewhat similar setup.

Intel core i7 3770k
32GB Kingston HyperX Blu RAM
OCZ Vertex 120GB SSD - (OS drive)
Seagate Momentus XT Hybrid Drive 750GB (Programs, storage)
Nvidia GTX 560 ti 2GB running in SLI
Gigabyte Intel Z77 LGA 1155 (GA-Z77X-UD3H)

Maybe we can find some similarity. I've gone back to reading posts over four years old with the same problems reported but have yet to find a solution. I'm at a loss because I did just make some hardware changes, I added the second video card and upgraded to that motherboard and reinstalled windows. I did not have any issues prior to making the changes, but I changed so much system wide it's difficult to pinpoint a cause.

Last night, I renamed the nvlddmkm.sys file in C:\Windows\Drivers to .old, and re-extracted the .sys file from a .sy_ file that is found somewhere in the nVidia program files (not sure where, just did a search for nvlddmkm.sy_, copied to desktop and used a cmd to extract the file. I have not yet used the machine enough to see if we still have issues. I haven't actually gotten the error during any gaming sessions yet, most time the errors happen during web browsing and mostly seem to happen randomly. Usually it's just once in awhile, but last night my eventvwr was spammed with the same message you've described above.

I have confirmed that all drivers are up to date and am not running any beta drivers. I am wondering if it would be worth it to go back to the previou NV drivers? Have you tried that?
 
Solution