560ti or Driver problem?

N

NotSoSimple

[H]F Junkie
Joined
May 17, 2003
Messages
14,618
I just purchased a MSI Twinfrozr 560ti from a member here on the forum. Have had it 1-2 weeks and it seemed to play awesome. I go to play BF3 last night and horrible texture issues. So I loaded up the newest beta drivers and I get the same thing. Tried a restart, and now I sometimes get an error that the graphics driver crashed. I rolled back to the latest release (non-beta) and still have the same problems. Did a repair of BF3 and it came back saying no issues/corrupt files. Some rocks are green and flicker, black boxes over some of the vehicles... Any help? It is making it unplayable. I was able to play for 2 weeks no problem. Before this I had a 9800GT and my system was rock solid.

System:
Win Vista 64-Bit
Asus Rampage Formula
Q6600
8GB RAM
MSI Twinfrozr 560 Ti
 
Did you trying running driver sweeper and reinstalling the drivers?
 
This is going to sound weird, but have you tried powering down the PC, and unplugging it for 5 minutes. Just try it first.
 
Nothing you do will "fix" this except to run BF3 on High instead of Ultra. I have the exact same problem with BF3 on Ultra with my 560 ti twin frozr ii and have research this issue extensively. It seems to be vram related and is most likely something EA will need to fix with the game. The odd thing is FPS do not suffer, just horrible artifacts on certain maps.

The "display driver has crashed" issue is also a very well known issue with the 560 ti in general, just try a different driver, some do it less than others. Think I'm on the 290.36 and havent really has this issue lately.
 
I run two of the Palit GTX 560ti 2gb versions in SLI and I still get the artifacting issues that you describe. I also get a random system crash every time I play BF3 but nothing else does it. Its always related to drivers, so I also dont know what to do. Not to thread jack sorry
 
Last edited:
Hmm, thats strange since most of what I've seen people with 2gb 560's do not encounter this issue.

Do you get artifacts on all maps? or only Caspian, Firestorm etc..
 
Caspian and one other that I cannot think of the name are the artifact maps. As far as the crashes I can play for a few hours sometimes before a crash or only 20 min. When the crash happens I lose video input on both cards, the fans kick into high and the system reboots. Only game that it does is BF3, not Rift, not BF:BC2 nothing else I play does it.
 
Are you running the game on Ultra? What happens if you run it on High instead? Do the artifacts go away?
 
Game is running on high actually. Artifacts on Karkand, Sharqi, and Caspian.

Weird though..I gave up on it and shut down my desktop for a couple days. Came back, everything is playable as normal. I have no idea...
 
NotSoSimple said:
Weird though..I gave up on it and shut down my desktop for a couple days. Came back, everything is playable as normal. I have no idea...
Click to expand...

In the 3rd post of this thread I said: "This is going to sound weird, but have you tried powering down the PC, and unplugging it for 5 minutes. Just try it first."
 
NotSoSimple said:
Weird though..I gave up on it and shut down my desktop for a couple days. Came back, everything is playable as normal. I have no idea...
Click to expand...

I have the same card and you might be seeing the same issue as me... Do you run your pc 24/7??

If so...unfortunately...I'd almost bet money that you'll start seeing the same problems again in about 7-12 days from when you reboot your computer last.

I've had an MSI 560ti (same card) for about 8-9 months now and I've been fighting this issue the whole time. I've been through all my hardware because I initially thought it was the graphics card and so I had it replaced with a new one and saw the same issue. So I figured it must be another piece of my hardware.

