[solved] Control center / Intel XTU Issues

[Soft Reaper]

Hi, i've just recieved my optimus X 15" yesterday and have seen critical temps on the CPU (30°c inside my flat, more than 86°c on CPU and heavy throttle even with cooling pad ...) and tried a bit of undervolt. As long as Throttlestop is not an official tool, i'd gave a try to Intel eXtreme Tuning Utility, such a big mistake ...

It asked me for a reboot after applying a 0.5GHz underclock on each turbo state, 95mv undervolt on IA Cores and Cache and reducing IccMax to normal value of 51.3 (set by default to 128A by XTU) and it ended by:

- Disabled Turbo (so max 2.6GHz on all core instead of 3.5 set and 4 default)
- 15w nominal TDP (so 2.6GHz become 2GHz and less)
- 30w Boost TDP (but no boost active)
- But stills 128A on IccMax

And unable to set thing back as XTU thinks it is his "defaults" values, each reboot lead to this and even using hwinfo on windows PE (so another OS) leads to the same numbers, tried to uninstall XTU, reset bios to default values, removing CMOS battery and doing a bios flashback.

The lonely thing i didn't done for now is a intel ME Region reflash (as i think XTU saved theses infos directly in MEFW)

any advice, tip or help would be really appreciated

Thank you by advance

 

[debiruman665]

from my experience XTU will assume the bootup parameters are your default.

Clevo control panel has a default setting you can revert back to and sometimes it just makes stuff up when you bootup.

Your bios should have a default settings reset in there to get things back.

As long as you dont boot up XTU it shouldn't try to override your existing settings... Clevo controll on the other hand...

 

[Soft Reaper]

XTU still do it's trick even without autoload and with services disabled, so, not really good, already tried Bios "optimal defaults (F9)" but without success, tried to uninstall it, the same (pictures after uninstall)

i'll take a look at clevo control panel now, i'll stay in touch, thank you for your advice

edit: Clevo Control center automaticaly switched to "eco mode", switching to another mode solved the problem, thank you so much