GTX 560 Ti 2GB - Possible driver problem and crashing on Win7 64bit

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

mrmaia

Distinguished
Aug 9, 2011
598
0
19,010
Good morning guys

Yesterday I did a fresh install of a brand new computer and it was working fine. All of a sudden (after ~5 hours of use), my system froze and the video went all crazy (actual photo from my monitor):

2v8ipgi.jpg


In this first freeze, the computer did not respond to anything for like 2 minutes, and then I rebooted it. The POST and the EFI display fine, then in the Welcome Screen the system crashes again, but now after 1 min it restarts.

To isolate the problem source, I ran a series of tests:

• Ran the computer on Safe Mode. It ran nicely.

• Then I turned iGPU on and plugged my computer to the onboard port. Ran nicely again (although the max res I could get is 1280x1024, which looks horrible on my 1600x1050 monitor).

•Then I uninstalled all the Nvidia drivers and let Windows install its default drivers for my GPU. It ran nicely once again.

This makes me think the problem is exclusively driver-related (i had installed Nvidia drivers 266.58, 275.33 and 285.62 and none worked). Funny is, even with the drivers installed EVGA Precision says it has detected no hardware and Virtu says it can't turn on.

My system configuration is this:

EVGA GTX560Ti 2Gb
Windows 7 Ultimate 64bit
Asus P8Z68-V Pro
Samsung SyncMaster 2233

Intel i7 2600k @4.0Ghz
16Gb Corsair Vengeance 1600Mhz
WD Caviar Green 2Tb
Corsair Force 3 90GB
Corsair HX650
Thermaltake Dokker Lite
3x Aerocool Shark Blue
2x Cooler Master Excalibur
Zalman CNPS 9900MAX

Although I had overclocked my CPU, I never touched my video clocks. System and drivers (including the Nvidia ones) are installed on my SSD and everything else on the HDD.

Any clue on what's going on and what can I do to solve this thing?
 


Oh my bad I forgot to mention the first thing I did with the code was google it. I came to this very same page - seems like it's an issue with 100.65 drivers, and for the current 285.62 it's been fixed. Thanks though.
 
okay came across this

Quote -





--------------------------------------------------------------------------------

Related to BSOD (Nvidia: nvlddmkm.sys/0x00000116 or ATI: ati3duag.dll/0x00000XXX)

I would like to share a success story in regards to this error message that hopefully will help others... My specs are below for both PCs.

I received this error message with 3 different video cards and 2 manufactures Nvidia & ATI (the ATI BSOD was a bit different but same results). I did all of the basic and advance steps in troubleshooting including testing all of my hardware components on identical motherboards & power supplies; however, the BSOD would only show up on one motherboard with the video card in the first PCIe 2.0 x16 slot but work fine in the second slot.

The actual issue was related to the North Bridge and the first PCIe 2.0 x16 slot not running the correct voltage for the video card. Needless to say, here are the steps that corrected my issue, from ASUS Support, and reset the voltage for the video card:

1. Uninstall video card driver utilities from Programs
2. Uninstall video card driver from Device Manager/Display Adapters
3. Shut down computer
4. Unplug everything including power connector... wait 30 seconds
5. Remove the video card from the motherboard
6. Clear the motherboard CMOS for 20 seconds (my motherboard has a convenient CMOS button on the back but you may have to use a jumper or remove the battery... follow your MB instructions)
7. Plug in the power and start PC... wait 15 seconds and shut back down
8. Unplug power and put the video card back on your motherboard
9. Plug back in power and start back up... DO NOT modify your BIOS settings yet
10. OPTIONAL: I use RAID drives so I had to turn back on my RAID management in the BIOS when starting up
11. Once Windows loads, install video drivers, restart and see if the issue is fixed
12. If the issue is fixed go back into BIOS update RAM Timings and any other component settings needed




source - http://www.sevenforums.com/crashes-debugging/160970-nvlddmkm-sys-bsod.html
 
also this which I have read a few threads stating changing ram helped
even though the ram passed Memtest
it was the RAM causing the error

quote


