some problems with crosshair hero VI (1002)

Pieter3dnow

Pieter3dnow

Supreme [H]ardness
Joined
Jul 29, 2009
Messages
6,784
I been having these problems with cold boot where the system would stop with 0d. It would clear up fine after cmos clear it is a morning ritual of applying the same settings and reboot until now.

My boot process stops at 54 or 55 (qled code) now. Even when changing something trivial as dram (boot) voltage from auto to 1.35 (both settings) it does not want to play any more. (btw no pci-e devices connected just SATA)

I'm not to sure what is going on.

The settings that I usually apply are adjustments to ram (3200 + timings).
 
Well this is odd , odd enough to mention this but running my sapphire tri-x R9 290x flipping the switch on the videocard allowed me to get the settings back again. Some problem between the card and the bios (the switch is for eufi compatibility) Something that I have never ever had to use.
 
I'm angry at AMD/ASUS with this shitshow of a release, so pardon my grumpiness (it's mostly AMD's fault, but ASUS shouldn't have rushed either).


There are known cold boot issues with the R6H. They have released a 0003 beta/test bios in the overclock.net forums, which has the main focus on the cold boot issue. It basically made my M.2 drive no longer be recognized, and flashing back to 1002 didn't fix it. They had to send me another weird BIOS to get my system back up and running.


This computer is a dumpster fire, and I expect a few more months of complete misery before they get shit ironed out.

I have never had so little fun with a computer build. My advice is to put your Ryzen build in a closed for 2 months, then get it back out and start tweaking.
 
I'm not going to even try and overclock it.

I can't blame Asus or AMD for anything I can understand that they have to release the cpu and release the motherboard , what you would hope for is that with the same enthusiasm they fix the bios problems.

AMD has not released anything in a good while and it is different from the FMx launch which was not that different from AM3+ . Early adopters to name a cliché ;)
 
I've been building computers A LONG TIME and I've never experienced early adoption bullshit like this. We are nearing 2 months in and you still can't reliably TURN ON YOUR F-ING COMPUTER.

There is "early adoption problems" and there is "here BETA TEST THIS RUSHED PRODUCT FOR US."

We are in the beta testing phase, but we paid retail.
 
I'm still using my P8Z68v- gen 3 but for the life of me I seem to remember that there was some kind of a shit storm with these mobo's and we had to send them all back to get gen 3. A search on Google does not net me any info about the original gen, or a gen 2. Could this be what's going to happen with the current crops of AM4 boards?
 
y0bailey said:
I've been building computers A LONG TIME and I've never experienced early adoption bullshit like this. We are nearing 2 months in and you still can't reliably TURN ON YOUR F-ING COMPUTER.

There is "early adoption problems" and there is "here BETA TEST THIS RUSHED PRODUCT FOR US."

We are in the beta testing phase, but we paid retail.
Click to expand...
Where are you paying retail for beta motherboards? Those generally cost four and five times what retail boards cost! :p
 
y0bailey said:
I've been building computers A LONG TIME and I've never experienced early adoption bullshit like this. We are nearing 2 months in and you still can't reliably TURN ON YOUR F-ING COMPUTER.

There is "early adoption problems" and there is "here BETA TEST THIS RUSHED PRODUCT FOR US."

We are in the beta testing phase, but we paid retail.
Click to expand...

I said it was a cliché. Something you expect but not hope for.

That feeling for me is with gaming software more then this hardware. AMD had a small window and the development window for the finished bios was not aligned with their financial goals for the fiscal year.
To bounce the ball back to Asus , Asus does not believe that any of these beta bios are worthy enough to release them to retail. That makes me wonder how much they are changed and that it prolly has more effect on memory that was down right incompatible.

I'm not happy about the procedure for this board but I can live with that, due in May were getting the fix that should set us on a better path.

.
 
Updated to latest bios on my CH VI and it overcloxks wonderfully. Not sure if you actually know how to overclock these?
 
RaptormanUSMC said:
Try this bios. Make sure you clear CMOS, and use USB Flashback to apply this one. Do not use EZ Flash. http://www.mediafire.com/file/3o3n5zdrx291lbf/CROSSHAIR-VI-HERO-ASUS-1107.zip

This bios and bios 0082 worked great for me overclocking, and 3200 strap. 0082 had cold boot issues if ambient temp was below 70F. 1107 Seems to be the best bios release so far.
Click to expand...

Yeah I saw this bios floating around waiting for the one that comes in May , that would prove the best solution in the end.

