Sometimes while I'm at the load a flight screen, or occasionally during flight, I get a black screen for about 1 second. It recovers and this message appears briefly: "Display driver nVidia windows kernel mode driver version 191.07 stopped responding and has recovered successfully".My specs are: core i7 920 o/c to 3.77 gHz with Asetek liquid cpu cooler, EVGA GTX285 1GB video with 191.07 driver, EVGA X58 Micro mobo.Peak temps are under 50C, and I have a 750 watt PSU. Running Win 7 64 bit professional.I searched the web and got mixed results .... some folks say to move up to the latest drivers, others say fall back to the 18x.xx series.Anybody had this issue and resolved it? krswen

Your CPU overclock is unstable. I've had the same problem before when pushing my CPU o/c too far. You either need to adjust your voltages or turn down your o/c a bit.

Hi,I had the same problem, my overclock at 4.1GHz is fine. Take a look at this web page that discusses this problem, it helped me resolve my problem.http://www.microsoft.com/whdc/device/displ...dm_timeout.mspx

Sometimes while I'm at the load a flight screen, or occasionally during flight, I get a black screen for about 1 second. It recovers and this message appears briefly: "Display driver nVidia windows kernel mode driver version 191.07 stopped responding and has recovered successfully".My specs are: core i7 920 o/c to 3.77 gHz with Asetek liquid cpu cooler, EVGA GTX285 1GB video with 191.07 driver, EVGA X58 Micro mobo.Peak temps are under 50C, and I have a 750 watt PSU. Running Win 7 64 bit professional.I searched the web and got mixed results .... some folks say to move up to the latest drivers, others say fall back to the 18x.xx series.Anybody had this issue and resolved it? krswen

Cause and effect. I had that problem. I lowered my CPU clock. The problem was no longer repeatable.

Cause and effect. I had that problem. I lowered my CPU clock. The problem was no longer repeatable.

I've seen this same issue also with an unstable overclock. Bumping up the CPU Vcore voltage one step in the BIOS was enough to fix it for me. If you've got temps <50 deg under load, you should have plenty of headroom to push the core voltage up another step or two (but stay below 1.45v).I'd start there followed by a good 3-6 hour test with Prime95 or OCCT. If that doesn't fix it, then start looking at a driver change.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Hmmmm, interesting. Digital Storm built the rig for me and ran Prime 95 for 24 hours to establish stability (supposedly). Currently the vcore is 1.27.Would you go into the BIOS or use ELEET?I may have mispoke about temps .... CPUID hardware monitor lists peak CPU temp as 57 C, but the i7 920 core temps as 67 - 70 C under load.Still bump the voltage, or back off a bit on the O/C? And if the latter, what do I adjust?krswen

Hmmmm, interesting. Digital Storm built the rig for me and ran Prime 95 for 24 hours to establish stability (supposedly). Currently the vcore is 1.27.Would you go into the BIOS or use ELEET?I may have mispoke about temps .... CPUID hardware monitor lists peak CPU temp as 57 C, but the i7 920 core temps as 67 - 70 C under load.Still bump the voltage, or back off a bit on the O/C? And if the latter, what do I adjust?krswen

I'd bump up the CPU Vcore a notch, and also look at the IOH (Northbridge), IOH/ICH I/O and ICH (Southbridge) voltages as well. If the cores are running close to 70 deg C with FS running, you don't have a whole lot of room to play with. If those core temps are only seen during a stress test like prime95 then you should be in the high 40s or low 50s with FSX running, which leaves plenty of room to push things a little harder.Have a look at eVGA's X58 overclocking guide--it has a good list of starting points for the voltages. I run IOH at 1.40v, IOH/ICH I/O at 1.65v, and ICH Vcore at 1.25v in my 4.4 GHz overclock profile.eVGA X58 Overclocking GuideCheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

I'm sorry but this is not always the case, I've got a machine that is guaranteed stable with an overclock that can prime95, OCCT all week long and pass no problem, but it still gets these brief black outs and driver restarts with an Nvidia GTX285. Its got nothing to do with the overclock, in my case its the god awful shite drivers from Nvidia that are the problem. I've gone back to 182.5 yet again for the millionth time because that driver still appears far more stable than anything that has been released by NV in the last 12 months. It still falls over every now and again but its still better than any driver you can get now. So please stop telling people to bump the Vcore of their processors, if it goes wrong are you going to pay for a replacement?...... Yeah I thought not.

I'm sorry but this is not always the case, I've got a machine that is guaranteed stable with an overclock that can prime95, OCCT all week long and pass no problem, but it still gets these brief black outs and driver restarts with an Nvidia GTX285. Its got nothing to do with the overclock, in my case its the god awful shite drivers from Nvidia that are the problem. I've gone back to 182.5 yet again for the millionth time because that driver still appears far more stable than anything that has been released by NV in the last 12 months. It still falls over every now and again but its still better than any driver you can get now.

Stability in one app does not mean stability across the board. As good as OCCT and Prime are, they're not a guarantee that every app will run without issue. I've had the exact same issue as described by the OP on an overclocked system (E8400 @ 4GHz) that was stable in OCCT linpack and every game I ran but one, which happened to be that which I played the most at the time (Titan Quest). I reduced my o/c as adding more voltage was simply not an option (already running more volts than the official maximum) and the problem was resolved.

So please stop telling people to bump the Vcore of their processors, if it goes wrong are you going to pay for a replacement?...... Yeah I thought not.

Processors don't fail because you bump up the Vcore by one notch. What an absurd remark.

I'm sorry but this is not always the case, I've got a machine that is guaranteed stable with an overclock that can prime95, OCCT all week long and pass no problem, but it still gets these brief black outs and driver restarts with an Nvidia GTX285. Its got nothing to do with the overclock, in my case its the god awful shite drivers from Nvidia that are the problem. I've gone back to 182.5 yet again for the millionth time because that driver still appears far more stable than anything that has been released by NV in the last 12 months. It still falls over every now and again but its still better than any driver you can get now. So please stop telling people to bump the Vcore of their processors, if it goes wrong are you going to pay for a replacement?...... Yeah I thought not.

Nope, it's not always the case. Nobody's offering a Doctor Good one-flavor-cures-all panacea here. Just some ideas, and some lessons from personal experience. What worked for me may not work for someone else, but one thing is for certain--it did work for me, on a similar system, with a similar problem.Intel's spec for max Vcore on an i7 is 1.55v...he's running his overclock at 1.27v, so there's still a LOT of headroom to play with there. Bumping up his Vcore a step or two (while keeping an eye on core temps) won't hurt anything. Anyone afraid of such trivial experimentation with hardware parameters that are well within Intel's design limits probably shouldn't be messing with overclocking at all anyway.You'll also note that up-thread I suggested some minor experimentation with voltages (because it worked for me, and I know others that had black-screen issues that went away after backing down an overclock), and then a driver change if that didn't work. There's also the interesting prospect (that I haven't personally had a need to try) of changing the TDR threshold and recovery parameters in the registry as described in the article Mike linked.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO