Sign in with
Sign up | Sign in
Your question
Solved

Nvidia 320.18 driver issues?

Tags:
Last response: in Graphics & Displays
Share
June 22, 2013 10:58:35 PM

Has anyone experienced the issues brought by this driver? I recently replaced my old HD 6570 with a GTX 650 Ti Boost and did a clean uninstall of all AMD drivers and installed the 320.18 drivers straight from Nvidia's website.

The total "on" time of my system was probably less than 2 days and I haven't experienced any POST problems, BSODs, freezing or games crashing. I have noticed a bit of a glitch in Far Cry 3 where there's a weird yellow silhouette of NPCs and the torches' burnt part isn't on the torch stick itself(I have the gfx settings at max). I haven't noticed any graphical glitch in other games.

I've only heard of the 320.18 issue a couple of days ago when I've already left home and returned to my college dorm and was looking around which 600 series cards where confirmed to be affected and experienced these issues/have been killed by it. I'm planning to rollback drivers but don't know if the 2nd latest (314.22) driver is going to be fine.
June 23, 2013 12:15:42 AM

ave200 said:
Has anyone experienced the issues brought by this driver? I recently replaced my old HD 6570 with a GTX 650 Ti Boost and did a clean uninstall of all AMD drivers and installed the 320.18 drivers straight from Nvidia's website.

The total "on" time of my system was probably less than 2 days and I haven't experienced any POST problems, BSODs, freezing or games crashing. I have noticed a bit of a glitch in Far Cry 3 where there's a weird yellow silhouette of NPCs and the torches' burnt part isn't on the torch stick itself(I have the gfx settings at max). I haven't noticed any graphical glitch in other games.

I've only heard of the 320.18 issue a couple of days ago when I've already left home and returned to my college dorm and was looking around which 600 series cards where confirmed to be affected and experienced these issues/have been killed by it. I'm planning to rollback drivers but don't know if the 2nd latest (314.22) driver is going to be fine.


you should rollback drivers to an earlier driver immediately . 320.18 has killed some gpu's according to forums. source: http://modcrash.com/nvidia-display-driver-damaging-gpus...
June 23, 2013 1:12:08 AM

u_gonna_squeal_b4_we_cookya said:
What Directx version are you running Far Cry 3 in? I had a glitch where there was no crosshairs in the sniper rifles in DX11. Switching to DX9 might fix it.


DX11. There aren't any other glitch besides the one pointed out, although it could be just Far Cry 3 files itself that have problems and not because of the 320.18 drivers.
Related resources
June 23, 2013 1:17:42 AM

SgtDoakes said:
ave200 said:
Has anyone experienced the issues brought by this driver? I recently replaced my old HD 6570 with a GTX 650 Ti Boost and did a clean uninstall of all AMD drivers and installed the 320.18 drivers straight from Nvidia's website.

The total "on" time of my system was probably less than 2 days and I haven't experienced any POST problems, BSODs, freezing or games crashing. I have noticed a bit of a glitch in Far Cry 3 where there's a weird yellow silhouette of NPCs and the torches' burnt part isn't on the torch stick itself(I have the gfx settings at max). I haven't noticed any graphical glitch in other games.

I've only heard of the 320.18 issue a couple of days ago when I've already left home and returned to my college dorm and was looking around which 600 series cards where confirmed to be affected and experienced these issues/have been killed by it. I'm planning to rollback drivers but don't know if the 2nd latest (314.22) driver is going to be fine.


you should rollback drivers to an earlier driver immediately . 320.18 has killed some gpu's according to forums. source: http://modcrash.com/nvidia-display-driver-damaging-gpus...


Will do right after I buy my new set of Corsair RAM, I sold the old 4GB stick my system had to purchase a new kit. Do you know where they listed which specific cards are affected though? And should I rollback to the 314.22 driver or something earlier?

Best solution

June 23, 2013 1:28:34 AM
Share

