# Spontaneous poweroffs on Framework Laptop 12

**URL:** <https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660>\
**Category:** Linux\
**Tags:** ubuntu\
**Created:** [May 20, 2026, 10:25am UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660 "2026-05-20T10:25:59Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![bdrung](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@bdrung](https://community.frame.work/u/bdrung)\
**Post date:** [May 20, 2026, 10:25am UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/1 "2026-05-20T10:25:59Z")

</div>

My Framework Laptop 12 turned off spontaneously. This is not the first time. It happened once today, once yesterday and one or two times last week. I saw this in the boot log afterwards:

```auto
Adapter: ISA adapter
in0: 5.00 V (min = +5.00 V, max = +5.00 V)
curr1: 3.00 A (max = +3.00 A)
cros_ec-isa-000c
Adapter: ISA adapter
fan1: 3043 RPM
cpu_f75303@4d: +48.9°C (high = -273.1°C, crit = +74.8°C)
                              (emerg = +84.8°C)
top_skin_f75303@4d: +43.9°C (high = -273.1°C, crit = +79.8°C)
                              (emerg = +89.8°C)
local_f75303@4d: +38.9°C (high = -273.1°C, crit = +83.8°C)
                              (emerg = +93.8°C)
battery_temp@b: +23.9°C (high = -273.1°C, crit = +60.9°C)
                              (emerg = +65.8°C)
peci-temp: FAULT (high = +114.8°C, crit = +119.8°C)
                              (emerg = +126.8°C)
charger_temp@9: +46.9°C (high = -273.1°C, crit = -273.1°C)
                              (emerg = -273.1°C)
nvme-pci-0100
Adapter: PCI adapter
Composite: +36.9°C (low = -40.1°C, high = +83.8°C)
                       (crit = +87.8°C)
Sensor 1: +54.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +36.9°C (low = -273.1°C, high = +65261.8°C)
coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +73.0°C (high = +100.0°C, crit = +100.0°C)
Core 0: +71.0°C (high = +100.0°C, crit = +100.0°C)
Core 4: +66.0°C (high = +100.0°C, crit = +100.0°C)
Core 8: +73.0°C (high = +100.0°C, crit = +100.0°C)
Core 9: +73.0°C (high = +100.0°C, crit = +100.0°C)
Core 10: +73.0°C (high = +100.0°C, crit = +100.0°C)
Core 11: +73.0°C (high = +100.0°C, crit = +100.0°C)
Core 12: +67.0°C (high = +100.0°C, crit = +100.0°C)
Core 13: +67.0°C (high = +100.0°C, crit = +100.0°C)
Core 14: +67.0°C (high = +100.0°C, crit = +100.0°C)
Core 15: +67.0°C (high = +100.0°C, crit = +100.0°C)
ucsi_source_psy_USBC000:001-isa-0000
Adapter: ISA adapter
in0: 0.00 V (min = +0.00 V, max = +0.00 V)
curr1: 3.00 A (max = +0.00 A)
acpitz-acpi-0
Adapter: ACPI interface
temp1: +80.8°C
temp2: +43.9°C
temp3: +38.9°C
temp4: +48.9°C
temp5: +24.6°C
ucsi_source_psy_USBC000:004-isa-0000
Adapter: ISA adapter
in0: 20.00 V (min = +5.00 V, max = +20.00 V)
curr1: 3.25 A (max = +3.25 A)
ucsi_source_psy_USBC000:002-isa-0000
Adapter: ISA adapter
in0: 5.00 V (min = +5.00 V, max = +5.00 V)
curr1: 3.00 A (max = +3.00 A)
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: N/A
BAT1-acpi-0
Adapter: ACPI interface
in0: 13.33 V
curr1: 1000.00 uA
acpi_fan-isa-0000
Adapter: ISA adapter
fan1: 3043 RPM
power1: N/A

```

`peci-temp` showing `FAULT` is not a good sign. I can touch the laptop and it does not feel hot. How can I debug that behavior?

My system:

- Batch 2 of Framework Laptop 12 (Intel Core i5-1334U) DIY
- Linux distro: Ubuntu 26.04 “resolute”
- Kernel: 7.0.0-15.15
- BIOS version: 3.7

---

<div class="post-metadata">

**Author:** ![Charlie\_6](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/charlie_6/32/22087_2.png) [@Charlie\_6](https://community.frame.work/u/Charlie_6)\
**Post date:** [May 20, 2026, 2:21pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/2 "2026-05-20T14:21:46Z")

</div>

The ACPI temp1 is the same as peci, which is the CPU temperature, although the FAULTy sensor doesn’t control the fan curve, this error can confuse the controller, making the fan stop or run erratically, causing an overheating shutdown, even if you don’t feel the temperature as heat dissipation is slow if the fan doesn’t work

---

<div class="post-metadata">

**Author:** ![bdrung](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@bdrung](https://community.frame.work/u/bdrung)\
**Post date:** [May 21, 2026, 8:19am UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/3 "2026-05-21T08:19:56Z")

</div>

It happened again. Before going to bed yesterday, I put the laptop into suspend. Last logs from that boot:

```auto
systemd-sleep[749957]: Successfully froze unit 'user.slice'.
systemd-sleep[749957]: Performing sleep operation 'suspend'...
kernel: PM: suspend entry (s2idle)

```

When I came back this morning, the laptop was powered off. The laptop had a power connection and showed 100% battery after booting.

---

<div class="post-metadata">

**Author:** ![bdrung](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@bdrung](https://community.frame.work/u/bdrung)\
**Post date:** [May 21, 2026, 1:47pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/4 "2026-05-21T13:47:30Z")

</div>

Just happened again. No heavy load this time. `peci-temp` showed `FAULT` again.

```auto
$ sensors
ucsi_source_psy_USBC000:003-isa-0000
Adapter: ISA adapter
in0: 5.00 V (min = +5.00 V, max = +5.00 V)
curr1: 3.00 A (max = +3.00 A)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +58.0°C (high = +100.0°C, crit = +100.0°C)
Core 0: +50.0°C (high = +100.0°C, crit = +100.0°C)
Core 4: +52.0°C (high = +100.0°C, crit = +100.0°C)
Core 8: +55.0°C (high = +100.0°C, crit = +100.0°C)
Core 9: +55.0°C (high = +100.0°C, crit = +100.0°C)
Core 10: +55.0°C (high = +100.0°C, crit = +100.0°C)
Core 11: +55.0°C (high = +100.0°C, crit = +100.0°C)
Core 12: +55.0°C (high = +100.0°C, crit = +100.0°C)
Core 13: +55.0°C (high = +100.0°C, crit = +100.0°C)
Core 14: +54.0°C (high = +100.0°C, crit = +100.0°C)
Core 15: +54.0°C (high = +100.0°C, crit = +100.0°C)

nvme-pci-0100
Adapter: PCI adapter
Composite: +36.9°C (low = -40.1°C, high = +83.8°C)
                       (crit = +87.8°C)
Sensor 1: +46.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +36.9°C (low = -273.1°C, high = +65261.8°C)

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: +35.0°C  

ucsi_source_psy_USBC000:001-isa-0000
Adapter: ISA adapter
in0: 0.00 V (min = +0.00 V, max = +0.00 V)
curr1: 3.00 A (max = +0.00 A)

acpitz-acpi-0
Adapter: ACPI interface
temp1: +66.8°C  
temp2: +44.9°C  
temp3: +38.9°C  
temp4: +48.9°C  
temp5: +24.6°C  

ucsi_source_psy_USBC000:004-isa-0000
Adapter: ISA adapter
in0: 20.00 V (min = +5.00 V, max = +20.00 V)
curr1: 3.25 A (max = +3.25 A)

ucsi_source_psy_USBC000:002-isa-0000
Adapter: ISA adapter
in0: 5.00 V (min = +5.00 V, max = +5.00 V)
curr1: 3.00 A (max = +3.00 A)

cros_ec-isa-000c
Adapter: ISA adapter
fan1: 3401 RPM
cpu_f75303@4d: +48.9°C (high = -273.1°C, crit = +74.8°C)
                              (emerg = +84.8°C)
top_skin_f75303@4d: +44.9°C (high = -273.1°C, crit = +79.8°C)
                              (emerg = +89.8°C)
local_f75303@4d: +38.9°C (high = -273.1°C, crit = +83.8°C)
                              (emerg = +93.8°C)
battery_temp@b: +23.9°C (high = -273.1°C, crit = +60.9°C)
                              (emerg = +65.8°C)
peci-temp: FAULT (high = +114.8°C, crit = +119.8°C)
                              (emerg = +126.8°C)
charger_temp@9: +41.9°C (high = -273.1°C, crit = -273.1°C)
                              (emerg = -273.1°C)

BAT1-acpi-0
Adapter: ACPI interface
in0: 13.31 V  
curr1: 0.00 A  

acpi_fan-isa-0000
Adapter: ISA adapter
fan1: 3401 RPM
power1: N/A  

```

A minute later:

```auto
$ sensors | grep peci
peci-temp: +66.8°C (high = +114.8°C, crit = +119.8°C)

```

---

<div class="post-metadata">

**Author:** ![AccelShark](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/accelshark/32/50137_2.png) [@AccelShark](https://community.frame.work/u/AccelShark)\
**Post date:** [May 21, 2026, 4:01pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/5 "2026-05-21T16:01:59Z")

</div>

Please tell us the [UEFI and EC](https://knowledgebase.frame.work/en_us/how-to-check-the-bios-version-on-windows-linux-bios-ryupu8HT3) firmware versions you are running. I think unexpected shutdowns are usually a low-level issue involving firmware or a faulty component.

---

<div class="post-metadata">

**Author:** ![bdrung](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@bdrung](https://community.frame.work/u/bdrung)\
**Post date:** [May 21, 2026, 4:44pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/6 "2026-05-21T16:44:16Z")

</div>

Same as mentioned in the first post:

```auto
$ sudo dmidecode | grep -A3 'Vendor:\|Product:' 
	Vendor: INSYDE Corp.
	Version: 03.07
	Release Date: 02/10/2026
	Address: 0xE0000
$ sudo LANG=C.UTF-8 lshw -C cpu | grep -A3 'product:\|vendor:'
       product: 13th Gen Intel(R) Core(TM) i5-1334U
       vendor: Intel Corp.
       physical id: 4
       bus info: cpu@0
       version: 6.186.3

```

**Note** : The [BIOS page](https://knowledgebase.frame.work/en_us/how-to-check-the-bios-version-on-windows-linux-bios-ryupu8HT3) should add `LANG=C.UTF-8`to the `lshw` command. Otherwise it will show nothing on non-English systems since the output is translated.

---

<div class="post-metadata">

**Author:** ![bdrung](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@bdrung](https://community.frame.work/u/bdrung)\
**Post date:** [May 21, 2026, 4:52pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/7 "2026-05-21T16:52:46Z")

</div>

And it happened again. My gut feeling is that the frequency starts to increase. `peci-temp` shows `FAULT` in the journal boot logs.

---

<div class="post-metadata">

**Author:** ![bdrung](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@bdrung](https://community.frame.work/u/bdrung)\
**Post date:** [May 21, 2026, 5:01pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/8 "2026-05-21T17:01:00Z")

</div>

I just verified that the system will behave differently when the kernel crashes by running:

```auto
echo c | sudo tee /proc/sysrq-trigger

```

The reboot afterwards has a correct `peci-temp` value:

```auto
$ journalctl -W -b 0 -g peci-temp
Mai 21 18:54:57 sensors[2671]: peci-temp: +81.8°C (high = +114.8°C, crit = +119.8°C)

```

---

<div class="post-metadata">

**Author:** ![bdrung](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@bdrung](https://community.frame.work/u/bdrung)\
**Post date:** [May 22, 2026, 4:59pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/9 "2026-05-22T16:59:06Z")

</div>

I was away for a few hours. When I came back the laptop was powered off.

---

<div class="post-metadata">

**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\
**Post date:** [May 22, 2026, 7:37pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/10 "2026-05-22T19:37:58Z")

</div>

Hi. It is only other users like you here.  
It sounds like a hardware fault to me, so probably best to contract FW support via their web form.

Some things that can help track down the source of the problem, in case it is software related.

1. What make, module and firmware is the SSD/NVME.  
`sudo nvme list`
2. Look in the logs after a reboot.  
Does it mention “Previous system reset reason” anywhere ? (Note this one might only work on AMD cpus)

---

<div class="post-metadata">

**Author:** ![bdrung](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@bdrung](https://community.frame.work/u/bdrung)\
**Post date:** [May 22, 2026, 11:01pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/11 "2026-05-22T23:01:17Z")

</div>

And it happened again.

I contacted FW in parallel to documenting my problems publicly in this thread.

```auto
$ sudo nvme list
[sudo] Passwort für bdrung: 
Node Generic SN Model Namespace Usage Format FW Rev  
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
/dev/nvme0n1 /dev/ng0n1 <some SN> WD_BLACK SN770M 2TB 0x1 2.00 TB / 2.00 TB 512 B + 0 B 731130WD

```

Found no reset reason:

```auto
journalctl -W -b 0 | grep -i "reset reason"

```

---

<div class="post-metadata">

**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\
**Post date:** [May 23, 2026, 1:02am UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/12 "2026-05-23T01:02:40Z")

</div>

There is a firmware update available for that SSD.  
Backup your valuable files and then try upgrading the firmware of the SSD using this guide:

> [@Western Digital Drive Update Guide Without Windows/WD Dashboard](https://community.frame.work/t/western-digital-drive-update-guide-without-windows-wd-dashboard/20616/54):
>
> I am not an expert on NVMe firmware updates, but I did have the same problem of updates not applying because the utility was broken and I had to do it manually. I’m not sure that all necessary fixes have been made upstream, and the maintainer has blocked me from interacting with all of their repositories for an unknown reason, so I can’t provide patches or clarifications. First, make sure you are using at least version 1.2.2, as the previous versions generated invalid download URLs without erro…

You have firmware: 731130WD  
Update available: 731150WD

There have been reports of old SSD firmware causing reboots of the system. I.e. Bugs fixed in more recent firmware.

---

<div class="post-metadata">

**Author:** ![bdrung](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@bdrung](https://community.frame.work/u/bdrung)\
**Post date:** [May 23, 2026, 5:57pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/13 "2026-05-23T17:57:15Z")

</div>

Thanks. I did the firmware update following these instructions.

1. Go to [https://wddashboarddownloads.wdc.com/wdDashboard/firmware/WD\_BLACK\_SN770M\_2TB/731150WD/device\_properties.xml](https://wddashboarddownloads.wdc.com/wdDashboard/firmware/WD_BLACK_SN770M_2TB/731150WD/device_properties.xml)
2. download [https://wddashboarddownloads.wdc.com/wdDashboard/firmware/WD\_BLACK\_SN770M\_2TB/731150WD/731150WD.fluf](https://wddashboarddownloads.wdc.com/wdDashboard/firmware/WD_BLACK_SN770M_2TB/731150WD/731150WD.fluf)
3. Apply:

```auto
sudo nvme fw-download -f 731150WD.fluf /dev/nvme0
sudo nvme fw-commit -s 2 -a 3 /dev/nvme0

```

Success:

```auto
$ sudo nvme list
Node Generic SN Model Namespace Usage Format FW Rev  
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
/dev/nvme0n1 /dev/ng0n1 <sn> WD_BLACK SN770M 2TB 0x1 2.00 TB / 2.00 TB 512 B + 0 B 731150WD

```

Let’s see if that makes a difference.

---

<div class="post-metadata">

**Author:** ![bdrung](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@bdrung](https://community.frame.work/u/bdrung)\
**Post date:** [May 26, 2026, 10:15pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/14 "2026-05-26T22:15:07Z")

</div>

No sudden poweroffs in the last days, but there were quite some kernel crashes: [Bug #2154305 “BUG: unable to handle page fault for address: ffff...” : Bugs : linux package : Ubuntu](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154305)

---

<div class="post-metadata">

**Author:** ![bdrung](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@bdrung](https://community.frame.work/u/bdrung)\
**Post date:** [May 28, 2026, 10:19am UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/15 "2026-05-28T10:19:35Z")

</div>

I am also seeing internal gcc compiler errors that other people do not see: [Bug #2154439 “libgit2 1.9.3+ds-1ubuntu1 fails to build on Framew...” : Bugs : gcc-15 package : Ubuntu](https://bugs.launchpad.net/ubuntu/+source/gcc-15/+bug/2154439)

---

<div class="post-metadata">

**Author:** ![Gene\_Hilton](https://avatars.discourse-cdn.com/v4/letter/g/82dd89/32.png) [@Gene\_Hilton](https://community.frame.work/u/Gene_Hilton)\
**Post date:** [May 29, 2026, 7:23pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/16 "2026-05-29T19:23:13Z")

</div>

I’m sure there are other way more qualified people than me to commenthere, and aplogies if my suggestions are completely obvious, but first I’d - test the memory. Then look into smartctl to make sure you aren’t having read errors. Next I’d make sure there aren’t any funny bios settings (maybe go to factory default). Lastly if it was some old fashioned deskop I’d look at the rail voltages. Since that’s hard here maybe try the software route - lm-sensors etc (which you’ve seemed to have done). If none of those things showed a problem, I ask support for a replacement.

---

<div class="post-metadata">

**Author:** ![Hytham\_Alihassan](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/hytham_alihassan/32/35854_2.png) [@Hytham\_Alihassan](https://community.frame.work/u/Hytham_Alihassan)\
**Post date:** [May 29, 2026, 9:17pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/17 "2026-05-29T21:17:39Z")

</div>

I just started having this issue today. I think I had received a Batch 3 framework, and suddenly it started powering off automatically on its own (using Windows 11). I tried plugging in power (battery was also at 100%) but that didn’t help.

Here’s the BIOS error message I saw:

[PANIC] panicked at /home/zoid/.cargo/git/checkouts/framework-system-c60818420f86c0a6/6f22231/framework\_lib/src/power.rs:416:36:  
attempt to divide by zero

Update: I was able to boot up again by plugging in a USB flash drive to boot Ubuntu live image and selected Windows from the BIOS. Now the battery is showing 0%. I will proceed with the latest driver and BIOS updates, then report back.

---

<div class="post-metadata">

**Author:** ![Hytham\_Alihassan](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/hytham_alihassan/32/35854_2.png) [@Hytham\_Alihassan](https://community.frame.work/u/Hytham_Alihassan)\
**Post date:** [May 29, 2026, 11:42pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/18 "2026-05-29T23:42:44Z")

</div>

I updated the BIOS and latest May 2026 drivers from Framework but I still have the same issue. I took apart my Framework 12 and removed the battery, then held down the power button to drain the motherboard. After reinstalling the battery, red leds on both sides blinked about 4x, then I reassembled the laptop and powered it on. Unfortunately, I yet have the same panic, and my battery is still reporting 0%.

---

<div class="post-metadata">

**Author:** ![Hytham\_Alihassan](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/hytham_alihassan/32/35854_2.png) [@Hytham\_Alihassan](https://community.frame.work/u/Hytham_Alihassan)\
**Post date:** [June 6, 2026, 12:54am UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/19 "2026-06-06T00:54:01Z")

</div>

FYI my issue was resolved and required a battery replacement.

---

<div class="post-metadata">

**Author:** ![bdrung](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@bdrung](https://community.frame.work/u/bdrung)\
**Post date:** [July 1, 2026, 11:22pm UTC](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660/20 "2026-07-01T23:22:56Z")

</div>

I was on vacation and busy. Today I tried again to check if the laptop still shows issues. I found following interesting result:

- when battery powered, libgit2 builds successful
- when power is plugged in, libgit2 fails to build with different failures like segmentation faults (dmesg does not show any kernel bugs; the laptop keeps running, no spontaneous poweroff)

This is 100% reproducible for me (tried 3-5 times).

[Next page](https://community.frame.work/t/spontaneous-poweroffs-on-framework-laptop-12/82660.md?page=2)
