Display driver stopped responding and has recovered

[Sgun]

For people having the "Display driver nvlddmkm stopped responding and has recovered" problem and the following Kernal-Power BSOD, try using a VGA cable to connect your monitor to the graphics card instead of a DVI cable. This worked for me for some reason, and I had no problems for over a week.

DVI is better than VGA ("DVI eliminates the analog conversion process and
improves the connection between source and display"), but I dont see any difference tbh. It doesn't slow down anything (for me).

Don't know if this fixes the problem for all people. Let me know please

 

[yowanvista]

This did not work for me

 

[MissMontenaro]

try using a VGA cable to connect your monitor to the graphics card instead of a DVI cable.

Thank you SOOOOO much. I have tried everything. Nvidia drivers, printer drivers, all the usual generic stuff. I was tearing my hair out. This worked for me. I award you 5 internets sir !!

 

[7xpm]

wow unbelievable

I have searched high and low and it appears this problem has been going on for at least 2 years since VISTA. And still no fix? WoW. It happens enough on this brand new 7 system to be highly annoying. Does microsoft even care? I see people disabbling stuff to try and resolve, but you would think a person shouldn't have to cripple thier dispaly settings for an answer.. I'm using a regular vid cable and still happens often..

Sounds like a 2 year old bug they still can't figure out. WOW Also seems to be accross the board, different video cards, systems, processors, etc..

People who upgrade from XP only start having problems after.. worked fine before..

 

[EmilG]

Put my wife on the list too.
She has Win7x64, 8800gtsv2 Q6600@3g.

My systems ok.
I have Win7x64 8800gts E6600@3g.

I wonder if it has anything to do with the processor going into it's slowdown mode, I forgot what the mode is called. I have it activated in the bios.
I'll turn it off and give it a try.

 

[EmilG]

I did a few things:

This I got from someone on the net, can't remember where.
Control Panel --> Power Options --> Select Power Plan
> Change Plan Settings (I kept it at 'Balanced')
>> Change Advance Power Settings
>>> (expand to) PCI Express
>>>> (expand to) Link State Power Management
>>>>> (select) OFF

Bumped my video card fan speed from 38% to 65%

Installed the newest Win7 drivers for nVidia cards


So far so good although it didn't happen very often for her, the weekend should tell.

 

[yowanvista]

I still get this error and I've tried everything

 

[Sgun]

yowanvista

ok, get riva tuner and underclock ur GPU, and uninstall Nvidia Physx.

Try this and see what happens.

 

[yowanvista]

ok, get riva tuner and underclock ur GPU, and uninstall Nvidia Physx.

Try this and see what happens.

I've already done this with no success, it's a driver issue for me

 

[EmilG]

Unfortunately this did not work either.

I did a clean install with the nVidia 191 drivers.
Been good since Saturday, fingers crossed.

 

[yowanvista]

I fixed NVLDDMKM error by using modded drivers from tweakforce.com instead of Nvidia's crappy drivers

TWeaKFoRCe.CoM your source for the latest Video Drivers

 

[cgrox]

Display Driver problem

My laptop is brand new off the shelf and I have experienced the same problem on occasion. Maybe once a month, but I dont use any graphic intense applications such as games, etc... (yet). Any thoughts???

 

[slaweklatka]

This Might help

I had exactly the same problem. And it looks like using drivers from microsoft for my ATI graphic card has solved the problem. You can try simply unistalling the drivers from control pannel or reinstalling windows and not installing the drivers from your card manufacturer (Ati, Nvidia).

And honestly I can't feel or see any difference in performance. Games and apps work as good as before.

Hope this will help. Please let me know if this solution solved your problem.

 

[alucardx]

I recently had to fix a video problem for a guy - "Display Drivr stopped responding & successfully recovered". It was a ATI Radeon HD 4300/4500. After trying a dozen solutions online, I found one myself that worked. I started up the CCC program, can't remember where the exact setting is but it's a panel with the temperature gages down the right hand side. There was a setting "Enable ATI OverDrive", when I disabled that everything seemed Ok. Seems like a lot of people are having similar issues. Hope this helps somebody.

 

[talcott]

After installing Windows 7 Ultimate on my new notebook with Vista Premium 64x I’ve been getting the following error: Display Driver Stopped Responding and Has Recovered. Sometimes my system will freeze for a little while then the screen will go black and reappear. And I couldn't save new power plans settings too. I could fix this making a full install of W7 instead of an upgrade. Hope this helps somebody

 

[2billy3]

Feature name="CoreClockTarget_0"
Property name="Want_0" value="40000" note: previous value should be "15700"

Feature name="MemoryClockTarget_0"
Property name="Want_0" value="90000" note: previous value should be "30000"
Save the file and close it.


when I went there there and opened that with the notepad tool it was just
"<Profile />" that... what should i copy/paste to the notepad??

 

[dwec]

I saw the thread that the issue has been solved but dont see any feedback that the solution is working or not.

 

[alucardx]

My last solution, about disabling the "Enable ATI OverDrive" did not hold. I've tried many of the fixes found online but nothing seems to work. The last thing I tried was a BIOS update. It's someone else's computer so I'll keep you updated as soon as I'm updated.

 

[dwec]

I did that too (&others posted in online too) but all doesnt help anyway, then i raise a trouble ticket to my GC vendor. They suspect it might the defect of the GC, they asked me to send back for checking. Now i cant use my rig until my GC back from RMA.

 

[EmilG]

I posted about a year ago that I've switched to the nvidia drivers, it still works with them. I accidentally "updated" to microsoft drivers at one point and the problem came back. Again switching to nvidia drivers fixed it.