I've recently purchase a Maximus IX "Hero" board and I've been seeing some oddities with it. Before I return the board for a replacement, I thought I might post here to see if they are common issues with the board or not.
The board has the most recent BIOS/UEFI as of April 23rd 2017 (0906). I've reset the CMOS a few times in trying to clear up some of these issues. An intel i7-7700k is installed alongside 4 sticks of Corsair LPX 3200 8GB DDR4 (for a total of 32GB.) The only mass storage device is a samsung 960 EVO m.2. I also have a few assorted fans, USB keyboard, USB mouse, GTX 1070 video card, power supply (EVGA 650 G2), and ethernet cable attached to the board.
1. With a cleared CMOS, I'll go into the BIOS and change it to use XMP. At the prompt for the asus multi-core enhancement, I select "No" (so that the board uses intel's stock settings for turbo speeds.) With only these changes, after I boot the machine, I've noticed that the VID reported by both HWInfo and HWMonitor will be locked to a specific voltage for a specific frequency. For example, if my processor has 4 cores at 4400, the VID is 1.17. This is the same REGARDLESS OF LOAD. I could be running 8 threads of linpack, or just have 4 threads churning no-ops. Those utilities do show a (often massive) difference in "package power" for those different loads, but vcore and vid are constant.
(#1 goes away if I start overclocking... I haven't narrowed it down, but one of the several changes in BIOS when overclocking allows the VID to change based on load even at the same frequencies.)
2. On the board itself, there's that little square LED segment thing that shows a 2 digit numeric representation of the boot process. ("Q-Code LED") Within BIOS, there's a setting ("Q-Code LED Function") to allow this to display ONLY the POST codes ("POST Code Only") or to display the CPU temp after the POST is completed ("Auto".) When I have this set to "Auto", the LED does show the processor temp (or within 1-2 degrees of the processor temp) but eventually the LED gets "stuck" showing 30, and nothing but "30." I can run 8 threads of linpack and drive the cores to 70C, and this still shows "30."
I considered that "30" might be some kind of BIOS code, but referring to the table in the manual shows that "30" is a ACPI code for "System is waking up from the S3 sleep state." Obviously, if I'm running linpack, it's not in a sleep state anymore... So, either the temp is getting stuck at 30, or the LED is getting stuck with the "wake from S3" code and never going back to showing the processor temp.
3. The BIOS has the ability to store and load multiple BIOS setting "profiles." If I save anything to profile #1, when I try to load those settings, the entire motherboard locks up immediately upon confirming the action. If I save to a different profile number, the profile loads properly. (In order to repeat this after a CMOS reset, I obviously have to first make some BIOS changes and save those settings to the first profile.)
Are others having the same issues?