ave200 said:
SgtDoakes said:
ave200 said:
Has anyone experienced the issues brought by this driver? I recently replaced my old HD 6570 with a GTX 650 Ti Boost and did a clean uninstall of all AMD drivers and installed the 320.18 drivers straight from Nvidia's website.

The total "on" time of my system was probably less than 2 days and I haven't experienced any POST problems, BSODs, freezing or games crashing. I have noticed a bit of a glitch in Far Cry 3 where there's a weird yellow silhouette of NPCs and the torches' burnt part isn't on the torch stick itself(I have the gfx settings at max). I haven't noticed any graphical glitch in other games.

I've only heard of the 320.18 issue a couple of days ago when I've already left home and returned to my college dorm and was looking around which 600 series cards where confirmed to be affected and experienced these issues/have been killed by it. I'm planning to rollback drivers but don't know if the 2nd latest (314.22) driver is going to be fine.


you should rollback drivers to an earlier driver immediately . 320.18 has killed some gpu's according to forums. source: http://modcrash.com/nvidia-display-driver-damaging-gpus...


Will do right after I buy my new set of Corsair RAM, I sold the old 4GB stick my system had to purchase a new kit. Do you know where they listed which specific cards are affected though? And should I rollback to the 314.22 driver or something earlier?


hmm,practically all cards seem be having problems like artifacts and bsod's while gaming. while others have problems like pc not booting up . and very rarely there are the cards that get critically damaged. its hard to tell which specific cards have these problems ( in the forum posts that cards range from gtx 400's - 600's ) i think for now it would be safer to rollback to an earlier driver. 314.22 sounds good.
June 23, 2013 1:34:53 AM

I haven't had any problems with that driver and neither have quite a few of regulars around here, this may well be AMD's shills doing their rounds.
June 23, 2013 1:38:45 AM

Mousemonkey said:
I haven't had any problems with that driver and neither have quite a few of regulars around here, this may well be AMD's shills doing their rounds.


all this happened on nvidia forums. https://forums.geforce.com/default/topic/544882/geforce...

this is not the youtube comment section for people to raise fanboy flags and point fingers haha :D 
June 23, 2013 1:42:18 AM

Yeah I've been through that and I saw little evidence of dead cards but lots of possible shilling, just because someone posts to a site doesn't mean they are telling the truth and AMD's shills are a fact and really do exist.
June 23, 2013 2:17:48 AM

Mousemonkey said:
Yeah I've been through that and I saw little evidence of dead cards but lots of possible shilling, just because someone posts to a site doesn't mean they are telling the truth and AMD's shills are a fact and really do exist.


Although one could say being extra cautious wouldn't hurt. Has there been an official statement from Nvidia about the 320.18 drivers? Kinda bit weird for them not to especially with how big of a problem it brings to Nvidia cards owners. An "nvidia 320.18" search on youtube shows mostly Battlefield 3 glitch videos with the driver but from what I've read those glitches appeared before the 320.18 driver and it was noted I think from the geforce forums that the glitch wasn't fixed yet.
June 23, 2013 2:24:51 AM

ave200 said:
Mousemonkey said:
Yeah I've been through that and I saw little evidence of dead cards but lots of possible shilling, just because someone posts to a site doesn't mean they are telling the truth and AMD's shills are a fact and really do exist.


Although one could say being extra cautious wouldn't hurt. Has there been an official statement from Nvidia about the 320.18 drivers? Kinda bit weird for them not to especially with how big of a problem it brings to Nvidia cards owners. An "nvidia 320.18" search on youtube shows mostly Battlefield 3 glitch videos with the driver but from what I've read those glitches appeared before the 320.18 driver and it was noted I think from the geforce forums that the glitch wasn't fixed yet.

