In UEFI, page Monitor > Q-Fan > COV fan is VRM fan.
I think I have a work around for issues with stuck fans/PWM. I am avoiding using multiple apps to access monitoring data. This seems to send Super IO chip wacko. I have spent about 6 days with back to back testing to believe this is issue.
I did 2 instances of 24hrs+ continuous usage. At each stage of testing I would take a screenshot where HWINFO had been logging monitoring data for run and I would open CPU-Z to get say stats like UEFI version, RAM SPD, etc. As CPU-Z also accesses Super IO chip it would create a clash which I would not be aware of. This clash could then later exhibit as stuck fans of (x)% or full blown crap out of PWM signal leading to water pump stuck at say ~800RPM = 40C+ water temps :eek: .
When I did my 3rd instance of testing I only used HWINFO, for over ~72hrs testing all was well,
link.
Rig config:
TR 1950X
ASUS ZE UEFI 0019
F4-3200C14Q-32GVK
RX VEGA 64
2x SATA SSD MX100 256GB, 1x SATA HDD HGST 2TB, 1x SATA HDD Seagate 2TB
Cooling is EK CPU/GPU blocks, 2x MagiCool G2 Slim 360mm rads, EK D5 PWM, 2 sets of 3x Arctic Cooling F12 PWM fans using CHA_FAN1 & 2 via 4in1 cables, Be Quiet Silent Wings 3 using CPU_FAN. Each header is custom PWM profile set in UEFI, T_Sensor1 is used to measure loop temp and used as source for fan profile. VRM stock fan also has custom profile set in UEFI.
ASUS are aware of this issue concerning the Super IO chip, a fix is in the pipeline from what Elmor has stated,
link.