280.26 Display driver nvlddmkm stopped responding and has successfully recovered.
  1 / 58    
[i]Display driver nvlddmkm stopped responding and has successfully recovered[/i]

I'm getting the above error when coming out of standby with the 280.26 whlq drivers. Actually it also happens with the 280.19 beta drivers as well but as they were beta's....

My graphics Card is an Asus GTX560 Ti DirectCU II. It is a stock o/c by Asus to Core 900 Mem 4200 Shaders 1800 and I am not overclocking further. I've had the card for about 8 weeks and no problems at all with the 275.33 whql drivers.

Not sure what to make of it. After booting up the PC the crash happens the first time only the computer comes out of standby. Subseqent standbys no problem. The crash has happened twice after booting up when IE9 is first opened but again not subseqently. Never happened with the 275.33 drivers I can play games and run MSIKombuster for hours with no problems.

I'm fairly certain this is not a hardware issue as it is clearly not heat related and my system has been rock solid since built with a GTX460 and with the GTX 560 Ti until the new drivers. Is it true nVidia messed with voltages in these new drivers (which is the likely cause) and are working on a fix??
Display driver nvlddmkm stopped responding and has successfully recovered



I'm getting the above error when coming out of standby with the 280.26 whlq drivers. Actually it also happens with the 280.19 beta drivers as well but as they were beta's....



My graphics Card is an Asus GTX560 Ti DirectCU II. It is a stock o/c by Asus to Core 900 Mem 4200 Shaders 1800 and I am not overclocking further. I've had the card for about 8 weeks and no problems at all with the 275.33 whql drivers.



Not sure what to make of it. After booting up the PC the crash happens the first time only the computer comes out of standby. Subseqent standbys no problem. The crash has happened twice after booting up when IE9 is first opened but again not subseqently. Never happened with the 275.33 drivers I can play games and run MSIKombuster for hours with no problems.



I'm fairly certain this is not a hardware issue as it is clearly not heat related and my system has been rock solid since built with a GTX460 and with the GTX 560 Ti until the new drivers. Is it true nVidia messed with voltages in these new drivers (which is the likely cause) and are working on a fix??

Asus P6X58D-E Bios 0701 - Intel i7 930 @ 3.8GHz - Corsair 3x2GB XMS3 12800 CAS 8-8-8-24

Intel SSD 160GB Gen2 - Samsung F3 1TB - LG Blu-ray RW BH10LS30

Asus GTX560 Ti DCII Top (C900MHz/M4200MHz/S1800MHz) - Hazro HZ27W 27" Widescreen 2560x1440

Zalman LQ1000 - Seasonic X-Series 760W 80+ Gold

#1
Posted 08/11/2011 09:10 PM   
[quote name='EasterEEL' date='11 August 2011 - 05:10 PM' timestamp='1313097003' post='1278119']
Is it true nVidia messed with voltages in these new drivers (which is the likely cause) and are working on a fix??
[/quote]

According to nvidia, voltage applied to the hardware has not changed... only the voltage reported to the user. Even so, it's unlikely that a small [i]increase[/i] in voltage would cause instability anyway.
[quote name='EasterEEL' date='11 August 2011 - 05:10 PM' timestamp='1313097003' post='1278119']

Is it true nVidia messed with voltages in these new drivers (which is the likely cause) and are working on a fix??





According to nvidia, voltage applied to the hardware has not changed... only the voltage reported to the user. Even so, it's unlikely that a small increase in voltage would cause instability anyway.

"This is your code. These are also your bugs. Really. Yes, the API runtime and the
driver have bugs, but this is not one of them. Now go fix it already." -fgiesen

#2
Posted 08/12/2011 04:49 AM   
I've got the same problem with 280.26.
Running on Windows 7 x64 with GTX 560 Ti, I've just been browsing with Firefox 5.0 and it crashed twice in one our.

Event ID 4101
I've got the same problem with 280.26.

