Sign in with
Sign up | Sign in
Your question
Solved

Nvidia - Display Kernel stops responding

Tags:
Last response: in Graphics & Displays
Share
January 19, 2014 11:28:50 AM

Ok, so I believe every1 has a lot of problems. Ever since I reinstalled Windows 7 since I transferred to my Solid State which is 128GB and a 1TB HDD I keep getting the "Nvidia Driver 332.21 kernel mode display has stopped responding but now has recovered" thing.

EVGA GTX 560
January 19, 2014 4:17:53 PM

I've seen this before too. Windows is designed to detect video card lockups and prompt the video card to stop what it's doing. If the video card doesn't respond, Windows forcefully flushes out the video card's tasks, and resets both the video card and the Windows display driver, resulting in the message you get after a black screen, I'm guessing.

This feature was implemented to allow the system to recover from graphics-related crashes without having to completely reboot.

If you're video card is actually locking up, that's a different problem entirely. However, if windows is just misbehaving, there's a way you can disable this feature in the registry. I forget which keys you have to add or edit, but you could probably look it up.

Keep in mind though that, if you do this, Windows will not automatically recover from video card errors. You'll have to reboot your computer any time your video card freezes. If that's actually what's happening... I don't know what to say. Have you dusted it out recently?
m
0
l
January 19, 2014 4:26:11 PM

Like the above Post says.

Usually a fresh Install of your Display Driver Fixes this. In your case, Roll back to 331.82.

Video Drivers are funny. Every once in a while you'll find a driver that just hates your Windows/System Config
m
0
l
Related resources
January 19, 2014 5:12:25 PM

I just dusted Yesterday and now I tried playing league of legends today and whenever i try to do something the screen just blacks out for a few seconds but I havent seen message saying stopped responding so probably a bad card or its loose.
m
0
l

Best solution

January 19, 2014 5:14:59 PM

Or a Buggy Driver....

A Display Driver crash isnt the only time you can have a Bad Driver. FPS Drops, Artifacts, Display Driver Crashing etc...

You could try readjusting the card in the PCI-E Slot.
Share
January 19, 2014 6:56:33 PM

Just did that 30 minutes ago since the screen kept bugging out when playing league now its fine. Havent had problems after I turned off one thing on Power options for the driver kernel.
m
0
l
April 6, 2014 7:58:57 PM

Justin Watson said:
Just did that 30 minutes ago since the screen kept bugging out when playing league now its fine. Havent had problems after I turned off one thing on Power options for the driver kernel.


Sorry for necropost, but what exactly was the "power option for the driver kernel" you did? I'm experiencing similar issues. Thanks.
m
0
l
April 7, 2014 4:31:24 AM

AEM said:
Justin Watson said:
Just did that 30 minutes ago since the screen kept bugging out when playing league now its fine. Havent had problems after I turned off one thing on Power options for the driver kernel.


Sorry for necropost, but what exactly was the "power option for the driver kernel" you did? I'm experiencing similar issues. Thanks.


To be honest I dont remember what it was. But did you try installing an older version of the Nvidia or what version is urs on?
m
0
l
April 7, 2014 6:42:28 AM

Well, I've rolled it back all the way to 322.21 and it still happens. This issue has only been happening for the past two months or so and I've had this GPU since August of 2013. I've literally tried every single option there is out there and none have worked. Funny thing is it usually only happens to source games and GPU intensive games don't cause anything. I don't know what to say...
m
0
l
April 7, 2014 7:18:02 AM

AEM said:
Well, I've rolled it back all the way to 322.21 and it still happens. This issue has only been happening for the past two months or so and I've had this GPU since August of 2013. I've literally tried every single option there is out there and none have worked. Funny thing is it usually only happens to source games and GPU intensive games don't cause anything. I don't know what to say...


Have you tried taking the graphics card out and putting it back in?
m
0
l
April 7, 2014 3:50:27 PM

Ok so I think this is the driver that fixes it. I first reseated my GPU, then got the beta driver (which was released today lol). Shader Cache was on and power management was set from adaptive to max performance. Be sure if you have Powermizer to disable that too.

I played CS:GO for 30 minutes free of stutters or black screens (knock on wood). I noticed temps were around 69-72C versus the constant 77C and GPU load was around 70-80% and occasional drop to 50% as opposed to the constant 90-98%. I have reference 660 ti.
m
0
l
April 13, 2014 7:35:05 PM

simmons33 said:
Like the above Post says.

Usually a fresh Install of your Display Driver Fixes this. In your case, Roll back to 331.82.

Video Drivers are funny. Every once in a while you'll find a driver that just hates your Windows/System Config


So true.

I just found myself in a situation where I had to replace my old E7400 CPU and corresponding MB. As it turned out, I was given an opportunity to pick up a Core i3, MB, and 4 Gigs of 1600 DDR3 on the cheap, so I did it as I don't need much of a system. I put my old 9800 GT vid card in and all went well for install of new Win 7 Ultimate but soon after running, I started getting these messages and BSOD crashes. I tried the "bandaid" solution of editing the registry to add a QWord delay value, which seems to be used widely. It didn't work for me, so I decided that my vid card was just too old and must be replaced. I went to see my favorite computer shop and explained the situation to my favorite tech, and he discouraged me from buying a new graphics card. He said that he's had to try up to 10 drivers to finally find a stable one in some situations, so I went home and started to approach the problem with better logic.

MY 9800 card was made circa 2009, so I searched the web for Nvidia drivers for 64 bit WIn 7 for it in 2009 and found references to version 295.73 as being a good one for that era. I downloaded it, uninstalled my other one (important to do, I believe) and installed 295.73. It works like a charm and my system is wonderfully stable now. The error message does quote the driver version number, after all, so wouldn't it made sense that that's where the real solution should be found?

Hopefully this helps.
m
0
l
May 4, 2014 12:56:24 AM

Well I tried all damn setups but no results,, I was using Quadro 5000 with windows 7 pro 6 bits and when I upgrade my window to 8.1 pro my life turn to misery.. I sent the graphics card to service center and I bought new Quadro K 4000 but the result is worst!!! I don't know what to do!!!!!! I can't work and finish any project,, each 3 mins my screen turn to black KERNEL DRIVER MODE HAS CRASHED AND RECOVERED some time never recover unless i do force restart using restart button in the case

The only thing i can tell you all I was too damn striped to invest a lot in NVIDIA (Quadro 4000, Quadro K 4000, Quadro 5000, Quadro K 5000 for Mac) cuz I run 4 workstation at my home and doing high end graphics for international clients but now I can't even earn good amount of money cuz of rabish NVIDA drivers

I decided to go for AMD PRO graphics card future wise much better preformance and less problems
m
0
l
!