The laptop doesn't turn off every other time

besstsoft@gmail.com · Yesterday 07:08:11

Hello everyone,

I'm experiencing a random issue where my system refuses to power off completely. During shutdown, the standard systemd text scrolls by, the screen goes black, but the laptop stays powered on (fans keep spinning, LEDs are on). It hangs in this state until I force it off by holding the power button.

The strange part is that it's completely random. It might shut down normally 5-10 times, and then hang on the next attempt.

What makes it even weirder is that this exact same bug is happening on two completely different laptops:

Laptop 1 (Main): Asus X510UF (Intel + NVIDIA), KDE Plasma, Limine bootloader.

Laptop 2: Intel only (Integrated GPU), XFCE, Limine bootloader (default config).

Both are running the latest kernel (7.2.11).

Things I'm considering:

An AI assistant suggested adding nowatchdog to my kernel parameters in Limine.

I also found an old forum thread suggesting tpm_tis.interrupts=0.
Before I start blindly applying these, has anyone else experienced this recently? Could it be a regression in the recent 7.2.x kernels regarding ACPI S5?

Note about the logs:
You might notice some USB/webcam errors (error -71) in my logs. My internal webcam's ribbon cable is damaged, so I disabled it via udev rules and usbcore.quirks in my cmdline. I use an external USB webcam instead, so please ignore the webcam spam.

Below are my kernel parameters and journalctl logs from the Asus laptop for the current boot:

cat /proc/cmdline
root=PARTUUID=4a94c7ce-f378-4b0d-9ed9-1e026506aa3b zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs quiet splash loglevel=3 usbcore.quirks=13d3:5a07:i acpi_osi="Windows 2015" nvidia_drm.modeset=1 nvidia.NVreg_PreserveVideoMemoryAllocations=1 pcie_aspm=off

journalctl -b -p err

Oct 25 10:40:49 archlinux kernel: x86/cpu: SGX disabled or unsupported by BIOS.
Oct 25 10:40:49 archlinux kernel: virt/tdx: TDX not supported by the host platform
Oct 25 10:40:51 AsusX510UF kernel: kvm_amd: CPU 2 isn't AMD or Hygon
Oct 25 10:40:52 AsusX510UF (udev-worker): 1-6:1.0: /etc/udev/rules.d/80-disable-webcam.rules:1 ATTR{authorized}="0"
Oct 25 10:40:52 AsusX510UF (udev-worker): 1-6:1.0: /etc/udev/rules.d/99-disable-internal-webcam.rules:1 ATTR{authorized}="0"
Oct 25 10:40:52 AsusX510UF (udev-worker): 1-6:1.1: /etc/udev/rules.d/80-disable-webcam.rules:1 ATTR{authorized}="0"
Oct 25 10:40:52 AsusX510UF (udev-worker): 1-6:1.1: /etc/udev/rules.d/99-disable-internal-webcam.rules:1 ATTR{authorized}="0"
Oct 25 10:40:52 AsusX510UF kernel: i2c_hid_acpi i2c-ELAN1300:00: device returned incorrect report (2 vs 14 expected)
Oct 25 10:40:52 AsusX510UF kernel: Bluetooth: hci0: Reading supported features failed (-16)
Oct 25 10:40:52 AsusX510UF bootctl[501]: Mount point '/boot' which backs the random seed file is world accessible
Oct 25 10:40:52 AsusX510UF bootctl[501]: Random seed file '/boot/loader/random-seed' is world accessible
Oct 25 10:40:55 AsusX510UF firewalld[550]: ERROR: NAME_CONFLICT: new_policy_object(): 'docker-forwarding'
Oct 25 10:41:04 AsusX510UF plasmalogin-helper[1253]: gkr-pam: unable to locate daemon control file
Oct 25 10:41:07 AsusX510UF bluetoothd[549]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor

journalctl -b -p warning (relevant parts)

