You get GPP8 and GPP0 (but also , while I got 8 and 1. Interesting.
I also got 3 USB ones on Windows 10, though I imagine that to be a lost cause.
Very interesting about the audio device. Do you have a 3.5mm expansion card?
I loaded mine exclusively with USB-Cs and USB-As (with the Cs on port 1 and 4, and As on the rest), so I dont have any of that.
Nope.
i use the Q35’s a lot. haven’t used the MB3 for ages. I should probably unpair it.
AMD Drivers:
Version: 32.0.12033.1030
Date: 27/11/2024
(I think this is the December “1” release?)
–
Here’s a GH thread I’ve replied to and have now started following, also: Sleep/Hibernate issue with Windows 11 · Issue #35 · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub
I’m also facing sudden "black screen+reboot"s on my F16 (7940HS, no discrete GPU) under Win11. It started happening after I installed the latest BIOS and drivers kit a few weeks ago. I don’t have anything exotic plugged in (no BT devices, no external monitors, no nothing). It seems to be happening consistently after a random period of time (minutes, up to one hour) following waking up from sleep.
Any help welcome.
I’m getting a similar issue but in Arch Linux, and it is not just on sleeps it will restart randomly while I am actively working.
I am also experiencing this issue, sudden “black screen+reboot”, primarily while gaming. I too have the 7940HS with 64GB of RAM. I have the RX 7700S dGPU installed. This also started after I installed the latest BIOS update. I am now also experiencing intermittent dramatic gaming performance lost since the latest BIOS update.
Can also confirm the dramatic gaming performance lost.
I’ve also uninstalled latest AMD december drivers thingy and re-installed the FRWK16 driver pack.
For example: was playing CIV6 last night on pretty a lower level screen res (on the laptop) while powered. The game confirmed that it was using the 7700S. FPS was in the 30-50. at some point, it displayed a 1fps.
urgh…
@Andrew250
Are you able to reproduce the problem or is it mostly random. I can reproduce the “screen goes blank, followed a short while later (30seconds approx) with a power off” problem about once every month so difficult to find a cause.
So if we can find a way to reproduce the problem more often, we can maybe find the cause.
Edit note: the above might have been a reboot and not power off. I am unsure which.
Can we not just install some low level app which just does the ‘watching and logging’ for us and when crap happens, we have a log file which we can share?
@PureKrome
That is the problem. There are no logs when it happens. Nothing to indicate what went wrong.
No logs in the sense that no extra lines are put in the logs when it happens that give any hint as to why it happens.
Yep - agreed.
So can the FW software dev team create a new low level app which we would have to manually install, which hooks into all these things to help diag the issue? Surely there’s some hooks which this new app could take advantage of?
Mind you - this is low level OS coding, which is pretty niche. But if FW are providing hardware specific drivers etc, then I would hazard a guess that there’s some specialized dev’s in house.
I have to confess, I have a 9-month-old girl at home, so don’t have much time to game these days. The last time I was on the laptop, the gaming performance issue was persistent, I just gave up after a minute or two. The power off issue happened the last time I was on, the time before that, and once more before that. My laptop powers off, PWR light off, immediately. I haven’t been patient enough to see if it reboots or powers back on. I manually turn it back on immediately.
FW16 AMD.
I just saw one of these today (2025-01-21):
Symptoms: Display freezes, pauses for about 20 seconds, then reboots the laptop. Not power off, a reboot.
Similar to just running “sudo reboot” at the command prompt except the command reboots quicker, without the 20 second freeze pause.
EC did not reset. The timestamps on console messages were old, so no recent reboot of the EC. Unfortunately, I did not capture an EC console log this time.
No ectool panicinfo.
What is in each slot:
Slot1: Power
Slot2: NC
Slot3: NC
Slot4: Usb-c - nothing connected
Slot5: NC
Slot6: Usb-A - nothing connected.
Watching youtube at the time using wifi to connect to internet.
Nothing in syslog.
No new crash entries in pstore /var/lib/systemd/pstore/
Linux kernel: 6.12.10
cat /etc/issue
Ubuntu 24.04.1 LTS \n \l
The system had only been powered on for 15 minutes from cold boot, when it happened.
Just done a bit of searching and found this.
It talks about C6 power issues with the 7840HS apu.
I have no idea if there is any truth in it, but just something else to explore.
Hi there Framework staff!
There seems to be quite a few FW16 owners complaining about spurious reboots. On my end, my FW16 is now sitting idle as it is simply not usable for any serious work any more as it went from rock stable to random reboots. Are there engineers actively working on the issue? Were you guys able to reproduce and potentially confirm this was introduced with latest BIOS? Any fix in sight?
Any official communication welcome. Best of luck!
Cheers
Cyril
@Cyril_Comparon
How often can you reproduce the problem?
I only see it once a month.
If you can reproduce it more often, you could help with finding the cause of the problem.
Hey James. I’m facing this issue litterally every time I wake up my laptop to do something. Usually after a few minutes, without any prior warning whatsoever, screen goes black, laptop reboots, all unsaved work lost in the process. Let me know what you have in mind for me to help debugging.
Well it is good that you can reproduce it.
Try some of the settings in that GTR7 link I put in a previous email. See if any of the settings improve it for you. If it helps, try to narrow down which of the many suggestions helped.
Hi,
I found a useful thread here:
Its a different piece of hardware, the Beelink GTR7, but it uses the same 7840-7940 CPUs as the FW16 uses.
Quote from that thread:
“From what I have heard is the original issue was a design hiccup on the motherboard which was causing problems with idle power management as well as issues when a display output over 1080p was used. This wasn’t just a Beelink issue as it also affected other vendors like Minisforum’s early versions as well and was due to an issue in the original reference design from AMD. So, anyone that just used the refence board design from AMD got hit with this and OEM’s like HP and Dell that design their own boards, had no issues with their 7840/7940 systems.”
Maybe FW used the same original reference design from AMD as the Beelink and Minisforum have?
That thread also contains a nice picture of the change to the Beelink mainboard that fixed the problem for them.
Near the 1R0 chip, towards the bottom right of the RAM sockets.
I have emailed FW support with this question. Awaiting a response.
Thanks a bunch @James3 . Be sure to report back here if you’ve got a reply from FW support. I sure am upset to have such an expensive brick at home. What puzzles me though is that my spurious reboot problems seem to have started with the latest BIOS update, which should theoretically rule out hw design flaws…
I got a response from FW support:
“We collaborate closely with AMD to leverage the latest technologies and optimize performance for the Framework 16. However, we are not aware of any issues between Laptop crashes and AMD designs.”
So probably a wild goose chase there.
On my FW16, I have modified its EC code so that I can get a dump of the last 4096 32bit PORT80 codes.
About 3580 codes are used for a reboot, so when I next see a “Freeze then reboot (FTR)”, I can at least capture all the port80 codes.
I have already determined that the EC does not do a reset as a result of the FTR so the 4096 Port80 EC history should be preserved when it happens.
I just have to wait for it to happen now.
My theory now is that, for what I see here, the FTR happens when the laptop is mostly idle, and just playing video. e.g. netflix.
I have not seen the problem happen while doing CPU intensive workloads.
It does not seem to depend on what expansion slot cards are being used.
