Can someone help me solve the issue I am having with applying the IMON values?

The problem is that even when I change the IMON values, they do not seem to be applied. I have tried different combinations of IMON Slope (always between 50-99) and IMON Offset, but they do not seem to have any effect when I monitor. For example, when I observe EC’s Long PL, it limits the power to 15W in processes that do not use the dGPU and 10W in processes that use the dGPU, as expected. However, according to the changes I made to the IMON values (Slope of 75% and Offset of -6000mV), [the real power consumption should be 28W and 21W](https://images2.imgbox.com/c8/79/9RKYWhoe_o.png), respectively. But when I check HWiNFO64, I see the same power consumption as shown in ThrottleStop (15W and 10W), indicating that my edits were not applied. This is also evident in the lack of increase in average temperatures and frequencies. However, I was able to unlock the under-volt by changing the CFG Lock and Overclocking Lock values using the same method of editing: firstly with Ru.efi, later with Grub ([their location](https://images2.imgbox.com/a7/c0/NJxzcs8O_o.png) and [in Ru.efi screen](https://images2.imgbox.com/ba/6c/EwkGmVDd_o.jpeg)).

**So why are the IMON values not being applied given that they follow the same steps?**

[Screenshot of my IMON Slope location](https://images2.imgbox.com/e3/02/kgPRIrPm_o.png) in the .ifr file and the in [Ru.efi UI with the altered values of 75%=004B, -6000mV=1770 and Prefix Negative=0x1](https://images2.imgbox.com/4e/73/CgokOV9P_o.jpeg). I would like to inform you that there is only one [IMON Slope available in the BIOS](https://images2.imgbox.com/bd/cc/pJNuebQr_o.png).

One more piece of information to add is that I also tried reducing the number of cores used and parked in isolated power plan by using the following commands:

>*Powercfg -setacvalueindex scheme\_current sub\_processor CPMAXCORES 50*
*Powercfg -setactive scheme\_current*
*Powercfg -setacvalueindex scheme\_current sub\_processor CPMINCORES 25*
*Powercfg -setactive scheme\_current*

This resulted in the CPU occasionally hitting higher frequencies (better than being all-time limited to 0.7\~0.9GHz). However, these spikes did not last long as the EC reduced the power as soon as the clockspeed increased (\~3s delay, to be fair), even though the energy remained capped at the Embedded Controller Long Term PL. For now, this trick may not be entirely viable. Further testing is needed to determine its effectiveness.

Write A Comment