- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After upgrading to microcode 0x12b, I encounter a blue screen with the original BIOS voltage settings. Previously, I could successfully complete CPU stress tests with the core voltage under 1.4V. However, after the microcode update, I had to increase the CPU core voltage to 1.62V to complete the tests without encountering blue screens or failures.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, TEI.
Thank you for posting in our Community for sharing the details. I understand that the 0x12B microcode update has had an impact on your system’s stability, particularly with the voltage settings. The need to increase the CPU core voltage to 1.62V after the update is quite significant and it might suggest that the new microcode is demanding more power to maintain stability under load.
This could be due to changes in how the processor handles certain tasks or optimizations introduced in the microcode. Could you please share the exact error message or the BSOD error code you noticed?
Have a nice day!
Best regards,
Von M.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for your reply.
This is my blue screen error code. Each time I run the AVX2 test in XTU, the system blue screens the instant I start the test.
Before updating the microcode 0x12b, my BIOS's CPU lite load setting was on mode7, which allowed core voltage below 1.4v to pass the AVX2 test and without causing crashes when rendering videos or playing games.
Now, I must set it to mode16 to pass the test, which pushes my core voltage over 1.62v.
I believe this is a very high voltage for a CPU that hasn't been manually overclocked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, TEI.
Could you please provide the exact make and model of the motherboard you're currently using? This will help me determine if there are any compatibility issues between the motherboard and the BIOS version you installed.
Best regards,
Von M.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
MAG Z790 TOMAHAWK WIFI DDR5
bios ver : 7D91vHE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, TEI.
Thank you for sharing your motherboard's model and BIOS version. We localized the Vmin Shift Instability issue to a clock tree circuit within the IA core which is particularly vulnerable to reliability aging under elevated voltage and temperature. We observed these conditions can lead to a duty cycle shift of the clocks and observed system instability.
The latest microcode update (0x129) will limit voltage requests above 1.55V as preventative mitigation for processors not experiencing instability symptoms. This latest microcode update will primarily improve operating conditions for K/KF/KS processors. Intel is also confirming, based on extensive validation, that all future products will not be affected by this issue. It is possible microcode update 0x12B and the latest BIOS update may provide some improvement for systems experiencing instability. Intel recommends adhering to the relevant Intel Default Settings for their Intel Core 13th and/or 14th Gen desktop processors, and ensuring they are running with the latest BIOS for their systems.
To ensure the microcode updates are effective, they need to be loaded through a BIOS update. Please reach out to your system or motherboard manufacturer for BIOS updates that include the microcode update 0x12B. Let me know if the issue still the same so we can proceed with the next steps.
Best regards,
Von M.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The BIOS I'm using now is the latest version that includes 0x12B, and the problem I encountered occurred when I started the system for the first time after updating 0x12B.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, TEI.
This indicates that the 0x12B update might have caused the problem. I have sent you an email with more details regarding this issue. If you do not see the email in your inbox, please check your SPAM email.
Best regards,
Von M.
Intel Customer Support Technician

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page