http://www.overclock.net/t/1624603/rog-crosshair-vi-overclocking-thread/12420#post_26055686
 
y0bailey said:
I'm angry at AMD/ASUS with this shitshow of a release, so pardon my grumpiness (it's mostly AMD's fault, but ASUS shouldn't have rushed either).


There are known cold boot issues with the R6H. They have released a 0003 beta/test bios in the overclock.net forums, which has the main focus on the cold boot issue. It basically made my M.2 drive no longer be recognized, and flashing back to 1002 didn't fix it. They had to send me another weird BIOS to get my system back up and running.


This computer is a dumpster fire, and I expect a few more months of complete misery before they get shit ironed out.

I have never had so little fun with a computer build. My advice is to put your Ryzen build in a closed for 2 months, then get it back out and start tweaking.
Click to expand...

Not all of us are experiencing this. I can cold boot 4/5 times successfully on 0082 with my 3.9/32GB/2666 build. The 20% of the time it doesn't work, a quick reset button press gets it booted.

Resuming from sleep doesn't work, and it can't clock down as low as my 4770K could (1900-2200mhz vs 800mhz) so I always shut the computer down after using it.... but I wouldn't call this a dumpster fire by any stretch of the imagination.
 
Out of curiosity, has anyone had an issue with the onboard RGB lights? More specifically, the ones on the I/O shroud? Mine completely stopped working after opening up my case to replace a fan- I double checked to see if may I disconnected a cable, but it doesn't appear to look like it. FYI, the RGB lighting featuring the ROG logo on the board works perfectly fine. I just don't know what the heck happened with the I/O shroud lighting...

ASUS support said it fell under warranty, but if there's a quick fix to avoid having to send this back in, I'd very much prefer giving that a shot before being down on a machine for a week or two.
 
