• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Concern about SLI

MVilla

n00b
Joined
Nov 29, 2011
Messages
8
Long story short:

I have a EVGA 560 Ti 2gb, that I get the "Display driver has stopped responding and has recovered" with every now and then (some days once or twice and some days not at all), and I've been looking to go SLI , but I'm concerned it won't work very well or at least worsen with the errors if I go SLI?

Am I totally mistaken with this?
 
Which driver are you running now and have you tried updating to the latest driver, if available?

Once you resolve your driver issue, you should be OK moving forward with SLI.
 
Last edited:
I'm running the 285.62, and I've tried the previous one as well where I get the same amount (maybe 10 a week) and I've tried one of the beta drivers as well.
 
your using firefox right?

update your browser or switch to another one. its a long time issue with nvidia drivers and firefox. i used to have it with one of my 560 ti's but after my most recent win 7 x64 install i have not had the problem come back.
 
You need to resolve that problem before you add another card to the mix. Trust me on this.
 
I recommend using a different browser with NVIDIA drivers. I've had the Firefox issue myself. It's damned annoying. If I pull one of my GTX 580's out, start the system, shut it back down and reinstall the physical card, the problem will clear for a week or so but always return. Once that problem starts my system becomes pretty much useless. I've tried all the fixes posted around the internet and nothing has permanently dealt with the problem.

In general my GTX 580's have been more problematic than all my previous NVIDIA cards combined. I've been lucky in that I've rarely had issues with any of them until now. Though I've had bigger issues with some of AMD's cards. Mainly their dual GPU cards. Then again dual GPU cards always seem to get the short stick when it comes to driver support.
 
I get the error when viewing flash in Firefox indeed, thanks for that great input. However I get it in battlefield 3 too on occasions and HoN as well. But I'll definitely check into this Firefox issue. I'm on a ASRock P67 Extreme4 Gen3 if that's relevant btw.
 
I get the error when viewing flash in Firefox indeed, thanks for that great input. However I get it in battlefield 3 too on occasions and HoN as well. But I'll definitely check into this Firefox issue. I'm on a ASRock P67 Extreme4 Gen3 if that's relevant btw.

There really doesn't seem to be much rhyme or reason to it. Some people experience the problem and some don't.
 
There really doesn't seem to be much rhyme or reason to it. Some people experience the problem and some don't.

Okay. Thanks for all the help. I'll do my best to solve the driver issues before going any further.
 
Hmmm - firefox ehh? I do experience the issue myself, but only (so far) really when browsing and I use firefox...

Maybe time to switch browsers for a while and see if it stops :)
 
Hmmm - firefox ehh? I do experience the issue myself, but only (so far) really when browsing and I use firefox...

Maybe time to switch browsers for a while and see if it stops :)

It did for me. Also I've found that sometimes disabling hardware acceleration of Flash resolves the problem on some systems.
 
Hi Dan.

Short after I replied to your last post, I launched Saints Row III with the Dx11.exe and when I left the game, I got this:

http://www.youtube.com/watch?v=Ie5DRZC5XMo (Sorry for the quality and camera handling)

Any idea would could be causing it? I've had it once before with HoN too. This is the only error I have with my current setup, besides the driver stopping and being restored.

After I rebooted, the computer hung at the starting windows logo for about a minute or a minute and a half (I normally only see the logo for 2 seconds with my SSD), and then it just went into windows like everything was normal.
 
Last edited:
Hi Dan.

Short after I replied to your last post, I launched Saints Row III with the Dx11.exe and when I left the game, I got this:

http://www.youtube.com/watch?v=Ie5DRZC5XMo (Sorry for the quality and camera handling)

Any idea would could be causing it? I've had it once before with HoN too. This is the only error I have with my current setup, besides the driver stopping and being restored.

After I rebooted, the computer hung at the starting windows logo for about a minute or a minute and a half (I normally only see the logo for 2 seconds with my SSD), and then it just went into windows like everything was normal.

I've had that happen due to this driver error on my system. I ended up reinstalling the driver manually to resolve the problem. It hasn't occured since.
 
I've had that happen due to this driver error on my system. I ended up reinstalling the driver manually to resolve the problem. It hasn't occured since.

What exactly does reinstalling the driver manually mean?
 
I'm on about my third 3x SLI setup and sixth overall all. Each upgrade had had fewer and fewer issues though there are rough patches in new driver releases from time to time. The 270s caused be all kinds of grief with 3D Blu Ray but the new drivers are better than ever in that regard. All of the games I play seem to be running just fine these days, 3D support in games seems to be progressing nicely, Surround is kind of hit or miss out of the box.

Overall I'm VERY happy with the current state of my sig rig and 3x SLI. It's not perfect but I simply don't see a lot of deep problems, my biggest concern isn't SLI these days but the hit and miss nature of Surround.
 
I reload the driver through device manager by browsing to the driver file's actual location rather than using the setup executable.
 
Back
Top