Running on Windows 7 x64 with GTX 560 Ti, I've just been browsing with Firefox 5.0 and it crashed twice in one our.



Event ID 4101

#3
Posted 08/12/2011 08:08 AM   
[quote name='Rittsel' date='12 August 2011 - 04:08 AM' timestamp='1313136485' post='1278307']
I've got the same problem with 280.26.
[/quote]

You're not alone. I've seen this problem reported across various forums. Hopefully NVIDIA doesn't wait 'til September release to address it.
[quote name='Rittsel' date='12 August 2011 - 04:08 AM' timestamp='1313136485' post='1278307']

I've got the same problem with 280.26.





You're not alone. I've seen this problem reported across various forums. Hopefully NVIDIA doesn't wait 'til September release to address it.

"This is your code. These are also your bugs. Really. Yes, the API runtime and the
driver have bugs, but this is not one of them. Now go fix it already." -fgiesen

#4
Posted 08/12/2011 08:30 AM   
As I have previously noted it seems that any of the 280.xx drivers will cause the same "stopped responding and recovery" message / situation for me when installed.
I am using Windows 7 x64 SP1 with my Gigabyte GTX 460 1GB card, which is not overclocked.
The event can happen at any time, whether using Firefox (with GPU acceleration on or off it does not matter)or just idling on the desktop.
Going back to the 275.33 drivers resolves this issue and then the system is back to 100% stability, as normal.
A clean removal and fresh install was done for each set of drivers tried.
As I have previously noted it seems that any of the 280.xx drivers will cause the same "stopped responding and recovery" message / situation for me when installed.

I am using Windows 7 x64 SP1 with my Gigabyte GTX 460 1GB card, which is not overclocked.

The event can happen at any time, whether using Firefox (with GPU acceleration on or off it does not matter)or just idling on the desktop.

Going back to the 275.33 drivers resolves this issue and then the system is back to 100% stability, as normal.

A clean removal and fresh install was done for each set of drivers tried.

#5
Posted 08/12/2011 09:04 AM   
also experiencing a very similar issue but in my case the screen just goes blank as i start up firefox 6 beta or whilst browsing, my GTX560 Ti was running perfectly until i installed 280.19 and the 280.26 drivers so for now i'm rolling back. need a fix for this it's damn iritating when people break something that was working so well
also experiencing a very similar issue but in my case the screen just goes blank as i start up firefox 6 beta or whilst browsing, my GTX560 Ti was running perfectly until i installed 280.19 and the 280.26 drivers so for now i'm rolling back. need a fix for this it's damn iritating when people break something that was working so well

#6
Posted 08/12/2011 01:07 PM   
I had a problem with my system crashing (monitor goes completely black, then after about 30 seconds there is an automatic restart). This happened any time I had more than one window open and I was viewing streaming video. Also, I was unable to connect a second monitor without the same type of crash. I thought that an update in the driver would help. I installed the recommended driver update 280.26, but it has only made the crashing more frequent! /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' />

In reviewing the problems others are having, my problem doesn't seem as severe, but it is still frustrating. Anyone out there have a suggestion on what step I should try next? System info attached, here's a brief summary:

Operating System: Windows 7 Home Premium, 64-bit (Service Pack 1)
DirectX version: 11.0
GPU processor: GeForce GT 220.

Thanks.

[attachment=21985:System Info 2.JPG]

[attachment=21984:NVIDIA System Information 08-11-2011 11-57-29.txt]

UPDATE:

I have been corresponding with NVIDIA customer "live help". Below is the latest solution that they recommended for me.

quote
So now if you perform a clean installation with 266.58, your issue should be fixed. To do this follow these steps:

Please download and save the Driver on the "desktop" using the following link:

http://www.nvidia.com/object/win7-winvista-64bit-266.58-whql-driver.html

While installing the drivers, Make sure that you select "custom" installation and then check all the options including "perform a clean install".


