3 ms·
It's hibernating. Apparently, Windows has the ability to perform some actions based on ACPI, which presumably is disabled by default. For whatever reason, some
by jotm 4y ago
It's hibernating. Apparently, Windows has the ability to perform some actions based on ACPI, which presumably is disabled by default. For whatever reason, some update enables this feature (once every 6+ months, but not right after restoring from backup, strange as hell), but I guess the thermal zones are improperly calibrated? No idea.
https://docs.microsoft.com/en-us/windows-hardware/drivers/bringup/acpi-defined-devices https://docs.microsoft.com/en-us/windows-hardware/drivers/br...
It just hibernates. Passive or active cooling setting, disabled thermal controls in group policy or not, registry tweaks or not. Tried everything.
It just hibernates, middle of work or not. At least it doesn't shut down ¯\_(ツ)_/¯.
I'd say upon reaching ~60-70 degrees on the CPU, but it does it at idle (<50degC) too, so it seems more random than anything. Once, it stopped when I had a Kali Linux VM with a USB Wifi adapter passed through to it (only difference at the time) running. Worked for a few days, then it started doing it regardless.
People with some Dell and Lenovo laptops also have this problem, and it seems so rare that the most common answer is "lol, it's overheating dumdum, thank Microsoft or it would break".
Only surefire solution is to restore from backup.
If it did that under Linux, at least I could easily tell it to ignore everything and let the hardware handle it.