• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Nvidia driver crash and recover

E

exia989

Member
So today I just picked up a new EVGA GTX 660 ti sc edition, and it was all freaking awesome for the first few minutes. After awhile, it started doing this thing any time i put a load on it where the screen would go all screwy, weird color squares, and general unresponsiveness. 15 seconds later, the driver would say it failed and recovered.

I have had the card for all of like 3 hours, and I'm starting to get really annoyed with it. I'm running the 314.07 drivers, and im starting to run out of ideas as to how to make this thing cooperate.

Please help!
 
Display driver nvlddmkm crashing and recovering can be caused by instability in other sub systems such as CPU and memory.

Getting weird color squares though would indicate instability in GPU memory. Could be defective memory on the card. Try downclocking GPU core and memory and rerun whatever you were running for troubleshooting purposes.
 
IDK if that card is overclocked or not, but my 670 did the same thing all the time when I had it new with the stock overclock. Had to either bump up the voltage a very minor bit or bump down the boost clock by like 10mhz, and its been stable ever since.
 
People people, lets not jump to conclusions. Before you do anything exia989, install different drivers. This same thing happened to me before, running a game. It would just freeze, be all screwy, purple, lines, squares, everything everywhere. If I waited about 10-15 seconds, it shows the same exact message exia mentioned. I just simply installed different drivers. Since then I have had no problems.
 
What you are describing usually comes from either faulty circuitry or unstable overclocks assuming the drivers are working right
 
I've tried about 3 other drivers, all with the same results. I popped my old amd card back in and it works fine. I'm going to try running it on my buddies rig tomorrow and see what happens. If it does the same thing, I'm taking it back to bestbuy and getting it exchanged. I have not messed with any of the clocks. The more i mess with it, the more likely a faulty card overall is to blame, because it worked just fine for a little while after bringing it home.
 
Returned the card to Best Buy, new one is running like a champ. No indications of any continued issues, so i think its safe to say that old card was just bad, and not something to do with the drivers. Although time will certainly tell 😛
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top