Well, the RMA guy tested the GPU on their test machine and it worked fine, through various tests - no issues whatsoever. They ran memtest on my RAM and again no errors. They tried another vid card on my machine and same nvlddmkm errors. They pulled out my RAM and tested it on their test machine - no issues but as soon as they put that same RAM back into my machine - the nvlddmkm errors came back. Eventually they just tried another set of RAM sticks, same manuf but slightly better model and no more nvlddmkm errors!! They tested extensively for around 3 days with various tests and no issues whatsoever.

So I've just had my system returned back yesterday and it's been running fine, not a single error (so far) so I'm smiling again - fingers crossed.

Sum up:
I thought my vid card was dying due to the artifacts and inability to run anything remotely 3D but I was wrong! It seems this nvlddmkm error is a very general error and causes symptoms that point the finger at drivers, OS and other hardware! There seems to be compatibility issues between RAM-mobo-GPU that is not well understood (at least by me).

source - http://forums.techguy.org/windows-7/925197-nvlddmkm-sys-tdr-bsods.html

found a few threads where changing memory sticks solved the problem

I would try the other power on fix first
then try changing RAM if possible
 



Boy, when I saw this my eyes started shining again. I tested it and... did not work!

Also the memory thing did not work also, I popped in a stick of Corsair Dominator (only 'same manuf but slightly better model' i could think of) and same thing.

Now looking at my BIOS monitor I came across to this:

pc5jq.jpg


Can those voltages be any trouble? Also I don't know how to change them, the values shown are read-only.
 
no those voltages dont get changed

did you try running with only one stick of different ram?

might be something with ram timings

the CAS,RAS etc

since you have an Asus board I would contact Asus support
sometimes you get lucky and get somebody who knows their stuff
 


Thank you for the help.

Yes, a single stick. The RAM timings are correct in the BIOS, so I'm almost giving up on the issue. Will contact both ASUS and EVGA though.
 
First I found someone with same problem turned off Aero theme and just used Windows basic theme
and it worked
boot with x8 slot and try that

if that doesnt work then carefully read and follow this
http://www.sevenforums.com/crash-lockup-debug-how/63320-stop-0x116-video_tdr_error-troubleshooting.html

that is a in-detail guide to the 116 stop error

BTW I lost my rig for over 3 weeks due to a mobo failure and I was fortunate
to have a decent laptop to use but it SUCKED

so I REALLY REALLY want this to work for you :)
 


Thank you both malmental and king smp for your effort into this issue. I definitely appreciate it.

Disabling Aero was one of the first things I tried. Needless to say what happened.

This Win7 link is bookmarked here for weeks. Of all the things it suggests, I haven't tried yet stress testing the card and resetting the pagefile. Now, even if I run Furmark on the x8 slot (which I'm using right now), will it be able to detect hardware problems?
 
I dont think so
Seems to be a voltage problem to the card being supplied to x16 slot
remember your Quadro card was a much lower wattage card than the 560

try resetting pagefile
long shot but easy to do

and I am sorry I am out of ideas after that
contact Asus support is the next option
if the person sounds competent then great
if the person sounds ignorant then immediately hang up
and call back until you get one the good ones

also I would contact Asus first
think it is mobo related not GPU

Wow did I want this one to work

Please let us know (use Private Message feature just click my Avatar)
how this works out

I do get so emotionally involved in these things :)
 
also when talking to Asus about RMA
let them know you have read of the problem with their Mobos on forums
with the same issue
try to get a different model Mobo (even if you have to pay a little difference if possible)
or at least see if there is a new revision of the same mobo
you dont want to get the same model RMAd and have the same problem
 


Well, in the end resetting the pagefile did not work and Furmark pinned my GPU temp at 75°C even at xtreme burn-in.

I'd contacted ASUS, even linking this thread for a complete story. Lets see if I can get something.

Thank you very much friends!
 
Hey Mrmaia

I just bought a Corsair 90 GB Force 3 Series SSD and am having the exact same problems as you i have been trying everything to get it resolved i find doing a simple CHKDSK on the SSD drive saves the issue from happening as regulaly but does still persist i also have a EVGA GTX 460 so the hardware seems comparative however i am pointing this at the SSD as before using my older drives i had no issues. Whats the status on your side there? im sure we can figure this out i have also rolled back drivers but this has not helped? Did you get the latest BIOS for your SSD when you bought it before your install?

