PC rebooting/crashing

Support and Help
1

Ubuntu Version:

24.04 LTS

Desktop Environment (if applicable):

GNOME

Problem Description:

Logout popup will appear automatically as if I have done so with the mouse (I hadn’t), I cancel it but keeps showing up after I cancel it but then just shuts down. It then tries to reboot several times but can’t. Keeps trying to reboot but fails. Sometimes seems to be doing it for different reasons.

Relevant System Information:

System Details Report

Report details

  • Date generated: 2025-02-26 21:14:09

Hardware Information:

  • Hardware Model: Micro-Star International Co., Ltd. MS-7C52
  • Memory: 16.0 GiB
  • Processor: AMD Ryzen™ 5 5500 × 12
  • Graphics: AMD Radeon™ RX 580 Series
  • Disk Capacity: 1.0 TB

Software Information:

  • Firmware Version: A.42
  • OS Name: Ubuntu 24.04.2 LTS
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 46
  • Windowing System: Wayland
  • Kernel Version: Linux 6.11.0-17-generic

Screenshots or Error Messages:

1st example after log out popup appears:

Feb 26 17:12:26 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:26 dad-MS-7C52 dbus-daemon[980]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.74' (uid=1000 pid=2>
Feb 26 17:12:26 dad-MS-7C52 systemd[1]: Starting packagekit.service - PackageKit Daemon...
Feb 26 17:12:26 dad-MS-7C52 PackageKit[19319]: daemon start
Feb 26 17:12:26 dad-MS-7C52 dbus-daemon[980]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 26 17:12:26 dad-MS-7C52 systemd[1]: Started packagekit.service - PackageKit Daemon.
Feb 26 17:12:26 dad-MS-7C52 gnome-shell[2681]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 17:12:26 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:26 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:27 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:27 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:28 dad-MS-7C52 gnome-session-binary[2646]: Entering running state
Feb 26 17:12:28 dad-MS-7C52 at-spi2-registr[2825]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 17:12:28 dad-MS-7C52 at-spi2-registr[2825]: Unable to register client with session manager
Feb 26 17:12:30 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:30 dad-MS-7C52 gnome-shell[2681]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 17:12:30 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:30 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:33 dad-MS-7C52 gnome-session-binary[2646]: Entering running state
Feb 26 17:12:33 dad-MS-7C52 at-spi2-registr[2825]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 17:12:33 dad-MS-7C52 at-spi2-registr[2825]: Unable to register client with session manager
Feb 26 17:12:35 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:35 dad-MS-7C52 gnome-shell[2681]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 17:12:35 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:35 dad-MS-7C52 gnome-session-binary[2646]: Entering running state
Feb 26 17:12:35 dad-MS-7C52 at-spi2-registr[2825]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 17:12:35 dad-MS-7C52 at-spi2-registr[2825]: Unable to register client with session manager
Feb 26 17:12:37 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:37 dad-MS-7C52 gnome-shell[2681]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 17:12:37 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:38 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:39 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:39 dad-MS-7C52 gnome-session-binary[2646]: Entering running state
Feb 26 17:12:39 dad-MS-7C52 at-spi2-registr[2825]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 17:12:39 dad-MS-7C52 at-spi2-registr[2825]: Unable to register client with session manager
Feb 26 17:12:42 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:42 dad-MS-7C52 gnome-shell[2681]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 17:12:43 dad-MS-7C52 gnome-session-binary[2646]: Entering running state
Feb 26 17:12:43 dad-MS-7C52 at-spi2-registr[2825]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 17:12:43 dad-MS-7C52 at-spi2-registr[2825]: Unable to register client with session manager
Feb 26 17:12:44 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:44 dad-MS-7C52 gnome-shell[2681]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 17:12:45 dad-MS-7C52 gnome-session-binary[2646]: Entering running state
Feb 26 17:12:45 dad-MS-7C52 at-spi2-registr[2825]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 17:12:46 dad-MS-7C52 systemd[2402]: Started app-gnome-org.gnome.Terminal-19351.scope - Application launched by gnome-shell.
Feb 26 17:12:46 dad-MS-7C52 dbus-daemon[2442]: [session uid=1000 pid=2442] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by >
Feb 26 17:12:46 dad-MS-7C52 systemd[2402]: Starting gnome-terminal-server.service - GNOME Terminal Server...
Feb 26 17:12:46 dad-MS-7C52 dbus-daemon[2442]: [session uid=1000 pid=2442] Successfully activated service 'org.gnome.Terminal'
Feb 26 17:12:46 dad-MS-7C52 systemd[2402]: Started gnome-terminal-server.service - GNOME Terminal Server.
Feb 26 17:12:46 dad-MS-7C52 gnome-shell[2681]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Feb 26 17:12:46 dad-MS-7C52 systemd[2402]: Started vte-spawn-d0d245ae-3ed2-441b-9978-2ade83f158f2.scope - VTE child process 19369 launched by gnome-terminal-server process 19361.
Feb 26 17:12:46 dad-MS-7C52 systemd[2402]: app-gnome-yelp-18991.scope: Consumed 18.485s CPU time.
Feb 26 17:12:47 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:47 dad-MS-7C52 gnome-shell[2681]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 17:12:48 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:48 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:48 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:49 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:49 dad-MS-7C52 gnome-session-binary[2646]: Entering running state
Feb 26 17:12:49 dad-MS-7C52 at-spi2-registr[2825]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 17:12:49 dad-MS-7C52 at-spi2-registr[2825]: Unable to register client with session manager
Feb 26 17:12:52 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:52 dad-MS-7C52 gnome-shell[2681]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 17:12:53 dad-MS-7C52 gnome-session-binary[2646]: Entering running state
Feb 26 17:12:53 dad-MS-7C52 at-spi2-registr[2825]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 17:12:53 dad-MS-7C52 at-spi2-registr[2825]: Unable to register client with session manager
Feb 26 17:12:53 dad-MS-7C52 systemd-logind[1010]: Power key pressed short.
Feb 26 17:12:53 dad-MS-7C52 gnome-shell[2681]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 17:12:54 dad-MS-7C52 gnome-session-binary[2646]: Entering running state
Feb 26 17:12:54 dad-MS-7C52 at-spi2-registr[2825]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 17:12:54 dad-MS-7C52 at-spi2-registr[2825]: Unable to register client with session manager