This ONLY SLIGHTLY improved the problem. The frequency of screen going blank incidents has been reduced by about a third. I'll update this post if they resolve the problem...but at this point I'm not very optimistic after spending hours with them over the past week trying different drivers, etc.

Hope the rest of you have better results.
I had a problem with my system crashing (monitor goes completely black, then after about 30 seconds there is an automatic restart). This happened any time I had more than one window open and I was viewing streaming video. Also, I was unable to connect a second monitor without the same type of crash. I thought that an update in the driver would help. I installed the recommended driver update 280.26, but it has only made the crashing more frequent! /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' />



In reviewing the problems others are having, my problem doesn't seem as severe, but it is still frustrating. Anyone out there have a suggestion on what step I should try next? System info attached, here's a brief summary:



Operating System: Windows 7 Home Premium, 64-bit (Service Pack 1)

DirectX version: 11.0

GPU processor: GeForce GT 220.



Thanks.



[attachment=21985:System Info 2.JPG]



[attachment=21984:NVIDIA System Information 08-11-2011 11-57-29.txt]



UPDATE:



I have been corresponding with NVIDIA customer "live help". Below is the latest solution that they recommended for me.



quote

So now if you perform a clean installation with 266.58, your issue should be fixed. To do this follow these steps:



Please download and save the Driver on the "desktop" using the following link:



http://www.nvidia.com/object/win7-winvista-64bit-266.58-whql-driver.html



While installing the drivers, Make sure that you select "custom" installation and then check all the options including "perform a clean install".





This ONLY SLIGHTLY improved the problem. The frequency of screen going blank incidents has been reduced by about a third. I'll update this post if they resolve the problem...but at this point I'm not very optimistic after spending hours with them over the past week trying different drivers, etc.



Hope the rest of you have better results.

#7
Posted 08/12/2011 03:47 PM   
I have the same problem with the 280.26 drivers running on a GTX 560 Ti.

Get it fixed NVIDIA.
I have the same problem with the 280.26 drivers running on a GTX 560 Ti.



Get it fixed NVIDIA.

Core i5 2500K @ 4GHz
ASUS P8Z68-V Pro (BIOS version 3603)
Geforce GTX 680 (Palit Jetstream 2GB)
8GB RAM
Samsung 2333SW (1920x1080)
Windows 8.1 Pro x64
ASUS Xonar D2X
Corsair HX650

#8
Posted 08/13/2011 03:47 PM   
[quote name='Rittsel' date='12 August 2011 - 10:08 AM' timestamp='1313136485' post='1278307']
I've got the same problem with 280.26.
Running on Windows 7 x64 with GTX 560 Ti, I've just been browsing with Firefox 5.0 and it crashed twice in one our.

Event ID 4101
[/quote]

Same thing happen to me while browsing (ref. gaiward gtx560ti, w7 x64, FF 5.0). Turned off HW acceleration (2 days ago) in it and no problems so far.
[quote name='Rittsel' date='12 August 2011 - 10:08 AM' timestamp='1313136485' post='1278307']

I've got the same problem with 280.26.

Running on Windows 7 x64 with GTX 560 Ti, I've just been browsing with Firefox 5.0 and it crashed twice in one our.



Event ID 4101





Same thing happen to me while browsing (ref. gaiward gtx560ti, w7 x64, FF 5.0). Turned off HW acceleration (2 days ago) in it and no problems so far.

CPU: Phenom x4 955 BE (3.2ghz)

RAM: 1x4gb Kingston (1333mhz)

GPU: Gainward nvidia gtx 560 ti (no OC)

MBO: ASUS M5A97

PSU: Seasonic 500W SS-500ET

#9
Posted 08/13/2011 04:20 PM   
One more "Display...and has recovered" today while setting up options in "WeatherBug" gadget. This is really annoying.
One more "Display...and has recovered" today while setting up options in "WeatherBug" gadget. This is really annoying.

CPU: Phenom x4 955 BE (3.2ghz)

RAM: 1x4gb Kingston (1333mhz)

