Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
As for the Asus, much like JayzTwoCents
Changing options in the EFI lead to the exact same results. Initial target was a flat 4Ghz at 1.35v.
Somehow, after one of those reboots, I ended up with the same BIOS is updating screen seen here:
After letting the machine sit for 20 minutes, I started to get worried. Luckily, I needed to run out for couple of hours, so I let it sit. Come home 3 hours later, same screen. Only thing left to do was to reset (which did nothing) then pull the power. Once that happened, it never started again. It was clearly getting power as the RGB lighting was still pulsing different colors and the ready LEDs were lit green as the manual says, but the power switches didn't function.
Non of the usual tricks worked. Pulling board power didn't work, pulling PSU power until it drained didn't work, using BIOS flashback didn't work, none of the onboard power/reset/safe mode buttons worked.
It literally shit itself.
At this point, I'm kinda done with Asus for a while. That's 3 boards in a row that have had some kind of un-correctable issue (X99-A, X99 Deluxe, and now the C6H), which is the wrong answer for what they charge. Switched to ASRock with X99 as well and the issues went away.
EDIT: Whoa, quoting timestamped vid links preview the same thing >.>
Well, admittedly, I am now just slightly concerned. However, I had an Asus 970 Pro Aura that gave no issues. Now I have a Prime X370 Pro and so far, no issues either. When I do an unstable overclock, I end up with the same machine will flat out black out and no come back until I do a hard shutdown and power on.
I'm very pleased. Well now I am. After watching the Asus Crosshair shit itself when attempting to OC, I exchanged it for an ASRock Fatality and I couldn't be more pleased. Getting to 4.05Ghz @ 1.344v was as easy as changing 3 or 4 EFI options.
http://valid.x86.fr/8zvdkq
So Curl. Still digging that board? I'm thinking about jumping ship on the asus for it.
I sure hope G.Skill validates https://hardforum.com/threads/g-skill-flare-x-and-fortis-for-ryzen.1926514/ with that fatality board.
If so that will wrap it up for me. I'm gonna have to get 1700, the fatality, the 32gb cl14 3200, and the 1080ti. I'm not waiting for Vega any longer. Plus that last "event" really pissed me off with the lack of product details. Kyle threw more meaningful shit with the episodic VR then AMD did about their product.
I have my Ryzen 1800X and my Asus Crosshair 6 and my 64gb of DDR4 3200 and even a Samsung 960 EVO 500gb stick etc... but not my AM4 bracket connector for my NZXT X62... douh! Literally staring at all the parts and missing 1. It looks fast... sigh
Got all my parts tonight. In the middle of building it now.
Ha, it's a 1800x. Wanted to go for the best. Not really much of an overclocker myself (it's never worked out for me) but I may try a little just to see.tell me you got the 1700 and planning on clocking it to 4ghz lol. and you put the other 180 bucks towards one of the rx 480. Hahaha
As for the Asus, much like JayzTwoCents
Changing options in the EFI lead to the exact same results. Initial target was a flat 4Ghz at 1.35v.
Somehow, after one of those reboots, I ended up with the same BIOS is updating screen seen here:
After letting the machine sit for 20 minutes, I started to get worried. Luckily, I needed to run out for couple of hours, so I let it sit. Come home 3 hours later, same screen. Only thing left to do was to reset (which did nothing) then pull the power. Once that happened, it never started again. It was clearly getting power as the RGB lighting was still pulsing different colors and the ready LEDs were lit green as the manual says, but the power switches didn't function.
Non of the usual tricks worked. Pulling board power didn't work, pulling PSU power until it drained didn't work, using BIOS flashback didn't work, none of the onboard power/reset/safe mode buttons worked.
It literally shit itself.
At this point, I'm kinda done with Asus for a while. That's 3 boards in a row that have had some kind of un-correctable issue (X99-A, X99 Deluxe, and now the C6H), which is the wrong answer for what they charge. Switched to ASRock with X99 as well and the issues went away.
EDIT: Whoa, quoting timestamped vid links preview the same thing >.>
That looks rather sharp! Way better then what mine will probably look like.Got the build almost done. Only thing left is adding the LEDs but otherwise all the hardware is in there.
Definitely the cleanest build I've ever done. Sadly I wasn't able to try it tonight. Did turn it on, and the lights lit up and the fans went on and everything, but the debug LED was showing a code that wasn't in the manual. Not going to worry to much, will test tomorrow.
Got the build almost done. Only thing left is adding the LEDs but otherwise all the hardware is in there.
Definitely the cleanest build I've ever done. Sadly I wasn't able to try it tonight. Did turn it on, and the lights lit up and the fans went on and everything, but the debug LED was showing a code that wasn't in the manual. Not going to worry to much, will test tomorrow.
It's the Phanteks ENTHOO EVOLV Tempered Glass.That is a really clean and sweet looking build.
Hey, what case is that? I plan to go pure m.2 so I don't need drive cages any longer.
Are you guys installing you mobo chipset driver ? Windows picks up everything on my 1700, X370 Pro build.
One thing on DDR4 that crops up in the X99 stuff, sometimes it needs quite a bit more voltage than recommended to run stable. I think my GSkill says 1.375v, I've been at 1.4v since 2015. Doesn't seem to hurt anything, a lot of X99 rigs are even higher voltage than I run.
Just something to consider, might make the difference on a marginal DRAM OC.
Would the Ryzen Chipset Driver direct from AMD site be better than the motherboard Chipset Driver ?
looks like the crosshair board is having some issues. I have seen more people complain about those than any other board. May be Asus just couldn't get their shit together with bios.