2nd example where there were no popups, it just suddenly shutdown.

RX 580 - no popups, just shutdown while using steam (not gaming, downloading)

- **Firmware Version:**                            A.20
- **OS Name:**                                     Ubuntu 24.04.2 LTS
- **OS Build:**                                    (null)
- **OS Type:**                                     64-bit
- **GNOME Version:**                               46
- **Windowing System:**                            X11
- **Kernel Version:**                              Linux 6.11.0-17-generic

$ journalctl -S "20:23:00" -U "20:26:00"
Feb 26 20:23:06 dad-MS-7C52 systemd[2412]: Started app-gnome-org.gnome.SystemMonitor-7682.scope - Application launched by gnome-shell.
Feb 26 20:23:06 dad-MS-7C52 org.gnome.SystemMonitor.desktop[7682]: glibtop(c=7682): [WARNING] statvfs '/run/user/1000/doc' failed: Operation not permitted
Feb 26 20:23:06 dad-MS-7C52 gnome-shell[2685]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Feb 26 20:23:29 dad-MS-7C52 systemd[2412]: app-gnome-org.gnome.SystemMonitor-7682.scope: Consumed 1.340s CPU time.
Feb 26 20:23:47 dad-MS-7C52 gnome-shell[2685]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Feb 26 20:23:48 dad-MS-7C52 systemd[2412]: app-gnome-org.gnome.TextEditor-6196.scope: Consumed 10.570s CPU time.
Feb 26 20:23:48 dad-MS-7C52 gnome-shell[2685]: JS ERROR: TypeError: this.actor is null
                                               _syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:145:25
                                               onStopped@resource:///org/gnome/shell/ui/windowManager.js:157:35
                                               _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                               _easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:247:60
                                               _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1607:21
                                               onStopped@resource:///org/gnome/shell/ui/windowManager.js:1575:39
                                               _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                               _easeActor/<@resource:///org/gnome/shell/ui/environment.js:160:64
                                               @resource:///org/gnome/shell/ui/init.js:21:20