Let me Know Rob.
 


Well, I wouldn't say I'm glad to know someone else is experiencing the same problem as me, but... well, somewhat comforting.

The only things I didn't blame were the SSD and Windows. I'll try running CHKDSK, plugging the board and see what happens when I get home. Now you're giving me hope, Pilk! 😀

I'm currently using the computer with the card in the x8 slot, and using my regular CAD programs hadn't disappointed me yet; to be honest I'm pretty happy. I did get a "driver has stopped responding and recovered" message twice but I'm not bothered.

I've contacted both ASUS and EVGA and both didn't even care to look into my problem; they said to contact my resellers (what I want desperately to avoid, especially with the video card) and start the RMA.

Also I didn't download anything to use my SSD (is there a BIOS for SSD? WTF?), I just cabled it and made it work.
 
Hear me out... I skimmed through this thread so im not 100% sure you said if you disabled realtek drivers or not. These have issues with Nvidia drivers (all of them).
Also if you use Logitech, sorry King, there is a .exe file called Khalscroll. Find that in the processes tab in task manager and end the process. It sounds like its a faulty card
but like I said I skimmed through this thread.
If it says nvlddmkm.sys- it could be everything.
 



the realtek drivers are worth a try
but if he is using onboard sound with Realtek
then what does the OP use for sound?

also with my mice and keyboards I rarely use the Logi software
just what comes with Win7

I have installed the Logitech Setpoint drivers to check them out
but never noticed that process
and I am a freak for checking out running processes

but it couldnt hurt to turn it off either
just does smooth scrolling in web browser to imitate a smartphone scroll

and BTW the Logitech thing is just to poke fun at Fanboys LOL

 
if it is a display driver issue also disable fraps and or precision. turn off aero. disable all audio/record devices not being used. decrease clock speeds, and increase fan. Replace the video card...i guess. These were the ones that I have heard work. well, and the khalscroll.exe. Keep us updated please
 
mordax86, thank you for your help but I've done absolutely everything you told me to do before, and nothing works as you can see from older posts.

Realtek drivers indeed have issues and I disable them to use the Nvidia audio drivers (which I think that work better). Oh well, and I don't use anything from Logitech.

I still have to try the chkdsk trick though, will do it tomorrow and post the result here.
 
HI Mirmira

Sorry its taken me so long to reply i had my issue sorted out in about 4 hours of re trying every driver under the sun, what i have found is that a particular firmware on EVGA cards does this and that is why so many people have this issue try this, this is what i did to sort my issue out. Did you have a dual screen setup at any time prior to your problems? if so then you probably have the same issue. (this is by the way a EVGA'S fault!)

What you need to do is going into advanced display options and set up dual display even if you do not have a secondary screen, it will give an option to forcefully extend your display to a secondary monitor, it gives you a list of resolutions to chose on the "non existing screen" just select the lowest res as you will not be using something that is not present, see if that does the trick, also if you have a spare screen or projector plug it in and use the extended display setup there instead of using the forcing option.

Let me know if you need a more visual guide to doing this but im sure you'll be alright.
 
I have a very similar problem, though my machine is a few years older. I have dual GTX 280s and am running vista (been too lazy to upgrade). I encountered this problem for the first time a couple of months ago right after a reboot. The system appeared to boot up fine, but right after vista loaded the screen changed to something similar to your photo. Occasional restarts over the next few days showed the problem appearing about 50-60% of the time. However, if I didn't experience the problem immediately after Vista loaded, then the machine would be fine (at least until the next reboot).

So, I put off dealing with the problem and just left my machine on for a couple months. I had to restart the other day, however, due to a pretty hard GPU related failure. On every restart I get this artifact-laden screen the moment after Vista loads. Starting in safe mode works fine; starting with the full OS without the nvidia drivers works fine; starting the full OS with the nvidia drivers fails.

About a month before the first occurrence of this problem I had memory issues. Prior to that, I'd been overclocking the memory and had to crank down the voltage to resolve the problem. This makes makes me suspect the RAM sticks, though I haven't done a mem test.