Oct 25 10:40:49 archlinux kernel: [Firmware Bug]: TSC ADJUST: CPU0: -220516645 force to 0
Oct 25 10:40:49 archlinux kernel: x86/cpu: SGX disabled or unsupported by BIOS.
Oct 25 10:40:49 archlinux kernel: [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors
Oct 25 10:40:49 archlinux kernel: MDS CPU bug present and SMT on, data leak possible.
Oct 25 10:40:49 archlinux kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible.
Oct 25 10:40:49 archlinux kernel: VMSCAPE: SMT on, STIBP is required for full protection.
Oct 25 10:40:49 archlinux kernel: virt/tdx: TDX not supported by the host platform
Oct 25 10:40:49 archlinux kernel: hpet_acpi_probe: no address or irqs in _CRS
Oct 25 10:40:49 archlinux kernel: usb: port power management may be unreliable
Oct 25 10:40:49 archlinux kernel: i8042: PNP: PS/2 appears to have AUX port disabled
Oct 25 10:40:49 archlinux kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 25 10:40:49 archlinux kernel: nvidia: loading out-of-tree module taints kernel.
Oct 25 10:40:49 archlinux kernel: nvidia: module license 'NVIDIA' taints kernel.
Oct 25 10:40:49 archlinux kernel: Disabling lock debugging due to kernel taint
Oct 25 10:40:50 archlinux kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  580.196.07  Wed Oct  7 19:57:28 UTC 2026
Oct 25 10:40:50 archlinux kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
Oct 25 10:40:50 archlinux kernel: nvidia 0000:01:00.0: [drm] No compatible format found
Oct 25 10:40:51 AsusX510UF kernel: kvm_amd: CPU 2 isn't AMD or Hygon
Oct 25 10:40:52 AsusX510UF kernel: asus_armoury: No matching power limits found for this system
Oct 25 10:40:52 AsusX510UF kernel: faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
Oct 25 10:40:52 AsusX510UF kernel: asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -19
Oct 25 10:40:52 AsusX510UF kernel: asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -19
Oct 25 10:40:52 AsusX510UF kernel: asus_wmi: fan_curve_get_factory_default (0x00110032) failed: -19
Oct 25 10:40:52 AsusX510UF kernel: i2c_hid_acpi i2c-ELAN1300:00: device returned incorrect report (2 vs 14 expected)
Oct 25 10:40:52 AsusX510UF kernel: hid-multitouch 0018:04F3:3057.0004: failed to fetch feature 14
Oct 25 10:40:52 AsusX510UF kernel: Bluetooth: hci0: Reading supported features failed (-16)
Oct 25 10:40:52 AsusX510UF kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
Oct 25 10:40:52 AsusX510UF bootctl[501]: Mount point '/boot' which backs the random seed file is world accessible
Oct 25 10:40:52 AsusX510UF bootctl[501]: Random seed file '/boot/loader/random-seed' is world accessible
Oct 25 10:40:54 AsusX510UF NetworkManager[592]: <warn> device (/net/connman/iwd/0): error setting IPv4 forwarding to '0': No such file or directory
Oct 25 10:40:55 AsusX510UF firewalld[550]: ERROR: NAME_CONFLICT: new_policy_object(): 'docker-forwarding'
Oct 25 10:40:55 AsusX510UF firewalld[550]: WARNING: COMMAND_FAILED: iptables/ip6tables DOCKER-related chains do not exist (cleanup noise)
Oct 25 10:40:57 AsusX510UF wireplumber[1152]: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
Oct 25 10:41:04 AsusX510UF plasmalogin-helper[1253]: gkr-pam: unable to locate daemon control file
Oct 25 10:41:06 AsusX510UF org_kde_powerdevil[1477]: [DDCutilDetector]: Failed to initialize callback
Oct 25 10:41:06 AsusX510UF kded6[1367]: Failed to connect to Bolt manager DBus interface
Oct 25 10:41:06 AsusX510UF dbus-broker-launch[547]: Activation request for 'org.freedesktop.ModemManager1' failed
Oct 25 10:41:06 AsusX510UF kernel: warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
Oct 25 10:41:07 AsusX510UF bluetoothd[549]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor
Oct 25 10:41:07 ... many "Failed to register with host portal" messages from kwin, plasmashell, powerdevil, etc.
Oct 25 10:45:22 AsusX510UF kernel: usb 1-6: can't read configurations, error -71
Oct 25 10:45:24 AsusX510UF kernel: usb 1-6: device descriptor read/64, error -71
Oct 25 10:45:26 AsusX510UF kernel: usb 1-6: device descriptor read/64, error -71

dmesg | grep -i nvidia

[    0.000000] Command line: ... nvidia_drm.modeset=1 nvidia.NVreg_PreserveVideoMemoryAllocations=1 pcie_aspm=off
[    1.801452] nvidia: loading out-of-tree module taints kernel.
[    1.801461] nvidia: module license 'NVIDIA' taints kernel.
[    1.801467] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    1.801468] nvidia: module license taints kernel.
[    2.428242] nvidia-nvlink: Nvlink Core is being initialized, major device number 237
[    2.436966] nvidia 0000:01:00.0: enabling device (0006 -> 0007)
[    2.647836] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  580.196.07  Wed Oct  7 19:57:28 UTC 2026
[    2.672672] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
[    2.681438] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  580.196.07
[    2.879208] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[    3.009724] [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 0
[    3.009747] nvidia 0000:01:00.0: [drm] No compatible format found
[    3.009750] nvidia 0000:01:00.0: [drm] Cannot find any crtc or sizes

dmesg | grep -i pcie

[    0.000000] Command line: ... pcie_aspm=off
[    0.077807] PCIe ASPM is disabled
[    0.258220] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.478563] pci 0000:00:02.0: [8086:5917] type 00 class 0x030000 PCIe Root Complex Integrated Endpoint   (Intel UHD Graphics 620)
[    0.486898] pci 0000:00:1c.0: [8086:9d10] type 01 class 0x060400 PCIe Root Port
[    0.488408] pci 0000:00:1c.5: [8086:9d15] type 01 class 0x060400 PCIe Root Port
[    0.496382] pci 0000:01:00.0: [10de:174d] type 00 class 0x030200 PCIe Endpoint   (NVIDIA GeForce MX130)
[    0.498369] pci 0000:02:00.0: [8086:24fd] type 00 class 0x028000 PCIe Endpoint   (Intel Wireless)

