05-23-2025 05:29 AM - edited 05-23-2025 09:16 AM
My laptop: ROG Strix G16 G614JVR-N4141W
-Cpu: i9-14900HX
-Window 10 22H2 build 19045.5854
-Bios ver: 320 (latest, 2024/11/13)
-Cpu microcode: 0x12B
-Problem: Since I bought it (April 2024), the machine has often had BSOD in window 10 and 11 (lasted update).
-Determine the cause: After many times of research and trying to fix it, I determined that the cause of the problem was when the CPU clock reached 5.8GHz, it would have BSOD. I searched online and found that it was related to the problem of the 13th and 14th generation CPU line.
-Before Present: I am using intel XTU to limit the max cpu clock (5.7GHz). And NEVER BSOD WHILE USING IT
But it has some certain inconveniences like I can't install windows hypervisor platform to use wsl or docker. Or during the window startup process, Intel XTU has not been launched (at the window service level), there is still a small chance of BSOD.
-Present: And now I have stopped using intel XTU and updated microcode to 0x12F (May 2025) (at window driver level) for a few days now but have not had any BSOD (but i still can't use hypervisor for the same reason). I will monitor over the next few weeks to see if there are any problems.
I hope Asus ROG team will update cpu microcode 0x12F for cpu via bios update release for laptop models using Intel HX 13 and 14 CPU.
Or can you give me some way to limit the cpu clock at bios level? I tried undervolt protection at -80mV (max limit in bios) but still no improvement (without intel XTU).
05-25-2025 02:19 AM - edited 05-25-2025 02:20 AM
Hello,
Interesting as the voltage issue is said by Intel to only impact desktop processors as they had the ability to push beyond 1.5v to the cores.
Also what is the exact issue with hypervisor and the other programs, they don't install or BSOD no matter what?
If you power the laptop on battery only it does not run any boost clocks so if things do not work in this state the problem lies elsewhere.
05-25-2025 02:35 AM - edited 05-25-2025 02:56 AM
About hypervisor: intel XTU doesn't work with it. And I also want to run hypervisor (for wsl, docker) but have to choose intel XTU to limit CPU clock.
I always plug in my laptop when I use it, and never seen BSOD on battery
And as for voltage, my HX cpu can easily go up to 1.55V, and I guess that when the voltage exceeds 1.55v a little bit, it will cause BSOD.
The image below is the voltage when I use microcode 0x12F. And now I have no BSOD after 5 days of using this microcode.
0x12F
05-25-2025 03:02 AM - edited 05-25-2025 03:10 AM
There were 2 problems with the bug, continuous high sustained voltage over time degraded the CPU.
And under a high load some that spiked to the higher voltages would crash instantly.
1.55v is the safe limit so it's strange, your laptop has been unstable since day 1? (does it run hot too?)
Same goes for the undervolting of -80mV, if this did not help then its strange and would suggest your CPU is just not stable at 5.8GHz on the cores?
05-25-2025 03:30 AM - edited 05-25-2025 03:45 AM
It will BSOD with microcode 0x12B and may be lower in previous bios version (since i bought it).
I was try -80mV (limit on bios), it still BSOD
So i make this post for request update bios 0x12F.
Currently I have used 2 solutions and have not had BSOD
-intel XTU limit maximum clock (was try set max at 5.7GHz for long time and it stable)
-microcode 0x12F (only been using it for 5 days, need more time to know if it is stable)
And of course these 2 solutions have their own inconveniences, so it is best to update microcode 0x12F to the new bios version.
05-25-2025 03:50 AM
I understand, what I'm suggesting to you is that perhaps you actually have a faulty CPU since day 1.
The reason I'm saying this is because if you ran a -80mv offset and it still crashed, that would imply it was no more than 1.55v -0.08v = 1.47v.
And if you consider that the intel bug doesn't apply to laptop CPU's, this is confirmed by Intel as the mobile CPUs didn't run the same power specifications or boost clocks.
Then you have to consider the alternative, which is maybe your CPU is faulty and that's the reason why it crashes when at 5.8GHz. I'm not saying this is the reason but a possibility.
If running the 0x12F is stable that's good but for a true and accurate comparison you would need to make sure the CPU is running at the exact same settings, if there is now a difference with the boost clock when compared to 0x12B it may be masking the issue.
So on 0x12B did it run 5785.8MHz or slightly higher?
I hope that makes sense,
05-25-2025 03:56 AM
Maybe it went over 1.55V with microcode 0x12B or lower.
And crashed at 5.8GHz which is really just my guess based on the above tests and results.
05-25-2025 04:22 AM
Maybe but if the issue was present from day 1, it does happen sometimes the CPU can be weak, as in they are not stable at the boost speeds.
In terms of running 0x12F, what did you mean by "inconveniences" this should be a perm solution if working so no need for XTU and you can re-enable Intel VT-d?
05-25-2025 04:33 AM
Perm solution if it load from bios. And according to the instructions here, Intel VT-d needs to be disabled.
I can't use linux (or find 0x12F for linux version).
05-25-2025 05:00 AM - edited 05-25-2025 05:00 AM
I see, its not perm and resets upon boot from the BIOS 😞