Game Window Freezes, GPU Spikes to 100% Usage Consistently

Support Gaming
, ,
1

Integrated GPU: Intel
Dedicated GPU: NVIDIA 3070
Using Proton on Steam
Kernel: 6.12.77-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
Desktop: KDE Plasma v: 6.5.6 tk: Qt v: N/A info: frameworks v: 6.24.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux

I’ve been having consistent problems with some games, where their window will unpredictably freeze, then show me an image from a few seconds before it stopped responding. Everything else works fine, though my computer considers the Steam window to be a part of the game as well; as in, the custom cursor from the game appears over the Steam window and I cannot interact with it in any way.

I suspected it was a problem with using the Integrated GPU, so I did some searching, installed envycontrol and ran sudo envycontrol -s nvidia --force-comp, which didn’t work, then found the prime-run command, which, when added as a launch option to the game in my Steam library, allowed my game to last longer, but it still eventually failed.

I managed to catch this screenshot, however, showing the PC splitting the work between both GPUs before deciding at some point to dump everything on GPU1 (which, although I believe it is my integrated GPU, I do not have a way to confirm this) (the freeze happens roughly when GPU1 reaches 100% usage):

GPU_Freezing_Issues
GPU_Freezing_Issues845×256 20.8 KB

The instant my game window closes GPU1 usage drops to zero. Does anyone have any advice on how to keep these spikes from occurring?

glxinfo | grep "OpenGL renderer" output:

OpenGL renderer string: Mesa Intel(R) UHD Graphics (TGL GT1)

prime-run glxinfo | grep "OpenGL renderer" output:

OpenGL renderer string: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 146 ()
Minor opcode of failed request: 5
Resource id in failed request: 0x6000003
Serial number of failed request: 55
Current serial number in output stream: 56

2

Please provide full system information using inxi -zv8 in a Terminal, use the </> button to paste the CLI output in your next post.

3 
System:
  Kernel: 6.12.77-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=25754e71-4f02-4035-bc3c-b7502ecd8672 rw quiet splash
    udev.log_priority=3 zswap.enabled=0
  Desktop: KDE Plasma v: 6.5.6 tk: Qt v: N/A info: frameworks v: 6.24.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: HP product: OMEN by HP Laptop 16-b0xxx v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 88FD v: 86.43 serial: <superuser required>
    part-nu: 475N8UA#ABA uuid: <superuser required> Firmware: UEFI vendor: AMI
    v: F.43 date: 01/31/2023
Battery:
  ID-1: BAT0 charge: 56.6 Wh (100%) condition: 56.6/70.1 Wh (80.8%)
    volts: 17.04 min: 15.4 model: HP Primary type: Li-ion serial: <filter>
    charging: status: full cycles: 71
