Laptop completely shutting down during heavy cpu loads

Hero478 · Yesterday 23:57:33

I've first discovered this tonight while watching a 4k movie, and the laptop shut down 4 times during it. Not immediately, but after around 10-15 mins of heavy work.
I've tried limiting the power consumption of my dGPU to 35 W, disabling the dGPU entirely and relying only on the iGPU but nothing worked. I examined journalctl right after turning the laptop on again but there was literally nothing. The logs cut off suddenly. I've also tried running a 15 mins stress test with stress-ng and it also shut down. My guess is that there's some issue with power delivery at a firmware level, but it would be great to have an opinion from someone who knows more than i do.

Useful things:

sudo dmidecode -s system-product-name             # command
Vivobook_ASUSLaptop K3605ZC_K3605ZC             # output

journalctl -b -1 -n 50 --no-pager:

Sep 19 01:40:25 arch warp-svc[674]: 2026-09-18T23:40:25.009Z DEBUG route-change: Routes changed:
Sep 19 01:40:25 arch warp-svc[674]: DelNeighbour;
Sep 19 01:40:31 arch warp-svc[674]: 2026-09-18T23:40:31.601Z DEBUG route-change: Routes changed:
Sep 19 01:40:31 arch warp-svc[674]: NewNeighbour; Destination: 192.168.1.19;
Sep 19 01:40:41 arch warp-svc[674]: 2026-09-18T23:40:41.852Z DEBUG upload_stats{context="timer"}: actor_statistics::handler: Starting to upload stats
Sep 19 01:40:41 arch warp-svc[674]: 2026-09-18T23:40:41.852Z  WARN upload_stats{context="timer"}: actor_statistics::handler: Skipped uploading aggregate stats because registration was none!
Sep 19 01:40:41 arch warp-svc[674]: 2026-09-18T23:40:41.852Z  INFO upload_stats{context="timer"}: actor_statistics::handler: close time.busy=127µs time.idle=33.2µs
Sep 19 01:40:41 arch warp-svc[674]: 2026-09-18T23:40:41.880Z DEBUG actor_connectivity::connectivity: Routes changed: 3 in the last 30 seconds
Sep 19 01:40:54 arch warp-svc[674]: 2026-09-18T23:40:54.705Z DEBUG route-change: Routes changed:
Sep 19 01:40:54 arch warp-svc[674]: NewNeighbour; Destination: 192.168.1.19;
Sep 19 01:40:54 arch warp-svc[674]: 2026-09-18T23:40:54.711Z DEBUG route-change: Routes changed:
Sep 19 01:40:54 arch warp-svc[674]: NewNeighbour; Destination: 192.168.1.19;
Sep 19 01:40:56 arch warp-svc[674]: 2026-09-18T23:40:56.892Z DEBUG collect_device_state: actor_device_state::collector: close time.busy=2.91µs time.idle=8.14µs
Sep 19 01:41:11 arch warp-svc[674]: 2026-09-18T23:41:11.881Z DEBUG actor_connectivity::connectivity: Routes changed: 2 in the last 30 seconds
Sep 19 01:41:24 arch warp-svc[674]: 2026-09-18T23:41:24.913Z DEBUG route-change: Routes changed:
Sep 19 01:41:24 arch warp-svc[674]: NewNeighbour; Destination: 192.168.1.19;
Sep 19 01:41:41 arch warp-svc[674]: 2026-09-18T23:41:41.881Z DEBUG actor_connectivity::connectivity: Routes changed: 1 in the last 30 seconds
Sep 19 01:41:55 arch warp-svc[674]: 2026-09-18T23:41:55.632Z DEBUG route-change: Routes changed:
Sep 19 01:41:55 arch warp-svc[674]: NewNeighbour; Destination: 192.168.1.19;
Sep 19 01:41:55 arch warp-svc[674]: 2026-09-18T23:41:55.647Z DEBUG route-change: Routes changed:
Sep 19 01:41:55 arch warp-svc[674]: NewNeighbour; Destination: 192.168.1.19;
Sep 19 01:42:11 arch warp-svc[674]: 2026-09-18T23:42:11.881Z DEBUG actor_connectivity::connectivity: Routes changed: 2 in the last 30 seconds
Sep 19 01:42:25 arch warp-svc[674]: 2026-09-18T23:42:25.841Z DEBUG route-change: Routes changed:
Sep 19 01:42:25 arch warp-svc[674]: NewNeighbour; Destination: 192.168.1.19;
Sep 19 01:42:41 arch warp-svc[674]: 2026-09-18T23:42:41.852Z DEBUG upload_stats{context="timer"}: actor_statistics::handler: Starting to upload stats
Sep 19 01:42:41 arch warp-svc[674]: 2026-09-18T23:42:41.852Z  WARN upload_stats{context="timer"}: actor_statistics::handler: Skipped uploading aggregate stats because registration was none!
Sep 19 01:42:41 arch warp-svc[674]: 2026-09-18T23:42:41.852Z  INFO upload_stats{context="timer"}: actor_statistics::handler: close time.busy=122µs time.idle=37.0µs
Sep 19 01:42:41 arch warp-svc[674]: 2026-09-18T23:42:41.880Z DEBUG actor_connectivity::connectivity: Routes changed: 1 in the last 30 seconds
Sep 19 01:42:44 arch warp-svc[674]: 2026-09-18T23:42:44.272Z DEBUG route-change: Routes changed:
Sep 19 01:42:44 arch warp-svc[674]: NewNeighbour; Destination: 192.168.1.19;
Sep 19 01:42:44 arch warp-svc[674]: 2026-09-18T23:42:44.279Z DEBUG route-change: Routes changed:
Sep 19 01:42:44 arch warp-svc[674]: NewNeighbour; Destination: 192.168.1.19;
Sep 19 01:42:56 arch warp-svc[674]: 2026-09-18T23:42:56.848Z DEBUG actor_api::persistence_manager: Extracted 0 persisted requests. namespace=Unauthenticated
Sep 19 01:42:56 arch warp-svc[674]: 2026-09-18T23:42:56.848Z DEBUG actor_api::persistence_manager: Extracted 0 persisted requests. namespace=Registration(Consumer("219ddcbf-208b-431e-8efa-ec6a61ca00da"))
Sep 19 01:42:56 arch warp-svc[674]: 2026-09-18T23:42:56.891Z DEBUG collect_device_state: actor_device_state::collector: close time.busy=3.08µs time.idle=7.69µs
Sep 19 01:43:11 arch warp-svc[674]: 2026-09-18T23:43:11.880Z DEBUG actor_connectivity::connectivity: Routes changed: 2 in the last 30 seconds
Sep 19 01:43:14 arch warp-svc[674]: 2026-09-18T23:43:14.480Z DEBUG route-change: Routes changed:
Sep 19 01:43:14 arch warp-svc[674]: NewNeighbour; Destination: 192.168.1.19;
Sep 19 01:43:41 arch warp-svc[674]: 2026-09-18T23:43:41.881Z DEBUG actor_connectivity::connectivity: Routes changed: 1 in the last 30 seconds
Sep 19 01:43:44 arch warp-svc[674]: 2026-09-18T23:43:44.688Z DEBUG route-change: Routes changed:
Sep 19 01:43:44 arch warp-svc[674]: NewNeighbour; Destination: 192.168.1.19;
Sep 19 01:43:44 arch warp-svc[674]: 2026-09-18T23:43:44.711Z DEBUG route-change: Routes changed:
Sep 19 01:43:44 arch warp-svc[674]: NewNeighbour; Destination: 192.168.1.19;
Sep 19 01:44:11 arch warp-svc[674]: 2026-09-18T23:44:11.881Z DEBUG actor_connectivity::connectivity: Routes changed: 2 in the last 30 seconds
Sep 19 01:44:14 arch warp-svc[674]: 2026-09-18T23:44:14.897Z DEBUG route-change: Routes changed:
Sep 19 01:44:14 arch warp-svc[674]: NewNeighbour; Destination: 192.168.1.19;
Sep 19 01:44:41 arch warp-svc[674]: 2026-09-18T23:44:41.852Z DEBUG upload_stats{context="timer"}: actor_statistics::handler: Starting to upload stats
Sep 19 01:44:41 arch warp-svc[674]: 2026-09-18T23:44:41.852Z  WARN upload_stats{context="timer"}: actor_statistics::handler: Skipped uploading aggregate stats because registration was none!
Sep 19 01:44:41 arch warp-svc[674]: 2026-09-18T23:44:41.852Z  INFO upload_stats{context="timer"}: actor_statistics::handler: close time.busy=68.5µs time.idle=31.7µs
Sep 19 01:44:41 arch warp-svc[674]: 2026-09-18T23:44:41.881Z DEBUG actor_connectivity::connectivity: Routes changed: 1 in the last 30 seconds