Feb 26 20:23:51 dad-MS-7C52 systemd[2412]: Started app-gnome-yelp-7900.scope - Application launched by gnome-shell.
Feb 26 20:23:51 dad-MS-7C52 gnome-shell[2685]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Feb 26 20:23:51 dad-MS-7C52 rtkit-daemon[1762]: Supervising 10 threads of 7 processes of 1 users.
Feb 26 20:23:51 dad-MS-7C52 rtkit-daemon[1762]: Failed to look up client: No such file or directory
Feb 26 20:23:51 dad-MS-7C52 rtkit-daemon[1762]: Supervising 10 threads of 7 processes of 1 users.
Feb 26 20:23:51 dad-MS-7C52 rtkit-daemon[1762]: Successfully made thread 7961 of process 7942 owned by '1000' RT at priority 5.
Feb 26 20:23:51 dad-MS-7C52 rtkit-daemon[1762]: Supervising 11 threads of 8 processes of 1 users.
Feb 26 20:23:51 dad-MS-7C52 rtkit-daemon[1762]: Supervising 11 threads of 8 processes of 1 users.
Feb 26 20:23:51 dad-MS-7C52 rtkit-daemon[1762]: Successfully made thread 7983 of process 7942 owned by '1000' RT at priority 5.
Feb 26 20:23:51 dad-MS-7C52 rtkit-daemon[1762]: Supervising 12 threads of 8 processes of 1 users.
Feb 26 20:24:10 dad-MS-7C52 systemd[2412]: app-gnome-yelp-7900.scope: Consumed 4.186s CPU time.
Feb 26 20:24:50 dad-MS-7C52 systemd[2412]: snap.firefox.firefox-9a160c40-04a2-4ae6-becd-2017ef1d996f.scope: Consumed 1min 15.111s CPU time.

Actions:

  • put GT 740 in, booted ok

  • updated BIOS to A42, successful

  • reinstalled RX 580, booted ok

3rd crash:

Feb 26 21:18:02 dad-MS-7C52 systemd[2399]: app-gnome-software\x2dproperties\x2dgtk-7199.scope: Consumed 3.716s CPU time.
Feb 26 21:18:08 dad-MS-7C52 systemd[2399]: Started app-gnome-org.gnome.Terminal-7552.scope - Application launched by gnome-shell.
Feb 26 21:18:09 dad-MS-7C52 dbus-daemon[2437]: [session uid=1000 pid=2437] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by >
Feb 26 21:18:09 dad-MS-7C52 systemd[2399]: Created slice app-org.gnome.Terminal.slice - Slice /app/org.gnome.Terminal.
Feb 26 21:18:09 dad-MS-7C52 systemd[2399]: Starting gnome-terminal-server.service - GNOME Terminal Server...
Feb 26 21:18:09 dad-MS-7C52 dbus-daemon[2437]: [session uid=1000 pid=2437] Successfully activated service 'org.gnome.Terminal'
Feb 26 21:18:09 dad-MS-7C52 systemd[2399]: Started gnome-terminal-server.service - GNOME Terminal Server.
Feb 26 21:18:09 dad-MS-7C52 gnome-shell[2684]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Feb 26 21:18:09 dad-MS-7C52 systemd[2399]: Started vte-spawn-266e6902-d9a4-4cba-9b0d-a5a8cb84308b.scope - VTE child process 7569 launched by gnome-terminal-server process 7562.
Feb 26 21:18:35 dad-MS-7C52 systemd-logind[1008]: Power key pressed short.
Feb 26 21:18:35 dad-MS-7C52 gnome-shell[2684]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 21:18:36 dad-MS-7C52 systemd-logind[1008]: Power key pressed short.
Feb 26 21:18:37 dad-MS-7C52 gnome-session-binary[2653]: Entering running state
Feb 26 21:18:37 dad-MS-7C52 at-spi2-registr[2832]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 21:18:37 dad-MS-7C52 at-spi2-registr[2832]: Unable to register client with session manager
Feb 26 21:18:37 dad-MS-7C52 systemd-logind[1008]: Power key pressed short.
Feb 26 21:18:37 dad-MS-7C52 gnome-shell[2684]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 21:18:38 dad-MS-7C52 gnome-session-binary[2653]: Entering running state
Feb 26 21:18:38 dad-MS-7C52 at-spi2-registr[2832]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 21:18:38 dad-MS-7C52 at-spi2-registr[2832]: Unable to register client with session manager
Feb 26 21:19:34 dad-MS-7C52 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP0.VGA], AE_ALREADY_EXISTS (20240322/dswload2-326)
Feb 26 21:19:34 dad-MS-7C52 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240322/psobject-220)
Feb 26 21:19:34 dad-MS-7C52 kernel: ACPI: Skipping parse of AML opcode: Device (0x5B82)
Feb 26 21:19:34 dad-MS-7C52 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP0.HDAU], AE_ALREADY_EXISTS (20240322/dswload2-326)
Feb 26 21:19:34 dad-MS-7C52 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240322/psobject-220)
Feb 26 21:19:34 dad-MS-7C52 kernel: ACPI: Skipping parse of AML opcode: Device (0x5B82)