Not that I've seen and yet there was with the driver that turned down fanspeeds and as I and many others have been using the driver since day one and both of my 660's and my 560 are still alive and well I have my doubts on the validity of these claims, one obscure website linked to by someone with a low post count tends to set off my shilll alarm.
June 23, 2013 2:40:45 AM

Mousemonkey said:
ave200 said:
Mousemonkey said:
Yeah I've been through that and I saw little evidence of dead cards but lots of possible shilling, just because someone posts to a site doesn't mean they are telling the truth and AMD's shills are a fact and really do exist.


Although one could say being extra cautious wouldn't hurt. Has there been an official statement from Nvidia about the 320.18 drivers? Kinda bit weird for them not to especially with how big of a problem it brings to Nvidia cards owners. An "nvidia 320.18" search on youtube shows mostly Battlefield 3 glitch videos with the driver but from what I've read those glitches appeared before the 320.18 driver and it was noted I think from the geforce forums that the glitch wasn't fixed yet.

Not that I've seen and yet there was with the driver that turned down fanspeeds and as I and many others have been using the driver since day one and both of my 660's and my 560 are still alive and well I have my doubts on the validity of these claims, one obscure website linked to by someone with a low post count tends to set off my shilll alarm.


.... i havent exactly been on this forum for years. just linked the article to him because some people are having issues with 320.18 an op is also having issues with 320.18. just told him to rollback to an earlier driver just to be on the safe side..
June 23, 2013 2:41:18 AM

Mousemonkey said:
ave200 said:
Mousemonkey said:
Yeah I've been through that and I saw little evidence of dead cards but lots of possible shilling, just because someone posts to a site doesn't mean they are telling the truth and AMD's shills are a fact and really do exist.


Although one could say being extra cautious wouldn't hurt. Has there been an official statement from Nvidia about the 320.18 drivers? Kinda bit weird for them not to especially with how big of a problem it brings to Nvidia cards owners. An "nvidia 320.18" search on youtube shows mostly Battlefield 3 glitch videos with the driver but from what I've read those glitches appeared before the 320.18 driver and it was noted I think from the geforce forums that the glitch wasn't fixed yet.

Not that I've seen and yet there was with the driver that turned down fanspeeds and as I and many others have been using the driver since day one and both of my 660's and my 560 are still alive and well I have my doubts on the validity of these claims, one obscure website linked to by someone with a low post count tends to set off my shilll alarm.


Hmm... I might try the 320.18 a bit more and see if there's truth to all these claims. I still have about 2 months warranty for my 650 Ti Boost and could get a replacement if the driver kills it. And it is weird that major tech sites haven't made an article about it or even a video from a major tech channel on YT talking about it.
June 23, 2013 2:44:45 AM

ave200 said:
Mousemonkey said:
ave200 said:
Mousemonkey said:
Yeah I've been through that and I saw little evidence of dead cards but lots of possible shilling, just because someone posts to a site doesn't mean they are telling the truth and AMD's shills are a fact and really do exist.


Although one could say being extra cautious wouldn't hurt. Has there been an official statement from Nvidia about the 320.18 drivers? Kinda bit weird for them not to especially with how big of a problem it brings to Nvidia cards owners. An "nvidia 320.18" search on youtube shows mostly Battlefield 3 glitch videos with the driver but from what I've read those glitches appeared before the 320.18 driver and it was noted I think from the geforce forums that the glitch wasn't fixed yet.

Not that I've seen and yet there was with the driver that turned down fanspeeds and as I and many others have been using the driver since day one and both of my 660's and my 560 are still alive and well I have my doubts on the validity of these claims, one obscure website linked to by someone with a low post count tends to set off my shilll alarm.


Hmm... I might try the 320.18 a bit more and see if there's truth to all these claims. I still have about 2 months warranty for my 650 Ti Boost and could get a replacement if the driver kills it. And it is weird that major tech sites haven't made an article about it or even a video from a major tech channel on YT talking about it.


Maybe they can't seem to reproduce these "issues" that kill cards?
June 23, 2013 2:53:52 AM

