Bios configuration data was erased upon starting Windows.
Bios configuration data was erased upon starting Windows.
I just assembled a system using the MSI X99a sli Krait Endition board with an Broadwell-E i7-6800 processor. I configured the BIOS to enable overclocking from the standard 3.5ghz up to 4.2ghz. After rebooting and returning to the BIOS, the system displays the current configuration in the upper right corner, confirming my overclock with temperatures under 30°C (water cooled). Once Windows 7 loads, the core speed returns to 3.5ghz. I can then adjust it back up to 4.2ghz via the MSI Command Center without issues. I’m curious why the BIOS core speed reverts to the default setting when Windows starts. XMP and OC Genie are disabled in the BIOS.
Check the CPU page in CPU-Z for the multiplier in the lower left. Also, verify if the system maintains accurate timing.
Check CPU-Z for the CPU page to view the multiplier in the lower left corner. Also, confirm if the system is maintaining the correct time.
Sorry this message took a while. Work and health have kept me away.
I've set my system time to automatically sync with 1.north-america.pool.ntp.org.
After tweaking the initial configurations, the BIOS updates each time I power it on...
This is the most recent BIOS version, showing a multiplier of 42.
Once Windows 7 Ultimate x64 loads, CPU-Z displays the multiplier as 36.
And Corsair Link 4 reports these temperatures too.
If I adjust the settings in MSI Command Center to increase the multiplier to 42, CPU-Z confirms it...
With these readings...
Experts have been earning money for building and fixing PCs for over two decades, yet this pattern has never occurred before.
The only possibility is that something in my startup process is resetting the settings, but I've reviewed everything thoroughly and found no evidence. Perhaps someone else might find better results?
My Autoruns report
Instead of using the MSI LIVE Update tool regularly, I checked the website directly and discovered version N.70, which had been accessible for about a month and a half. Installing it resolved the issue. It's curious why this update wasn't included in the update tool's listings, especially since the tool has been updated multiple times since then.