Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread
New Posts  All Forums:Forum Nav:

ROG Crosshair VI overclocking thread - Page 976

post #9751 of 17654
Quote:
Originally Posted by majestynl View Post

I'm not saying it isn't. I'm just suggesting it could be a different one if you are in development. Nothing more so please read whole story before answering..

We don't keep the same UEFI version number when a change has been made. And you should follow your own advice. Had you looked at my screenshots, you'd have seen the tRC wasn't as claimed.
post #9752 of 17654
Quote:
Originally Posted by Raja@ASUS View Post

We don't keep the same UEFI version number when a change has been made. And you should follow your own advice. Had you looked at my screenshots, you'd have seen the tRC wasn't as claimed.

What kind of results do you see with tight timings?

On bios 0081

I am able to boot and train 3200mhz memory with the 3200 strap.

My timings are set to 12-12-12-22. I have however found that the M.2 Drive will give errors, sometimes it will not even boot windows (M.2 link set to auto) saying it is unable to read from the drive.

I was tempted to just throw more voltage at the DRAM, but I was already at 1.41v... Is there anyway to stabilize the M.2 with tight memory timings without just turning up the DRAM voltage?

Also... The PLL voltage and the sub-36 CPU ratio are limiting my ability to run 3600mhz Dram.

I can boot and run fine at 3600mhz memory at the 3200 strap (14-14-14-32 is as low as I tried) all the way down to the 2400 strap with high BCLKs, but the Thermal throttle kicks in at 95'C tctl; which made no sense to me as I should not be running that hot.

After some testing I have found that since I need to raise my PLL to 1.9v, It artificially raises the tctrl temp, so I see CPU throttling under load, even thought the CPU is not running anywhere near 95'C (it is closer to 60'C). Another user here set PLL to 1.7v and his Tctl showed -7'C

Is there anything we can do to fix this in the BIOS?

Validations:

https://valid.x86.fr/a5eexw

https://valid.x86.fr/q0n4fa

https://valid.x86.fr/alj9hi

https://valid.x86.fr/gs4kk6
Edited by Gadfly - 4/16/17 at 10:58pm
post #9753 of 17654
You can try playing with Sense MI Skew, but I'm not sure that will sort out the problem. In truth, any overclock that needs multiple changes just to POST, is best dialed back to a level that doesn't. The platform is what it is right now.
post #9754 of 17654
Did anyone have an issue with their NVMe Drive where it would detect just fine on system power on boot, yet after OS restart you'd be dropped straight into BIOS because your drive isn't detected? OCZ RD400 here, really have no clue what the issue is. And it's repeatable - first boot everything is fine, restart from windows > drive not detected.
P.S.: 0083 bios currently, had the same issue on 2 previous versions.
post #9755 of 17654
Quote:
Originally Posted by Ne01 OnnA View Post

Try to dust-off it a little or Re-apply Termal Comp. biggrin.gif

I've dusted it off so many times. Its actually so bad that trying to run it at its factory setting causes Raedon Wattman to crash, or in worse cases 8 code PC crash.

Havent re/applied thermal comp on a vid card before. I'm not even sure its worth the effort for this thing.
Quote:
Originally Posted by SwiperNoSwiping View Post

Did anyone have an issue with their NVMe Drive where it would detect just fine on system power on boot, yet after OS restart you'd be dropped straight into BIOS because your drive isn't detected? OCZ RD400 here, really have no clue what the issue is. And it's repeatable - first boot everything is fine, restart from windows > drive not detected.
P.S.: 0083 bios currently, had the same issue on 2 previous versions.

that happens with any type of drive. I've had it happen with 2 SATA SSD's. Usual fix for me is to just save + reset in bios with no changes made, go back into bios each time and check and see if my drive(s) are detected again in SATA device config, and if so fix the boot priority. Usually takes no more than 2 resets to get them detected again. I'm not sure what triggers the loss of drive detection. Its possibly due to a qualified device deal.
http://dlcdnet.asus.com/pub/ASUS/mb/SocketAM4/CROSSHAIR-VI-HERO/CROSSHAIR-VI-HERO_DEVICE_QVL.pdf?_ga=1.101158785.1020007620.1477006342

