Sign in with
Sign up | Sign in
Your question

SLI Option not showing up?

Last response: in Graphics & Displays
Share
July 5, 2013 1:58:56 PM

I just plopped another 660ti into my rig, thus a 660ti [One is 2gb other is 3gb] SLi.

However, I saw little to no performance improvement. So I went into Nvidia control panel, as it one must manually activate it, but the option to do so [enable SLI] is not present.

so far I have:
*Reinstalled GFX card drivers- nothing.
^And that's pretty much it. Was considering reloading OS, etc- but other posters with the same problem say it is ineffective.

My motherboard is a Z68X-UD3H-B3, I have 8 Gigs of Ram with a i5 3570k psu.

When I finally figure out how to do so, I will slap a picture of what my Nvidia control panel looks like. Thank you in advance.

Uploaded with ImageShack.us" alt="" class="imgLz frmImg " />


Got the picture to work. Totally.

More about : sli option showing

July 5, 2013 2:05:39 PM

Have you connected the two cards together via the sli bridge cable? If not do it and your problem is solved.
m
0
l
July 5, 2013 2:07:19 PM

Trenchcoat said:
Have you connected the two cards together via the sli bridge cable? If not do it and your problem is solved.


don't think this is the problem, as the cable is present and it is showing up in my hardware department [picture is derping]
m
0
l
Related resources
July 5, 2013 2:13:50 PM

Are they made by the exact same manufacturer? Many manufacturers are well known for making all of their cards slightly different than another, which has been known to cause issues with SLi configurations. It is ALWAYS best to match your cards the best you can. Also, I notice that one card has 1gb less than your other card, while it shouldn't be an issue, this has also been linked to causing problems. It should just lower itself to the amount of VRAM that the other card has.
m
0
l
July 5, 2013 2:19:39 PM


skept1k said:
Are they made by the exact same manufacturer? Many manufacturers are well known for making all of their cards slightly different than another, which has been known to cause issues with SLi configurations. It is ALWAYS best to match your cards the best you can. Also, I notice that one card has 1gb less than your other card, while it shouldn't be an issue, this has also been linked to causing problems. It should just lower itself to the amount of VRAM that the other card has.


One is EVGA [3gb model] and I believe the other is Gigabyte.
m
0
l
July 5, 2013 2:20:09 PM

What resolution are you playing with and what games are you playing? It will also help if we know what processor you are running.
m
0
l
July 5, 2013 2:22:35 PM

Trenchcoat said:
What resolution are you playing with and what games are you playing?


1920x1080 [37in monitor] 1080p LED, etc. etc.

Games include Metro 2033, Skyrim [ENB enabled (requires more firepower)] Aswell BF3, which I haven't dropped below 60 FPS at any point but it has the same framerate after #2 card was thrown in there. As far as I know, they're all SLI compatible. [few of the games]
m
0
l
July 5, 2013 2:27:48 PM

Praedos said:

skept1k said:
Are they made by the exact same manufacturer? Many manufacturers are well known for making all of their cards slightly different than another, which has been known to cause issues with SLi configurations. It is ALWAYS best to match your cards the best you can. Also, I notice that one card has 1gb less than your other card, while it shouldn't be an issue, this has also been linked to causing problems. It should just lower itself to the amount of VRAM that the other card has.


One is EVGA [3gb model] and I believe the other is Gigabyte.


EVGA is DEFINITELY known for making small alterations to their graphics cards, I know, I own two EVGA 460 GTX's in SLi and they have issues occasionally even though they're the "same" card. Sometimes it can be so bad (although extremely rare) that two of their own cards won't match up, even if they're the same model, series, etc. The fact that you're trying to SLi two cards from two entirely different manufacturers, both of which have undoubtedly modified them in some way, is more than likely your problem here. You'd be better off trying to get another 3GB EVGA 660 Ti, or if you prefer, you can match it with another Gigabyte 660 Ti 2GB. I'm sorry you're having issues :/ 
m
0
l
July 5, 2013 2:31:20 PM

@skept are there any ways around this?
m
0
l
July 5, 2013 2:40:44 PM

Praedos said:
Trenchcoat said:
What resolution are you playing with and what games are you playing?


1920x1080 [37in monitor] 1080p LED, etc. etc.

