ROG Crossair VII Hero Wifi witn Ryzen 3700x CPU 0 RPM

[Hurricane28]

The problem is not 100% solvable as its BIOS/Sensor related. I am sure Assus regrerts the day they bought this cheap Sensor which is causing so much trouble.

Only thing you can do is reset the cmos, pull the BIOS battery, pull the power cord from the psu and push the power button on your case for a few seconds to be sure no current is in the board anymore. Than put everything back and test.

[fapb48]

The problem is not 100% solvable as its BIOS/Sensor related. I am sure Assus regrerts the day they bought this cheap Sensor which is causing so much trouble.

Only thing you can do is reset the cmos, pull the BIOS battery, pull the power cord from the psu and push the power button on your case for a few seconds to be sure no current is in the board anymore. Than put everything back and test.

You have the same motherboard as me. Did this ever happened to you before?

So, you're saying that is the sensor that its causing this randoms shutdowns? I will try to do your suggestion. Thank you

[Hurricane28]

Yes, on my CH6 this was very common and there was no fix for it as its the IT sensor that is crapping out which than gives weird readings and this sensor is also responsible for the fans at the same time. Later Elmor (Jon) came with an "fix' and i never encountered this issue after that but it can still happen as this IT sensor is utterly crap and it was the baddest decision ever to buy this cheapo sensor. It only costs like 2-5 euro's each on Aliexpress..

Good luck man.

[gupsterg]

Only thing you can do is reset the cmos, pull the BIOS battery, pull the power cord from the psu and push the power button on your case for a few seconds to be sure no current is in the board anymore. Than put everything back and test.

I own/owned from launch:-

i) ASUS ROG Crosshair VI Hero
ii) ASUS ROG Zenith Extreme
iii) ASUS ROG Crosshair VII Hero Wifi
iv) ASUS ROG Zenith Extreme Alpha

I do at times runs of say folding@home that can exceed ~24hr+ continuous usage, besides the other things I may do.

In all my systems I have used board fan headers to control fans/water pump, used UEFI to set fan profiles.

I have never done what you highlight.

As previously stated to fapb48, this fix is to use SW that uses ASUS WMI if it interacts with Super IO Chip, UEFI must have ASUS WMI support.

In the case of ASUS ROG Crosshair VII Hero Wifi UEFI 1002 was first to have working ASUS WMI, 0804 & 0702 had broken implementation, 0601 and earlier had no ASUS WMI.

Approximately from UEFI 2008 (ie when ComboPi-AM4 x.x.x.x became AGESA in UEFI) ASUS WMI was again broken AFAIK. Even then I only experienced 2-3 times issues with fan headers. That UEFI was released back in March 2019, I clocked up obscene amount of usage on my C7H from then til now.

UEFI 0002 should fix fapb48, as stated it is pointless to think the UEFI fixes issue if a user continues to use SW that accesses Super IO Chip not using ASUS WMI. If a user does that they will think issue is still present when it is not.

So as stated before, for fix to work, it is a two fold action, SW accessing Super IO Chip must use ASUS WMI and UEFI must have working implementation of ASUS WMI, if either is not in place user will have issues.

A simple reboot or power on and off will reinitialise Super IO Chip, no need for pulling CMOS battery, etc, etc...

[fapb48]

Thanks everyone.

I have installed UEFI 0002 and uninstalled AI Suite 3 and Aura apps. 24h has passed and so far, so good.

Lets hope it fixed the issue indeed.

Thanks everyone for your precious help!

[fapb48]

3 days running on a 24 hour cycle and all good.

Thank you everyone very, very much!!

My EZ Flash app is saying that my UEFI is outdated.. Should i just ignore and carry on with the 0002 version as long as possible?

[Hurricane28]

I own/owned from launch:-

i) ASUS ROG Crosshair VI Hero
ii) ASUS ROG Zenith Extreme
iii) ASUS ROG Crosshair VII Hero Wifi
iv) ASUS ROG Zenith Extreme Alpha

I do at times runs of say folding@home that can exceed ~24hr+ continuous usage, besides the other things I may do.

In all my systems I have used board fan headers to control fans/water pump, used UEFI to set fan profiles.

I have never done what you highlight.

As previously stated to fapb48, this fix is to use SW that uses ASUS WMI if it interacts with Super IO Chip, UEFI must have ASUS WMI support.

In the case of ASUS ROG Crosshair VII Hero Wifi UEFI 1002 was first to have working ASUS WMI, 0804 & 0702 had broken implementation, 0601 and earlier had no ASUS WMI.

Approximately from UEFI 2008 (ie when ComboPi-AM4 x.x.x.x became AGESA in UEFI) ASUS WMI was again broken AFAIK. Even then I only experienced 2-3 times issues with fan headers. That UEFI was released back in March 2019, I clocked up obscene amount of usage on my C7H from then til now.

UEFI 0002 should fix fapb48, as stated it is pointless to think the UEFI fixes issue if a user continues to use SW that accesses Super IO Chip not using ASUS WMI. If a user does that they will think issue is still present when it is not.

So as stated before, for fix to work, it is a two fold action, SW accessing Super IO Chip must use ASUS WMI and UEFI must have working implementation of ASUS WMI, if either is not in place user will have issues.

A simple reboot or power on and off will reinitialise Super IO Chip, no need for pulling CMOS battery, etc, etc...

Excellent info as usual man.

I did the things to prevent the issue from happening again as i mentioned before because i couldn't get rid of it flashing to other BIOS or any other way.

I did this as some times the registers get corrupted and it can only be wiped by pulling the BIOS battery. I agree its a bit excessive but in some cases its necessary to do so if you can't get rid of the issue.

On my Ch6 i encountered this fan issues even without software monitoring programs running and it even happens in BIOS as i have a video that proof is. So its not only the SW that is causing this but mostly the Asus BIOS that is causing this behavior as i had issues on 2703 BIOS but now on 1103 i do not encounter this.

The conclusion is that multiple sources can cause this sensor to get corrupt as its one of the worst if not the worst IO chips out there and i am sure if Asus knew this before they never bought this crappy sensor. They just tried to cheap out on a sensor and it backfired on them, that is what i think.

Their newer boards are all with Nuvoton instead of IT now.

[Hurricane28]

3 days running on a 24 hour cycle and all good.

Thank you everyone very, very much!!

My EZ Flash app is saying that my UEFI is outdated.. Should i just ignore and carry on with the 0002 version as long as possible?

If you have no issues and every thing is working well for you i see no reason why you should flash other BIOS.