Framework 16 Randomly Shuts Off

It happened to me again - again while playing OW2 (but then again, I use this for mostly gaming, so I am worried if it ever happens in a middle of something more important like work or in a middle of a video editing session).

The only thing I can think of is the firmware version? This didn’t start happening prior to 3.05 (was on 3.03 before).

I do have the 7700S if that makes a difference. No warning, just all of a sudden everything just turns off (screen goes off, power light goes off - almost like a desktop getting the power plug pulled).

So far it hasn’t happened to me in Fedora, just in Windows. May or may not mean anything. Just putting this into the experience pile so we can get more data points to troubleshoot.

Here’s what I found in Event Viewer:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

No other errors. So Windows didn’t experience any errors that would cause it to shut it down. Apparently, it didn’t even know the power was going to cut to log anything - it was only booting back up the next time before it logged something about being unexpected power loss.

IMO, it’s random and not predictable. If it was, I would train a camera to capture it happening.

Experiencing random shutdown now since I’ve updated the BIOS to 3.05 from 3.03. I checked my event logs and the only critical log was the “Event 41, Kernel-Power”. While the power to the battery is still at around 80% and laptop is connected to power.

This occurred while playing Marvel Rivals with external monitor connected to the dGPU. I didn’t experience this problem prior to the bios update to 3.05.

CPU: Ryzen 7 7840HS
GPU: AMD RX 7700S
OS: Windows 11

I experienced the shut off problem too last night.

Loaded the new bios version 3.05 one week ago and had my first random power off last night while starting up Helldiver2. Could there be something going on with the power ramp when it has to hand over to the separate graphics card?
First time this has happened since I’ve had the laptop in July 2024.

Can confirm this is also happening to me when doing GPU-heavy workloads in Davinci Resolve. May need to regress to bios 3.03 (which sucks because of the disconnecting usb problem).

CPU: Ryzen 7 7840HS
GPU: AMD RX 7700S
OS: Windows 11

Has happened to me more than once.

FW16 with 7840/7700s. Laptop is plugged in to the back right USB port. Battery is set to sit at 60% and not charge more. Kubuntu 24.04.

2x USB-C ports. 1x HDMI, 1x Ethernet, 1x SD, 1x USB-A. The USB-C powering the laptop is the back one on the right, closest to the screen.

Laptop will just shut down instantly. Has been several times on initially trying to load a game and once when in game but an obvious memory leak was slowly killing performance in that case, but same behavior. I am running a second screen using a USB-C out port.

Laptop requires restarting by using the power button. The issue is most likely not an overheating as it doesn’t make any sense. I’d be hard pressed to even suspect heating as the culprit. Highly likely it’s a power issue.

Using the “official” power supply offered during checkout. If it was a desktop and doing this the first thing I would change is the power supply. It’s either drawing too much and protecting itself of not being supplied enough and failing.

