splay Driver nvlddmkm Stopped Responding - 197.44

I know there are many topics about this but I am unsure about how to fix this issue.

I have a GT 330m. Temps are fine. I did overclock it and I figured it had to do with overclocking, after about 15 minutes of gameplay the game would lockup. So I lowered the clock speeds.

Now they are:

700/900/1575

I was playing Just Cause 2 for an hour and it was flawless. Died a couple of times, reloaded checkpoints, etc. Thought I was good to go. Then I go into a car and start driving like I was doing before, same area, and just crashed! there was a lot less detail to be loaded driving the car than flying in the plane which I was doing before that.

Why do my games keep locking up?!

Running Windows 7 64bit, 6gigs of ram, core i7 720qm

 

What model/manufacterer? What are the "fine" temps? Do other games cause this problem? Have you used GPU stress-testing programs?

 

You will get "driver stopped responding" error sometimes if you have overclocked your GPU too far, sometimes it has nothing to do with high temp at all, it will happen even if you have perfect fine temp.

I used to get lots of these errors when I tried to overclock my card. Lower your clock speed a bit will usually make the error disappear.

 

@Forge, Sony VAIO F series. My card did not exceed 65C.

@lidowxx, Blahh if I lower my clock speeds Just Cause 2 is barely playable.

Could I put my GPU clock and Memory clock back to default and make the shader clock more? That's what I found increased my performance a lot.

 

If you want to keep your GPU alive for more than just a few months, you really want it to run stably. You don't need to set everything back to default speed, you can just try to decrease the core/shader clock by a small amount each time and then stress test the current clock using furmark, until you find you are not getting the same error.

Keep in mind that you'd better off keeping the core/shader a ratio of 1:2.5 to maintain stability. And it's not wise just to overclock just shader and leave core alone. Also overclocking video memory can be very dangerous to your card because it doesn't have its own temp sensor, and make things worse, they are usually the first thing to fry when exposed to abnormal temps.

 

I looked up the reference clocks. Man, no wonder you're crashing. That overclock looks very high, and from what you're telling us it's too high for your GPU to handle. Start off with a 5% overclock over reference and keeping raising clocks and testing stability from there.

Like Lidow says, do relatively little to the memory. Memory speed is more important for high resolution, high powered video cards, so the 330m won't benefit much from a memory overclock.