Microcode 0x12B: Intel identifies degradation in cycle engine as fault source

The microcode 0x129 can fix the problem by eliminating both generations of Intel core processors proper. Now that the fix has yielded a new microcode update 0x12B, the specific problems of the degradation bzw can occur. Alterung aufgreifen soll.

It is likely that the fact that there has been a change in the statistics of the current situation, the processes with their high voltages and problems have been resolved. If Intel knows that this is known, it is possible to make money and never get a war clear, who can that difference come. With the microcode update on 0x129 limited Intel voltage to 1.55 V – take care of the expansion of the current, if the blutung comes, the war is unclear. Some changes to the performance with the microcode 0x129 can bring a change and a konntenkeinerlei significant Änderungen festivities.

From Microcode 0x12B it is now:

Intel has localized the Vmin Shift Instability issue to a clock tree circuit within the IA core, which is particularly vulnerable to reliability aging under elevated voltages and temperatures. Intel has observed that these conditions can lead to clock duty cycle shifting and has observed system instability.

– so Intel

Demnach is the “Clock Tree Circuit” in the Performance Cores (“IA Cores”) and causes a degradation by higher voltages and temperatures. The “Clock Tree Circuit” works with a reference branch of 100 MHz, over branch dividers and multipliers that become different branches in the process cores. The complexity of the construction and the representation of the “Clock Tree Circuit” causes Intel to spend so much time, that a specific design of the processors causes a high voltage and temperature identification.

Due to the Intel knowledge, which identifies four people, in the event of a Vmin change that may occur, it may be that the problems are solved:

1. The motherboard power supply settings exceed Intel guidelines.
a. Mitigation: Intel® default settings recommendations for 13th and 14th Generation Intel® Core™ desktop processors.

2. eTVB Microcode algorithm that enabled Intel® Core™ 13th and 14th Gen i9 desktop processors to operate at higher performance levels even at high temperatures.
a. Mitigation: Microcode 0x125 (June 2024) fixes an issue with the eTVB algorithm.

3. Microcode SVID algorithm that requests high voltages with a frequency and duration that can cause Vmin shift.
a. Mitigation: Microcode 0x129 (August 2024) addresses the high voltages requested by the processor.

4. Microcode and BIOS code requiring higher core voltages, which may cause Vmin shifts, especially during periods of inactivity and/or light activity.
a. Mitigation: Intel® releases microcode 0x12B, which includes microcode updates 0x125 and 0x129 and addresses increased processor voltage requests during idle and/or light activity periods.

– so Intel

The first time you notice aggressive settings of the motherboard is that. That man with the entspeaken Presets is occupied. Most Ursache were errors in the eTVB algorithm, which were occupied with the microcode 0x125. The microcode 0x129 has found the SVID algorithm, which allows a Vmin version to work again. The last time the microcode 1x12B has the voltage in idle operation in the Griff relation, so a Vmin switch is no longer possible.

Let Intel’s own Benchmarks which the Microcode 1x12B makes possible on the Performance. Intel speaks in this combination of typical variations in the Benchmark Durometers. You can also see an image of the tests with microcode 0x129 here. As you can see, future processors such as Lunar Lake and Arrow Lake are not affected by the problems. Once this has happened, the drop of the “Clock Tree Circuit” has become a design error in Raptor Lake (-Refresh).

The motherboard fixes will be implemented with Microcode 1x12B in the upcoming BIOS updates.