Did you solve your issue? I'm curious because mine has a somewhat related (but not exactly same) problem. Been trying UEFI 1002, 2001 and 9943. No luck so far.
Edit: When you turn off the system, do you unplug it completely? (either turn off PSU's switch or unplug it from the wall).
 
Xyvotha said:
Did you solve your issue? I'm curious because mine has a somewhat related (but not exactly same) problem. Been trying UEFI 1002, 2001 and 9943. No luck so far.
Edit: When you turn off the system, do you unplug it completely? (either turn off PSU's switch or unplug it from the wall).
Click to expand...

I actually ended up exchanging the board for another one- did an RMA with ASUS, but they never got a shipping label sent for me, so I just swapped out the board at Fry's where I had picked it up. I'm using the 9945 BIOS right now, and it's a bit strange: RGB lights don't come on unless I boot into Windows after having entered the BIOS at some point. Doesn't matter much to me at this stage, was happy I had a working board with the lights.

I don't have my system unplugged completely- but I did somewhat mimic it by adjusting the ErP settings in BIOS. I think I'm using S4+S5, but I have lights still enabled (in the sense that the Start button's lights are active, as are my GPU's power lights). I know if I have a full shutdown without any power going to the board, I'll have trouble booting up into Windows (3-6 cycle reboots before I can enter BIOS).

EDIT: just saw your other thread - I don't think I've 'bricked' to the point where I'd have to flash a new BIOS, just typical cold boot problems that I've kind of grown used to.
 
Xyvotha said:
Did you solve your issue? I'm curious because mine has a somewhat related (but not exactly same) problem. Been trying UEFI 1002, 2001 and 9943. No luck so far.
Edit: When you turn off the system, do you unplug it completely? (either turn off PSU's switch or unplug it from the wall).
Click to expand...

Fix no , work around yes , the bios 1201 is far more stable then previous ones for me. I saw your the thread you posted. My ordeal is that the cycle of the bios was so erratic that it took sometimes half a hour to fix cold boot because it was stuck on 54 (error code) and would not get past it after power down.

The system is quirky, but nothing that can't be fixed in updates.
 
Pieter3dnow said:
Fix no , work around yes , the bios 1201 is far more stable then previous ones for me. I saw your the thread you posted. My ordeal is that the cycle of the bios was so erratic that it took sometimes half a hour to fix cold boot because it was stuck on 54 (error code) and would not get past it after power down.

The system is quirky, but nothing that can't be fixed in updates.
Click to expand...
Similar situation here, cold boot takes around half an hour for the Start button to be responsive.
 
Running 1201 bios now I ran into this problem, maybe it is my lack of knowledge of how memory overclock work but still.

So the daily routine of getting out of the cold boot problem is either adjust normal dram voltage or boot voltage. Doesn't matter which I pick they work I'm booting into 3200 every time.
So today nothing changes but some of the settings which can help I changed after bios posted the setting were bankgroupswap (disabled) and the failcnt (3). saving bios would result in ( you did not change anything are you sure you want to save).
Then the whole thing goes into the reboot loop, that makes so little sense there must be something terribly wrong either with my limited settings or with the bios as a whole.

What causes the bios to behave so erratic?
 
Last edited:
Araxie said:
a failed or corrupted BIOS Flash.

Can you at least go into BIOS and reset default/optimized settings?.
Click to expand...

It never causes any permanent failure just that it is not willing to play nice at all times.
 
Pieter3dnow said:
Running 1201 bios now I ran into this problem, maybe it is my lack of knowledge of how memory overclock work but still.

So the daily routine of getting out of the cold boot problem is either adjust normal dram voltage or boot voltage. Doesn't matter which I pick they work I'm booting into 3200 every time.
So today nothing changes but some of the settings which can help I changed after bios posted the setting were bankgroupswap (disabled) and the failcnt (3). saving bios would result in ( you did not change anything are you sure you want to save).
Then the whole thing goes into the reboot loop, that makes so little sense there must be something terribly wrong either with my limited settings or with the bios as a whole.

What causes the bios to behave so erratic?
Click to expand...
If it is an AMD AGESA setting which ASUS does not have a separate setting (they have many that overrides the AMD section, basically a repeat of the setting) then when you save the bios it will not indicate those settings and at times you will get that nothing change bit before you save, even though you did and it will save.

If memory fails to train on boot (especially cold) it will reset the bios, if your memory is not quite stable on that initial bootup then those irritating boot loops results. Are you using a ram boot voltage? For example unless you set the ram boot voltage it will try to train at 1.2v which is more likely to fail if you are OCing the ram vice at 1.35v+.
 
noko said:
If it is an AMD AGESA setting which ASUS does not have a separate setting (they have many that overrides the AMD section, basically a repeat of the setting) then when you save the bios it will not indicate those settings and at times you will get that nothing change bit before you save, even though you did and it will save.

If memory fails to train on boot (especially cold) it will reset the bios, if your memory is not quite stable on that initial bootup then those irritating boot loops results. Are you using a ram boot voltage? For example unless you set the ram boot voltage it will try to train at 1.2v which is more likely to fail if you are OCing the ram vice at 1.35v+.
Click to expand...

My boot voltage is up to 1.36 my normal dram voltage is 1.37.

When you use a feature as DOCP standard , that does not even set the dram boot voltage on 1201. While it does set others (timing and normal voltage)
 
I would recommend going down to 2933 and see if this is still problem, if not then you might need more volts for the ram and play around with the settings. DDR 4 it is safe (as long as you keep the ram cool) up to 1.5v, a lot of lead way there for voltage. Now if you have a big pocket book and love playing around and have excellent cooling up to 1.9v (I wouldn't use that for a daily driver though).
 
I just recently started having a problem with my ch6 where all the boards rgb lighting quit working and the aura software would crash as soon as it opened everytime... Asus is having me rma the board :-/ really bummed out about that...

I have the 1700x and 4 sticks of trident z rgb 3200. I never played with the ram heavy but I had it running 3000mhz with its rated timings at 1.35v... I kept the cpu at 3.8ghz with no issues... other then the freaking rgb burning itself out...
 
check out the overclockers thread on it. Apparently a ton of people are having issues the RGB lighting. I also have still having issues with the mobo, if you populate the three 16x slots, even if you set slot 4_3 to 1x mode manually, it ignores the setting and uses 4 lanes, so I can't use my discrete sound card.

This is basic stuff, really disappointed.
 
noko said:
I would recommend going down to 2933 and see if this is still problem, if not then you might need more volts for the ram and play around with the settings. DDR 4 it is safe (as long as you keep the ram cool) up to 1.5v, a lot of lead way there for voltage. Now if you have a big pocket book and love playing around and have excellent cooling up to 1.9v (I wouldn't use that for a daily driver though).
Click to expand...

Here is the odd thing :) cold boot failure just now , my boot at 1.36 normal at 1.375. I lower my normal voltage to 1.37 and it boots to 3200mhz.

In this link I posted the video which describes the "Zen is happy" process. What I get when scaling back the voltage is not the hiccup where the computer powers down. I'm getting the version of it stays spinning then retraining and boot (short version not the long one).
 
Well I am going to jinx it but this is the 3rd day in a row where I don't have the cold boot problem any more all of this under bios 9943.
It seems to be pretty stable it retrains a few times yellow red and reboot after F9 (yellow again) and it keeps booting into 3200 with out to much trouble it seems (it is pretty fast boot).

I ran my kit with the usual timings 14 14 14 34 and added trc of 48 at 1.3750 boot and the same voltage I think for normal dram voltage.
 
Pieter3dnow said:
Well I am going to jinx it but this is the 3rd day in a row where I don't have the cold boot problem any more all of this under bios 9943.
It seems to be pretty stable it retrains a few times yellow red and reboot after F9 (yellow again) and it keeps booting into 3200 with out to much trouble it seems (it is pretty fast boot).

I ran my kit with the usual timings 14 14 14 34 and added trc of 48 at 1.3750 boot and the same voltage I think for normal dram voltage.
Click to expand...
I normally don't power down the computer, just off. So booting up is usually normal. I have to say bios 1107 and prior I had virtually zero issue booting up cold (no power to motherboard to on), bios 9943 which is suppose to have fixed the cold boot gave me a few times cold boot issues??? go figure. I am waiting for the official AGESA 1.0.0.6 bios and hope it is an improved 9943 and not 9943 beta or 9945 beta. 9945 was not very good overall for me.
 
noko said:
I normally don't power down the computer, just off. So booting up is usually normal. I have to say bios 1107 and prior I had virtually zero issue booting up cold (no power to motherboard to on), bios 9943 which is suppose to have fixed the cold boot gave me a few times cold boot issues??? go figure. I am waiting for the official AGESA 1.0.0.6 bios and hope it is an improved 9943 and not 9943 beta or 9945 beta. 9945 was not very good overall for me.
Click to expand...
That is what I find so disappointing about this Asus board, breaking things in updates make it looks like they have a development team of 20 people and there randomly making changes..
The other problem I have is that I bought ram of the QVL list and it still ended up not working as well as I would have expected it to.
 
Pieter3dnow said:
That is what I find so disappointing about this Asus board, breaking things in updates make it looks like they have a development team of 20 people and there randomly making changes..
The other problem I have is that I bought ram of the QVL list and it still ended up not working as well as I would have expected it to.
Click to expand...
It is also compounded significantly with their software layers, pure poison for this board in my experience. Every piece of software had significant stability issues for me. Running clean this board is like a new revised board. Their software packages are huge, bloated and more in tune with Intel hardware. Even there I would probably not use it except the sound software which I had to pull from the CH6 due to stability issues with Sonic 3 and Sonic Radar. The good sound hardware of the board has not changed so using Windows sound stuff works well enough without all the bloat.
 
Well it seemed like a good idea to try the 1403 bios and how was I wrong about that one it is so unstable finding any voltage to boot in 3200 with decent settings is so hard and the cold boot problems (makes 9943 a walk in the park).

Same problems I can cycle through any voltage for dram and dram boot but it is not willing to go anywhere. Booting under this bios is a fluke rather then something you achieved by settings as I did under 9943.

9943 voltages for PLL and sb were hard set to 1.8V and 1.05V the CPU soc was hard set to 1.08V (which was weird coz the auto voltage in 1403 is 1.09V) It would boot repeatedly with 1.375V boot and normal dram. The timings on 3200 settings were 14 14 14 14 34 48 1T gear down bank swap disabled.

And none of these settings work any more. I'm getting straight up 54 (error code on led) as a reward for anything I change. Even tried DOCP standard for a laugh that was the same thing.
The thing is that when I get into the bios after a failed boot it stops pops the screen from the bios I read the memory speed and it is 3200 not 2100 as it is supposed to show after failing to train the memory

How can these clowns at Asus get all of it wrong with so little effort ?

G.SKILL F4-3200C14D-16GTZ 16GB(8GB*2) SS 14-14-14-34 1.35V
It is still the same kit that is supported by them

***
To add insult to injury :
9943 flash back
change dialled in settings boot without any drama ....
 
Last edited:
9943 didn't work for me with basically the same issues as you are describing, I couldn't boot with any settings. I'm back on 0083
 
dook43 said:
9943 didn't work for me with basically the same issues as you are describing, I couldn't boot with any settings. I'm back on 0083
Click to expand...

If you are running 4 sticks of ram you should have used 9945. I can not recall if there was anything about using 2 16gb sticks.
 
You must log in or register to reply here.
Back
Top