And then a 4th time:

Feb 26 21:22:49 dad-MS-7C52 at-spi2-registr[2857]: Unable to register client with session manager
Feb 26 21:22:49 dad-MS-7C52 at-spi2-registr[2857]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 21:22:49 dad-MS-7C52 gnome-session-binary[2664]: Entering running state
Feb 26 21:22:48 dad-MS-7C52 systemd-logind[1033]: Power key pressed short.
Feb 26 21:22:48 dad-MS-7C52 gnome-shell[2698]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 21:22:48 dad-MS-7C52 systemd-logind[1033]: Power key pressed short.
Feb 26 21:22:43 dad-MS-7C52 at-spi2-registr[2857]: Unable to register client with session manager
Feb 26 21:22:43 dad-MS-7C52 at-spi2-registr[2857]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 21:22:43 dad-MS-7C52 gnome-session-binary[2664]: Entering running state
Feb 26 21:22:43 dad-MS-7C52 systemd-logind[1033]: Power key pressed short.
Feb 26 21:22:43 dad-MS-7C52 gnome-shell[2698]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 21:22:43 dad-MS-7C52 systemd-logind[1033]: Power key pressed short.
Feb 26 21:22:41 dad-MS-7C52 at-spi2-registr[2857]: Unable to register client with session manager
Feb 26 21:22:41 dad-MS-7C52 at-spi2-registr[2857]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 21:22:41 dad-MS-7C52 gnome-session-binary[2664]: Entering running state
Feb 26 21:22:40 dad-MS-7C52 gnome-shell[2698]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 21:22:40 dad-MS-7C52 systemd-logind[1033]: Power key pressed short.
Feb 26 21:22:38 dad-MS-7C52 at-spi2-registr[2857]: Unable to register client with session manager
Feb 26 21:22:38 dad-MS-7C52 at-spi2-registr[2857]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 21:22:38 dad-MS-7C52 gnome-session-binary[2664]: Entering running state
Feb 26 21:22:37 dad-MS-7C52 gnome-shell[2698]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 21:22:37 dad-MS-7C52 systemd-logind[1033]: Power key pressed short.
Feb 26 21:22:27 dad-MS-7C52 at-spi2-registr[2857]: Unable to register client with session manager
Feb 26 21:22:27 dad-MS-7C52 at-spi2-registr[2857]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Feb 26 21:22:27 dad-MS-7C52 gnome-session-binary[2664]: Entering running state
Feb 26 21:22:25 dad-MS-7C52 gnome-shell[2698]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Feb 26 21:22:25 dad-MS-7C52 systemd-logind[1033]: Power key pressed short.
Feb 26 21:21:50 dad-MS-7C52 systemd[2415]: Started app-gnome-org.gnome.DejaDup.Monitor-4887.scope - Application launched by gnome-session-binary.
Feb 26 21:21:46 dad-MS-7C52 rtkit-daemon[1755]: Supervising 10 threads of 7 processes of 1 users.
Feb 26 21:21:46 dad-MS-7C52 rtkit-daemon[1755]: Successfully made thread 4881 of process 4630 owned by '1000' RT at priority 10.
Feb 26 21:21:46 dad-MS-7C52 rtkit-daemon[1755]: Supervising 9 threads of 6 processes of 1 users.
Feb 26 21:21:46 dad-MS-7C52 rtkit-daemon[1755]: Supervising 9 threads of 6 processes of 1 users.
Feb 26 21:21:39 dad-MS-7C52 systemd[1]: systemd-timedated.service: Deactivated successfully.
Feb 26 21:21:14 dad-MS-7C52 rtkit-daemon[1755]: Supervising 9 threads of 6 processes of 1 users.
Feb 26 21:21:14 dad-MS-7C52 rtkit-daemon[1755]: Supervising 9 threads of 6 processes of 1 users.
Feb 26 21:21:12 dad-MS-7C52 rtkit-daemon[1755]: Supervising 9 threads of 6 processes of 1 users.

