2017 Hardware Thread

Oh, so Slippery did get his today. Just OldMike and me waiting. Figures. They probably looked at our hardware and said these two guys are used to waiting for software fixes. They have Corsair coolers.

Thanks guys.

I'm using the 3504 UNvalidated bios. I typically get this when I run Time Spy/Firestrike even no OC.



Not clear to me if it's the 3504 bios or Rivatuner beta 7. I ran Time Spy with Rivatuner disabled (no OSD, no FPS monitoring) which shuts Rivatuner down. Still got this. Hard to isolate. It doesn't always happen.

Dude: do you get this? You also run latest AB/RTSS

"specialkone

Oh, so Slippery did get his today. Just OldMike and me waiting. Figures. They probably looked at our hardware and said these two guys are used to waiting for software fixes. They have Corsair coolers. "


Yeah, well my 3401 was never validated
And I do have the Corsair cooler and have to run the 4.6 link so it'll start in my user acct. So, I don't get to have 24 fans

Oh, my 3401 was Asus validated. If it shows up on their download site (not beta) for your MB is should be Asus tested. But my 3504 isn't validated and thus not on their download site.

Ah yes you do have the Corsair cooler Slippery with the billion phantom fans issue. I have to go back to 4.5.055 to show the right number of fans. Not doing that because older Links versions don't run my fans at specified settings (while in bios) until I'm on the desktop. Still waiting for a PHANTOM FAN FIX. Not going to happen so it seems.

specialkone said:

I'm using the 3504 UNvalidated bios. I typically get this when I run Time Spy/Firestrike even no OC.



Not clear to me if it's the 3504 bios or Rivatuner beta 7. I ran Time Spy with Rivatuner disabled (no OSD, no FPS monitoring) which shuts Rivatuner down. Still got this. Hard to isolate. It doesn't always happen.

Dude: do you get this? You also run latest AB/RTSS

Ran fine here RTSS 7.0 with OSD running in everything, works great. Stock run at 4.4, GPU def, bios 3504

http://www.3dmark.com/3dm/21520147?

Dude said:

No,
.. try nudging your vcore either up or down just a bit. Its the way it reads timings so it needs tweaking sometimes

I've heard that suggestion before. Vcore is at about 1.25 at stock. When I go to 4.8 I set it at 1.37. Under both those scenarios I still get the time measurement message.