Any advice on how to properly debug this ACPI/shutdown hang would be greatly appreciated!

seth · Yesterday 08:47:03

It hangs in this state until I force it off by holding the power button.

Have you tried to get a cup of coffee instead and see whether the system eventually powers off after maybe 10 minutes?

relevant parts

The relevant part is the tail of "sudo journalctl -b -1" after the poweroff failed (-1 being the most previous boot, you can increase the digit for older ones)

this exact same bug is happening on two completely different laptops … Both are running the latest kernel

Same w/ the LTS kernel?

acpi_osi="Windows 2015" …  pcie_aspm=off

Are those mitigational efforts or pot. causes?

Limine bootloader

You could try to swap that out (maybe try to boot a UKI?)
The bootloader should™ completely hand off and become irrelvant, but it's a common and kinda non-standard factor…

besstsoft@gmail.com · Yesterday 09:16:16

Have you tried to get a cup of coffee instead and see whether the system eventually powers off after maybe 10 minutes?

Yes, I tried that. I waited for about 40 minutes until the battery just died. Also, when this hang occurs, the fans spin up to maximum speed and get very loud, even though they were completely quiet right before that (while the systemd shutdown commands were scrolling on the screen).

The relevant part is the tail of "sudo journalctl -b -1" after the poweroff failed (-1 being the most previous boot, you can increase the digit for older ones)

I will capture and post the journalctl -b -1 -e logs as soon as the issue happens again.

Same w/ the LTS kernel?

I haven't tried the LTS kernel yet. The problem is very intermittent; for example, it didn't happen for about 10 days, and then it suddenly came back.

Are those mitigational efforts or pot. causes?

Regarding acpi_osi="windows 2015" and pcie_aspm=off — these were mitigational efforts. I read on some forums that adding them might fix the issue, so I put them in, but I'm not an expert in this area.

