swift3x pc remains hot after pc set to sleep.

RyuzuMeyer

I have a acer swift3x and recently I just installed a graphic driver for both my intel iris xe and iris xe max. The problem is the gpu's temperature remains not less than 50 celsius and when the pc is set to sleep, it become hotter which cause the battery drained fast. I'm not sure whether it's the driver's problem or else but the issue come out after i installed the driver from intel.

Thread was edited to add model name to the title

billsey

Two things to look for, check to make sure Fast Startup isn't enabled. When enabled it leaves some stuff active during sleep which allow it to come back up quickly. Double check to make sure Intel hasn't updated the update. They often release a version that runs hot, then replace that with one that runs cooler fairly quickly. I did an update last week that had me running over 80C when playing solitaire, followed by another update yesterday that dropped it back under 50C.

RyuzuMeyer

I have rolled back the gpu update to it's previous version and it seems the pc won't be overheating anymore. It seems that Intel newest driver update has caused the issues. Btw, thanks for the advice!

billsey

Yes, it seems like every other one runs hot...

Callistemon

Fast power drain in sleep mode and crashes while resuming are often caused by Connected Standby. Fast Startup is also an unwanted feature, but affects Shut Down, not Sleep. Fast Startup hibernates the kernel, which doesn't increase battery drain, but slows startup and causes errors. Connected Standby is what spins down the fans while continuing to use CPU, which not only causes overheating, but is highly inefficient since semiconductors are less efficient at higher temperatures. To disable Connected Standby, open Command Prompt as administrator and paste

powercfg /setacvalueindex scheme_current sub_none F15576E8-98B7-4186-B944-EAFA664402D9 0

powercfg /setdcvalueindex scheme_current sub_none F15576E8-98B7-4186-B944-EAFA664402D9 0

billsey

Note that the letters and number in that can be different for different models and OS versions...

Callistemon

billsey said:

Note that the letters and number in that can be different for different models and OS versions...

In that case, an alternative is this, but it also has a random string. Why did Microsoft decide to make it obfuscated?

reg add HKLM\SOFTWARE\Policies\Microsoft\Power\PowerSettings\f15576e8-98b7-4186-b944-eafa664402d9 /v ACSettingIndex /t REG_DWORD /d 0

reg add HKLM\SOFTWARE\Policies\Microsoft\Power\PowerSettings\f15576e8-98b7-4186-b944-eafa664402d9 /v DCSettingIndex /t REG_DWORD /d 0

billsey

It's not really obfuscated, since they are consistent within their framework. It's just that different sleep mode use different codes. IIRC the ones you are pointing to add a specific function to the current power plan and works if the underlying hardware matches. A lot of power plans are trimmed to not have the full potential functionality, since they are easier to deal with without all the options. My newest laptop (which I'm using as a desktop) didn't have the option to leave the laptop running when the screen was closed, so I used a similar technique to add that option to the power plan.