No issues with my chipset fan. My chipset maintains a near constant 63 degrees C and the chipset fan idles at about 2950 RPM (plus or minus about 20 RPM). During a Cinebench run, it went up to 2994 RPM. So, it seems normal to me.

check event viewer and see if you're having any new errors - i am, and quite a few.

one of them that's concerning me is WHEA-Logger "A fatal hardware error has occurred."

There's a bunch of new AppModel-Runtime, Kernel-EventTracing, Perflib, DeviceSetupManager, and DHCP-Client errors too.

criznittle wrote:
check event viewer and see if you're having any new errors - i am, and quite a few.

one of them that's concerning me is WHEA-Logger "A fatal hardware error has occurred."

There's a bunch of new AppModel-Runtime, Kernel-EventTracing, Perflib, DeviceSetupManager, and DHCP-Client errors too.

I learned that a number of the new event viewer errors were due to the latest W10 update. That said, the WHEA-Logger error was almost certainly from the latest BIOS update. After some searching and testing, it became clear that the 3950x(not overclocked) was unstable. I'm not sure why else it suddenly would start happening after updating the BIOS. I think the performance gains ASUS claimed to have added came at a cost, and they needed to up the voltage slightly for some(all?) 3950x owners. After increasing the voltage by 0.015, the instability was gone and suddenly it could complete the RealBench benchmark and hours of stress testing.
Hopefully i didn't need to add that voltage because my CPU is already degrading - it's only been 7 months, and without any OC.

If anyone is getting the same WHEA-Logger error "A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event." Event ID: 1
There's a chance it's processor instability and adding the tiniest amount of voltage could fix it.

I'm literally unable to boot into Windows with this latest bios if I try to run my RAM at 3600 like it's supposed to be rated for. 1302 I went months with zero issues with custom timings, 2010 I'm trying right now due to the issues with 2103 but I managed to boot into Windows with it and no random reboots so far, but 2103 will either stay stuck in a reboot cycle without even letting me into the BIOS or it will start to boot into Windows but reboot in the middle of loading it.

I've tried my previously working custom settings, I've tried just using the stock xmp settings with no other modifications, and I even had some trouble just running at the stock 2133 speed. I'm not sure what's going on, but this bios does NOT like my setup at all.

Edit: Also for troubeshooting I tried Re-flashing 2103 multiple times, I tried optimized defaults, I tried different USB sticks to load the file from, I tried loading from bios 1302 to 2010 to 2103 each bios in order, I tried messing with RAM, SOC, VDDP, and VDDG voltages, etc. I spent at least 3 hours trying every trick I knew and nothing would let me boot with that bios.