# Extreme (burning) overheating with the lid closed **URL:** \ **Category:** Framework Laptop 13\ **Created:** [January 20, 2022, 10:42am UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983 "2022-01-20T10:42:19Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Art](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@Art](https://community.frame.work/u/Art)\ **Post date:** [January 20, 2022, 10:42am UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/1 "2022-01-20T10:42:19Z")
Windows 10. Battery settings set to 50% max charge in BIOS. Set to performance mode when plugged in and battery saving mode when unplugged. After working on some tasks (Word, Slack, Browser), I closed the lid, assuming the computer would go to sleep. I then unplugged the computer and left for an hour. Came back and winced in pain touching the laptop. It was extremely hot all over and a slight burning smell reminiscent of plastic or some other synthetic material was evident. After letting it cool, I plugged it in and the computer had _luckily_ run out of battery power sometime while I was away. This means I lost all my work but at least the computer still worked. ---
**Author:** ![reanimus](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/reanimus/32/4487_2.png) [@reanimus](https://community.frame.work/u/reanimus)\ **Post date:** [January 20, 2022, 4:38pm UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/2 "2022-01-20T16:38:02Z")
Did you have the computer put away in your bag? It might be that the performance plan you were on didn’t sleep your computer when you closed the lid (as some high performance plans do). Then, when you unplugged, the computer was still awake, and when you put it into your bag, it was running in high performance mode with no ventilation. I’ve had this happen in the past and had it result in laptops that are uncomfortably hot to touch… Assuming you had it in a bag, of course. ---
**Author:** ![Art](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@Art](https://community.frame.work/u/Art)\ **Post date:** [January 21, 2022, 5:09am UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/3 "2022-01-21T05:09:31Z")
Hi. Thanks for the reply! The laptop should’ve gone to sleep upon closing the lid based on my power management settings when it’s plugged in or when it’s on battery. It didn’t, and that’s the root of the problem I would hazard to guess. This happens in Ubuntu as well. However, failure to enter sleep upon lid closure is inconsistent in either Windows 10 or Ubuntu. So I can’t explain that. I had placed the laptop in its case/sleeve after closing the lid, assuming it would just enter sleep mode. ---
**Author:** ![2disbetter](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/2disbetter/32/1176_2.png) [@2disbetter](https://community.frame.work/u/2disbetter)\ **Post date:** [January 21, 2022, 9:43am UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/4 "2022-01-21T09:43:01Z")
I’m glad that it is still alive. I have had a few cases with other laptops that were similar. As such I have since made it a habit to ensure the device is off or in standby (slighty lift the lid and see if the power button is blinking). However, please understand that the OS is responsible for putting the computer to sleep. If the OS does not, the computer will perform as though it is on. Under Windows there are MANY programs that will prevent the computer from entering sleep or wake it from sleep (including Windows itself. It does house cleaning, indexing, and updates during this time). You can run powrconf.exe /lastwake (I think, might want to google/brave that) to see if something woke it from sleep. I would also go into the advance power settings, and under sleep disable ALL wake timers. ---
**Author:** ![Art](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@Art](https://community.frame.work/u/Art)\ **Post date:** [January 22, 2022, 2:43pm UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/5 "2022-01-22T14:43:18Z")
None of this ever happens in my Toshiba, with the same Ubuntu and Windows 10 installed. After searching around, this extreme overheating is apparently not an isolated issue and some possible solutions lie here: > [@Too hot to handle and boot problems](http://community.frame.work/t/too-hot-to-handle-and-boot-problems/11279): > > Installed a new WD Black SN850 2 TB. Tried to install from USB drive prepared by Rufus. This did not work. No media found. Read [Windows 10 Installation on the Framework Laptop DIY Edition - Framework Guides](https://guides.frame.work/Guide/Windows+10+Installation+on+the+Framework+Laptop+DIY+Edition/92#:~:text=%20Windows%2010%20Installation%20on%20the%20Framework%20Laptop,you%20purchased%20Windows%2010%20Home%20or...%20More%20) It’s a good guide if you’re not using Rufus. My Framework community login did not work for adding a comment to this guide. Searched. Decided to start over after disabling secure boot. It was an educated guess, which turned out to be correct. Installed Windows 10. Installed all Windows 10 upd… > [@Laptop Overheating and Losing Connection to M.2 Drive](http://community.frame.work/t/laptop-overheating-and-losing-connection-to-m-2-drive/10508): > > Essentially the problem is that I find my computer overheating while the lid is closed, and this overheating (presumably) causes the M.2 drive to disconnect. I downloaded the latest firmware update today, which said that it solved this problem, but this has not fixed my problem. I already backed up my data because of the possibility of my M.2 drive failing, and I believe I am still under warranty, but wanted to see if anyone else is having this problem (and perhaps any solutions). So I strongly suspect the issue is with the Framework computer. It’s been an issue for at least 2 months (for others) and I’m concerned that it wasn’t addressed by Framework and I wasn’t notified by email of something so potentially serious prior to doing the latest BIOS update. I’m now worried that this extreme overheating shortened the lifespan of what is a very expensive laptop. This is disconcerting for any future ipotential ssues and plenty of unresolved ones I’ve spent days trying to manage with this unit. In any case, thank you for the community’s help. ---
**Author:** ![Art](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@Art](https://community.frame.work/u/Art)\ **Post date:** [January 22, 2022, 2:43pm UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/6 "2022-01-22T14:43:57Z")
A couple other cases: > [@Hot and unable to turn off/on](http://community.frame.work/t/hot-and-unable-to-turn-off-on/5927): > > I set my laptop down on a carpeted floor (maybe a bad idea) with the lid closed. When I opened the lid again it was extremely hot. The blue light was flashing slowly, but pressing would not turn on the laptop. I left it sit on a table, upside down for a while but it remained really hot. I tried to force it to shutdown by holding the power button for 5-10s and it wouldn’t shut down. After letting it sit for 30m I was able to turn it on. The fan immediately turned on full blast, and it coole… > [@Closed lid, plugged into charger, and tossed onto bed. Came back to fan screaming and computer super hot](http://community.frame.work/t/closed-lid-plugged-into-charger-and-tossed-onto-bed-came-back-to-fan-screaming-and-computer-super-hot/11328): > > I just got the laptop today. I have windows 10 installed. I closed the lid and plugged it in and tossed it on the bed. I came back an hour later and the fan was spinning extremely fast and since the vent was facing the bed covers, it couldn’t breathe. How do i just make it sleep/hibernate and not try to cool itself down? Or am i missing something. Thanks! ---
**Author:** ![2disbetter](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/2disbetter/32/1176_2.png) [@2disbetter](https://community.frame.work/u/2disbetter)\ **Post date:** [January 22, 2022, 3:07pm UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/7 "2022-01-22T15:07:19Z")
I would suggest that you open a support ticket. It is possible that there is a Windows 10 modern standby bug that is plaguing the Framework, but I have not dealt with this because I hibernate my 2 frameworks. (both are running Windows 10.) I’m trying to remember if I had any similar issues with Linux, and I think I didn’t. ---
**Author:** ![reanimus](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/reanimus/32/4487_2.png) [@reanimus](https://community.frame.work/u/reanimus)\ **Post date:** [January 22, 2022, 8:29pm UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/8 "2022-01-22T20:29:33Z")
> [@Extreme (burning) overheating with the lid closed](http://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/7): > > I would suggest that you open a support ticket. It is possible that there is a Windows 10 modern standby bug that is plaguing the Framework, but I have not dealt with this because I hibernate my 2 frameworks. (both are running Windows 10.) I’m trying to remember if I had any similar issues with Linux, and I think I didn’t. Yeah, my guess is either a bug in Windows or a possible hardware issue with the lid close sensor. I haven’t seen this happening with my Linux installation, for what it’s worth. ---
**Author:** ![JPC](https://avatars.discourse-cdn.com/v4/letter/j/74df32/32.png) [@JPC](https://community.frame.work/u/JPC)\ **Post date:** [January 23, 2022, 3:38am UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/9 "2022-01-23T03:38:50Z")
The WD Black firmware update solved the overheating problem. I gave up on sleep working like it does on my HP laptops. Now I use hibernate instead of sleep. It’s slower fully waking up from hibernate than from sleep, but it’s tolerable. I custom installed Windows 10 on my HPs and the Framework identically. Only the Framework doesn’t sleep properly. I’m more interested in Framework staying in business than fixing the sleep problem. It would be nice if they could eventually get around to fixing the sleep problem. ---
**Author:** ![Kieran\_Levin](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/kieran_levin/32/110_2.png) [@Kieran\_Levin](https://community.frame.work/u/Kieran_Levin)\ **Post date:** [January 24, 2022, 3:45am UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/10 "2022-01-24T03:45:05Z")
@Art Could you post your hardware specs (especially if you have a DIY edition) and output of ```auto powercfg.exe /SleepStudy ``` After one of these events happens. The laptop fan will turn on in S0 or modern standby. You don’t happen to have S3 standby enabled? ---
**Author:** ![JPC](https://avatars.discourse-cdn.com/v4/letter/j/74df32/32.png) [@JPC](https://community.frame.work/u/JPC)\ **Post date:** [May 8, 2022, 4:48pm UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/11 "2022-05-08T16:48:10Z")
The Framework device has a Western Digital Black gen 4 NVMe. C:\Windows\system32\> **powercfg /availablesleepstates** Host Name: GRUMPYNOTSLEEPY OS Name: Microsoft Windows 10 Pro OS Version: 10.0.19043 N/A Build 19043 OS Manufacturer: Microsoft Corporation OS Configuration: Standalone Workstation OS Build Type: Multiprocessor Free Registered Owner: Me Registered Organization: Product ID: 00330-80138-30407-AA265 Original Install Date: 11/17/2021, 5:32:07 PM System Boot Time: 5/7/2022, 8:25:28 AM System Manufacturer: Framework System Model: Laptop System Type: x64-based PC Processor(s): 1 Processor(s) Installed. [01]: Intel64 Family 6 Model 140 Stepping 1 GenuineIntel ~2419 Mhz BIOS Version: INSYDE Corp. 03.02, 7/1/2021 Windows Directory: C:\Windows System Directory: C:\Windows\system32 Boot Device: \Device\HarddiskVolume1 System Locale: en-us;English (United States) Input Locale: en-us;English (United States) Time Zone: (UTC-06:00) Central Time (US & Canada) Total Physical Memory: 32,551 MB Available Physical Memory: 23,116 MB Virtual Memory: Max Size: 37,415 MB Virtual Memory: Available: 27,812 MB Virtual Memory: In Use: 9,603 MB Page File Location(s): C:\pagefile.sys Domain: WORKGROUP Logon Server: \GRUMPYNOTSLEEPY Hotfix(s): 9 Hotfix(s) Installed. [01]: KB5012157 [02]: KB5000736 [03]: KB5005716 [04]: KB5012599 [05]: KB5006753 [06]: KB5007273 [07]: KB5011352 [08]: KB5011651 [09]: KB5005260 Network Card(s): 3 NIC(s) Installed. [01]: Realtek USB GbE Family Controller Connection Name: Ethernet DHCP Enabled: Yes DHCP Server: 192.168.2.1 IP address(es) [01]: 192.168.2.163 [02]: fe80::a58e:1e7f:84a9:83e8 [02]: Bluetooth Device (Personal Area Network) Connection Name: Bluetooth Network Connection 2 Status: Media disconnected [03]: Intel(R) Wi-Fi 6E AX210 160MHz Connection Name: Wi-Fi 2 Status: Media disconnected Hyper-V Requirements: VM Monitor Mode Extensions: Yes Virtualization Enabled In Firmware: Yes Second Level Address Translation: Yes Data Execution Prevention Available: Yes C:\Windows\system32\> **powercfg /availablesleepstates** The following sleep states are available on this system: Standby (S0 Low Power Idle) Network Connected Hibernate Fast Startup The following sleep states are not available on this system: Standby (S1) The system firmware does not support this standby state. This standby state is disabled when S0 low power idle is supported. ``` Standby (S2) The system firmware does not support this standby state. This standby state is disabled when S0 low power idle is supported. Standby (S3) This standby state is disabled when S0 low power idle is supported. Hybrid Sleep Standby (S3) is not available. ``` C:\Windows\system32\> **wmic diskdrive** Availability BytesPerSector 512 Capabilities “{3, 4}” CapabilityDescriptions “{”“Random Access”“, ““Supports Writing””}” Caption WD\_BLACK SN850 2TB CompressionMethod ConfigManagerErrorCode 0 ConfigManagerUserConfig FALSE CreationClassName Win32\_DiskDrive DefaultBlockSize Description Disk drive DeviceID \.\PHYSICALDRIVE0 ErrorCleared ErrorDescription ErrorMethodology FirmwareRevision 614900WD Index 0 InstallDate InterfaceType SCSI LastErrorCode Manufacturer (Standard disk drives) MaxBlockSize MaxMediaSize MediaLoaded TRUE MediaType Fixed hard disk media MinBlockSize Model WD\_BLACK SN850 2TB Name \.\PHYSICALDRIVE0 NeedsCleaning NumberOfMediaSupported Partitions 3 PNPDeviceID SCSI\DISK&VEN\_NVME&PROD\_WD\_BLACK\_SN850\_2\5&307B379&0&000000 PowerManagementCapabilities PowerManagementSupported SCSIBus 0 SCSILogicalUnit 0 SCSIPort 0 SCSITargetId 0 SectorsPerTrack 63 SerialNumber E823\_8FA6\_BF53\_0001\_001B\_448B\_417B\_4A5C. Signature Size 2000396321280 Status OK StatusInfo SystemCreationClassName Win32\_ComputerSystem SystemName GRUMPYNOTSLEEPY TotalCylinders 243201 TotalHeads 255 TotalSectors 3907024065 TotalTracks 62016255 TracksPerCylinder 255 ![sleepOffenders](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/2X/8/842c9093013426fb14bcabacfb6e793940f2266f.png) ![sleepLog](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/2X/7/7414fabf879611aa2efadea385b987addaa66f1a.png) A recurring theme is that Modern Standby is the culprit. Another is that it’s not Framework’s problem. I have two $300 HP laptops that sleep and resume from sleep without any problems. This empirical evidence invalidates any response that shifts blame and responsibility away from Framework. The two HP devices have Hynix gen 3 NVMe as can be seen below: Availability BytesPerSector 512 Capabilities {3, 4} CapabilityDescriptions {“Random Access”, “Supports Writing”} Caption SHGP31-1000GM-2 CompressionMethod ConfigManagerErrorCode 0 ConfigManagerUserConfig FALSE CreationClassName Win32\_DiskDrive DefaultBlockSize Description Disk drive DeviceID \.\PHYSICALDRIVE0 ErrorCleared ErrorDescription ErrorMethodology FirmwareRevision 41061C20 Index 0 InstallDate InterfaceType SCSI LastErrorCode Manufacturer (Standard disk drives) MaxBlockSize MaxMediaSize MediaLoaded TRUE MediaType Fixed hard disk media MinBlockSize Model SHGP31-1000GM-2 Name \.\PHYSICALDRIVE0 NeedsCleaning NumberOfMediaSupported Partitions 3 PNPDeviceID SCSI\DISK&VEN\_NVME&PROD\_SHGP31-1000GM-2\5&32FEC70B&0&000000 PowerManagementCapabilities PowerManagementSupported SCSIBus 0 SCSILogicalUnit 0 SCSIPort 0 SCSITargetId 0 SectorsPerTrack 63 SerialNumber FFFF\_FFFF\_FFFF\_FFFF. Signature Size 1000202273280 Status OK StatusInfo SystemCreationClassName Win32\_ComputerSystem SystemName SLEEPYNOTGRUMPY TotalCylinders 121601 TotalHeads 255 TotalSectors 1953520065 TotalTracks 31008255 TracksPerCylinder 255 ---
**Author:** ![Be\_Far](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/be_far/32/43857_2.png) [@Be\_Far](https://community.frame.work/u/Be_Far)\ **Post date:** [May 8, 2022, 5:24pm UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/12 "2022-05-08T17:24:14Z")
Ironic that your hostname is GRUMPYNOTSLEEPY, because this laptop certainly is grumpy and absolutely never sleepy lol. Specs: Dual Boot Win10 Pro + linux flavor of the week 1x16GB taiwanese brand ram 2TB WD\_BLACK SN750 TB3 eGPU - NVIDIA GTX1650S I have similar experiences with modern standby Working As Intended™ and not letting the darn thing turn off. I actually made a post about this - rarely the power button starts breathing and will slowly spin the fans down to stop over about a minute (which is what I want), the other 90% of the time it just ramps up the fans and sits there for however long the lid is closed, cooking wherever I chose to put it down, whether that’s on my custom maximum-airflow laptop stand, in my backpack, or on the couch. On or off my egpu. I’m thinking Ubuntu is maybe trying experimental support for Modern Standby and that’s why you experience it there. I haven’t seen it in Fedora or Mint, those both use S3. At this point it is likely a bug with Windows as I’ve seen other people with bleeding edge laptops complaining about the same thing, I can only hope it’s fixed soon, because S3 doesn’t work properly with my eGPU on Windows _cries_ ---
**Author:** ![JPC](https://avatars.discourse-cdn.com/v4/letter/j/74df32/32.png) [@JPC](https://community.frame.work/u/JPC)\ **Post date:** [May 9, 2022, 11:37am UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/13 "2022-05-09T11:37:39Z")
I added the **PlatformAoAcOverride** registry key REG\_DWORD making it 0 and rebooted. C:\Users\Me\> **powercfg /availablesleepstates** The following sleep states are available on this system: Standby (S3) Hibernate Hybrid Sleep Fast Startup The following sleep states are not available on this system: Standby (S1) The system firmware does not support this standby state. ``` Standby (S2) The system firmware does not support this standby state. Standby (S0 Low Power Idle) The system firmware does not support this standby state. ``` It does appear to sleep. Presumably this state doesn’t cause wear on the SSD. It does not wake in respond to keyboard or mouse actions. I have to use the power button to wake the machine. Since this is a lid shut desktop replacement, this is quite inconvenient and not what is wanted. My HP laptops work as wanted. If other machines work properly, so should Framework machines. ---
**Author:** ![Be\_Far](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/be_far/32/43857_2.png) [@Be\_Far](https://community.frame.work/u/Be_Far)\ **Post date:** [May 19, 2022, 12:57pm UTC](https://community.frame.work/t/extreme-burning-overheating-with-the-lid-closed/13983/14 "2022-05-19T12:57:17Z")
> [@JPC](#): > > this is quite inconvenient and not what is wanted. I have issues with this solution as well. S3 doesn’t play nice with my Thubderbolt devices and I have to hot-plug my GPU after suspend with this option.