GPU: Gainward nvidia gtx 560 ti (no OC)

MBO: ASUS M5A97

PSU: Seasonic 500W SS-500ET

#10
Posted 08/14/2011 01:53 PM   
[quote name='Vimes' date='12 August 2011 - 10:04 AM' timestamp='1313139862' post='1278331']
As I have previously noted it seems that any of the 280.xx drivers will cause the same "stopped responding and recovery" message / situation for me when installed.
I am using Windows 7 x64 SP1 with my Gigabyte GTX 460 1GB card, which is not overclocked.
The event can happen at any time, whether using Firefox (with GPU acceleration on or off it does not matter)or just idling on the desktop.
Going back to the 275.33 drivers resolves this issue and then the system is back to 100% stability, as normal.
[/quote]

Hello, I registered to let you know what I experienced:
I had the same problems, sometimes black screen while booting Windows at start just before the Windows logo should appear, then I had to push the reset button.

Very often I got the "display driver stopped responding" error and 1 time a blue screen with the nvlddmkm.sys as problem. One time I had horizontal coloured lines on the desktop and when scrolling a picture they were flickering. Most of the times I was browsing with Firefox 5.01 when those problems happened. Hardware acceleration for Firefox is turned on.

Well, I sent my new 3 weks old card back to get a working one. Now I suspect, it was not a hardware fault. /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' />
My card: GTX 560 ti (2 GB RAM) from Point of view, BIOS: 70.24.11.00.00 and driver version 275.33! So they also don't work well, unlike Vimes thought.

Now until I get my card back, I have a GTS 450 (1 GB RAM) and BIOS: 70.06.33.00.52 and with that I had 7 days not a single problem. Hopefully that may help in finding this bug.
System: Windows Vista Home Premium 32 bit, SP 2, CPU Q6600 @ 3 GHz, 4 GB RAM

Error log: [quote] System

- Provider

[ Name] Display

- EventID 4101

[ Qualifiers] 0

Level 3

Task 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2011-08-03T07:42:39.000Z

EventRecordID 420890

Channel System

Computer Sledge-PC

Security


- EventData

nvlddmkm
[/quote]
[quote name='Vimes' date='12 August 2011 - 10:04 AM' timestamp='1313139862' post='1278331']

As I have previously noted it seems that any of the 280.xx drivers will cause the same "stopped responding and recovery" message / situation for me when installed.

I am using Windows 7 x64 SP1 with my Gigabyte GTX 460 1GB card, which is not overclocked.

The event can happen at any time, whether using Firefox (with GPU acceleration on or off it does not matter)or just idling on the desktop.

Going back to the 275.33 drivers resolves this issue and then the system is back to 100% stability, as normal.





Hello, I registered to let you know what I experienced:

I had the same problems, sometimes black screen while booting Windows at start just before the Windows logo should appear, then I had to push the reset button.



Very often I got the "display driver stopped responding" error and 1 time a blue screen with the nvlddmkm.sys as problem. One time I had horizontal coloured lines on the desktop and when scrolling a picture they were flickering. Most of the times I was browsing with Firefox 5.01 when those problems happened. Hardware acceleration for Firefox is turned on.



Well, I sent my new 3 weks old card back to get a working one. Now I suspect, it was not a hardware fault. /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' />

My card: GTX 560 ti (2 GB RAM) from Point of view, BIOS: 70.24.11.00.00 and driver version 275.33! So they also don't work well, unlike Vimes thought.



Now until I get my card back, I have a GTS 450 (1 GB RAM) and BIOS: 70.06.33.00.52 and with that I had 7 days not a single problem. Hopefully that may help in finding this bug.

System: Windows Vista Home Premium 32 bit, SP 2, CPU Q6600 @ 3 GHz, 4 GB RAM



Error log:
System



- Provider



[ Name] Display



- EventID 4101



[ Qualifiers] 0



Level 3



Task 0



Keywords 0x80000000000000



- TimeCreated