Games include Metro 2033, Skyrim [ENB enabled (requires more firepower)] Aswell BF3, which I haven't dropped below 60 FPS at any point but it has the same framerate after #2 card was thrown in there. As far as I know, they're all SLI compatible. [few of the games]


It seems that your cards just don't work well together, they are very different.
m
0
l
July 5, 2013 2:51:06 PM

Praedos said:
@skept are there any ways around this?


Hmm, very very few. If you have GPU-Z downloaded, would you mind taking a screenshot of each card? Then myself and others could definitely tell you if this is the problem.
m
0
l
July 5, 2013 2:54:28 PM

theonerm2 said:
Praedos said:
@skept are there any ways around this?


Run DifferentSLI the modded driver. Run the latest one 320.18. You problem should be solved after that. I had the same problem with an OEM GTX 460 and a PNY XLR8 GTX 460.

http://www.techpowerup.com/forums/showthread.php?t=1589...


Careful with the new 3xx+ series drivers, they've been known to kill fermi cards. 320.49 WHQL is the most stable, although still VERY problematic. Moving on, even if he does get this setup to work, it doesn't change the fact that he could be presented with a plethora of issues because they're made by different manufacturers with entirely different modifications.
m
0
l
July 5, 2013 3:13:24 PM

skept1k said:
theonerm2 said:
Praedos said:
@skept are there any ways around this?


Run DifferentSLI the modded driver. Run the latest one 320.18. You problem should be solved after that. I had the same problem with an OEM GTX 460 and a PNY XLR8 GTX 460.

http://www.techpowerup.com/forums/showthread.php?t=1589...


Careful with the new 3xx+ series drivers, they've been known to kill fermi cards. 320.49 WHQL is the most stable, although still VERY problematic. Moving on, even if he does get this setup to work, it doesn't change the fact that he could be presented with a plethora of issues because they're made by different manufacturers with entirely different modifications.


Oh really? So how comes they haven't killed mine then?
m
0
l
July 5, 2013 3:41:23 PM

Mousemonkey said:
skept1k said:
theonerm2 said:
Praedos said:
@skept are there any ways around this?


Run DifferentSLI the modded driver. Run the latest one 320.18. You problem should be solved after that. I had the same problem with an OEM GTX 460 and a PNY XLR8 GTX 460.

http://www.techpowerup.com/forums/showthread.php?t=1589...


Careful with the new 3xx+ series drivers, they've been known to kill fermi cards. 320.49 WHQL is the most stable, although still VERY problematic. Moving on, even if he does get this setup to work, it doesn't change the fact that he could be presented with a plethora of issues because they're made by different manufacturers with entirely different modifications.


Oh really? So how comes they haven't killed mine then?


I didn't say they killed EVERYONE's Fermi-based GPU, but there have been more than a few accounts where they have
caused an overvoltage problem, undeniably killing a card if it's bad enough. It was supposedly because of the new stock profiles, some even had their Kepler-based GPU's short out as well. It's not directly tied to Fermi, it's just in this case they've been the most affected from what I've researched. I know for a fact that I've had nothing but relentless problems with all of the 3xx.xx series drivers with my 460 GTX SLi setup, moved down to 296.10 and haven't had a single problem since. I'm just giving him and others fair warning, it's not guaranteed to fry your card, but it certainly does have its problems, and I personally don't think it's worth the risk. I mean honestly though, do you really think they're still optimizing a card that's almost 4 years old? I haven't seen a single optimization in their latest driver changelogs for 4xx or 5xx fermi cards .
m
0
l
July 5, 2013 3:48:27 PM

Has your card been killed by these drivers? Personally I think it's just a load of cobblers being spread by AMD/ATi shills as I can't find anything to substantiate the so called issue other than anecdotal evidence, there is a big difference between artifacts and crashing and dead cards.
m
0
l
July 5, 2013 3:51:02 PM

vLol failed quote attempt.

[/quotemsg]

Hmm, very very few. If you have GPU-Z downloaded, would you mind taking a screenshot of each card? Then myself and others could definitely tell you if this is the problem. [/quotemsg]

Uploaded with ImageShack.us" alt="" class="imgLz frmImg " />

Uploaded with ImageShack.us" alt="" class="imgLz frmImg " />


m
0
l
July 5, 2013 4:00:51 PM

Mousemonkey said:
Has your card been killed by these drivers? Personally I think it's just a load of cobblers being spread by AMD/ATi shills as I can't find anything to substantiate the so called issue other than anecdotal evidence, there is a big difference between artifacts and crashing and dead cards.