SgtDoakes said:
Mousemonkey said:
ave200 said:
Mousemonkey said:
Yeah I've been through that and I saw little evidence of dead cards but lots of possible shilling, just because someone posts to a site doesn't mean they are telling the truth and AMD's shills are a fact and really do exist.


Although one could say being extra cautious wouldn't hurt. Has there been an official statement from Nvidia about the 320.18 drivers? Kinda bit weird for them not to especially with how big of a problem it brings to Nvidia cards owners. An "nvidia 320.18" search on youtube shows mostly Battlefield 3 glitch videos with the driver but from what I've read those glitches appeared before the 320.18 driver and it was noted I think from the geforce forums that the glitch wasn't fixed yet.

Not that I've seen and yet there was with the driver that turned down fanspeeds and as I and many others have been using the driver since day one and both of my 660's and my 560 are still alive and well I have my doubts on the validity of these claims, one obscure website linked to by someone with a low post count tends to set off my shilll alarm.


.... i havent exactly been on this forum for years. just linked the article to him because some people are having issues with 320.18 an op is also having issues with 320.18. just told him to rollback to an earlier driver just to be on the safe side..


TBH I can't confirm if the Far Cry 3 glitch is caused by the driver or is actually just a problem within Far Cry 3 itself, just got scared of all the forum posts in other sites about the 320.18 killing cards. I played Metro Last Light and War Thunder with no issues at all. Maybe there really is a major issue with the 320.18 and for some cards the symptoms appear immediately and for others gradually, or it could be just as Mousemonkey says.
June 23, 2013 2:58:59 AM

ave200 said:
SgtDoakes said:
Mousemonkey said:
ave200 said:
Mousemonkey said:
Yeah I've been through that and I saw little evidence of dead cards but lots of possible shilling, just because someone posts to a site doesn't mean they are telling the truth and AMD's shills are a fact and really do exist.


Although one could say being extra cautious wouldn't hurt. Has there been an official statement from Nvidia about the 320.18 drivers? Kinda bit weird for them not to especially with how big of a problem it brings to Nvidia cards owners. An "nvidia 320.18" search on youtube shows mostly Battlefield 3 glitch videos with the driver but from what I've read those glitches appeared before the 320.18 driver and it was noted I think from the geforce forums that the glitch wasn't fixed yet.

Not that I've seen and yet there was with the driver that turned down fanspeeds and as I and many others have been using the driver since day one and both of my 660's and my 560 are still alive and well I have my doubts on the validity of these claims, one obscure website linked to by someone with a low post count tends to set off my shilll alarm.


.... i havent exactly been on this forum for years. just linked the article to him because some people are having issues with 320.18 an op is also having issues with 320.18. just told him to rollback to an earlier driver just to be on the safe side..


TBH I can't confirm if the Far Cry 3 glitch is caused by the driver or is actually just a problem within Far Cry 3 itself, just got scared of all the forum posts in other sites about the 320.18 killing cards. I played Metro Last Light and War Thunder with no issues at all. Maybe there really is a major issue with the 320.18 and for some cards the symptoms appear immediately and for others gradually, or it could be just as Mousemonkey says.


This is the reaction that the shills aim for, spread enough rumours and then let peoples paranoia do the rest.
June 23, 2013 3:06:55 AM

Mousemonkey said:
ave200 said:
Mousemonkey said:
ave200 said:
Mousemonkey said:
Yeah I've been through that and I saw little evidence of dead cards but lots of possible shilling, just because someone posts to a site doesn't mean they are telling the truth and AMD's shills are a fact and really do exist.


Although one could say being extra cautious wouldn't hurt. Has there been an official statement from Nvidia about the 320.18 drivers? Kinda bit weird for them not to especially with how big of a problem it brings to Nvidia cards owners. An "nvidia 320.18" search on youtube shows mostly Battlefield 3 glitch videos with the driver but from what I've read those glitches appeared before the 320.18 driver and it was noted I think from the geforce forums that the glitch wasn't fixed yet.

