Threads
- Intel users are reporting problems while running the Black Myth: Wukong benchmark.
- It seems that lowering CPU speeds is a potential solution, but it may cause worse performance.
- Intel recently released a microcode update to address CPU instability, but the update does not seem to have done much.
Intel’s 13th and 14th-generation stability problems have been going on for a while. Many users are even switching to AMD because of the prevalent issues, but the company has not been able to solve the problem.
Team Blue shipped the latest microcode, 0x129, as its ultimate weapon. Microcode 0x129 seemed to work well until one of the most anticipated upcoming titles of 2024, Black Myth: Wukong, launched its benchmarks on Steam.
Why it matters: Black Myth: Wukong is shaping up to be a massive launch. If millions of Intel users are unable to play the title at release, team Blue’s situation will quickly go from bad to worse.
Scheduled to arrive on August 20, this action RPG has recently released a free benchmark tool for Steam users. The game has already impressed audiences with its high-quality visuals, which can be seen in the benchmark.
Similar to numerous other benchmarks, this one also compiles the shaders before execution in order to maximize performance before running the test. However, the benchmark crashes on Intel CPUs, and the error shown above is displayed.
This appears to be caused by an issue with 13th—and 14th-generation Intel Core CPUs, as we observed months ago in a related topic. In this instance, the frequency of one or more cores is momentarily elevated to the maximum, and the voltage produces instability.
It hasn’t been a week since Intel launched its microcode solution, and this is happening. However, some users report that with microcode 0x129, they customized some parameters in the Intel default settings and did not receive this message.
Those that changed settings too much might experience issues with the updated microcode.
In fact, according to Game Science, Black Myth: Wukong’s publisher and creator, customers would need to manually lower their CPU speeds or forego compiling the shaders altogether to solve the problem.
The main issue is that this will lead to performance loss in certain situations. As a result, it becomes evident in the absence of other information and proof that the microcode for some CPUs came late and that an RMA will be required.
Thank you! Please share your positive feedback. 🔋
How could we improve this post? Please Help us. 😔
Join Our Community