Actually yes, my first EVGA 460 GTX died as soon as I installed the new drivers, I only recently got another one back from RMA. Whether or not it kills card it besides the point, the fact of the matter is is that myself and countless other Nvidia GPU users have experienced absolute hell with 320.18 WHQL. That is a fact, and can be found from hundreds of users all over forums everywhere. There's no reason to upgrade if there's nothing new for your card unless you're experiencing problems that they have fixed in the latest update. Short answer, if it isn't broken, why fix it?
m
0
l
July 5, 2013 4:05:52 PM

skept1k said:
Mousemonkey said:
Has your card been killed by these drivers? Personally I think it's just a load of cobblers being spread by AMD/ATi shills as I can't find anything to substantiate the so called issue other than anecdotal evidence, there is a big difference between artifacts and crashing and dead cards.


Actually yes, my first EVGA 460 GTX died as soon as I installed the new drivers
, I only recently got another one back from RMA. Whether or not it kills card it besides the point, the fact of the matter is is that myself and countless other Nvidia GPU users have experienced absolute hell with 320.18 WHQL. That is a fact, and can be found from hundreds of users all over forums everywhere. There's no reason to upgrade if there's nothing new for your card unless you're experiencing problems that they have fixed in the latest update. Short answer, if it isn't broken, why fix it?


Of course it did and as this is the internet your word is gospel.
m
0
l
July 5, 2013 4:10:38 PM

Praedos said:
vLol failed quote attempt.



Hmm, very very few. If you have GPU-Z downloaded, would you mind taking a screenshot of each card? Then myself and others could definitely tell you if this is the problem. [/quotemsg]

Uploaded with ImageShack.us" alt="" class="imgLz frmImg " />

Uploaded with ImageShack.us" alt="" class="imgLz frmImg " />


[/quotemsg]

Well, aside from the BIOS, Clock & Boost rates, amount of VRAM, and the Pixel and Texture fillrates, there's not too much different with these cards. Clock rates can be adjusted, VRAM will usually drop to the card with the lowest, and the BIOS's can always be flashed. However, I noticed that the other card is in fact MSI, not Gigabyte, and regardless of the manufacturer, it still stands that each vendor modifies their cards in some ways, usually done so to the hardware itself where you won't always be informed of the difference. You could try theonerm2's driver fix and see if that helps, but it doesn't change the fact that those are two very different cards. I wish I could help you more beyond that but it's really all that can be said now. Please continue to let us know if you're still experiencing problems, I'll be more than glad to help!
m
0
l
July 5, 2013 4:18:20 PM

Mousemonkey said:
skept1k said:
Mousemonkey said:
Has your card been killed by these drivers? Personally I think it's just a load of cobblers being spread by AMD/ATi shills as I can't find anything to substantiate the so called issue other than anecdotal evidence, there is a big difference between artifacts and crashing and dead cards.


Actually yes, my first EVGA 460 GTX died as soon as I installed the new drivers
, I only recently got another one back from RMA. Whether or not it kills card it besides the point, the fact of the matter is is that myself and countless other Nvidia GPU users have experienced absolute hell with 320.18 WHQL. That is a fact, and can be found from hundreds of users all over forums everywhere. There's no reason to upgrade if there's nothing new for your card unless you're experiencing problems that they have fixed in the latest update. Short answer, if it isn't broken, why fix it?


Of course it did and as this is the internet your word is gospel.


I'm not here to argue with you, I'm here to help the OP with his current issues. I'm just sharing what has happened to me and explain what has happened to others. The internet is here as a resource for many, that is why people come to places like Tom's Hardware's forums. It's the reason that I came here originally. You clearly don't believe me, and that's fine, your entitled to your beliefs. It was my card, it ceased to function after 320.18 WHQL along with a few others, I RMA'ed the card and reinstalled 296.10 WHQL drivers and have yet to have any problems whatsoever. Now, instead of arguing with me, perhaps you should try to help the OP as I am.
m
0
l
July 5, 2013 4:27:09 PM

skept1k said:
Mousemonkey said:
skept1k said:
Mousemonkey said:
Has your card been killed by these drivers? Personally I think it's just a load of cobblers being spread by AMD/ATi shills as I can't find anything to substantiate the so called issue other than anecdotal evidence, there is a big difference between artifacts and crashing and dead cards.