Not that I've seen and yet there was with the driver that turned down fanspeeds and as I and many others have been using the driver since day one and both of my 660's and my 560 are still alive and well I have my doubts on the validity of these claims, one obscure website linked to by someone with a low post count tends to set off my shilll alarm.


Hmm... I might try the 320.18 a bit more and see if there's truth to all these claims. I still have about 2 months warranty for my 650 Ti Boost and could get a replacement if the driver kills it. And it is weird that major tech sites haven't made an article about it or even a video from a major tech channel on YT talking about it.


Maybe they can't seem to reproduce these "issues" that kill cards?


Mousemonkey said:
ave200 said:
SgtDoakes said:
Mousemonkey said:
ave200 said:
Mousemonkey said:
Yeah I've been through that and I saw little evidence of dead cards but lots of possible shilling, just because someone posts to a site doesn't mean they are telling the truth and AMD's shills are a fact and really do exist.


Although one could say being extra cautious wouldn't hurt. Has there been an official statement from Nvidia about the 320.18 drivers? Kinda bit weird for them not to especially with how big of a problem it brings to Nvidia cards owners. An "nvidia 320.18" search on youtube shows mostly Battlefield 3 glitch videos with the driver but from what I've read those glitches appeared before the 320.18 driver and it was noted I think from the geforce forums that the glitch wasn't fixed yet.

Not that I've seen and yet there was with the driver that turned down fanspeeds and as I and many others have been using the driver since day one and both of my 660's and my 560 are still alive and well I have my doubts on the validity of these claims, one obscure website linked to by someone with a low post count tends to set off my shilll alarm.


.... i havent exactly been on this forum for years. just linked the article to him because some people are having issues with 320.18 an op is also having issues with 320.18. just told him to rollback to an earlier driver just to be on the safe side..


TBH I can't confirm if the Far Cry 3 glitch is caused by the driver or is actually just a problem within Far Cry 3 itself, just got scared of all the forum posts in other sites about the 320.18 killing cards. I played Metro Last Light and War Thunder with no issues at all. Maybe there really is a major issue with the 320.18 and for some cards the symptoms appear immediately and for others gradually, or it could be just as Mousemonkey says.


This is the reaction that the shills aim for, spread enough rumours and then let peoples paranoia do the rest.


If it really is a shill I hope those people responsible for it have their cards die for no reason. It's really unfair for both the user and manufacturer. We don't get the new fixes and performance improvement from the new driver and makes users lose trusts in the company.
June 23, 2013 3:12:27 AM

Alien Babel Tech have an interesting article/thread where the owner of ABT lays out what he found out about AMD's underhand marketing tactics and although the article/thread has been there for some time AMD have yet to have it taken down for defamation which only lends credence to there being some truth to it.
June 23, 2013 5:31:42 PM

Mousemonkey said:
Alien Babel Tech have an interesting article/thread where the owner of ABT lays out what he found out about AMD's underhand marketing tactics and although the article/thread has been there for some time AMD have yet to have it taken down for defamation which only lends credence to there being some truth to it.


Seems like there is some truth to the issues:
ManuelG's comment(mod) and
Official Twitter of Nvidia Customer Care mention releasing a new driver that addresses these issues by the end of the month.
June 23, 2013 6:05:03 PM

Has anyone proven that this is only a rumor put on by AMD fanboys? If not, wouldn't it be better to play it safe and be cautious of this release?

No offense but many of the posts putting down the claims seem to be from people that believe that NVidia is not capable of releasing a bad driver. The truth is both AMD and NVidia put out good drivers and bad drivers.

Nobody is perfect and sometimes a bad one slips through the crack.

*Note that I have not personal experience with this but it is not intended to be a fanboy post.
June 23, 2013 6:45:51 PM

