# FRWK16 - Random Crash then Reboots **URL:** \ **Category:** Community Support\ **Tags:** framework-laptop-16-amd-7040\ **Created:** [December 28, 2024, 3:07am UTC](https://community.frame.work/t/frwk16-random-crash-then-reboots/62411 "2024-12-28T03:07:55Z")\ **Posts on this page:** 1\ **Showing post:** 79
**Author:** ![Will\_Nilges](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/will_nilges/32/23820_2.png) [@Will\_Nilges](https://community.frame.work/u/Will_Nilges)\ **Post date:** [April 29, 2025, 7:17pm UTC](https://community.frame.work/t/frwk16-random-crash-then-reboots/62411/79 "2025-04-29T19:17:16Z")
Fair point, my mistake. That is why I encourage everyone to open tickets. That said, I would think that for seemingly widespread issues like this one, a mega thread that Framework actively watches would be beneficial. An example of this is the battery flipping thread. > [@\[TRACKING\] Battery flipping between charging and discharging / Draws from battery even on AC](https://community.frame.work/t/tracking-battery-flipping-between-charging-and-discharging-draws-from-battery-even-on-ac/22484): > > With AC connected and battery charge at the set threshold, the battery status as reported by the kernel often flips between charging and discharging, sometimes even within one or two seconds. (This can be seen using the Gnome battery icon or upower -d). AC is always reported as online. This also means I get a constant stream of udev events starting tlp, which then notices that AC is still online and does nothing, but this could probably be solved by tweaking udev rules. Some more observations: … --- _[View the full topic](https://community.frame.work/t/frwk16-random-crash-then-reboots/62411)._