Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
I heard the .2 drivers are iffy so im just using the .1 drivers for now which introduced drivers for 6700xt cards.
Hey I got mine also ... wondering. Im trying to give 3d mark timespy a whirl and I get a driver time out everytime - reinstalled windows and latest beta driver and my mb bios etc ... can you give timespy a whirl to see if yours can run it (its the demo version from steam).
So I take you your replacement was fine and your original was indeed faulty judging by the above comment.
You are now using two separate PCIE cables to feed the card ie PCIE > 8 pin and PCIE > 6 pin and not PCIE > 6+8 pin.
Before I knew that there were some Fighters in stock still I asked about getting a Sapphire Nitro as a replacement and paying the difference but they did not want to do that.
Yea very, pleased with it so far. It’s quieter than I expected actually given it’s smaller cooler, bit quieter than my old MSI 1080Ti with Twin Frozer cooler ... and half the size at that.I think I got 'lucky' with the exchange, your fighter is running well and quiet?
Yea very, pleased with it so far. It’s quieter than I expected actually given it’s smaller cooler, bit quieter than my old MSI 1080Ti with Twin Frozer cooler ... and half the size at that.
I was able to send the fighter back and get the nitro, I assume the fighter was dead, I only know that they are going to give me a refund for the fighter - didnt tell me if it was indeed broken. The nitro booted up fine with the same pcie cable 8 and 6, if I have to test with 2 different cables Ill need to tear my system apart again (dont really want to do that), let me put it this way - in order for me to connect 2 pcie cables I need to take off my top radiator, 1/2 way take out my psu, unplug some cables, and plug some in and plug a different cable into the mb cpu power ... anyways its a real pain ... but I will if this is the problem.

It is best if you can do 2 separate pcie cables, for high or highish gpus just so the power is full on both of the pcie lines going into gpu so theres no drop off if sharing 1 cable for 2 ends. Lower end or low power usage cards i wouldnt imagine needing it like 150w or below ones. Tho if it works atm for you then leave it tbh, sometimes ppl can have issues some dont, sometimes 2 separate ones helps.
djxput: About xmp, i dunno mate, it shouldnt affect the gpu tbh, maybe take xmp off and manually do the timings as i tried once to help someone in memory forum and he had loads of crashes and what not, it turns out the mb didnt do the right timings when using xmp so u had to do it manually. He never got back to me if it fixed it but pretty sure i found the fix for him.
So try manual timings, might help i dunno? If theres any ocing going on, maybe ease off it somewhat or try stock for a bit?
Also to anyone using that SAM thing, ive heard ppl having crashes with it, so if you are having issues with a system and u have it on, try turning it off see if it helps.
Im thinking its one of my ram sticks - funny I previously tested using mem86+ or whatever that test is called and ran it for 6 hours (64 gigs of ram takes forever) and no errors. But I decided to try each stick separately and the first one was the usual crash in timespy but I did 1 pass with the 2nd stick and I finished the run and will try again. Its been awhile since I purchased this thou.
If it is ram then at least its replaceable as i think all ram state lifetime warranty's so you can get some replacements for free tho they might charge postage?
Sorry should have updated... My one ramstick was bad, although that wasn't the issue with my 6700xt not posting - thst was a dead card.
Because the next card I got booted fine, I also got replacement ram and my benchmarks ran fine which before using the bad stick I'd get a Radeon driver crash, not even sure how I figured out it was the ram. But it was...
