Crosshair VI Hero bug reports

[Lextra]

I have a cold-boot-bug with 7302 and CSM disabled: Every time I boot up the PC (after having it turned off for ~8 hours) the first boot will result in a freeze (when windows 10 shows the spinning animation). I guess this only ever happens if CSM is disabled. I disabled it since it makes reboots faster (going from windows task manager, it saves about 2 seconds, 16.5s to 14.5s) and on top of that, the LED under the post code would ALWAYS stay on (in bright white) even if all the LEDs were disabled in the bios options.

Summary: CSM disabled makes reboots faster, and fixes the LED, but causes a freeze on the first cold boot of the day.
CSM enabled makes reboots slower, and causes the LED under the postcode to be constantly on, in bright white, but cold boots work fine?(again, not sure if this cold boot bug is related to CSM or if it always happens with 7302.)
[B]

[MeNot]

Under "Advanced\AMD CBS\NBIO Common Options\FAN Control\FAN Table Control" I can set a manual value for the critical temperature which is 75°C in the Q-Fan Control and leads the fan spinning on max speed when reaching it.

Sadly, the set value gets ignored and the critical temperature is still 75°C after changing it manually.

[KeithMyers]

I finally have figured out my maddening problem of my computer constantly rebooting with a cpu overtemp error. C7H with a 2700X and the 1001 BIOS had been running with no issues for years.

Then I upgraded to the 3900X and the 2501 BIOS. Then the problem started. Constant overtemp errors dumping me to the BIOS splash screen which will not go any further till you acknowledge the error with a F1 key press. So if the system is unattended, then the system is offline till you notice the monitor display with the error.

I have custom water cooling with the pump powered off a SATA connector. But the radiator fans are powered off the cpu fan header on the motherboard. As well as 4 other case fans. I was finally in front of the computer when I noticed the cpu temp was reporting 92°C and all five fan headers were reporting 0 rpm. I took off the computer side panel to access the fans and saw in fact every fan in the case connected to the motherboard headers were not spinning. I switched the radiator fans to the cpu opt header to see if anything changed but they still did not spin up. At that point the cpu hit 95° C. and then the computer rebooted to the BIOS splash screen with the cpu overtemp error displayed and demanding a F1 key press. All the fans started spinning again.

So for now I have cobbled together a cable to connect the radiator fans to a molex connector since the motherboard and BIOS can't be trusted to provide +12V all the time. But the case fans are still powered from the motherboard and they cool the memory and VRM's an 3 gpus.

So when is the BIOS going to be fixed to prevent the loss of fan header output?

[Ravwyn]

Sounds like you need a bleeding-edge beta UEFI. I've had my issues resolved with a UEFI version that is based on AGESA 1.0.0.3 - no suffixes at all. The latest I know of is ABB. Since this thread deals with your board predecessor, the Crosshair VI, I would advise you to find a specialized thread. I'm sure there are some more recent files available.

What really worries me is how similar the issues are on a supposedly different chipset and board - we had issues like this before. The qfan-control always was a weak point - and the AURA implementation. These two ALWAYS cause issues. But i've never heard of a board cutting power to running pumps and or fans - that is a severe issue! I would even say that you escalate the problem and contact ASUS support directly - yes that might be a hassle, but you did nothing wrong and bought a supported GPU - used an official UEFI. Tell ASUS of your troubles and link them to this thread. That's the best you can do for now, I guess.

[KeithMyers]

Sounds like you need a bleeding-edge beta UEFI. I've had my issues resolved with a UEFI version that is based on AGESA 1.0.0.3 - no suffixes at all. The latest I know of is ABB. Since this thread deals with your board predecessor, the Crosshair VI, I would advise you to find a specialized thread. I'm sure there are some more recent files available.

What really worries me is how similar the issues are on a supposedly different chipset and board - we had issues like this before. The qfan-control always was a weak point - and the AURA implementation. These two ALWAYS cause issues. But i've never heard of a board cutting power to running pumps and or fans - that is a severe issue! I would even say that you escalate the problem and contact ASUS support directly - yes that might be a hassle, but you did nothing wrong and bought a supported GPU - used an official UEFI. Tell ASUS of your troubles and link them to this thread. That's the best you can do for now, I guess.

I posted in this thread as there is no thread for bug reports for the Crosshair VII Hero and this was labeled for X370/X470.

I have contacted AMD and have a ticket open with them.

[Lextra]

The VDDCR SOC Voltage control inside the Advanced > AMD Overclocking settings does nothing. I set it to as low as 100mv which shouldn't be possible to boot with, but it still worked. AMD Ryzen Master reported the soc voltage as 0.1.

[FoxTech]

Hi Community,

Having a problem since the beginning with my C6H Rev 1.00 ( I guess)
Can't read Rev. Number, because the GPU Waterblock is that massiv.

So, what does it:
When I enter voltage- settings in the bios, for example SOC Voltage 1.025v its always shows 1,003v
Same with Dram Voltage. My setting is 1,355v for my Dominator Platinum 3466@3200Mhz. But it never went above 1,330v
I guess, 1,330v are enough for 3200 Mhz but if I try to go a little step further, the system wont boot. No matter what timings.
The only voltage, that seems to be showing the exact vltage is, CPU VDD Voltage.

So, is this a bug or does it only show wrong numbers?

[marblesrx7]

Has anyone experienced a problem where the PC does not wake from sleep/S3. Debug just stays on e1 (C6H 7201) I just updated the Bios from 7106. wondering if I should reflash or try a beta bios. I haven't experienced any of the problems I've read about just this one. Running a 3700x.

[FoxTech]

Yes, I had that Issue every time, with any bios.
I disabled Sleep/hybernation. Otherwise, I have to hard power down my PC

Seems, my board has all the bugs oO

[marblesrx7]

Guess I'm not the only one, I'm just going to try reflashing to the same bios tonight and see if it does anything.