Memory:
  System RAM: total: 32 GiB available: 30.99 GiB used: 6.85 GiB (22.1%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 2 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: Bottom - Slot 1 (left) type: DDR4 detail: synchronous
    size: 16 GiB speed: 2400 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: 0x0C26
    part-no: TIMETEC-S16G-2400 serial: N/A
  Device-2: Bottom - Slot 2 (right) type: DDR4 detail: synchronous
    size: 16 GiB speed: 2400 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: 0x0C26
    part-no: TIMETEC-S16G-2400 serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: 11th Gen Intel Core i7-11800H bits: 64 type: MT MCP
    arch: Tiger Lake gen: core 11 level: v4 note: check built: 2020
    process: Intel 10nm family: 6 model-id: 0x8D (141) stepping: 1
    microcode: 0x58
  Topology: cpus: 1x dies: 1 clusters: 8 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 10 MiB
    desc: 8x1.2 MiB L3: 24 MiB desc: 1x24 MiB
  Speed (MHz): avg: 2536 min/max: 800/4600 scaling: driver: intel_pstate
    governor: powersave cores: 1: 2536 2: 2536 3: 2536 4: 2536 5: 2536 6: 2536
    7: 2536 8: 2536 9: 2536 10: 2536 11: 2536 12: 2536 13: 2536 14: 2536
    15: 2536 16: 2536 bogomips: 73744
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 avx512_bitalg avx512_vbmi2
    avx512_vnni avx512_vp2intersect avx512_vpopcntdq avx512bw avx512cd
    avx512dq avx512f avx512ifma avx512vbmi avx512vl bmi1 bmi2 bts cat_l2
    cdp_l2 clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault cx16
    cx8 de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est f16c flexpriority
    flush_l1d fma fpu fsgsbase fsrm fxsr gfni ht hwp hwp_act_window hwp_epp
    hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ibt ida intel_pt invpcid
    lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b movdiri msr mtrr
    nonstop_tsc nopl nx ospke pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs
    pge pku pln pni popcnt pse pse36 pts rdpid rdrand rdseed rdt_a rdtscp
    rep_good sdbg sep sha_ni smap smep split_lock_detect ss ssbd sse sse2
    sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust
    tsc_deadline_timer tsc_known_freq umip user_shstk vaes vme vmx vnmi
    vpclmulqdq vpid x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology
    xtpr
Graphics:
  Device-1: Intel TigerLake-H GT1 [UHD Graphics] vendor: Hewlett-Packard
    driver: i915 v: kernel alternate: xe arch: Xe process: Intel 10nm
    built: 2020-21 ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5,
    HDMI-A-1 bus-ID: 0000:00:02.0 chip-ID: 8086:9a60 class-ID: 0300
  Device-2: NVIDIA GA104M [GeForce RTX 3070 Mobile / Max-Q]
    vendor: Hewlett-Packard driver: nvidia v: 590.48.01
    alternate: nouveau,nvidia_drm non-free: 550-580.xx+ status: current (as
    of 2025-11; EOL~2026-12-xx) arch: Ampere code: GAxxx
    process: TSMC n7 (7nm) built: 2020-2023 ports: active: none
    empty: DP-6,HDMI-A-2,eDP-2 bus-ID: 0000:01:00.0 chip-ID: 10de:24dd
    class-ID: 0300
  Device-3: Quanta HP Wide Vision HD Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6:3 chip-ID: 0408:5425
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: modesetting,nvidia dri: iris
    gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x09e5 built: 2020 res:
    mode: 2560x1440 hz: 165 scale: 110% (1.1) to: 2327x1309 dpi: 183 gamma: 1.2
    chroma: red: x: 0.639 y: 0.329 green: x: 0.298 y: 0.600 blue: x: 0.149
    y: 0.059 white: x: 0.314 y: 0.329 size: 355x200mm (13.98x7.87")
    diag: 407mm (16") ratio: 16:9 modes: 2560x1440
  EDID-Warnings: 1: parse_edid: unknown flag 2 2: parse_edid: unknown tag
    112
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris
    inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 26.0.2-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (TGL GT1)
    device-ID: 8086:9a60 memory: 30.26 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.341 layers: 6 device: 0 type: discrete-gpu name: NVIDIA
    GeForce RTX 3070 Laptop GPU driver: nvidia v: 590.48.01
    device-ID: 10de:24dd surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Tiger Lake-H HD Audio vendor: Hewlett-Packard
    driver: sof-audio-pci-intel-tgl alternate: snd_hda_intel, snd_soc_avs,
    snd_sof_pci_intel_tgl bus-ID: 0000:00:1f.3 chip-ID: 8086:43c8
    class-ID: 0401
  Device-2: NVIDIA GA104 High Definition Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel bus-ID: 0000:01:00.1 chip-ID: 10de:228b
    class-ID: 0403
  API: ALSA v: k6.12.77-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.6.2 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Tiger Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 0000:00:14.3 chip-ID: 8086:43f0 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000
    bus-ID: 0000:2d:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-14:5 chip-ID: 8087:0026
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:9a0b rev: class-ID: 0104
Drives:
  Local Storage: total: 953.87 GiB used: 557.64 GiB (58.5%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZVL21T0HCLR-00BH1 size: 953.87 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: HPS2NGXH temp: 48.9 C scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 953.57 GiB size: 937.53 GiB (98.32%)
    used: 557.64 GiB (59.5%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 25754e71-4f02-4035-bc3c-b7502ecd8672
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 328 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: 23D7-BC4B
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 8 GiB used: 358 MiB (4.4%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16
    dev: /dev/zram0
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-2:2 info: Logitech Optical Wheel Mouse type: mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 046d:c016 class-ID: 0301
  Device-2: 3-6:3 info: Quanta HP Wide Vision HD Camera type: video
    driver: uvcvideo interfaces: 3 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 500mA chip-ID: 0408:5425 class-ID: fe01
    serial: <filter>
  Device-3: 3-8:4 info: Primax HP OMEN 16 KBM type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 0461:4e9b class-ID: 0300
  Device-4: 3-14:5 info: Intel AX201 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0026 class-ID: e001
  Hub-4: 4-0:1 info: super-speed hub ports: 8 rev: 3.1
    speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 66.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 3208 fan-2: 3500
Info:
  Processes: 368 Power: uptime: 4h 43m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.33 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 259 default: graphical
    tool: systemctl
  Compilers: clang: 22.1.1 gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole
    inxi: 3.3.40
1 Like
4

My guess is this could be related to (X)Wayland somehow. You could try this by installing kwin-x11 and log into an X11 session, or by installing icewm.

5

I installed kwin-x11, but I’m not sure how to use it, and I can’t find any guides online.

I tried running the --desktopfile command and got:

kwin: unable to claim manager selection, another wm running? (try using --replace)
QThreadStorage: entry 1 destroyed before end of thread 0x55ee117dd7d0
QThreadStorage: entry 0 destroyed before end of thread 0x55ee117dd7d0

So I ran kwin_x11 --replace and received:

qt.qpa.services: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: App info not found for ‘org.kde.kwin’”)
kwin: another window manager is running (try using --replace)
QThreadStorage: entry 7 destroyed before end of thread 0x55a7354277d0
QThreadStorage: entry 1 destroyed before end of thread 0x55a7354277d0
QThreadStorage: entry 0 destroyed before end of thread 0x55a7354277d0

I found this post and followed its advice, but all that accomplished was hiding the first two lines of output. It still recommends running --replace to the --replace command…

Any idea what’s going on here? I’m a bit lost.

6

You need to install plasma-x11-session too and the log out choose X11 and log back in.

1 Like
10

When you say log out, do you mean of my account on my computer? I didn’t receive a choice for anything after doing so.

I set my auto-login in System Settings > Login Screen SDDM > Behavior to use a Plasma(X11) session, then logged out and logged back in, but the command echo "$XDG_SESSION_TYPE" still printed

wayland

Okay. I reset my computer and that seems to have done it. The session is now x11, and when I run glxinfo | grep "OpenGL renderer", it prints out my NVIDIA GPU.

I’m going to test if this actually fixes the issue or not, but my thinking would be the problem is different from what I assumed if it still occurs.

Edit: It seems to work now. Surprisingly, GPU1 is the NVIDIA one, so I’m not sure what was going on previously, but hopefully I do not have to worry about that.

Okay, I was mistaken. It might be an issue related to overheating, as it didn’t start to happen until my computer became noticeably hot (which is consistent with the circumstances that caused me to make the post in the first place), but according to inxi -zv8, my GPU is only 66 degrees C, and my fans are still working fine, so… I don’t know.

Something that was different is that my game closed seconds after freezing, rather than staying on screen until I forced it to stop like I had to before.

Edit: Okay, X11 is just worse. Second freeze made my entire laptop unusable even after the game closed, forcing me to manually reset it. I’m going to uninstall and switch back to wayland.

Mod edit: Consecutive posts merged. Please edit your previous post(s) instead to add further information.

11

X11 mostly gives better gaming performance, specially on nvidia GPU’s. Probably your hardware utilise better on X11 as on Wayland and when your hardware is overheating the crash cascade then even stronger.

Are you aware that we also have the magic system hotkeys? As long you get have a Kernel Crash, you can revive your system, or at least you can initiate a clean shutdown.

For investigating closer around your problem, you might want to temporary disable your i-gpu in your Bios to find the culprit… its not always a easy task to find a solution.

You can also try out different Kernels 6.18 LTS for example.

Did you created this system info, while your game was running?
I ask this because for idle CPU temps, 66 degree is really hot.

12

I was not playing anything at the time of posting my system info.

Although, that’s also the result of spending most of the day on my laptop. Grabbing the temp rn, the resting temperature seems to be about 42 degrees C.

13

There are many Firmware Updates. That is the latest.
https://support.hp.com/us-en/drivers/swdetails/omen-16.1-inch-gaming-laptop-pc-16-b0000/model/2100371532/swItemId/ob-351718-1?sku=475N8UA

Same for the Storage

https://support.hp.com/us-en/drivers/swdetails/omen-16.1-inch-gaming-laptop-pc-16-b0000/model/2100371532/swItemId/ob-330572-1?sku=475N8UA

Full List here
https://support.hp.com/us-en/drivers/omen-16.1-inch-gaming-laptop-pc-16-b0000/model/2100371532?sku=475N8UA

Why Kernel 6.12 ?

14

I don’t know? I install updates as they arrive. I was under the impression I had the latest versions of everything, and I only moved to Manjaro a year ago.

Found Manjaro Settings Manager; I didn’t know about this until now. Thanks for the advice.

Can’t find a way to install the .exe updates from HP, though.

15

Hirens Boot CD ?

16

Can you elaborate, please?

17
18

Okay, I was wrong. The idle CPU temperature does seem to be around 60 degrees C, with just LibreOffice Writer and Firefox running. I can’t do anything with my fans, though, because I have “no pwm-capable sensor modules installed.”

I’m going to attempt to use Hiren’s Boot CD as soon as I can, but that’ll be a minimum of two weeks from now. Any suggestions until then?

19

Open your Laptop, clean the dust and depends how much dust can be removed or not.
I would thinking about to repaste your Heatpaste then, if you can’t adjust the fanspeed in your Bios or with a Software Tool.

Idk how many reminder’s you need to change your Kernel :wink:

20

I was just about to suggest this. I have seen a similar report elsewhere (unfortunately I can’t find it now) but when the card was overheating, it would fail causing the kernel to drop the module or perhaps the card just failed to communicate any longer; I can’t quite remember the specifics.

Definitely add some heat monitoring (preferably with logging), remove any overclocks if you have any.

Also you don’t seem to have mentioned or provided any info from your syslogs? That should at least narrow down the issue.

21

Please post the Output from sensors

23

Rn, not doing anything super strenuous but I’ve been using it most of the day (10 hours, give or take):

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +75.0°C  

hp-isa-0000
Adapter: ISA adapter
fan1:        3985 RPM
fan2:        4178 RPM
pwm1:             N/A

BAT0-acpi-0
Adapter: ACPI interface
in0:          16.80 V  
power1:           N/A  

ucsi_source_psy_USBC000:001-isa-0000
Adapter: ISA adapter
in0:           0.00 V  (min =  +0.00 V, max =  +0.00 V)
curr1:         0.00 A  (max =  +0.00 A)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +96.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +86.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +92.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:        +91.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:        +96.0°C  (high = +100.0°C, crit = +100.0°C)
Core 4:        +90.0°C  (high = +100.0°C, crit = +100.0°C)
Core 5:        +95.0°C  (high = +100.0°C, crit = +100.0°C)
Core 6:        +88.0°C  (high = +100.0°C, crit = +100.0°C)
Core 7:        +91.0°C  (high = +100.0°C, crit = +100.0°C)

nvme-pci-e100
Adapter: PCI adapter
Composite:    +47.9°C  (low  = -273.1°C, high = +80.8°C)
                       (crit = +84.8°C)
Sensor 1:     +47.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +63.9°C  (low  = -273.1°C, high = +65261.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +77.0°C

Edit: Although, I had powered off my computer 2 hours ago and it was about room temperature when I turned it back on (I was moving it around). So, it’s probably not related to length of time I’ve been using it?

Edit 2: I shut down the Steam app and a bit later the Cores all dropped by 40 degrees C. Not sure how to interpret that. I had only been playing Rocket League with Discord open when the 90’s were recorded.

@Kobold
I updated to the latest LTS version the same day weingeist alerted me to the issue.

Mod edit: Consecutive posts merged. Please edit your previous post(s) instead to add further information.

24

Am I misunderstanding you? You were playing Rocket League with Discord open and hitting 96C; when you stopped playing and closed Steam the temps dropped to 50C?

The workload is too high for your current cooling solution/configuration. The freezes are likely due to overheating and hardware shutdown from error or self-preservation.

Check your systemlog for kernel messages relating to “temperature above threshold”, “cpu clock throttled”, or “core power limit notification” or similar. I would assume you would notice this during use though as you’d be getting some harsh latency issues at the least.

If your GPU is running at 100% you probably need to reduce some graphics settings to give it some breathing space; but your CPU is also hammered with temps like that. Laptops generally use common airflow pathways between CPU and GPU and depending on which gets the coolest air will affect the temps of the other.

The HP Omen laptop marketing boasts some fancy thermal management, but a lot of that heavy lifting is done by software - that as far as I know doesn’t run on linux. So you’ll have to manage it yourself if at all possible. I don’t know to what extent software can control your fans but you might want to try here: GitHub - arfelious/omen-fan-control: HP Omen Max, Omen & Victus Fan Control CLI & GUI tool for Linux thermal management. Implements upcoming hp-wmi patches directly to allow manual fan controls. · GitHub

You might need to consider further environmental or additional cooling solutions:

1 Like