You could try to swap that out (maybe try to boot a UKI?)
The bootloader should™ completely hand off and become irrelvant, but it's a common and kinda non-standard factor…

The Asus laptop used to have GRUB, but it was booting very slowly, which is why I switched to Limine. I can try switching back to GRUB to test, but I struggled a lot with configuring GRUB in the past before finally moving to Limine.

seth · Yesterday 09:18:19

I will capture and post the journalctl -b -1 -e logs as soon as the issue happens again.

Not! "-e" - never apply random filters unless you actually know what you're precisely looking for.

The Asus laptop used to have GRUB

Did it exhibit this problem back then?

besstsoft@gmail.com · Yesterday 10:33:03

1. Understood, I will run `journalctl -b -1` without the `-e` flag and share the relevant tail of the log when the hang happens again.

2. To be honest, I don't remember if this shutdown problem occurred back when I was using GRUB on the Asus laptop. Since the issue is so intermittent, I simply might not have caught it.

However, I did have a different problem back then (GRUB was booting extremely slowly), which is exactly why I switched to Limine. Here is the link to my old thread regarding that GRUB issue, just in case there is any useful context or logs in there for you to check:
My old GRUB slow boot thread

seth · Yesterday 14:14:36

grub loads the kernel and the kernel loads the initramfs, you can https://wiki.archlinux.org/title/Genera … l_messages and https://wiki.archlinux.org/title/GRUB/T … ramebuffer to hopefully get more early messages and see where (and maybe why) things stall.

besstsoft@gmail.com · Yesterday 15:04:41

Thank you, Seth! Since I'm using Limine instead of GRUB, I have applied the kernel message parameters directly to my limine.conf.

I removed `quiet`, `splash`, and `loglevel=3` from my kernel_cmdline, and added `loglevel=7` as suggested in the Wiki link you provided.

Now, when the shutdown hang happens again, my screen shouldn't go black. I will take a picture of the final kernel messages frozen on the screen and share the exact output here.

seth · Yesterday 15:12:20

Now, when the shutdown hang happens again

Removing splash and quiet might help but if the panel turn off you're not gonna see much still.

The links were in response to your grub delays.

besstsoft@gmail.com · Yesterday 21:26:04

seth wrote:

Now, when the shutdown hang happens again
Removing splash and quiet might help but if the panel turn off you're not gonna see much still.
The links were in response to your grub delays.

The hang still happens with the cleaned cmdline.

Current kernel command line:
root=PARTUUID=4a94c7ce-f378-4b0d-9ed9-1e026506aa3b zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs loglevel=7 usbcore.quirks=13d3:5a07:i nvidia_drm.modeset=1 nvidia.NVreg_PreserveVideoMemoryAllocations=1

What happens:
- systemd shutdown messages scroll normally
- screen goes black
- fans spin up to maximum speed and stay loud
- system never powers off
- I waited ~5 minutes, then forced power-off with the power button

Here is the tail of journalctl -b -1 from the failed shutdown:

 
Oct 30 23:07:11 AsusX510UF systemd[1273]: Stopped target plasma-workspace-wayland.target.
Oct 30 23:07:11 AsusX510UF kwin_wayland[1378]: Atomic commit failed: EACCESS
Oct 30 23:07:11 AsusX510UF kwin_wayland[1378]: PipeWire remote error:  connection error
Oct 30 23:07:11 AsusX510UF systemd[1273]: Stopping KDE Wayland Compositor...
Oct 30 23:07:12 AsusX510UF systemd[1273]: Stopped KDE Wayland Compositor.
...
Oct 30 23:07:13 AsusX510UF systemd[1]: Unmounting /boot...
Oct 30 23:07:13 AsusX510UF systemd[1]: Unmounting /home...
Oct 30 23:07:13 AsusX510UF systemd[1]: Unmounting Temporary Directory /tmp...
Oct 30 23:07:13 AsusX510UF systemd[1]: Unmounting /var/cache/pacman/pkg...
Oct 30 23:07:13 AsusX510UF systemd[1]: home.mount: Deactivated successfully.
Oct 30 23:07:13 AsusX510UF systemd[1]: Unmounted /home.
Oct 30 23:07:13 AsusX510UF systemd[1]: tmp.mount: Deactivated successfully.
Oct 30 23:07:13 AsusX510UF systemd[1]: Unmounted Temporary Directory /tmp.
Oct 30 23:07:13 AsusX510UF systemd[1]: var-cache-pacman-pkg.mount: Deactivated successfully.