Actually yes, my first EVGA 460 GTX died as soon as I installed the new drivers
, I only recently got another one back from RMA. Whether or not it kills card it besides the point, the fact of the matter is is that myself and countless other Nvidia GPU users have experienced absolute hell with 320.18 WHQL. That is a fact, and can be found from hundreds of users all over forums everywhere. There's no reason to upgrade if there's nothing new for your card unless you're experiencing problems that they have fixed in the latest update. Short answer, if it isn't broken, why fix it?


Of course it did and as this is the internet your word is gospel.


I'm not here to argue with you, I'm here to help the OP with his current issues. I'm just sharing what has happened to me and explain what has happened to others. The internet is here as a resource for many, that is why people come to places like Tom's Hardware's forums. It's the reason that I came here originally. You clearly don't believe me, and that's fine, your entitled to your beliefs. It was my card, it ceased to function after 320.18 WHQL along with a few others, I RMA'ed the card and reinstalled 296.10 WHQL drivers and have yet to have any problems whatsoever. Now, instead of arguing with me, perhaps you should try to help the OP as I am.


Try the driver again and see if it kills the new card, I have a problem with people spreading BS and having had no issues with said driver I take exception to your attitude.
m
0
l
July 5, 2013 4:37:56 PM

Mousemonkey said:
skept1k said:
Mousemonkey said:
skept1k said:
Mousemonkey said:
Has your card been killed by these drivers? Personally I think it's just a load of cobblers being spread by AMD/ATi shills as I can't find anything to substantiate the so called issue other than anecdotal evidence, there is a big difference between artifacts and crashing and dead cards.


Actually yes, my first EVGA 460 GTX died as soon as I installed the new drivers
, I only recently got another one back from RMA. Whether or not it kills card it besides the point, the fact of the matter is is that myself and countless other Nvidia GPU users have experienced absolute hell with 320.18 WHQL. That is a fact, and can be found from hundreds of users all over forums everywhere. There's no reason to upgrade if there's nothing new for your card unless you're experiencing problems that they have fixed in the latest update. Short answer, if it isn't broken, why fix it?


Of course it did and as this is the internet your word is gospel.


I'm not here to argue with you, I'm here to help the OP with his current issues. I'm just sharing what has happened to me and explain what has happened to others. The internet is here as a resource for many, that is why people come to places like Tom's Hardware's forums. It's the reason that I came here originally. You clearly don't believe me, and that's fine, your entitled to your beliefs. It was my card, it ceased to function after 320.18 WHQL along with a few others, I RMA'ed the card and reinstalled 296.10 WHQL drivers and have yet to have any problems whatsoever. Now, instead of arguing with me, perhaps you should try to help the OP as I am.


Try the driver again and see if it kills the new card, I have a problem with people spreading BS and having had no issues with said driver I take exception to your attitude.


Why would I take that risk and make the same mistake again? I don't exactly want to wait another 2 weeks to get another card in the event that it does. I'm not quite sure what "attitude" you're referring to, and if I've given the impression that I have one then I apologize. I'm not trying to spread BS, I'm just making it known that 320.18 WHQL drivers were an issue for a lot of people, myself included, just because your rig doesn't have an issue with them doesn't mean someone else's doesn't. Everyone out there has a rig with extremely varied hardware and with that comes unique problems for everyone. You can't compare your experience and set it as a standard to everyone else's. Now, I have installed 320.49 and they appear to work just fine, but as for 320.18, I do not recommend them. Again, if I appeared to have given "attitude" then I am sorry.
m
0
l
July 5, 2013 4:48:40 PM

skept1k said:
Mousemonkey said:
skept1k said:
Mousemonkey said:
skept1k said:
Mousemonkey said:
Has your card been killed by these drivers? Personally I think it's just a load of cobblers being spread by AMD/ATi shills as I can't find anything to substantiate the so called issue other than anecdotal evidence, there is a big difference between artifacts and crashing and dead cards.


Actually yes, my first EVGA 460 GTX died as soon as I installed the new drivers
, I only recently got another one back from RMA. Whether or not it kills card it besides the point, the fact of the matter is is that myself and countless other Nvidia GPU users have experienced absolute hell with 320.18 WHQL. That is a fact, and can be found from hundreds of users all over forums everywhere. There's no reason to upgrade if there's nothing new for your card unless you're experiencing problems that they have fixed in the latest update. Short answer, if it isn't broken, why fix it?