What I’ve Tried:

It is a new system (everything new except Graphics cards and case), built by me.

Tried (and continue to get issues) with:

Xubuntu 24.04 (X11)
Manjaro 24 XFCE (X11)
Ubuntu 24.04 (Gnome Wayland) w/ RX 580
Ubuntu 24.04 (Gnome X11) w/ GT 740

2 graphics cards (separately)

  • NVIDIA GT 740 2GB
  • AMD RX 580 8GB

2 different sets of RAM (both new)

  • Corsair Vengeance 2x16GB
  • Team 2x8GB

2 different CMOS batteries (1 the mobo came with and a new one)

Tried default BIOS and updated BIOS but issue persists.

Sorry for the long post, just trying to give as much detail as possible. This has been a really frustrating issue for the past couple of weeks and I have no idea what I’m looking at when it comes to logs. I have searched all over the internet and every time I think I have narrowed it down it happens again. Any help would be appreciated.

Thanks

1 Like
2

Have you checked your wiring? It looks like the system is doing what it is supposed to do when the power button is pressed, you should check where that button-press-event comes from, this looks more like a physical problem than anything with software (especially since you seem to see it with different distros).

4 Likes
3

Yeah I was starting to wonder if it might be a physical issue with the power switch. 10 yr old case and power switch sometimes gets stuck when pushed in. But I’ll have a closer look at the wiring, I just found it strange that on another occasion it would just crash. Thanks.

1 Like
4

Just thought I would post an update before the topic closes if anyone else is searching this issue. I found a forum where some industrial IT types were discussing this issue affecting one of their servers, and I will list their recommended checks but the TLDR version is …drum roll please…the front I/O panel had a short in it.

What they recommended to isolate the problem was:

  1. check and recheck all connections to the mobo and make sure they are properly seated.
    1a. if dust is an issue disconnect all components and clean the mobo (only do this if you now what you are doing - my mobo was brand new so not an issue)
  2. remove front I/O panel connectors and start the mobo with a screwdriver (plenty of videos on youtube about this) to see if it is still misbehaving (sending computer to suspend or restart while testing for a couple of days instead of shutting down)
  3. the above at point 2 worked well for me - no issues.
  4. reconnect the power switch only - issue returned for me
  5. remove power switch and reconnect other front I/O panel connectors (eg front USB, audio) - issue returned - therefore a front I/O panel short
  6. they recommended cleaning the front I/O board and switches with electrical contact cleaner (NB: not with lubricant) and I just so happened to have a can that I use on my electric guitar components (purchased from any good electronics or auto-electrical store eg Jaycar here in Australia, Radioshack in the US), but alas the issue was still there.
  7. purchased new AUD$5 power switch from eBay - works like a charm, issue gone after 2 days of testing

So hopefully that may help anyone with a similar issue in the future. I may purchase one of those fancy external power switches with usb hub. :smiley:

1 Like
5

This topic was automatically closed after 30 days. New replies are no longer allowed.