After this the journal just stops. No further messages.

I can upload the full journalctl -b -1 if needed.

besstsoft@gmail.com · Yesterday 21:38:19

However, when I run:

systemctl poweroff -f

the laptop powers off quickly and reliably (tested 3 times in a row).

This suggests that some service is hanging / not stopping cleanly during the normal shutdown sequence.

Fixxer · Today 07:57:59

According to last sentence - list and find last boot, which after normal "poweroff" system has frozen:

#  journalctl --list-boots

Next check if any errors has occurred before system hangs:

#  journalctl -q -b -NUMBER -p 4

Last edited by Fixxer (Today 08:49:17)

besstsoft@gmail.com · Today 08:06:51

The problem occurs during shutdown. The usual shutdown messages appear on the screen (services stopping, processes terminating, etc.), but eventually the screen goes completely black while the laptop itself remains powered on. The fans and hardware are still running, and the laptop does not shut down completely. I have to hold the power button to force it off.

I can monitor the situation using the LTS kernel, but the problem is difficult to reproduce because it happens randomly. It does not occur every time I shut down the laptop. Based on my observations, it may happen once every 10 shutdowns or even less frequently.

There were no shutdown issues for approximately 14 days, but it happened twice over the last two days.

I have also noticed (although this is only a guess) that the issue might occur more often when many applications are running and the laptop has been in use for a long time. I have not confirmed this yet.

I really like Arch Linux and would like to find the root cause of this problem rather than just work around it.

I installed Arch Linux using archinstall.

I would appreciate any suggestions on how to diagnose this issue, especially considering that it is intermittent and difficult to reproduce.

besstsoft@gmail.com · Today 08:30:55

Fixxer wrote:

According to last sentence - list and find last boot, which after normal "poweroff" has frozen:
#  journalctl --list-boots
Next check if any errors has occurred before systemd hangs:
#  journalctl -q -b -NUMBER -p 4

Thanks for the suggestions. I have collected the journal logs from the shutdown that occurred on October 30 at approximately 23:07.

The affected boot was boot `-5`, which started at 22:06:46 and ended at 23:07:13.

Here are my system details:

$ uname -r
7.2.11-arch1-1

$ pacman -Q linux linux-lts limine limine-mkinitcpio-hook
linux 7.2.11.arch1-1
linux-lts 6.18.59-1
limine 12.9.6-1
limine-mkinitcpio-hook 1.40.0-1

I also checked the kernel command line:

root=PARTUUID=4a94c7ce-f378-4b0d-9ed9-1e026506aa3b zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs loglevel=7 usbcore.quirks=13d3:5a07:i nvidia_drm.modeset=1 nvidia.NVreg_PreserveVideoMemoryAllocations=1

My `/etc/mkinitcpio.conf` contains:

MODULES=(i915 nvidia nvidia_modeset nvidia_uvm nvidia_drm)

I collected the full journal for the affected boot and also checked warnings and errors using `journalctl -p 4`.

A few messages caught my attention during shutdown:

Oct 30 23:07:11 AsusX510UF kwin_wayland[1378]: Atomic commit failed: EACCESS

There are also several systemd transaction errors:

Oct 30 23:07:11 AsusX510UF systemd[1]: Requested transaction contradicts existing jobs: Transaction for systemd-rfkill.socket/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).

Oct 30 23:07:11 AsusX510UF systemd[1]: Requested transaction contradicts existing jobs: Transaction for sound.target/start is destructive (poweroff.target has 'start' job queued, but 'stop' is included in transaction).