Of course it did and as this is the internet your word is gospel.


I'm not here to argue with you, I'm here to help the OP with his current issues. I'm just sharing what has happened to me and explain what has happened to others. The internet is here as a resource for many, that is why people come to places like Tom's Hardware's forums. It's the reason that I came here originally. You clearly don't believe me, and that's fine, your entitled to your beliefs. It was my card, it ceased to function after 320.18 WHQL along with a few others, I RMA'ed the card and reinstalled 296.10 WHQL drivers and have yet to have any problems whatsoever. Now, instead of arguing with me, perhaps you should try to help the OP as I am.


Try the driver again and see if it kills the new card, I have a problem with people spreading BS and having had no issues with said driver I take exception to your attitude.


Why would I take that risk and make the same mistake again? I don't exactly want to wait another 2 weeks to get another card in the event that it does. I'm not quite sure what "attitude" you're referring to, and if I've given the impression that I have one then I apologize. I'm not trying to spread BS, I'm just making it known that 320.18 WHQL drivers were an issue for a lot of people, myself included, just because your rig doesn't have an issue with them doesn't mean someone else's doesn't. Everyone out there has a rig with extremely varied hardware and with that comes unique problems for everyone. You can't compare your experience and set it as a standard to everyone else's. Now, I have installed 320.49 and they appear to work just fine, but as for 320.18, I do not recommend them. Again, if I appeared to have given "attitude" then I am sorry.


If they replaced the last one because the driver killed it then they will replace the next one and that might help in getting Nvidia to remove the driver like they did the last one they messed up, unless of course it was just a coincidence or BS in which case that may explain why you don't want to take the chance?
m
0
l
July 5, 2013 4:50:34 PM

skept1k said:
Mousemonkey said:
skept1k said:
Mousemonkey said:
skept1k said:
Mousemonkey said:
Has your card been killed by these drivers? Personally I think it's just a load of cobblers being spread by AMD/ATi shills as I can't find anything to substantiate the so called issue other than anecdotal evidence, there is a big difference between artifacts and crashing and dead cards.


Actually yes, my first EVGA 460 GTX died as soon as I installed the new drivers
, I only recently got another one back from RMA. Whether or not it kills card it besides the point, the fact of the matter is is that myself and countless other Nvidia GPU users have experienced absolute hell with 320.18 WHQL. That is a fact, and can be found from hundreds of users all over forums everywhere. There's no reason to upgrade if there's nothing new for your card unless you're experiencing problems that they have fixed in the latest update. Short answer, if it isn't broken, why fix it?


Of course it did and as this is the internet your word is gospel.


I'm not here to argue with you, I'm here to help the OP with his current issues. I'm just sharing what has happened to me and explain what has happened to others. The internet is here as a resource for many, that is why people come to places like Tom's Hardware's forums. It's the reason that I came here originally. You clearly don't believe me, and that's fine, your entitled to your beliefs. It was my card, it ceased to function after 320.18 WHQL along with a few others, I RMA'ed the card and reinstalled 296.10 WHQL drivers and have yet to have any problems whatsoever. Now, instead of arguing with me, perhaps you should try to help the OP as I am.


Try the driver again and see if it kills the new card, I have a problem with people spreading BS and having had no issues with said driver I take exception to your attitude.


Why would I take that risk and make the same mistake again? I don't exactly want to wait another 2 weeks to get another card in the event that it does. I'm not quite sure what "attitude" you're referring to, and if I've given the impression that I have one then I apologize. I'm not trying to spread BS, I'm just making it known that 320.18 WHQL drivers were an issue for a lot of people, myself included, just because your rig doesn't have an issue with them doesn't mean someone else's doesn't. Everyone out there has a rig with extremely varied hardware and with that comes unique problems for everyone. You can't compare your experience and set it as a standard to everyone else's. Now, I have installed 320.49 and they appear to work just fine, but as for 320.18, I do not recommend them. Again, if I appeared to have given "attitude" then I am sorry.


Yeah so I did the alternative drivers, and it's not detecting any gfx card, and can't run any games.
m
0
l
July 5, 2013 4:50:34 PM

skept1k said:
Mousemonkey said:
skept1k said:
Mousemonkey said:
skept1k said:
Mousemonkey said:
Has your card been killed by these drivers? Personally I think it's just a load of cobblers being spread by AMD/ATi shills as I can't find anything to substantiate the so called issue other than anecdotal evidence, there is a big difference between artifacts and crashing and dead cards.