Here's the the problem in a nutshell. If you run your pc 24/7, never powering it down then after about 1-2 weeks of time you'll start getting bsod/artifacting/momentary black screens in games or desktop/black momentary screen followed by display driver not responding but has recovered message/etc. Once you start seeing these problems they will likely persist (sometimes so frequently that it forces you do take some sort of action and sometimes with only once or twice a day) until you FULLY POWER DOWN your system. And I mean...pull the plug or flip your psu switch (you can't just reset/reboot/power pc off and then on...you have to remove power completely). After doing this and rebooting your system will run perfectly for another 7-12 days... Rinse and repeat.

I've just been seeing a lot of other people very similar problem and some even claim its a widespread bug in all 500 series nvidia cards.

Some of my sources for this same issue:
See negative reviews on newegg. Many describe the problem without knowing all details. Some even mention the problem exactly...see StevenP's review on 8/16/2011

http://www.evga.com/forums/tm.aspx?m=811877&mpage=1


I'm not sure what I should do with my card at this point... :(
 
bobn4burton I'm pretty sure that is a separate issue though perhaps that is the issue the OP is having. But sounded like the OP's issue was specific to BF3.

I've had this same problem with artifacts that are only fixed by a cold boot, but I've had this card for almost a year and I have only experienced it 3 times, so some cards definitely have it worse than others. Guess I got lucky.
 
NotSoSimple said:
Game is running on high actually. Artifacts on Karkand, Sharqi, and Caspian.

Weird though..I gave up on it and shut down my desktop for a couple days. Came back, everything is playable as normal. I have no idea...
Click to expand...

Textures are on High? What about AA and are you running HBAO?
 
NotSoSimple said:
...Tried a restart, and now I sometimes get an error that the graphics driver crashed...
Click to expand...
Definitely could be a different problem. Although OP did say he was getting "driver crash errors" as well as artifacting...which i assume is the black screen followed by bubble saying your driver has stopped responding and has recovered...
 
bobn4burton said:
Definitely could be a different problem. Although OP did say he was getting "driver crash errors" as well as artifacting...which i assume is the black screen followed by bubble saying your driver has stopped responding and has recovered...
Click to expand...

Yeah but that is a completely separate issue from either of the artifacting issues being discussed and is mostly happens to people using firefox. The artifact issue you describe-at least when I've experience it-is not accompanied by the driver crash issue and the times I've had the driver crashing on me I never had any artifacting.

But perhaps it was the "cold boot" artifacting he was getting and he just never noticed it affecting other games/applications.
 
8du8 said:
Yeah but that is a completely separate issue from either of the artifacting issues being discussed and is mostly happens to people using firefox. The artifact issue you describe-at least when I've experience it-is not accompanied by the driver crash issue and the times I've had the driver crashing on me I never had any artifacting.

But perhaps it was the "cold boot" artifacting he was getting and he just never noticed it affecting other games/applications.
Click to expand...

Oh wow, makes some sense now... I run firefox too. I have the MSI 560TI Hawk and had to RMA it last week because of 5 second stuttering when using FF (every 2 minutes at it's worse) mixed in with artifacting in windows. Oddly, gaming is perfect. I tried both the latest beta and latest stables with no change.
 
I've had some odd issues with BF3 they seems to have once out of 50 play sessions. The last one was a shadow corruption that was really odd. I have only had the PC crash once, and I have most of my settings in BF3 to high.

It sucks to hear its a 560 ti issue in general :/ , I was looking to jump to Sli at some point with two of these but its not a good sign.

Also using a MSI twin Frozer.
 
s3rvb0t said:
Oh wow, makes some sense now... I run firefox too. I have the MSI 560TI Hawk and had to RMA it last week because of 5 second stuttering when using FF (every 2 minutes at it's worse) mixed in with artifacting in windows. Oddly, gaming is perfect. I tried both the latest beta and latest stables with no change.
Click to expand...

Nvidia actually posted a statement on their forums they were willing to buy cards from people who were having issues when using firefox as they were having trouble reproducing/finding a fix for the issue.

I never really use firefox but my wife does when she uses my rig and she would always complain about firefox crashing "the screen goes black and then it crashes" my reply was always "just use chrome". :)
 
8du8 said:
Nvidia actually posted a statement on their forums they were willing to buy cards from people who were having issues when using firefox as they were having trouble reproducing/finding a fix for the issue.

I never really use firefox but my wife does when she uses my rig and she would always complain about firefox crashing "the screen goes black and then it crashes" my reply was always "just use chrome". :)
Click to expand...

Crazy.... do you happen to have a link? I can't seem to find the thread.
 
Hi all,

I think I might be on to something, I have 6 ASUS 560 Ti that have been driving me crazy with various issues as here in the forums,  4 of these cards fail this memory test intermittently.

See if you can get video memory errors running BurtInTest PRO: (ON A SYSTEM ON FOR 24/7)

Do NOT buy it ! 30 day trial is more than enough…

Under test selection and duty cycles set only to test 2D and 3D at 100% (uncheck ALL other tests)

I find that many systems return errors within the first seconds/minute of running it; only way to clear is to under clock (only works sometimes) or to do a complete hard shutdown (pull plug from workstation for one minute).

This, I think, is possibly related indirectly to some of the issues other people are getting.

BurnInTest Pro for my 4 cards seems to catch the videocard when it is in its “Fail Mode”, i.e. the BIOS/firmware issue has occurred, leading to video memory error in BurnInTest not yet showing up as TDR driver resets or other “artifacts” yet.
The video memory might also be used by the video card for running some “video system files”, and if an error in memory occurs then code goes out the window and you get more serious BSOD, TDR resets etc, i.e. these small memory errors start because some firmware issue has occurred (fail on BurnInTest), and eventually memory error affects running driver code occur which leads to BSOD, TDR etc

i.e. the BSOD, TDR, “”Display driver nvlddmkm stopped responding”” crashes occur NOT because of you traditional driver code “BUG” issue or poorly written drivers, but that perfectly good code/drivers get “””hosed””” by errors in memory if some of the code that is used to run the video card uses the same physical memory pool that is failing on BurnInTest.

1.) BIOS/firmware error causes settings for video card memory to run out of spec leading to occasional errors (BurnInTest).

