This was also the solution for me under a Linux OS. one of my RAM sticks was bad. I setill experience this crash/sudden power loss occasionally but its now less frequent and appears to be related to mouse input during wake (which is probably a topic for another thread)
I had this happen to me once as well. I’ve contact support and they’ve asked for a video of the computer booting. For the record I ordered late enough to not be in the batch system, i5, Windows 11 DIY with 1TB Intel SSD and 16GM RAM (Dual 8GB).
The same thing just happened to me for the first time.
I was in a meeting reading information off of my laptop screen, the laptop was on battery with over 60% charge. The laptop just turned itself off. After a few seconds I pressed the power button and the computer turned back on.
I hope it will not happened again!
Got my 11th gen (i7-1165G7) framework a few weeks ago, just had my first random poweroff at ~62% battery. Instant shutoff under low cpu load (just browser idle and playing a very low-resource game (dungeon crawl stone soup)).
I will run another memtest overnight; first one passed, but memory faults can take several tries to find if they exist.
My operating system is OpenBSD, I have the sysctls machdep.pwraction=0 (do nothing on pressing power button), and machdep.lidaction=1 (suspend on lid close) set, so I doubt it’s anything intended OS side if it is in fact a software bug. Nothing in the syslog that helps, just normal daemon messages and the message for the next boot.
I am also on the latest bios revision (03.07 iirc), I also was touching the touchpad when the shutoff happened, and I was not touching the keyboard. Palms were resting on the palm rest.
I assume you got the DYI version. I had random shutoffs all the time. I got it to stop once I removed 1 of my 2 ram sticks. Your mileage may vary. I suggest contacting customer support.
I don’t know anything about OpenBSD, but this sounds like a driver issue. Have you looked at the OP’s blog link in the OpenBSD on the Framework Laptop thread, specifically the support log section?
Are all the relevant drivers loading at boot - pchgpio, iic, dwiic, ihidev, imt? You might compare your dmesg output with this post from the OpenBSD mailing list. If you have:
ihidev1 at iic2 addr 0x2c gpio 3, vendor 0x93a product 0x274, PIXA3854
somewhere in there, then it’s probably not a touchpad issue and you can move on to other diagonses.
$ dmesg | grep -E '^(pchgpio|iic|dwiic|ihidev|imt)[0-9]'
pchgpio0 at acpi0 GPI0 addr 0xfd6e0000/0x10000 0xfd6d0000/0x10000 0xfd6a0000/0x10000 0xfd690000/0x10000 irq 14, 360 pins
dwiic0 at pci0 dev 21 function 3 "Intel 500 Series I2C" rev 0x20: apic 2 int 30
iic0 at dwiic0
ihidev0 at iic0 addr 0x2c gpio 3, vendor 0x93a product 0x274, PIXA3854
ihidev0: 67 report ids
imt0 at ihidev0: touchpad, 5 contacts
iic1 at ichiic0
dwiic0: timed out reading remaining 37
dwiic0: timed out reading remaining 37
The timeouts occur seemingly at random during runtime.
I am using the fix for suspend/hibernate in the mailing list (otherwise a kernel panic occurs):
/etc/bsd.re-config
change 226
y
21
3
0
this happened to me yesterday when I was editing a document on the train (on battery). Screen went entirely blank and nothing in event viewer other than “the previous shutdown was unexpected”.
This is the first time I’ve seen it happen but I suspect it’s been happening when Windows does the suspend-to-hibernate thing, as sometimes I will start up my laptop having put it to sleep the day before and none of my programs will be open. Same situation in Event Viewer.
My config is the i5-1135G7, 1x 8GB RAM, 1TB WD SN750, Windows 10, bios 3.07
What OS are you using?
There is a process where sleep goes to hibernate, not that that should close your programmes
So is this just overnight, like 6 to 9 hours?
Can you tell what the battery charge is at either end of the ‘sleep’?
I’m not sure this was/is a BIOS issue though
This is unsettling indeed, I just had this happen to me (First gen, Pop!_Os kernel, 5.18.10-76051810-generic)
95% full battery, not attached to a wall, doing a simple vi on a file. nothing big or load inducing.
Only real error in Dmesg:
[ 9.832199] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20211217/psargs-330)
[ 9.832208] kernel:
[ 9.832209] kernel: No Local Variables are initialized for Method [_OSC]
[ 9.832209] kernel:
[ 9.832210] kernel: Initialized Arguments for Method [_OSC]: (4 arguments defined for method invocation)
[ 9.832210] kernel: Arg0: 00000000b9835554 <Obj> Buffer(16) 5D A8 3B B2 B7 C8 42 35
[ 9.832217] kernel: Arg1: 00000000ba4aa013 <Obj> Integer 0000000000000001
[ 9.832219] kernel: Arg2: 000000006af5c972 <Obj> Integer 0000000000000002
[ 9.832221] kernel: Arg3: 000000000df2bf7f <Obj> Buffer(8) 00 00 00 00 05 00 00 00
[ 9.832226] kernel:
[ 9.832227] kernel: ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[ 9.846326] kernel: mc: Linux media interface: v0.10
But I don’t think it’s related.
Topic reviving!
Instant power loss while watching something (HDMI → TV and aux cable → amplifier). Batch 5, i5, Fedora 36 KDE (just updated from 35 today). Laptop not plugged into wall, battery at ~65%, no active interaction with keyboard to rest of laptop so no fn keys being pressed. Laptop wasn’t hot to the touch, no fan whirring.
journalctl logs say:
Sep 18 10:51:17 fedora plasmashell[6268]: libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so
Sep 18 10:51:17 fedora plasmashell[6268]: libva info: Found init function __vaDriverInit_1_14
Sep 18 10:51:17 fedora plasmashell[6268]: libva info: va_openDriver() returns 0
Sep 18 10:56:43 fedora org_kde_powerdevil[2620]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Sep 18 10:57:58 fedora org_kde_powerdevil[2620]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
...aaaand power loss.
Can’t figure out what powerdevil wanted to do - power settings don’t call for sleep or shutdown or even screen dimming.
Going to assume it’s a hardware issue…as the issue wasn’t unexpected graceful system shutdown…but an instant power loss.
If that’s the case, then one ‘typically’ likely (read with a pinch of salt) cause is the cells in the battery pack are not as well balanced as they should be (actual charge / capacity wise).
What you can typically do is to give the laptop a few charge / discharge cycles just to ‘freshen’ up the pack. Sometimes, that’s all it takes to back the battery pack back onto the happy path. If the issue persists…reach out to support.
2 Likes
I’ve been experiencing random shut offs since I got my framework laptop a week ago (batch 3 12th gen). While typing it will shutoff instantly. Wakes up as if from hibernate. Some relevant event viewer text below (laptop died in use at 3:25, made sure to wait and turned it on at 3:50). “Button or lid” seems to be the reason.
Log Name: System
Source: Microsoft-Windows-UserModePowerService
Date: 10/1/2022 3:50:31 PM
Event ID: 12
Task Category: (10)
Level: Information
Keywords:
User: SYSTEM
Computer: serkanframework
Description:
Process C:\Windows\System32\WUDFHost.exe (process ID:1380) reset policy scheme from {381b4222-f694-41f0-9685-ff5bb260df2e} to {381b4222-f694-41f0-9685-ff5bb260df2e}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-UserModePowerService" Guid="{ce8dee0b-d539-4000-b0f8-77bed049c590}" />
<EventID>12</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>10</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2022-10-01T22:50:31.7662385Z" />
<EventRecordID>5045</EventRecordID>
<Correlation />
<Execution ProcessID="1096" ThreadID="14964" />
<Channel>System</Channel>
<Computer>serkanframework</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="ProcessPath">C:\Windows\System32\WUDFHost.exe</Data>
<Data Name="ProcessPid">1380</Data>
<Data Name="OldSchemeGuid">{381b4222-f694-41f0-9685-ff5bb260df2e}</Data>
<Data Name="NewSchemeGuid">{381b4222-f694-41f0-9685-ff5bb260df2e}</Data>
</EventData>
</Event>
Log Name: System
Source: Win32k
Date: 10/1/2022 3:50:31 PM
Event ID: 701
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: serkanframework
Description:
Power Manager has not requested suppression of all input (INPUT_SUPPRESS_REQUEST=0)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Win32k" />
<EventID Qualifiers="32768">701</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-10-01T22:50:31.5277076Z" />
<EventRecordID>5044</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="1840" />
<Channel>System</Channel>
<Computer>serkanframework</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>000000000100000000000000BD020080000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
Log Name: System
Source: Win32k
Date: 10/1/2022 3:50:31 PM
Event ID: 701
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: serkanframework
Description:
Power Manager has not requested suppression of all input (INPUT_SUPPRESS_REQUEST=0)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Win32k" />
<EventID Qualifiers="32768">701</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-10-01T22:50:31.5277076Z" />
<EventRecordID>5043</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="1840" />
<Channel>System</Channel>
<Computer>serkanframework</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>000000000100000000000000BD020080000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-Kernel-General
Date: 10/1/2022 3:50:31 PM
Event ID: 1
Task Category: (5)
Level: Information
Keywords: Time
User: N/A
Computer: serkanframework
Description:
The system time has changed to 2022-10-01T22:50:31.500000000Z from 2022-10-01T22:25:48.757061000Z.
Time Delta: 1482742 ms
Change Reason: System time synchronized with the hardware clock.
Process: '' (PID 4).
RTC time: 2022-10-01T15:50:31.500000000Z
Current time zone bias: 420
RTC time is in UTC: false
System time was based on RTC time: false
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-General" Guid="{a68ca8b7-004f-d7b6-a698-07e2de0f1f5d}" />
<EventID>1</EventID>
<Version>4</Version>
<Level>4</Level>
<Task>5</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2022-10-01T22:50:31.5002524Z" />
<EventRecordID>5042</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="13260" />
<Channel>System</Channel>
<Computer>serkanframework</Computer>
<Security />
</System>
<EventData>
<Data Name="NewTime">2022-10-01T22:50:31.5000000Z</Data>
<Data Name="OldTime">2022-10-01T22:25:48.7570610Z</Data>
<Data Name="TimeDeltaInMs">1482742</Data>
<Data Name="Reason">2</Data>
<Data Name="ProcessName">
</Data>
<Data Name="ProcessID">4</Data>
<Data Name="CmosTime">2022-10-01T15:50:31.5000000Z</Data>
<Data Name="TimeZoneBias">420</Data>
<Data Name="RealTimeIsUniversal">false</Data>
<Data Name="SystemInCmosMode">false</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 10/1/2022 3:25:48 PM
Event ID: 107
Task Category: (102)
Level: Information
Keywords: (1024),(64),(4)
User: N/A
Computer: serkanframework
Description:
The system has resumed from sleep.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>107</EventID>
<Version>1</Version>
<Level>4</Level>
<Task>102</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000444</Keywords>
<TimeCreated SystemTime="2022-10-01T22:25:48.7523664Z" />
<EventRecordID>5041</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="13260" />
<Channel>System</Channel>
<Computer>serkanframework</Computer>
<Security />
</System>
<EventData>
<Data Name="TargetState">5</Data>
<Data Name="EffectiveState">5</Data>
<Data Name="WakeFromState">5</Data>
<Data Name="ProgrammedWakeTimeAc">1601-01-01T00:00:00.0000000Z</Data>
<Data Name="ProgrammedWakeTimeDc">1601-01-01T00:00:00.0000000Z</Data>
<Data Name="WakeRequesterTypeAc">0</Data>
<Data Name="WakeRequesterTypeDc">0</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 10/1/2022 3:25:47 PM
Event ID: 42
Task Category: (64)
Level: Information
Keywords: (1024),(4)
User: N/A
Computer: serkanframework
Description:
The system is entering sleep.
Sleep Reason: Button or Lid
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>42</EventID>
<Version>3</Version>
<Level>4</Level>
<Task>64</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000404</Keywords>
<TimeCreated SystemTime="2022-10-01T22:25:47.8842305Z" />
<EventRecordID>5040</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="13260" />
<Channel>System</Channel>
<Computer>serkanframework</Computer>
<Security />
</System>
<EventData>
<Data Name="TargetState">5</Data>
<Data Name="EffectiveState">5</Data>
<Data Name="Reason">0</Data>
<Data Name="Flags">0</Data>
<Data Name="TransitionsToOn">27</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-UserModePowerService
Date: 10/1/2022 3:25:45 PM
Event ID: 12
Task Category: (10)
Level: Information
Keywords:
User: SYSTEM
Computer: serkanframework
Description:
Process C:\Windows\System32\WUDFHost.exe (process ID:1380) reset policy scheme from {381b4222-f694-41f0-9685-ff5bb260df2e} to {381b4222-f694-41f0-9685-ff5bb260df2e}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-UserModePowerService" Guid="{ce8dee0b-d539-4000-b0f8-77bed049c590}" />
<EventID>12</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>10</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2022-10-01T22:25:45.9086802Z" />
<EventRecordID>5039</EventRecordID>
<Correlation />
<Execution ProcessID="1096" ThreadID="16388" />
<Channel>System</Channel>
<Computer>serkanframework</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="ProcessPath">C:\Windows\System32\WUDFHost.exe</Data>
<Data Name="ProcessPid">1380</Data>
<Data Name="OldSchemeGuid">{381b4222-f694-41f0-9685-ff5bb260df2e}</Data>
<Data Name="NewSchemeGuid">{381b4222-f694-41f0-9685-ff5bb260df2e}</Data>
</EventData>
</Event>
Log Name: System
Source: Win32k
Date: 10/1/2022 3:25:45 PM
Event ID: 700
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: serkanframework
Description:
Power Manager has requested suppression of all input (INPUT_SUPPRESS_REQUEST=1)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Win32k" />
<EventID Qualifiers="32768">700</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-10-01T22:25:45.8583544Z" />
<EventRecordID>5038</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="5312" />
<Channel>System</Channel>
<Computer>serkanframework</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>000000000100000000000000BC020080000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
Log Name: System
Source: Win32k
Date: 10/1/2022 3:25:45 PM
Event ID: 700
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: serkanframework
Description:
Power Manager has requested suppression of all input (INPUT_SUPPRESS_REQUEST=1)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Win32k" />
<EventID Qualifiers="32768">700</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-10-01T22:25:45.8583544Z" />
<EventRecordID>5037</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="5312" />
<Channel>System</Channel>
<Computer>serkanframework</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>000000000100000000000000BC020080000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 10/1/2022 3:25:45 PM
Event ID: 566
Task Category: (268)
Level: Information
Keywords: (1024),(512),(4)
User: SYSTEM
Computer: serkanframework
Description:
The system session has transitioned from 56 to 57.
Reason WinRT
BootId: 6
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>566</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>268</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000604</Keywords>
<TimeCreated SystemTime="2022-10-01T22:25:45.8359049Z" />
<EventRecordID>5036</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="5312" />
<Channel>System</Channel>
<Computer>serkanframework</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BootId">6</Data>
<Data Name="Reason">25</Data>
<Data Name="PreviousSessionId">56</Data>
<Data Name="PreviousSessionType">0</Data>
<Data Name="PreviousSessionDurationInUs">323007545</Data>
<Data Name="PreviousEnergyCapacityAtStart">28274</Data>
<Data Name="PreviousFullEnergyCapacityAtStart">53992</Data>
<Data Name="PreviousEnergyCapacityAtEnd">27135</Data>
<Data Name="PreviousFullEnergyCapacityAtEnd">53992</Data>
<Data Name="NextSessionId">57</Data>
<Data Name="NextSessionType">3</Data>
<Data Name="PowerStateAc">false</Data>
<Data Name="MonitorReason">25</Data>
</EventData>
</Event>
You may have activated the sleep / suspend by having magnets* near the left edge of the laptop, near the Cap lock and shift keys.
** Magnets …as in from headphones, purse, wallet, another laptop…etc.
2 Likes
Wow you were right, my chromebook sits right next to my laptop and it has a really strong magnet. If I move my framework close to the laptop the framework will shut off. Thank god its not an actual issue then! Thanks
Another one to add to the list. In my case, it was just sitting there idling with the lid closed for nearly a day.
AC plugged in. 80% battery. No event log messages aside for “The previous system shutdown was unexpected.” No BSOD. No dumps. Nothing. System died as if someone powered it off.
12th Gen DYI - 3rd Batch, but I purchased their memory.
Whatever this is hasn’t been fixed. Using a 12th gen i7-1260P. I was on battery around 85% with a little bit of WebGL going and it instantly powered off mid-keystroke with no logs. I was nowhere near max TDP and had minimal disk usage but notably using the GPU.
I’m running Arch with the beta 3.06 BIOS, so this isn’t a windows-only thing. My power settings are tuned for savings, with some cores turned off when not in use, turbo disabled on battery, etc.
Putting my engineer hat on for a second, I’d guess it is a power management problem for the CPU/GPU package in response to big spiky demand changes. I’ve seen other machines, notably desktop GPUs have brownouts and their VRM regulation algorithms needed tweaks in firmware.
Which kernel version are you running and which kernel parameters did you set?
uname -r && cat /proc/cmdline
Nothing exotic:
6.1.7-arch1-1
initrd=\intel-ucode.img initrd=\initramfs-linux.img cryptdevice=<BLAB> root=<BLAB> rw rootfstype=xfs mem_sleep_default=deep resume=<BLAB> resume_offset=<BLAB>
I haven’t been able to replicate the power failure despite trying a bunch of stuff. It did happen from a clean boot, so I’m sure there are no S3 sleep or hibernation effects. I also have hid_sensor_hub blacklisted, and here’s the powertop report on battery showing which power management options are available/enabled/disabled