06-06-2014 12:56 AM - last edited on 03-05-2024 09:46 PM by ROGBot
06-06-2014 07:37 AM
06-06-2014 08:45 AM
06-06-2014 09:09 AM
06-06-2014 09:30 AM
06-06-2014 09:30 AM
06-06-2014 09:41 AM
MatsGlobetrotter wrote:
maybe its your version of drivers, Firestrike, DX11 Win 7 patches and so forth test in another benchmarker that push the card the same way. If its 3 different computers, 2 different GPUs then its not 100% the GPU card.. then it can be a whole lot of other issues. . Unless ofcourse you have a generic hardware issue in the PCIE port that destroy the card in the first machine and then show the same issue in the others, who knows.
Arne Saknussemm wrote:
If you downclock the card to standard refference base clock and boost clock with Afterburner or something like that does this still happen.
Arne Saknussemm wrote:
Also when you say three different systems is that different installs of Firestrike and different graphics driver versions? Just to rule those things out...
06-06-2014 10:40 AM
trelokomio wrote:
If i downclock the card to standard refference base clock and boost clock the gpu runs 3dmark fire strike with no issues, no problem.
06-06-2014 11:22 AM
Arne Saknussemm wrote:
In that case and with all the other substitutions... I think the card is bad and can't handle the factory OC...you sure they gave you a new one not the old one back?...either way you'll just have to send it back and this time with a damning letter of complaint. 😞
06-26-2014 03:03 AM
trelokomio wrote:
Yes i am sure, because i hold the s/n of the fisrt one and the second one had different serial number, so iam absolutely sure that he gave me new card!
If cant handle the factory oc both of the cards, how is possible to run stable other benches an the problem appears only at 3dmark fire strike?