Asus Crosshair VI Hero Q-Code 8 / Not Starting

[nazzario]

Hi

I have a big Problem and i hope someone can help me.
Yesterday i have received all my components. Ryzen 1800x, 32 GB Ram, M.2 SSD, RX480 Graphic Card and Silent Loop 280.

I have installed all components and now the PC is not booting. I received the code 8. My Problem is i cannot goes into the bios because i have no Screen.
The RGB on the Boards is ok. The CPU-Ready is green but the onboards LED is off.
I have tried to remove the RAM, than just use 1 Ram /2/3/4 etc. I remove all other components, Graphics Card, SSD but still Code 8 and nothing working. I just not removed the CPU because it's a lot of work. And the Status is green so i think that will be ok.
I Flashback the bios to 0902 from the asus page and i think that installed sucessfully.

I don't know what i can do and i hope someone can help me.

Thanks and Regards
Nazzario

[Demoniacstar]

icubed wrote:
Yes, I had similar errors reported in Windows before I installed the AMD Balanced Power Plan package found on their website. Once I installed this power plan my challenges with these errors went away.
I did keep using the High Performance Power Plan even after installing the AMD Balanced Power Plan.

as far as i know the only thing that the amd power plan changes wuz the core parking and that wuz it ...and that can be done by the high performance power plan or in any power plan as far as that goes.... please correct me if i'm wrong..

[icubed]

Demoniacstar wrote:
as far as i know the only thing that the amd power plan changes wuz the core parking and that wuz it ...and that can be done by the high performance power plan or in any power plan as far as that goes.... please correct me if i'm wrong..

I believe you are correct.

In my case, the OS was not holding the High Performance Power Plan from boot to boot and the System Event Viewer showed CPU errors. Once I installed the AMD package the High Performance Power Plan was able to be maintained.

[BaneSilvermoon]

It also changed the thresholds and transitions for some of the P-states. I had heard there was some more going on, but have never seen any details beyond that.

[Gordz]

I have a completely different Qcode 8 error to all you guys.... I can leave my computer over night (as I do every night) come back to it after work the next day, see that it's happily sitting on Qcode 24, and as I turn my screens on, I get the USB 'bing' sound, telling me that the computer is recognising devices turning on, but before I get to see anything on the screens, it Code8's and I have to press the white button on the motherboard to reset, which is does, and boots to windows just fine. It's quite bizarre.

1700x, coolermaster watercooled
64gb corsair
R9 290 (...i know...)
2 SSDs, 4 HDD
Win 10 pro
Triple screen

any ideas?

[Demoniacstar]

Gordz wrote:
I have a completely different Qcode 8 error to all you guys.... I can leave my computer over night (as I do every night) come back to it after work the next day, see that it's happily sitting on Qcode 24, and as I turn my screens on, I get the USB 'bing' sound, telling me that the computer is recognising devices turning on, but before I get to see anything on the screens, it Code8's and I have to press the white button on the motherboard to reset, which is does, and boots to windows just fine. It's quite bizarre.

1700x, coolermaster watercooled
64gb corsair
R9 290 (...i know...)
2 SSDs, 4 HDD
Win 10 pro
Triple screen

any ideas?

yeah you're running 64 gigs of ram ......windows 10 has a hard time coming back from sleep mode on Ryzen .....windows 10 does not fully shut down either..
i have to shut down my psu or most my fans slowly run all night and the rings still glow ....
it's hard to say what you issue is for certain ....but i am willing to bet your ram might seem stable ...but i do not think its fully stable ....
my ram passes every test i throw at it ....but it to can not wake from sleep or hibernation ....windows thing?....ram thing? ....bios thing?..
i don't know.... try with half you ram installed and see what it does then try one stick maybe and see what it does.....
or relax some timings and see what happens ..... remember to when upgrading the bios with newer versions the same overclock settings you used in the older version may not work for you anymore .....as they make improvements to the system in bios programing our voltages and other settings may need to change to..

[icubed]