jonno2002 · Today 02:09:51

that laptop has a 13900h cpu, some intel 13/14th gen cpus have stability/crashing issues, i wonder if yours is one of them, theres alot of conflicting info out there as to which cpus are affected but i know for a fact that a 13700 (non-k) in a shuttle had the issue and was replaced under warranty, now that shuttle was running the cpu at intel stock power requirements or below so definately not a case of motherboard manufacturer over stressing the cpu, it was just a plain faulty cpu.

all i can suggest is make sure you have the latest firmware and microcode and hope for the best, maybe check the thermal compound under the heatsink in case someone did a rubbish job a some stage, try a memtest or even better use a different stick of ram for testing, even try another ssd if you can, just try eliminate all possibilities

EDIT:
also try another power supply if you have access to one and try with the battery disconnected too

Last edited by jonno2002 (Today 02:13:56)

Hero478 · Today 11:25:12

My laptop has actually a 12th gen i5 12500h cpu, i dont know if what you said about crashing issues still applies. i will try and verify that the firmware is on the latest version. should it be, could i ask for a repair or something since it's still under warranty?

jonno2002 · Today 12:46:32

no 12th gen arent affected, if its under warranty get hold of them and start the process i guess, they will tell you what to test before they consider it defective

dimich · Today 12:54:24