Some additional details for what I see on FW16 AMD:
USB-C in slot 1, nothing plugged into it.
Ethernet in slot 4, passing traffic sometimes, wifi being used otherwise (unsure which I was using at the time of the “pause, shutdown”
USB-C in slot 5, with FW 180W PSU plugged in.
USB-A in slot 6, with headphones plugged in.
FW16 with 7840HS and No dGPU, No 7700,
Had the laptop been through any suspend cycles beforehand…For me, not known.

My FW16 shut itself off also.
No messages in the syslog.
Ectool panicinfo was empty.
Ectool console did not show a EC power cycle.
No MCE info.
No pstore info.
Symptoms:

  1. Screen goes blank or freezes.
  2. Wait about 30 seconds.
  3. Fw16 powers itself off.
    On reboot there is no evidence in any of the logs as to what went wrong.
    It only happens occasionally, say once a month. Every time it has been while watching a video.
    Os: Ubuntu 24.04 with 6.12.3 mainline kernel

So, if anyone is able to reproduce this more often, and notices any sort of pattern/cause it would help.

There might be two different problems people are seeing:

  1. Screen blanks for 30 seconds, powers off itself.
  2. Powers off immediately, no screen blank pause before hand.
    I was seeing (1).

I am planning to write some modifications to the EC firmware so that it leaves some trace of why it powered off, that should allow the “ectool” to then retrieve the power off reason with a new command.
For the ectool to be useful, the laptop needs to be attached to a power supply at the time because if attached to a power supply, the EC keeps itself powered on, even if the laptop powers itself off. Fortunately, I think everyone so far, if they give enough details, has said the laptop was attached to a PSU at the time.
Another thing to maybe add could be the EC keeps track of how many times it has power cycled, suspended since the last EC reset. This would let us know if the EC also reset itself when the problem occured. Note. If the EC resets itself, the whole laptop powers off.
This might be something that could help diagnose the EC resets.
Before the problem, if people could do a “ectool console” and note down the timestamp at the beginning of the line. Call it timestamp A.
After the “random shut off”, do an “ectool console” and note down the timestamp at the beginning of the line. Call it timestamp B.
If B < A the EC reset itself.
If B > A the EC did not reset itself when the laptop “random shut off”.

One can test this (EC not resetting).

  1. Have PSU connected.
  2. Use ectool to note down timestamp A.
  3. Select Power off and power off the laptop the normal way (from start menu etc.)
  4. Power on the laptop.
  5. Use ectool to note down timestamp B.
  6. Expected result: B > A.

One can test this (EC resetting).

  1. Have PSU connected.
  2. Use ectool to note down timestamp A.
  3. Select Power off and power off the laptop the normal way (from start menu etc.)
  4. Remove the PSU.
  5. Wait more than 40 seconds. (This should reset the timestamp to zero as the EC resets itself)
  6. Plug PSU back in.
  7. Power on the laptop.
  8. Use ectool to note down timestamp B.
  9. Expected result: B < A.

Have had the same problem twice since the latest BIOS upgrade

No freezing, just instant shutdown

My BIOS 60% charge limit also seems to be experiencing problems around when the computer crashes, reaching levels of ~80% around the crash, though it hasn’t happened often to be certain the two always coincide

@Kieran_Levin any feedback from Framework about this issue ? Did you or your team experienced this kind of sudden shutdown yet ?
Can we (the community) help in any way to help you iron out the issue ?

1 Like

Still trying to find a way to replicate this issue but I’ve noticed another issue. The power supply seems insufficient to power the FW16 would be my initial thought, but that it seems like a new issue that hasn’t always been there I am at a bit of a loss to speculate on.

Running a High Power mode and with a game running, my meter says the FW16 180W power supply is drawing 177.4W from the wall. That value remains consistent over a period of time(30 mins+).

I have my battery set to maintain 60% charge capacity. After about 30 mins of being in game, my battery has dropped to 53%. There is no reason it should be losing charge that fast unless something is drawing current from it. I have not ran a game long enough for the battery to hit 0% so the crash is not from that, and has happened shortly after powering on the laptop so the battery would have been at its charge limit. When I do not have any game running and am just at a desktop the battery never appears to be losing capacity so I am unsure if it is being used and recharged fast enough to not notice or if it is not being asked to provide any power during those moments.

The exact inner workings of whether the battery can supplement the wall power is an option or not is beyond my electrical knowledge. None of my crashes have happened at a time when the battery would have reached 0% so it is not a direct relationship but possibly linked.

I’m currently of the mind that if this issue was not happening before the latest bios (I upgraded to latest bios during initial setup), then it appears that there may have been some power usage changes in it that had a second tier effect to the power delivery.

As I am not remotely an electrical engineer or know the inner workings of power delivery I think it’s out of my ability to further isolate without some direction from FW on a test method to replicate the issue.

I’m also having a similar issue, specifically under GPU-heavy workloads. The system just dies at random, the screen going black but audio continuing to play, while completely unresponsive to any form of input. Prolonged waiting and aggressive key mashing can lead to the screen turning back on, but not much else.

This is really annoying, I can’t use this laptop to its fullest like this. I don’t know what’s up either, but I’ve had to do a lot of support interaction with this laptop before. I don’t know what’s going on, but at this point I’m frankly shy to ask support for help, I’ve bugged the crap out of them with other issues prior.

You are definitely on to something with the correlation to the power level exceeding the setting in the BIOS. My FW16 has now shut down suddenly 3 times (mostly when playing CyberPunk 2077). In all of those cases, I review the battery levels in the history and preceding the crash the charge level went significantly above the set level (60% in my case)

1 Like

Any fix for the random shutdown? does support even read the forum?

Hi,

I think we have 2 different faults reported here.

  1. an instant power off. Needing power button to switch on.
  2. a system pause/blank screen, for about 20 seconds, then a reboot.
    In both cases, no logs or crash dumps to help diagnose the problem.
  3. the screen goes blank, but does not power off and does not reboot.

Both are difficult to reproduce.
I see (2) about once a month.
If people are seeing (3), that is just a gpu driver bug, so gather crash traces and report to amd.

1 Like

No. There are a couple of Framework employees that occasionally read the forum, but not to refer things to support. If you need help from support then you need to put in a support request, these forums are not a route to them.

1 Like

Ok fair enough. Then i guess the forum is more for users to help each other.
Have you filed support ticket? is the support good in your view?
I’m waiting to for a update to the cpus and really considering to buy their laptop so doing some early research to see the level of support. This is a new brand for me.

I am not using an officially supported Linux distribution so I don’t know if I should create a ticket. Even though it looks like people are getting this issue regardless of OS.

Also just noticed all the charging and discharging of a battery that should not be getting used and only just holding 60% has dropped to 90% total capacity in just over a month already.

Something significant is wrong in the power system on this thing.

Same problem. Framework 16, occasionally shut itself off during GPU-related activities. Easiest way to replicate is to play minecraft with shaders, getting shutoff in like 5-10 minutes. “Best” part here is that there is no evidence in journalctl or any other logs i tried to check. This is 100% GPU related, but i don’t know how to debug it deeper

Places to look for stack traces:
a) the Linux kernel logs in /var/log
b) journalctl -b -1
c) /var/lib/systemd/pstore

Not many people know about the pstore (c) one.

1 Like