smeezekitty said:
Has anyone proven that this is only a rumor put on by AMD fanboys? If not, wouldn't it be better to play it safe and be cautious of this release?

No offense but many of the posts putting down the claims seem to be from people that believe that NVidia is not capable of releasing a bad driver. The truth is both AMD and NVidia put out good drivers and bad drivers.

Nobody is perfect and sometimes a bad one slips through the crack.

*Note that I have not personal experience with this but it is not intended to be a fanboy post.


I haven't found any article or forum post that these are false rumors or something but it just feels strange that it hasn't been covered by major tech sites/YT channels. However my last comment links to a comment by a Mod in the GeForce official forums saying that the issues will be fixed by a new driver to be released by the end of the month. He didn't elaborate what issues these were like if one of them causes cards to die, or the BSODs, CTDs and other issues pointed out by nvidia users. So there is some truth that the 320.18 drivers have issues that needed immediate remedy. I'm guessing right now the guys at Nvidia are trying to reproduce all the reported issues and fixing them as they confirm them.

All this started with that modcrash.com article linked by SgtDoakes and spread earlier this June by others. I'm not a fanboy of any side but this grinds my gears because I haven't really had any problems with the 320.18 drivers (except maybe that Far Cry 3 minor glitch and I'm not even sure it's because of the drivers). However I've only had the drivers about 2 days and that might not be enough for the issues to appear. I will choose the extra caution route and rollback to 314.20 once I get back home.
June 23, 2013 9:16:56 PM

Bugs and game crashes are one thing and I don't doubt that some people are experiencing those but cards dying and burning up, that's what I'm not seeing.
June 23, 2013 9:22:31 PM

I am willing to bet that the ones with cards dieing are either by coincidence or about ready to die and perhaps new optimizations which increase GPU usage are killing them.

I agree it probably isn't actually killing healthy cards (or there would be more outrage)
June 23, 2013 9:24:07 PM

Just had my first 320.18 graphics problem tonight. After 1 hour playing BF3 I had this:

http://i90.photobucket.com/albums/k244/jerreece/bf32013...

GPU temp was 59C. Ran 60FPS (VSync) all night long without a twitch in FPS numbers.

I have to admit the American Flag graphic error on the concrete barriers was pretty neat.
June 23, 2013 9:26:48 PM

jerreece said:
Just had my first 320.18 graphics problem tonight. After 1 hour playing BF3 I had this:

http://i90.photobucket.com/albums/k244/jerreece/bf32013...

GPU temp was 59C. Ran 60FPS (VSync) all night long without a twitch in FPS numbers.

I have to admit the American Flag graphic error on the concrete barriers was pretty neat.

Is your card dead now?
June 23, 2013 9:33:44 PM

Mousemonkey said:
jerreece said:
Just had my first 320.18 graphics problem tonight. After 1 hour playing BF3 I had this:

http://i90.photobucket.com/albums/k244/jerreece/bf32013...

GPU temp was 59C. Ran 60FPS (VSync) all night long without a twitch in FPS numbers.

I have to admit the American Flag graphic error on the concrete barriers was pretty neat.

Is your card dead now?


Nope! Works perfectly fine. Until now I've had no issues but keep reading about other people having all kinds of problems. So far I've only seen the graphic anomalies with BF3 though. And even that happened after an hour.
June 23, 2013 9:40:57 PM

jerreece said:
Mousemonkey said:
jerreece said:
Just had my first 320.18 graphics problem tonight. After 1 hour playing BF3 I had this:

http://i90.photobucket.com/albums/k244/jerreece/bf32013...

GPU temp was 59C. Ran 60FPS (VSync) all night long without a twitch in FPS numbers.

I have to admit the American Flag graphic error on the concrete barriers was pretty neat.

Is your card dead now?