I also replaced all my long-used SATA cables. Some of them were warped at the connectors, but that of course wont work on an M.2 drive
Edited by Reikoji - 4/16/17 at 11:34pm
post #9756 of 17654
Quote:
Originally Posted by Reikoji View Post

that happens with any type of drive. I've had it happen with 2 SATA SSD's. Usual fix for me is to just save + reset in bios with no changes made, go back into bios each time and check and see if my drive(s) are detected again in SATA device config, and if so fix the boot priority. Usually takes no more than 2 resets to get them detected again. I'm not sure what triggers the loss of drive detection. Its possibly due to a qualified device deal.
http://dlcdnet.asus.com/pub/ASUS/mb/SocketAM4/CROSSHAIR-VI-HERO/CROSSHAIR-VI-HERO_DEVICE_QVL.pdf?_ga=1.101158785.1020007620.1477006342

I also replaced all my long-used SATA cables. Some of them were warped at the connectors, but that of course wont work on an M.2 drive

Yeah, but I was hoping that there's a permanent fix to this. It's really quite bothersome.
post #9757 of 17654
Quote:
Originally Posted by XEKong View Post

Is anyone getting this error pop up in the event viewer.

The IO operation at logical block address 0x25d62740 for Disk 0 (PDO name: \Device\00000039) was retried.
Reset to device, \Device\RaidPort0, was issued.

@XeKong
I'm getting the same error and some more with the AMD raid driver. I assume you are using the AMD raid driver and running some sort of raid config.

I'm running two "raid 1" with 4 SSD's. After booting in Windows 10 Pro x64 I'm always getting a BSOD with a power state failure. I did a minidump analysis.
The AMD raid driver "AMD-RAID Controller [storport]" has a problem with the power states. I've tried a lot of tricks to get this driver stable, but no luck.
After reboot from the BSOD the driver is stable as a rock, runs for hours without any problem. So I opened a support ticket at AMD. I'm still waiting for an answer from AMD.
When I got feedback from AMD I will post it here.
post #9758 of 17654
I found my 1700's sweet spot (balance between silent/cool/performance). Seems to be 3.85Ghz with voltage offset of .131. It will idle at 1.33V and 27-28C and go to full load (IBT High) at 60C, voltage drops to 1.28. Cooling is H110i GT with fans running at 900 constantly (can't hear them).

Memory stays at 2666, 14-14-34 until new agesa comes.
CPU-z validation
post #9759 of 17654
Alright so as a last-ditch effort I tried to flash my BIOS back to 902 which at least made it through POST once yesterday and also the BIOS on the Disc and yet both eventually get stuck on Boot LED Q-Code 0d ... I'll wait till tomorrow and try to contact asus tech support and I'll prepare to buy a new Board :/
Edited by Karpata - 4/17/17 at 2:09am
post #9760 of 17654
Quote:
Originally Posted by carlosdivega View Post

@XeKong
I'm getting the same error and some more with the AMD raid driver. I assume you are using the AMD raid driver and running some sort of raid config.

I'm running two "raid 1" with 4 SSD's. After booting in Windows 10 Pro x64 I'm always getting a BSOD with a power state failure. I did a minidump analysis.
The AMD raid driver "AMD-RAID Controller [storport]" has a problem with the power states. I've tried a lot of tricks to get this driver stable, but no luck.
After reboot from the BSOD the driver is stable as a rock, runs for hours without any problem. So I opened a support ticket at AMD. I'm still waiting for an answer from AMD.
When I got feedback from AMD I will post it here.

No, I am not running RAID. Just two separate SSD's.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread