Need help with Nvidia driver problem while folding!

[ScOuT]

Well...My GTX 260 graphics driver has been crashing running F@H the last week. I have never had any issue of any sort until now folding. It will run several work units just fine and then all of a sudden the "graphics display driver has stopped working but has recovered" message will pop up. This of course stops the work unit and starts a new one Here are a few screen shots...

It will just crash for no reason

Windows problem screen shot...NVLDDMKM has stopped

Windows error log

Temps are great...low 60c range running GPU wide open That is considering it's almost 30c here in Germany...heat wave Normally it runs in the high 50c range (57c-60c)

Things I have done
1. Uninstalled the graphics card and drivers and reinstalled it many times. Tried different drivers including the original one on the eVGA CD. Scrubbed all old drivers also many times.

2. Reset graphics card and all wires many times...thought maybe a bad connection

3. Searched all over Google for the error...found a few things about a certain Windows update...many people have had success by uninstalling it. Tried that and it worked good for a day.

Anybody ever had to deal with this? Got any suggestions

 

[mep916]

Have you made any changes to your PC (installed new hardware) since the errors started to occur?

 

[ScOuT]

A new Zalman fan controller and an 80mm fan for a little extra air That's all...other than that...everything is the same It literately started from one day to the next.

****EDIT****

I saw in another forum where a guy had the exact same problem and he replaced the power supply and it solved it Hopefully that is not going out...it's only about 10 months old

 

[mep916]

A new Zalman fan controller and an 80mm fan for a little extra air That's all...other than that...everything is the same

That shouldn't be responsible for the errors you're having. What RAM are you using? I ask because, back in the day, I had the same driver issues due to my Dominators not acting right with my 680i board and Ultras in SLi. i know you're not running a dual card config, but eVGA told me that certain RAM configurations can cause this error. When I replaced the dominators with XMS2 sticks, then went on to some tracers, the error disappeared. I did everything you did too. Wiped drivers, tried different versions, checked and double checked connections, etc... It's a bitch.

 

[ScOuT]

It's all over the eVGA forums...Google the NVLDDMKM.SYS and you get hundreds of posts everywhere.

One guy in eVGA forum RMA'd his card for a new one...problem solved. One guy changed RAM...just like you stated...problem solved. One guy changed RAM timings...problem solved This sucks already.

Damn :gun:

****EDIT****

It just did it while I was typing this...Oh the irony, LOL

 

[ScOuT]

I'll start with RAM timings and give it a run tomorrow. I have 4x1GB Kingston Value RAM in my daughters computer...I'll try that if timings don't work. After that...i7 build

 

[mep916]

Try the timings and see what happens. Do you have any other memory you can try out?

 

[bomberboysk]

Is yokur card overclocked atm? Could try lowering that down if it is... If not, could possibly be memory voltages not correctly set in bios, unstable overclock on cpu, etc... I used to get that error alot frmo my card overheating when i forget to set the fan speed to 100%, but your card doesnt seem to be overheating..

 

[ScOuT]

I changed all the timings to "auto" and I'll see what happens.

Here is how "auto" set them at. G Skill says 5-5-5-15 2T @1.8v...we'll see what happens.

I do have some Kingston RAM I can pull out of my daughters computer and give that a run also.

I reinstalled F@H maybe that will help How do I get F@H to auto start when my computer starts? Every time I have installed it, it always auto starts...this time not

 

[ScOuT]

Hey I tried a different approach. I thought maybe it's the WU and the program itself...I searched the F@H forum and many people are failing the 57** series WUs with GTX2** series card They have threads about it...all the failures are identical to mine.

They are working on pin pointing the problem now. It might be bad work units and one of the mods said they might ditch those units because of all the problems.