2.) This error condition which causes the video memory to cause errors will continue until there is a hard reset of the video card by pulling the plug.

3.) Formal Video Drivers still not affected as errors are rare, but over time errors in Formal Video Drivers code are created from theses memory errors causing more serious BSOD, TDR, artifacts from what now are corrupted driver files/code etc.

This looks more as a firmware/design issue possibly controlling memory voltage etc..


Can any else reproduce this?

ASUS USER
 
Last edited:
What I think is happening in some of these 560 Ti cards: In a Win 7 64 bit system.

1.) Only on systems on for 24/7 plus, will a low-level Firmware/Power Management Module corruption/error occur over time in a computer during long times of IDLE over several days (i.e. you do not touch the computer for over 24 hours).

2.) This Firmware/Power Management Module corruption/error can be documented by errors in video memory running BurnInTest Pro (2D and 3D only tests at 100%), or possibly some other video memory test.

3.) This corruption/error will remain in place even during a conventional shutdown (power still reaching video card), during a conventional restart, and even when changing drivers, all documented by continuing to generate errors in video memory running BurnInTest Pro or other tests of a similar nature.

4.) This corruption/error in the Firmware/Power Management Module will then eventually manifest itself as artifact, TDRs, and other instability.

5.) ONLY a complete power down, i.e. pull the plug for two minutes or reseat the card, will the card be restored to a more stable state without the Firmware/Power Management Module corruption/error, as documented by no more memory errors in running BurnInTest Pro or other tests.

i.e. to paraphrase:::

6.) That is; the running of BurnInTest or other similar type programs show the “Hidden” corruption/error in the Firmware/Power Management Module.

7) This corruption/error in the Firmware/Power Management Module can eventually but not necessarily always/immediately lead to more serious BSOD, artifact, TDRs.

8.) This corruption/error in the Firmware/Power Management Module can only be eliminated by a complete power down as noted above, pull power supply plug for at least two minutes or reseat the card with power leads pulled off.
 
Last edited:
I was having issues with my 560 SLI setup until I started using the 285.79 driver. I also found that if I do any overclocking, the driver starts acting up so I typically overclock the card then reinstall the new driver and have no problems.
 
ASUS USER said:
Can any else reproduce this?

ASUS USER
Click to expand...

YES! YES I CAN!

The longer my system has been 'on' the more likely I'll suffer a display driver crash/total lock up. This even occurs when I've had the machine in sleep mode or shut down, because even though the machine is off, power is still being supplied to the motherboard/graphics.

When the crash derp cycle starts, if I'm fast enough, I can catch the vram errors with burnit shortly before the system dies.

Once the cycle of doom has started, it will keep crashing, over and over and over again, sometimes even BSOD'ing before windows has even hit the desktop.

The only fix is to power off the machine by pulling the plug, draining the caps by trying to power on again and leaving it to drain out.

I can repeat this bug, at least several times a day, and certainly every morning, when the machine craps it's pants on first boot/resume.

I wonder if you found out exactly what it was, it seems to fail on every driver from 275 to the latest 301.
 
You must log in or register to reply here.
Back
Top