Gordz wrote:
I have a completely different Qcode 8 error to all you guys.... I can leave my computer over night (as I do every night) come back to it after work the next day, see that it's happily sitting on Qcode 24, and as I turn my screens on, I get the USB 'bing' sound, telling me that the computer is recognising devices turning on, but before I get to see anything on the screens, it Code8's and I have to press the white button on the motherboard to reset, which is does, and boots to windows just fine. It's quite bizarre.

1700x, coolermaster watercooled
64gb corsair
R9 290 (...i know...)
2 SSDs, 4 HDD
Win 10 pro
Triple screen

any ideas?

Are you running the latest version of Radeon Crimson?
Are you running the R9 290 with an OC?
I did have some challenges with my R9 Fury X and crashing to a code 8 when the Radeon WattMan OC settings failed.
My system always re-started with this code 8.

I corrected this issue by setting the OC of the GPU with different software.

[shervosky]

hi everyone, I buyed Corsair Vengeance LPX CMK16GX4M2A2400C16 ver 5.29 and i have the error q-code 'Ad' and yellow led dram.
In the list of memory supported say that this model is supported but with ver 3.31
what can i do?
You can see the other of my pc spec in my profile.


Issues solved with upgrade the bios to CROSSHAIR VI HERO BIOS 1201

[Spec-Chum]

Demoniacstar wrote:
i get the same type of code....stuck on red light with 55.....ive seen it be caused by low vcore.....and or low PLL voltage will also cause that ..for some reason even at stock settings pll likes to be around 1.875 on my board.... too much SoC voltage will also cause this to happen
this board is not a bad board if you slow down and learn it .,.....it's not like magic ..put it together and poof it's the fastest thing ever
it takes work and a lot ...and i do mean a lot of patients .....you just can't jump from 2133 to 2666 or 3200 ...you have to work it up to it ...so it learns ..as well as you learning what it needs what as far as voltages.....
everyone thinks if you slap these things together and slam the voltage to them it's all you gotta do to get it overclock...its does not work like that ....this bios and this platform are totally new ....it is better to learn how to use these board and overclocking features then it is to just see someone's settings and try them ....each and every system is different and will use different voltages and this board and Ryzen alone seem to be very picky when it comes to the voltages it will run at.......
if you're raising bclk you need to raise the pll voltage.....if your going for higher then 2666 you have to raise the pll voltage due to the fact that most ram wont go higher unless you set 2666 and raise thru bclk....
to low pll will give you that 55 code....
to low ram volts will show f9 or 0d code
to much soc will make cpu stick on red light with code 33.....or you will get the 8 code.....when you see the 8....you turn the psu off at the psu .....
reboot try again...lol....and again ....and again ....and again .....
i should really make a video on all this man....
i have spent the better part of two weeks every day testing and tuning i have learned a lot about this system and the way it works
not once sence i have built this have i needed to hit the bios reset button cept the first time i powered it in
i have always got into bios on a bad oc....the reset button the boot to bios button and the retry button are way better then on the old crosshair boards....
even if it dont boot right away i keep messing and pressing those buttons io can get into bios.....
and i have yet to see any real ...and i mean a real overclocking video that shows people how to overclock and what to do when things fail like so many people have seen.....and then just think the motherboard is crap ....when in fact it is not!......
if you would like some help on that board before sending it back ...we can do a google hangouts chat and i can lend a hand to help you get it up and running

Thanks for this, great info.

I don't get a code 8 error but I do get an F9 boot loop unless I set DDR boot voltage to 1.43v+, and even then it F9 boot loops twice always successfully booting on the 3rd boot, never 2nd or 4th, always 3rd. It's weird.

Interestingly, once it POSTS the DDR is perfectly fine at 1.35v, I don't need to change that at all. The system runs all tests and benchmarks fine at 3200 14-14-14-34-1T, it's just getting the damn thing to POST!

[lorenkos]

Ops, was a memory iusse, solved replacing G.skill 3000 with Corsair 3200 (Next time I'll read the QVL) 😄 😉

[angus52022]

I think the code 8 is about the pressure of the motherboard for the CPU area. I have same problem and I am the EK water block. I remove the center rubber of my block and the problem is gone.*
What *rediculous.*