Nope! Works perfectly fine. Until now I've had no issues but keep reading about other people having all kinds of problems. So far I've only seen the graphic anomalies with BF3 though. And even that happened after an hour.


Yes, I've seen a fair amount of complaints of graphic anomalies in BF3 and AC3 but as I recall BF3 has always been a bit shoddy as far as bugs go. Did it not have a huge patch needed shortly after release? I'm sure I recall people moaning about the time it took to download.
June 23, 2013 9:45:35 PM

jerreece said:
Mousemonkey said:
jerreece said:
Just had my first 320.18 graphics problem tonight. After 1 hour playing BF3 I had this:

http://i90.photobucket.com/albums/k244/jerreece/bf32013...

GPU temp was 59C. Ran 60FPS (VSync) all night long without a twitch in FPS numbers.

I have to admit the American Flag graphic error on the concrete barriers was pretty neat.

Is your card dead now?


Nope! Works perfectly fine. Until now I've had no issues but keep reading about other people having all kinds of problems. So far I've only seen the graphic anomalies with BF3 though. And even that happened after an hour.


From what I've read the BF3 problems surfaced even before the 320.18 drivers and that it hasn't been fixed yet. Still, if you're planning on playing games with the 320.18 drivers update us if you experience any issues that are similar to those that have already been reported by people, although I'll feel really guilty if it wrecks your card. :( 
June 23, 2013 9:51:11 PM

I've been gaming on the 320.18 drivers since they came out but I don't play BF3 or AC3! :lol: 
June 24, 2013 12:58:02 PM

I have seen random black screens and artifacting in Metro Last lite Crysis 3 and Far Cry 3. Ill be replacing my PSU later to rule that out (needed to do this anyway for future SLI setup) if that does not fix it then it has to be the card or the drivers. I had a 680 in my rig with the same drivers and it was doing much of the same things so Im hopeing/guessing its not my gtx770 but the drivers OR my PSU.
June 26, 2013 12:48:35 PM

I just installed the new 320.49 last night AFTER playing BF3. The bug reports @ Geforce.com suggest BF3 performance DROPS with this latest driver. Though I cannot confirm that myself.

I did play Sleeping Dogs last night @ max everything @ 1080p. I had VSync on and it sat perfectly @ 30FPS and was butter smooth. GPU was only at like 41-44% usage and at around 46C. I was just horsing around so I didn't mess with settings to remove VSYNC at all.
June 26, 2013 5:28:13 PM

Well Im hoping the new drivers work as I just RMA d a card and then purchased another one for SLI lol. While the card was working it was awesome being that I was coming from a HD6950.....then the artifacts crept in. I know SLI is overkill for 1080p but I figure with the two cards and the fact that I got 4gb models that should give me two things. For now I should be able to use vsync at max settings with alomost no drop below 60fps. Then as the new consoles come out hopefully the devs will start cranking out better looking games and then hopefully I wont have to upgrade for a long time lol.
June 26, 2013 5:45:13 PM

jerreece said:
Just had my first 320.18 graphics problem tonight. After 1 hour playing BF3 I had this:

http://i90.photobucket.com/albums/k244/jerreece/bf32013...

GPU temp was 59C. Ran 60FPS (VSync) all night long without a twitch in FPS numbers.

I have to admit the American Flag graphic error on the concrete barriers was pretty neat.


Guess I'll barge into this thread real quick, no one mentioned that this is actually a really common problem with the 320, and the 314 drivers. It happens to me on my new 660, and it happens to my friend with his 660 ti. It's not near common enough for either or us to take the time to properly uninstall, then reinstall older drivers though. Also happens to us on Crysis 2,
June 27, 2013 5:10:36 AM

Two 680 Top's W/modded bios's and not a nare problem with 320.18 WHQL. In fact, I had more issues with 314.14/22 and it's annoying texture flicker esp. in BF3. I have videos of it and it was bad.

314.14 drivers but had the same issue with 314.22.

!