Shutdown with display backlight and LEDs off or hard freeze?
This might be thermal protection shutdown (and throttling didn't help for some reason) or power supply issue.
What GPU is on this laptop?

Hero478 · Today 12:57:46

dimich wrote:

Shutdown with display backlight and LEDs off or hard freeze?
This might be thermal protection shutdown (and throttling didn't help for some reason) or power supply issue.
What GPU is on this laptop?

complete shutdown. everything turns off (keyboard backlight, integrated monitor, and it even disconnects from the external 2k monitor i usually attach it to) and i have to manually turn it on again. it is indeed hot at touch but when i run sensors to check after i turn it back on it says all cores are around 75 C or below, so i would exclude that. if anything a power supply issue seems more likely
it mounts a nvidia rtx 3050 4gb

Last edited by Hero478 (Today 12:58:26)

dimich · Today 13:09:17

Hero478 wrote:

when i run sensors to check after i turn it back on it says all cores are around 75 C or below

It might have time to cool down.
If your CPU supports Intel Turbo Boost, try to disable it for test:

$ echo 1 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo

seth · Today 13:59:15

journalctl -b -1 -n 50 --no-pager

thath's just spam from warp-svc

The logs cut off suddenly.

The interesting info would at most be at the start of the new journal (MCE errors etc)

Emergency shudowns/reboots generally are
* overheated
* underpowered
* broken cpu
* bad RAM

The former two more likely in your scenario. 100°C is usually the critical cut-off.

Don't wait for the shutdown, monitor the temperatures while loading the system.
Once the CPU is cut off power the core will cool down rapidly - it's a teeny tiny bit of metal.

while watching a 4k movie

Watch how? Does eg. mpv indicate hardware decoding (and does it happen there as well)?

Hero478 · Today 14:28:59

seth wrote:

The interesting info would at most be at the start of the new journal (MCE errors etc)

I've ran this right after boot

journalctl -b -p 4

Sep 19 16:15:41 archlinux kernel: x86/CPU: Running old microcode
Sep 19 16:15:41 archlinux kernel:   #1  #3  #5  #7
Sep 19 16:15:41 archlinux kernel: virt/tdx: TDX not supported by the host platform
Sep 19 16:15:41 archlinux kernel: hpet_acpi_probe: no address or irqs in _CRS
Sep 19 16:15:41 archlinux kernel: usb: port power management may be unreliable
Sep 19 16:15:41 archlinux kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Sep 19 16:15:41 archlinux kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 19 16:15:42 archlinux kernel: pci 10000:e0:06.0: Primary bus is hard wired to 0
Sep 19 16:15:42 archlinux kernel: pci 10000:e0:06.0: Primary bus is hard wired to 0
Sep 19 16:15:42 archlinux kernel: pcieport 10000:e0:06.0: can't derive routing for PCI INT D
Sep 19 16:15:42 archlinux kernel: pcieport 10000:e0:06.0: PCI INT D: no GSI
Sep 19 16:15:42 archlinux kernel: pcieport 10000:e0:06.0: can't derive routing for PCI INT A
Sep 19 16:15:42 archlinux kernel: nvme 10000:e1:00.0: PCI INT A: no GSI
Sep 19 16:15:44 arch systemd-journald[365]: File /var/log/journal/09326ab5e60c45b7bec1e64e8d989502/system.journal corrupted or uncleanly shut down, renaming and replacing.
Sep 19 16:15:44 arch kernel: kvm_amd: CPU 14 isn't AMD or Hygon
Sep 19 16:15:44 arch kernel: vboxdrv: loading out-of-tree module taints kernel.
Sep 19 16:15:44 arch kernel: VBoxNetFlt: Successfully started.
Sep 19 16:15:44 arch kernel: VBoxNetAdp: Successfully started.
Sep 19 16:15:44 arch kernel: resource: resource sanity check: requesting [mem 0x00000000fedc0000-0x00000000feddffff], which spans more than PNP0C02:01 [mem 0xfedc0000-0xfedc7fff]
Sep 19 16:15:44 arch kernel: caller igen6_probe+0xcc/0xf18 [igen6_edac] mapping multiple BARs
Sep 19 16:15:44 arch kernel: resource: resource sanity check: requesting [mem 0x00000000fedc0000-0x00000000fedcffff], which spans more than PNP0C02:01 [mem 0xfedc0000-0xfedc7fff]
Sep 19 16:15:44 arch kernel: caller igen6_probe+0x22e/0xf18 [igen6_edac] mapping multiple BARs
Sep 19 16:15:44 arch kernel: ACPI Warning: \_SB.IETM._TRT: Return Package has no elements (empty) (20260408/nsprepkg-94)
Sep 19 16:15:44 arch kernel: spi-nor spi0.0: supply vcc not found, using dummy regulator
Sep 19 16:15:44 arch kernel: asus_armoury: No matching power limits found for this system
Sep 19 16:15:44 arch kernel: faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
Sep 19 16:15:44 arch kernel: Bluetooth: hci0: No dsm support to set reset delay
Sep 19 16:15:44 arch kernel: asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -19
Sep 19 16:15:44 arch kernel: asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -19
Sep 19 16:15:44 arch kernel: asus_wmi: fan_curve_get_factory_default (0x00110032) failed: -19
Sep 19 16:15:44 arch kernel: nvidia: unknown parameter 'NVreg_UsePageAttributeTable' ignored
Sep 19 16:15:44 arch kernel: 
Sep 19 16:15:44 arch kernel: ucsi_acpi USBC000:00: Partner rejected swap
Sep 19 16:15:44 arch kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)
Sep 19 16:15:44 arch kernel: ucsi_acpi USBC000:00: Partner rejected swap
Sep 19 16:15:44 arch kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)
Sep 19 16:15:46 arch kernel: NVRM: GPU0 nvAssertOkFailedNoLog: Assertion failed: Invalid data passed [NV_ERR_INVALID_DATA] (0x00000025) returned from PlatformRequestHandler failed to get target temp from SBIOS @ platform_request_>
Sep 19 16:15:46 arch kernel: NVRM: GPU0 nvAssertOkFailedNoLog: Assertion failed: Invalid data passed [NV_ERR_INVALID_DATA] (0x00000025) returned from PlatformRequestHandler failed to get platform power mode from SBIOS @ platform_>
Sep 19 16:15:46 arch kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  615.71.09  Release Build  (root@arch)  
Sep 19 16:15:46 arch kernel: nvidia 0000:01:00.0: [drm] No compatible format found
Sep 19 16:15:46 arch grub-btrfsd[679]: [!] Unknown option --timeshit-auto
Sep 19 16:15:46 arch systemd[1]: grub-btrfsd.service: Failed with result 'exit-code'.
Sep 19 16:15:46 arch kernel: pcieport 10000:e0:06.0: Primary bus is hard wired to 0
Sep 19 16:15:46 arch kernel: pcieport 10000:e0:06.0: Primary bus is hard wired to 0
Sep 19 16:15:46 arch (modprobe)[672]: lm_sensors.service: Referenced but unset environment variable evaluates to an empty string: BUS_MODULES
Sep 19 16:15:46 arch kernel: pcieport 10000:e0:06.0: Primary bus is hard wired to 0
Sep 19 16:15:46 arch kernel: pcieport 10000:e0:06.0: Primary bus is hard wired to 0
Sep 19 16:15:46 arch kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: Parent card not yet available, widget card binding deferred
Sep 19 16:15:46 arch kernel: skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3
Sep 19 16:15:47 arch wpa_supplicant[694]: wlan0: nl80211: kernel reports: multicast RX registrations are not supported
Sep 19 16:15:47 arch NetworkManager[666]: <warn>  [1789827347.2195] device (94:32:C1:D6:8B:2F): error setting IPv4 forwarding to '0': Invalid argument
Sep 19 16:15:47 arch wpa_supplicant[694]: p2p-dev-wlan0: nl80211: kernel reports: multicast RX registrations are not supported
Sep 19 16:15:47 arch NetworkManager[666]: <warn>  [1789827347.2406] device (p2p-dev-wlan0): error setting IPv4 forwarding to '0': Success
Sep 19 16:15:47 arch accounts-daemon[868]: Unable to open /etc/tcb: No such file or directory
Sep 19 16:15:47 arch dbus-broker-launch[663]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
Sep 19 16:15:47 arch accounts-daemon[868]: couldn't list homed users: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.freedesktop.home1': activation request failed: unknown unit
Sep 19 16:15:47 arch dbus-broker-launch[663]: Activation request for 'org.freedesktop.Avahi' failed: The systemd unit 'dbus-org.freedesktop.Avahi.service' could not be found.
Sep 19 16:15:47 arch dbus-broker-launch[1017]: Service file '/usr/share//dbus-1/services/fr.emersion.mako.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Sep 19 16:15:47 arch dbus-broker-launch[1017]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Sep 19 16:15:47 arch dbus-broker-launch[1017]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service'
Sep 19 16:15:47 arch dbus-broker-launch[1017]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Sep 19 16:15:47 arch dbus-broker-launch[1017]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Sep 19 16:15:47 arch dbus-broker-launch[1017]: Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service'
Sep 19 16:15:47 arch dbus-broker-launch[1017]: Service file '/usr/share//dbus-1/services/org.knopwob.dunst.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Sep 19 16:15:47 arch dbus-broker-launch[1017]: Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share//dbus-1/services/org.knopwob.dunst.service'
Sep 19 16:15:47 arch libvirtd[845]: Libvirt doesn't support VirtualBox API version 7002016
Sep 19 16:15:48 arch gsd-usb-protection[1199]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Sep 19 16:15:49 arch gsd-media-keys[1190]: Failed to grab accelerator for keybinding settings:playback-repeat
Sep 19 16:15:49 arch gsd-media-keys[1190]: Failed to grab accelerator for keybinding settings:hibernate
Sep 19 16:15:49 arch gsd-media-keys[1190]: Unable to get default sink
Sep 19 16:15:49 arch gnome-shell[1070]: Failed to record usage: GDBus.Error:org.freedesktop.MalcontentTimer1.Child.Error.IdentifyingUser: Error identifying user: Invalid or unknown user
Sep 19 16:15:49 arch geoclue[2064]: Failed to connect to avahi service: Daemon not running
Sep 19 16:15:49 arch dbus-broker-launch[663]: Activation request for 'org.freedesktop.ModemManager1' failed: The systemd unit 'dbus-org.freedesktop.ModemManager1.service' could not be found.
Sep 19 16:15:49 arch gsd-xsettings[2448]: Failed to get current UI scaling factor: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Destination does not exist
Sep 19 16:15:50 arch xdg-desktop-portal-gnome[2491]: Monitor 'Built-in display' has no configuration which is-current!
Sep 19 16:15:50 arch gnome-keyring-daemon[2527]: The Secret Service was already initialized
Sep 19 16:15:50 arch gnome-keyring-daemon[2525]: discover_other_daemon: 1
Sep 19 16:15:50 arch gnome-keyring-daemon[2527]: The Secret Service was already initialized
Sep 19 16:15:54 arch kernel: warning: `tokio-rt-worker' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
Sep 19 16:16:09 arch gdm-password][3559]: gkr-pam: unable to locate daemon control file
Sep 19 16:16:09 arch systemd-xdg-autostart-generator[3793]: /home/ricky/.config/autostart/windscribe.desktop: stat() failed, ignoring: No such file or directory
Sep 19 16:16:09 arch dbus-broker-launch[3796]: Service file '/usr/share//dbus-1/services/fr.emersion.mako.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Sep 19 16:16:09 arch dbus-broker-launch[3796]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Sep 19 16:16:09 arch dbus-broker-launch[3796]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service'
Sep 19 16:16:09 arch dbus-broker-launch[3796]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Sep 19 16:16:09 arch dbus-broker-launch[3796]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Sep 19 16:16:09 arch dbus-broker-launch[3796]: Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service'
Sep 19 16:16:09 arch dbus-broker-launch[3796]: Service file '/usr/share//dbus-1/services/org.knopwob.dunst.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Sep 19 16:16:09 arch dbus-broker-launch[3796]: Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share//dbus-1/services/org.knopwob.dunst.service'
Sep 19 16:16:09 arch gsd-media-keys[1190]: Unable to get default sink
Sep 19 16:16:09 arch gsd-media-keys[1190]: Unable to get default source
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4191]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4191]: > Warning:          Multiple symbols for level 1/group 1 on key <FK23>
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4191]: >                   Using F23, ignoring XF86TouchpadOff
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4191]: > Warning:          Symbol map for key <FK23> redefined
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4191]: >                   Using last definition for conflicting fields
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4191]: > Warning:          Symbol map for key <FK24> redefined
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4191]: >                   Using last definition for conflicting fields
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4191]: > Warning:          Could not resolve keysym XF86ElectronicPrivacyScreenOn
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4191]: > Warning:          Could not resolve keysym XF86ElectronicPrivacyScreenOff
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4191]: > Warning:          Could not resolve keysym XF86ActionOnSelection
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4191]: > Warning:          Could not resolve keysym XF86ContextualInsert
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4191]: > Warning:          Could not resolve keysym XF86ContextualQuery
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4191]: Errors from xkbcomp are not fatal to the X server
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4204]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4204]: > Warning:          Unsupported maximum keycode 709, clipping.
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4204]: >                   X11 cannot support keycodes above 255.
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4204]: > Warning:          Virtual modifier Hyper multiply defined
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4204]: >                   Using 0, ignoring 0
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4204]: > Warning:          Virtual modifier ScrollLock multiply defined
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4204]: >                   Using 0, ignoring 0
Sep 19 16:16:14 arch /usr/lib/gdm-wayland-session[4204]: Errors from xkbcomp are not fatal to the X server
Sep 19 16:16:14 arch hyprpolkitagent[4128]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for ''")
Sep 19 16:16:14 arch xdg-desktop-portal-kde[4208]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Sep 19 16:16:19 arch gnome-shell[1070]: Connection to xwayland lost
Sep 19 16:16:19 arch accounts-daemon[868]: Unable to open /etc/tcb: No such file or directory
Sep 19 16:16:19 arch accounts-daemon[868]: couldn't list homed users: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.freedesktop.home1': activation request failed: unknown unit
Sep 19 16:16:20 arch systemd[962]: dbus-:1.2-org.gnome.Settings.GlobalShortcutsProvider@0.service: Failed with result 'exit-code'.
Sep 19 16:16:28 arch kdeconnectd[5135]: QObject::connect(QUdpSocket, Unknown): invalid nullptr parameter

as for the rest, i ran another stress test that lasted around 9-10 minutes, while constantly monitoring both temperatures and live error messages from journalctl.
temperatues:
cores from C0 to C3 constantly oscillated bewteen 90 and 96 C, but never more than that. They're supposed to be performance cores so it's understandable. core from C4 to C15 started from 83 C and they steadily increased. unfortunately, the last 30 seconds of the test i got a little distracted and laid my eyes on another thing, but the last temperature i saw was 89, and it's highly unlikely that in 30 seconds they got from 89 to 100 if it took them 9 minutes to go from 83 to 89.
logs:
nothing appeared in journalctl or even dmesg while testing

seth · Today 14:41:19

journalctl -b -p 4

Don't apply random filters to the journal.

unlikely that in 30 seconds they got from 89 to 100 if it took them 9 minutes to go from 83 to 89.

oscillated bewteen 90 and 96 C

The temperature of a core can rase 10°C in a second. Again: very tiny piece of metal - 10°C is not much energy there.
Also, why does the system start at 83°C?

set wrote:

Watch how? Does eg. mpv indicate hardware decoding (and does it happen there as well)?

(HW accelerated 4k video should™ not heat up the CPU this way at all - but also the baseline should™ not be 83°C)

And finally: constrain the cores, limit their top frequency and disable the turbo boost.
Does that stabilize the system?

Hero478 · Today 14:53:25

seth wrote:

Don't apply random filters to the journal.

i figured that if something important had to pop up it would at least be a warning

seth wrote:

Also, why does the system start at 83°C?

yeah i didnt explain myself properly. the base temperature when idle is anywhere from 50 to 55 C. then when i start the stress test it has massive spikes (55 -> 63 -> 77 -> 83) and from there it raises gradually

(HW accelerated 4k video should™ not heat up the CPU this way at all - but also the baseline should™ not be 83°C)

yeah sorry i forgot that part. it's a 4k movie streamed from a jellyfin server through mpv with hardware decoding. i didnt accurately measure the temperatures during streaming but im pretty sure they weren't as high as during the test since i made sure mpv recognized and used the dGPU. ill check again while testing all the other stuff too

headkase · Today 14:56:21

Since you start at a high-temperature, have you opened the laptop and physically inspected whether or not the cooling parts are clogged with dust? Like heat sinks mainly, and perhaps your thermal compound was improperly applied at the factory for the CPU if the temperatures have always been high.

Hero478 · Today 15:45:28

i measured the temperatures while streaming and nothing out of the ordinary happened: all the cores were mostly between 65 and 75 C, with occasionally 2 of the performance cores in the mid 90s, but still the laptop gave up.
i also ran the stress test with turbo off and the laptop didnt crash, all cores remained below 85 C and the frequency was a stable 2.5 ghz.

headkase wrote:

Since you start at a high-temperature, have you opened the laptop and physically inspected whether or not the cooling parts are clogged with dust? Like heat sinks mainly, and perhaps your thermal compound was improperly applied at the factory for the CPU if the temperatures have always been high.

is 50 high?

dimich · Today 15:56:59

Hero478 wrote:

i also ran the stress test with turbo off and the laptop didnt crash, all cores remained below 85 C and the frequency was a stable 2.5 ghz.

This is normal operating mode for the CPU. 4.5GHz turbo frequency in laptops is marketing bullshit.

Hero478 · Today 16:01:30

yeah im not saying it should reach that frequency but im not entirely sure i want to cap my cpu to 2.5 ghz on heavy workload when i know it could comfortably reach 3.5, especially considering that the laptop is not even a year old

seth · Today 19:09:12

is 50 high?

My system idles at 28° or room temperature when that's higher.
On regular works it's ~35°C; stressing it the fans kick in at ~60°C and I don't think I've ever seen it go > 70°C

I assume there's some problem w/ the thermal management - do the fans run at full speed when it crashes?

Hero478 · Today 19:45:05

Yeah buy mine is (theoretically) a high performances laptop so it should be normal to have higher idle temperatures, especially considering that 28 C here is a chill day in this period

The fans run at around 3200 rpm while under heavy load and then shut completely when the laptop crashes

seth · Today 19:50:31

so it should be normal to have higher idle temperatures

No?
Idle is idle.

28 C here is a chill day in this period

Can you get it into a climate controlled environment?

Hero478 · Today 19:58:00

with ac on best i can do is 26, and i still have the same temperatures

seth · Today 20:20:07

The system is either overheating or under-powered for the higher frequencies.
Since there's a build up it's most likely the temperatures.

The system should™ first ramp up the fans and then clock down.
Cutting power to protect the CPU is the last resort.

Are the fans controlled by firmware or OS?
Do you overclock anything (or is the system overclocked by design) what might prevent downclocks for temperature control?
https://wiki.archlinux.org/title/CPU_frequency_scaling

Don't underestimate dust (or other blockages to the air flow, like placing it in a box or w/ the vent facing a wall etc) - if the warm air cannot be transported out of the system, the environmental temperature becomes irrelevant. Otherwise you'd expect a notable difference between a 16°C and 40°C environment.

Arch Linux

#1 Yesterday 23:57:33

Laptop completely shutting down during heavy cpu loads

#2 Today 02:09:51

Re: Laptop completely shutting down during heavy cpu loads

#3 Today 11:25:12

Re: Laptop completely shutting down during heavy cpu loads

#4 Today 12:46:32

Re: Laptop completely shutting down during heavy cpu loads

#5 Today 12:54:24

Re: Laptop completely shutting down during heavy cpu loads

#6 Today 12:57:46

Re: Laptop completely shutting down during heavy cpu loads

#7 Today 13:09:17

Re: Laptop completely shutting down during heavy cpu loads

#8 Today 13:59:15

Re: Laptop completely shutting down during heavy cpu loads

#9 Today 14:28:59

Re: Laptop completely shutting down during heavy cpu loads

#10 Today 14:41:19

Re: Laptop completely shutting down during heavy cpu loads

#11 Today 14:53:25

Re: Laptop completely shutting down during heavy cpu loads

#12 Today 14:56:21

Re: Laptop completely shutting down during heavy cpu loads

#13 Today 15:45:28

Re: Laptop completely shutting down during heavy cpu loads

#14 Today 15:56:59

Re: Laptop completely shutting down during heavy cpu loads

#15 Today 16:01:30

Re: Laptop completely shutting down during heavy cpu loads

#16 Today 19:09:12

Re: Laptop completely shutting down during heavy cpu loads

#17 Today 19:45:05

Re: Laptop completely shutting down during heavy cpu loads

#18 Today 19:50:31

Re: Laptop completely shutting down during heavy cpu loads

#19 Today 19:58:00

Re: Laptop completely shutting down during heavy cpu loads

#20 Today 20:20:07

Re: Laptop completely shutting down during heavy cpu loads

Board footer