Oct 30 23:07:12 AsusX510UF systemd[1]: Requested transaction contradicts existing jobs: Transaction for polkit.service/start is destructive (sysinit.target has 'stop' job queued, but 'start' is included in transaction).

NetworkManager also reports the following:

Oct 30 23:07:12 AsusX510UF dbus-broker-launch[550]: Activation request for 'org.freedesktop.nm_dispatcher' failed.

Oct 30 23:07:12 AsusX510UF NetworkManager[597]: <warn> dispatcher: (17) failed (after 0.007 sec): Could not activate remote peer 'org.freedesktop.nm_dispatcher': activation request failed: unit is invalid

The shutdown process appears to progress quite far. For example:

Oct 30 23:07:12 AsusX510UF systemd[1]: Finished Generate shutdown-ramfs.
Oct 30 23:07:12 AsusX510UF systemd[1273]: Reached target Shutdown.
Oct 30 23:07:12 AsusX510UF systemd[1]: Stopped Network Manager.
Oct 30 23:07:13 AsusX510UF systemd[1]: Stopped Wireless service.
Oct 30 23:07:13 AsusX510UF systemd[1]: Unmounted /home.
Oct 30 23:07:13 AsusX510UF systemd[1]: Unmounted Temporary Directory /tmp.

However, I cannot find a final message indicating that the system successfully powered off.

I am not sure whether the KWin or systemd messages are related to the problem, so I would appreciate any advice on how to interpret these logs.

The issue is intermittent. It does not happen on every shutdown. When it occurs, the screen goes black, but the laptop remains powered on and the fans continue running. I have to hold the power button to turn it off completely.

seth · Today 08:46:38

However, I cannot find a final message indicating that the system successfully powered off.

forced power-off with the power button

See whether https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB works instead (nb. you'll have to explicitly enable this)

issue might occur more often when many applications are running and the laptop has been in use for a long time

Can you make it a habit to log out of plasma and shut down from the DM?
https://bbs.archlinux.org/viewtopic.php?id=315261

I can upload the full journalctl -b -1 if needed.

Might be a good idea to see the complete journal for an affected boot, yes.

besstsoft@gmail.com · Today 11:42:12

Thanks for the suggestions.

I tried the following:

1. `systemctl poweroff -f` — works reliably (tested several times, powers off quickly).
2. Logout from Plasma → shut down from the Display Manager — also works without hanging.
3. Enabled Magic SysRq (`kernel.sysrq = 1`).

The normal shutdown from inside the Plasma session still hangs sometimes (black screen + fans at maximum).

So the issue seems related to how Plasma / the session is being stopped, rather than a complete inability of the system to power off.

I also restored the original kernel command line parameters, since the higher loglevel didn't show anything useful during the hang (screen goes black immediately).

Should I upload the full `journalctl -b -1` from the last hang, or is there something specific I should test next?

Arch Linux

#1 Yesterday 07:08:11

The laptop doesn't turn off every other time

#2 Yesterday 08:47:03

Re: The laptop doesn't turn off every other time

#3 Yesterday 09:16:16

Re: The laptop doesn't turn off every other time

#4 Yesterday 09:18:19

Re: The laptop doesn't turn off every other time

#5 Yesterday 10:33:03

Re: The laptop doesn't turn off every other time

#6 Yesterday 14:14:36

Re: The laptop doesn't turn off every other time

#7 Yesterday 15:04:41

Re: The laptop doesn't turn off every other time

#8 Yesterday 15:12:20

Re: The laptop doesn't turn off every other time

#9 Yesterday 21:26:04

Re: The laptop doesn't turn off every other time

#10 Yesterday 21:38:19

Re: The laptop doesn't turn off every other time

#11 Today 07:57:59

Re: The laptop doesn't turn off every other time

#12 Today 08:06:51

Re: The laptop doesn't turn off every other time

#13 Today 08:30:55

Re: The laptop doesn't turn off every other time

#14 Today 08:46:38

Re: The laptop doesn't turn off every other time

#15 Today 11:42:12

Re: The laptop doesn't turn off every other time

Board footer