Actually yes, my first EVGA 460 GTX died as soon as I installed the new drivers
, I only recently got another one back from RMA. Whether or not it kills card it besides the point, the fact of the matter is is that myself and countless other Nvidia GPU users have experienced absolute hell with 320.18 WHQL. That is a fact, and can be found from hundreds of users all over forums everywhere. There's no reason to upgrade if there's nothing new for your card unless you're experiencing problems that they have fixed in the latest update. Short answer, if it isn't broken, why fix it?


Of course it did and as this is the internet your word is gospel.


I'm not here to argue with you, I'm here to help the OP with his current issues. I'm just sharing what has happened to me and explain what has happened to others. The internet is here as a resource for many, that is why people come to places like Tom's Hardware's forums. It's the reason that I came here originally. You clearly don't believe me, and that's fine, your entitled to your beliefs. It was my card, it ceased to function after 320.18 WHQL along with a few others, I RMA'ed the card and reinstalled 296.10 WHQL drivers and have yet to have any problems whatsoever. Now, instead of arguing with me, perhaps you should try to help the OP as I am.


Try the driver again and see if it kills the new card, I have a problem with people spreading BS and having had no issues with said driver I take exception to your attitude.


Why would I take that risk and make the same mistake again? I don't exactly want to wait another 2 weeks to get another card in the event that it does. I'm not quite sure what "attitude" you're referring to, and if I've given the impression that I have one then I apologize. I'm not trying to spread BS, I'm just making it known that 320.18 WHQL drivers were an issue for a lot of people, myself included, just because your rig doesn't have an issue with them doesn't mean someone else's doesn't. Everyone out there has a rig with extremely varied hardware and with that comes unique problems for everyone. You can't compare your experience and set it as a standard to everyone else's. Now, I have installed 320.49 and they appear to work just fine, but as for 320.18, I do not recommend them. Again, if I appeared to have given "attitude" then I am sorry.


Yeah so I did the alternative drivers, and it's not detecting any gfx card, and can't run any games.
m
0
l
July 5, 2013 4:58:38 PM

Mousemonkey said:
skept1k said:
Mousemonkey said:
skept1k said:
Mousemonkey said:
skept1k said:
Mousemonkey said:
Has your card been killed by these drivers? Personally I think it's just a load of cobblers being spread by AMD/ATi shills as I can't find anything to substantiate the so called issue other than anecdotal evidence, there is a big difference between artifacts and crashing and dead cards.


Actually yes, my first EVGA 460 GTX died as soon as I installed the new drivers
, I only recently got another one back from RMA. Whether or not it kills card it besides the point, the fact of the matter is is that myself and countless other Nvidia GPU users have experienced absolute hell with 320.18 WHQL. That is a fact, and can be found from hundreds of users all over forums everywhere. There's no reason to upgrade if there's nothing new for your card unless you're experiencing problems that they have fixed in the latest update. Short answer, if it isn't broken, why fix it?


Of course it did and as this is the internet your word is gospel.


I'm not here to argue with you, I'm here to help the OP with his current issues. I'm just sharing what has happened to me and explain what has happened to others. The internet is here as a resource for many, that is why people come to places like Tom's Hardware's forums. It's the reason that I came here originally. You clearly don't believe me, and that's fine, your entitled to your beliefs. It was my card, it ceased to function after 320.18 WHQL along with a few others, I RMA'ed the card and reinstalled 296.10 WHQL drivers and have yet to have any problems whatsoever. Now, instead of arguing with me, perhaps you should try to help the OP as I am.


Try the driver again and see if it kills the new card, I have a problem with people spreading BS and having had no issues with said driver I take exception to your attitude.


Why would I take that risk and make the same mistake again? I don't exactly want to wait another 2 weeks to get another card in the event that it does. I'm not quite sure what "attitude" you're referring to, and if I've given the impression that I have one then I apologize. I'm not trying to spread BS, I'm just making it known that 320.18 WHQL drivers were an issue for a lot of people, myself included, just because your rig doesn't have an issue with them doesn't mean someone else's doesn't. Everyone out there has a rig with extremely varied hardware and with that comes unique problems for everyone. You can't compare your experience and set it as a standard to everyone else's. Now, I have installed 320.49 and they appear to work just fine, but as for 320.18, I do not recommend them. Again, if I appeared to have given "attitude" then I am sorry.