[ SystemTime] 2011-08-03T07:42:39.000Z



EventRecordID 420890



Channel System



Computer Sledge-PC



Security





- EventData



nvlddmkm

#11
Posted 08/15/2011 06:41 PM   
[quote name='EasterEEL' date='11 August 2011 - 02:10 PM' timestamp='1313097003' post='1278119']
[i]Display driver nvlddmkm stopped responding and has successfully recovered[/i]

Same Here. I have MSI N560GTX-TI Twin Frozr II

Sound is also lost upon recovery.

Windows 7 Professional 64bit
Direct X 11
Driver Version 280.26
[quote name='EasterEEL' date='11 August 2011 - 02:10 PM' timestamp='1313097003' post='1278119']

Display driver nvlddmkm stopped responding and has successfully recovered



Same Here. I have MSI N560GTX-TI Twin Frozr II



Sound is also lost upon recovery.



Windows 7 Professional 64bit

Direct X 11

Driver Version 280.26

#12
Posted 08/15/2011 08:59 PM   
[quote name='nvtweakman' date='12 August 2011 - 07:30 PM' timestamp='1313137838' post='1278319']
You're not alone. I've seen this problem reported across various forums. Hopefully NVIDIA doesn't wait 'til September release to address it.
[/quote]

its not a driver problem, its the hardware, i've had 5 GF104 based cards come through and all were preoverclocked models from gigabyte/gainward/msi.

the psycho overclocks these guys use are the problem, gigabyte also uses a wrong lower vid voltage for the 460's.
none of the evga gf104's i've updated to have had problems, even with heavy overclocks.

how i wish i could keep one for myself.
[quote name='nvtweakman' date='12 August 2011 - 07:30 PM' timestamp='1313137838' post='1278319']

You're not alone. I've seen this problem reported across various forums. Hopefully NVIDIA doesn't wait 'til September release to address it.





its not a driver problem, its the hardware, i've had 5 GF104 based cards come through and all were preoverclocked models from gigabyte/gainward/msi.



the psycho overclocks these guys use are the problem, gigabyte also uses a wrong lower vid voltage for the 460's.

none of the evga gf104's i've updated to have had problems, even with heavy overclocks.



how i wish i could keep one for myself.



In Memory of Chris "ChrisRay" Arthington, 1982-2010

CPU:Intel i7 920 @ 3.8(D0), Mainboard:Asus Rampage II Gene, Memory:12GB Corsair Vengeance 1600
Video:EVGA Geforce GTX 680+ 4GB, Sound:Creative XFI Titanium Fatal1ty Pro, Monitor:BenQ G2400WD
HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
Case:NZXT Guardian 921RB, PSU:Corsair 620HX, OS:Windows 7 SP1

#13
Posted 08/16/2011 04:32 AM   
I have same problem with this card : [url="http://www.gigabyte.com/products/product-page.aspx?pid=3836#ov"]GIGABYTE GTX 560 Ti[/url]
Im going back to last driver until they fix it. [url="http://www.nvidia.co.uk/object/win7-winvista-64bit-275.33-whql-driver-uk.html"]275.33[/url]
I have same problem with this card : GIGABYTE GTX 560 Ti

Im going back to last driver until they fix it. 275.33

#14
Posted 08/16/2011 09:12 AM   
[quote name='Sora' date='16 August 2011 - 12:32 AM' timestamp='1313469123' post='1279925']
its not a driver problem, its the hardware

the psycho overclocks these guys use are the problem
[/quote]

It's a combination of all of those things..
[quote name='Sora' date='16 August 2011 - 12:32 AM' timestamp='1313469123' post='1279925']

its not a driver problem, its the hardware



the psycho overclocks these guys use are the problem





It's a combination of all of those things..

"This is your code. These are also your bugs. Really. Yes, the API runtime and the
driver have bugs, but this is not one of them. Now go fix it already." -fgiesen

#15
Posted 08/16/2011 12:42 PM   
  1 / 58    
Scroll To Top