If they replaced the last one because the driver killed it then they will replace the next one and that might help in getting Nvidia to remove the driver like they did the last one they messed up, unless of course it was just a coincidence or BS in which case that may explain why you don't want to take the chance?


Praedos said:
skept1k said:
Mousemonkey said:
skept1k said:
Mousemonkey said:
skept1k said:
Mousemonkey said:
Has your card been killed by these drivers? Personally I think it's just a load of cobblers being spread by AMD/ATi shills as I can't find anything to substantiate the so called issue other than anecdotal evidence, there is a big difference between artifacts and crashing and dead cards.


Actually yes, my first EVGA 460 GTX died as soon as I installed the new drivers
, I only recently got another one back from RMA. Whether or not it kills card it besides the point, the fact of the matter is is that myself and countless other Nvidia GPU users have experienced absolute hell with 320.18 WHQL. That is a fact, and can be found from hundreds of users all over forums everywhere. There's no reason to upgrade if there's nothing new for your card unless you're experiencing problems that they have fixed in the latest update. Short answer, if it isn't broken, why fix it?


Of course it did and as this is the internet your word is gospel.


I'm not here to argue with you, I'm here to help the OP with his current issues. I'm just sharing what has happened to me and explain what has happened to others. The internet is here as a resource for many, that is why people come to places like Tom's Hardware's forums. It's the reason that I came here originally. You clearly don't believe me, and that's fine, your entitled to your beliefs. It was my card, it ceased to function after 320.18 WHQL along with a few others, I RMA'ed the card and reinstalled 296.10 WHQL drivers and have yet to have any problems whatsoever. Now, instead of arguing with me, perhaps you should try to help the OP as I am.


Try the driver again and see if it kills the new card, I have a problem with people spreading BS and having had no issues with said driver I take exception to your attitude.


Why would I take that risk and make the same mistake again? I don't exactly want to wait another 2 weeks to get another card in the event that it does. I'm not quite sure what "attitude" you're referring to, and if I've given the impression that I have one then I apologize. I'm not trying to spread BS, I'm just making it known that 320.18 WHQL drivers were an issue for a lot of people, myself included, just because your rig doesn't have an issue with them doesn't mean someone else's doesn't. Everyone out there has a rig with extremely varied hardware and with that comes unique problems for everyone. You can't compare your experience and set it as a standard to everyone else's. Now, I have installed 320.49 and they appear to work just fine, but as for 320.18, I do not recommend them. Again, if I appeared to have given "attitude" then I am sorry.


Yeah so I did the alternative drivers, and it's not detecting any gfx card, and can't run any games.


Well, there goes that possible fix. Try upgrading to 320.49 again (assuming that's what you were on) or whichever driver you had before. Honestly, there's not much you can do aside from getting a matching card. SLi setups have always been pretty finicky. AMD's a bit more forgiving as far as mixing and matching goes, you can mix a 7950 with a 7970 and so and so forth, but we all know crossfire has its downsides and so does SLi. Try running Driver Sweeper in safe mode and then reinstall your preferred driver. That may or may not help but if you install drivers pretty frequently it's always best to ensure you get the cleanest installation possible.
m
0
l
July 5, 2013 10:15:21 PM

Mousemonkey said:
skept1k said:
theonerm2 said:
Praedos said:
@skept are there any ways around this?


Run DifferentSLI the modded driver. Run the latest one 320.18. You problem should be solved after that. I had the same problem with an OEM GTX 460 and a PNY XLR8 GTX 460.

http://www.techpowerup.com/forums/showthread.php?t=1589...


Careful with the new 3xx+ series drivers, they've been known to kill fermi cards. 320.49 WHQL is the most stable, although still VERY problematic. Moving on, even if he does get this setup to work, it doesn't change the fact that he could be presented with a plethora of issues because they're made by different manufacturers with entirely different modifications.


Oh really? So how comes they haven't killed mine then?


I used 300 series drivers on my GTX 460's and the were fine. I bought them on ebay for $90 each. Then I found 2 GTX 470's for $100 each... Sold the 460's and bought the 470's. GTX 470's actually can't overvolt because there is a resistor on the board that prevents overvolting. So I'm not worried about that. This is the first I've heard of that problem.
m
0
l
!