PC freezes with looping audio and needs to be force shut down, causes issues with hard drive

anonymousdormouse · January 22, 2026, 7:25pm

Ubuntu Version:
24.04, Desktop

Problem Description:
I’ve had an issue now for a day or two where watching YouTube videos via Firefox or trying to play Arknights: Endfield through Steam (the only game that I know for sure right now causes issues) will eventually cause the entire PC to freeze and loop about a second of audio indefinitely, and the only way I’ve gotten it to stop is to force a shutdown with the power button. How long it takes to crash varies, the shortest time was about a minute, while I was once able to play AE for at least half an hour before it froze.

Upon restarting, there is usually an issue with the hard drive I have alongside the drive I have windows 10 on and the one I have Ubuntu on (so three drives total), so I’ve had to go into windows to check and repair the drive. Fortunately it seems to be okay so far, but obviously this probably isn’t good for it.

Relevant System Information:
Nvidia graphics card, Linux and home folder on a separate drive to the one that needs repairing after crashes

I’ve seen some threads around but some of them at least are a couple years old so I don’t know if it’s exactly the same issue and if the same solutions still apply, so I’d be grateful for assistance. I also realise there’s not a lot of technical information in this post, so if some specific information would be helpful to diagnose this problem, I would also love to get instructions not only on what information, but also how to obtain it since I’m new to Linux and it’s a bit different to windows.

Thank you for reading.

yancek · January 22, 2026, 10:01pm

Does that drive have a windows filesystem on it? Nvidia graphics cards are great ONE WINDOWS but often problematic on Linux. When you shut down and reboot, are you prompted to run a filesystem check on your Ubuntu partition(s)?

A method that works on a qwerty keyboard as well as many others using Linux is to simultaneously hold down the Alt and prtsc/Sysrq key and while holding them down, tap consecutively the reisub keys to reboot or reisuo keys to shutdown. Powering off by using the power button is a good way to corrupt a filesystem.

Have you looked at the log files in /var/log after you have this problem?

Try posting some information on your specific graphics card. The page at the link below gives a number of methods to get detailed information.

https://www.cyberciti.biz/faq/linux-tell-which-graphics-vga-card-installed/

anonymousdormouse · January 23, 2026, 2:50pm

Hi yancek, thank you for looking into this.

The drive that gets issues is a NTFS drive, and it does have a windows reserved partition.
The Ubuntu partitions do not seem to get any errors themselves after the crashes, I’m not prompted to check on them and they seem to work fine.
The Nvidia graphics card is a Nvidia GeForce RTX 4060.
I’ve been on the recommended Nvidia driver (nvidia-driver-580-open) but today I saw that there’s a new one (nvidia-driver-580-open) so I’ve updated. I’ll update the main post if this solves my issues
I see now that the log keeps regularly giving me this message: kernel: audit: type=1400 audit(1769178625.125:405): apparmor=“DENIED” operation=“open” class=“file” profile=“snap.firefox.firefox” name=“/proc/pressure/memory” pid=4912 comm=“MemoryPoller” requested_mask=“r” denied_mask=“r” fsuid=1000 ouid=0 which seems like it could be related since videos in Firefox looked like a potential issue. I don’t know what exactly MemoryPoller is though.

EDIT:

Upon restart post Nvidia driver update I also noticed these messages:

warning: `gnome-system-mo’ uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211

tracker-miner-fs-3[7351]: (tracker-extract-3:7351): GLib-GIO-CRITICAL **: 17:00:05.556: g_file_get_path: assertion ‘G_IS_FILE (file)’ failed
tracker-miner-fs-3[7351]: (tracker-extract-3:7351): GLib-GIO-CRITICAL **: 17:00:05.556: GTask 0x62a4d9f4e210 (source object: 0x62a4d9f30410, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
tracker-miner-fs-3[7351]: (tracker-extract-3:7351): GLib-GIO-CRITICAL **: 17:00:05.556: g_file_new_for_uri: assertion ‘uri != NULL’ failed

EDIT 2:

I was able to watch at least one full YouTube video, but Arknights still crashed the PC. I was using System Monitor to check how the PC was doing as I was playing the game, and at the point where the PC froze, again with the audio looping, everything at least looked normal on that front, so I can’t tell from that what might be the issue.

EDIT 3:

Crashed without having video or game open, but Firefox was open. It seems that it might more be a question about time than what exactly is happening? Copy pasting the logs from Logs that were marked as important:

19:47:04 gdm3: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
19:46:59 kernel: /dev/sr0: Can't open blockdev
19:46:52 systemd: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-3358.scope - Application launched by gnome-session-binary.
19:46:46 gdm3: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
19:46:45 gdm-session-wor: gkr-pam: unable to locate daemon control file
19:45:38 (udev-worker): event17: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
19:45:38 kernel: 
19:45:38 kernel: uvcvideo 1-9.4.1:1.1: Failed to set UVC probe control : -32 (exp. 26).
19:45:14 kernel: hid-generic 0003:1532:0531.0002: No inputs registered, leaving
19:45:14 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
19:45:14 kernel: x86/cpu: VMX (outside TXT) disabled by BIOS

uusijani · January 24, 2026, 5:06pm

Cool, I’m not going crazy! I’ve had a very, very similar issue for a couple of weeks now. Identical in fact, except for the triggers and frequency: three incidents so far, since the first one on January 11th, with the last two within two days earlier this week. In all instances I’ve had Twitch playing video in Librewolf, when suddenly the desktop freezes, leaving only a half-second clip of the audio looping endlessly. I had forgotten about magic SysRq, so I have yet to try if it works; I’ve also just done a hard reset instead.

If the logs posted by anonymousdormouse are related to the issue, then that’s one difference wrt. what’s happening here: there’s been nothing related to the problem in any logs. The system seems to just die completely, instantly.

My Ubuntu 24.04 is on an NVMe drive instead of a HDD, and it’s the only OS on the drive. It’s using a standard ext4 filesystem, so it should be (and so far has been) safe from getting corrupted by the abrupt shutdown.

I have done one pass of memtest to rule out memory errors.

My system doesn’t have Nvidia; instead it’s using the integrated GPU of a Core i7-8700 with two external displays (one DP-connected, one HDMI-). (This is a Dell XPS desktop that originally came with an external Nvidia GPU, but I ripped it right out before installing the system. I’ve had enough bad experiences with Nvidia to know to avoid them whenever possible.)

uusijani · January 24, 2026, 5:15pm

Actually, had this only occurred this week, I might have put my money on it being caused by the “biggest ‘solar radiation storm’ in 23 years”. But, alas, I did have that one incident on the 11th.

timo-jyrinki · January 25, 2026, 6:51am

Can you first check which kernel you are on?

uname -a

Are you on the 6.8 series or the hwe, currently at 6.14.

If I’d be having such a problem, I’d try to go back to earlier kernel versions - one or more are available in the boot menu under Advanced options.

According to https://launchpad.net/ubuntu/+source/linux-hwe-6.14/6.14.0-37.37~24.04.1 (linked from https://launchpad.net/ubuntu/+source/linux-hwe-6.14) the latest 6.14 series kernel has been there since 2025-12-10, so if you have both installed it right away back then and rebooted the computer, you should have experienced the problem after that in case it would be caused by the kernel.

Current 6.8 series kernel (90.91) has been available since mid-December.

So you should currently be able to, if you get to the boot menu, select something older than those two to try out. Although note that new kernel in both series is in “proposed” and might replace the current one soon, at which point also older kernels might be automatically cleaned away from your system.

If you continue to have the problem also with the older kernel (please post uname -a also from there), then one can rule a kernel bug out.

uusijani · January 25, 2026, 7:29am

Right, I’m on (the non-HWE) 6.8 series:

Linux saegusa 6.8.0-90-generic #91-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 18 14:14:30 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

According to /var/log/apt/history.log*, I installed it freshly back in December (2025-12-12), and journalctl shows I’d rebooted the next day (the 13th), so have been running it ever since.

Since this is so rare an occurrence on my system, hopefully @anonymousdormouse has the ability to try older/newer kernels with their easily repeatable trigger.

anonymousdormouse · January 25, 2026, 11:34am

Hi,

I’m on 6.14.0-37-generic, and that was the only option in my advanced boot options, aside from starting in recovery mode.

Linux [My Unit's Name] 6.14.0-37-generic #37~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 20 10:25:38 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

I installed Ubuntu in January on this PC, so this is probably the only version it’s had right now. The issues didn’t present right away, though. Is it possible/advisable to download an older kernel to test if it’s a kernel issue?

uusijani · January 25, 2026, 12:16pm

So we’re running different kernels, even curiouser and curiouser.

You’re right that the one you currently have probably has been the only one it’s had since installing (judging from 6.14’s publishing history).

Could you check to see which updates, if any, you’ve installed just prior to the lockups starting? The log files should be under /var/log/apt/ as history.log (the most recent), then history.1.gz (next newest) etc. The .log files are plain text. The .gz ones are compressed, so have to be decompressed first, or, if you’re comfortable with the command line, you can use zless to view them directly.

To me this does look like a kernel issue, but if any non-kernel updates are the trigger, you could perhaps work around the issue by downgrading the package(s), if you can pinpoint which one(s) started the issue.

anonymousdormouse · January 25, 2026, 3:07pm

The issues started somewhere the 21st I think, so I included a few more days here. Most of this was just me running sudo apt update / upgrade or running updates through App Center and Software, with the exception of installing the Hiuon driver for my pen tablet. As a note, that driver seems to be working just fine on my laptop, which was changed from Win10 to Ubuntu earlier this autumn, so while it’s not impossible that it is causing problems I don’t think it’s the culprit.

Additionally, today I seem to be running Firefox and media in Firefox okay (so far), but the game still crashed the PC after some tens of minutes.

Update Logs

Start-Date: 2026-01-19 22:46:01
Commandline: packagekit role=‘install-files’
Requested-By: [My Username] (1000)
Install: huiontablet:amd64 (15.0.0.175)
End-Date: 2026-01-19 22:46:10

Start-Date: 2026-01-20 20:10:27
Commandline: apt upgrade
Requested-By: [My Username] (1000)
Upgrade: libavahi-common-data:amd64 (0.8-13ubuntu6, 0.8-13ubuntu6.1), libavahi-common-data:i386 (0.8-13ubuntu6, 0.8-13ubuntu6.1), libavahi-core7:amd64 (0.8-13ubuntu6, 0.8-13ubuntu6.1), avahi
-daemon:amd64 (0.8-13ubuntu6, 0.8-13ubuntu6.1), libavahi-common3:amd64 (0.8-13ubuntu6, 0.8-13ubuntu6.1), libavahi-common3:i386 (0.8-13ubuntu6, 0.8-13ubuntu6.1), libavahi-glib1:amd64 (0.8-13u
buntu6, 0.8-13ubuntu6.1), thermald:amd64 (2.5.6-2ubuntu0.24.04.2, 2.5.6-2ubuntu0.24.04.3), libavahi-client3:amd64 (0.8-13ubuntu6, 0.8-13ubuntu6.1), libavahi-client3:i386 (0.8-13ubuntu6, 0.8-
13ubuntu6.1)
End-Date: 2026-01-20 20:10:46

Start-Date: 2026-01-22 13:46:11
Commandline: apt upgrade
Requested-By: [My Username] (1000)
Upgrade: libopencc1.1:amd64 (1.1.7+ds1-1build1, 1.1.7+ds1-1ubuntu0.1), libglib2.0-bin:amd64 (2.80.0-6ubuntu3.6, 2.80.0-6ubuntu3.7), gir1.2-glib-2.0:amd64 (2.80.0-6ubuntu3.6, 2.80.0-6ubuntu3.
7), libglib2.0-data:amd64 (2.80.0-6ubuntu3.6, 2.80.0-6ubuntu3.7), libopencc-data:amd64 (1.1.7+ds1-1build1, 1.1.7+ds1-1ubuntu0.1), libglib2.0-0t64:amd64 (2.80.0-6ubuntu3.6, 2.80.0-6ubuntu3.7)
, libglib2.0-0t64:i386 (2.80.0-6ubuntu3.6, 2.80.0-6ubuntu3.7)
End-Date: 2026-01-22 13:46:24

Start-Date: 2026-01-22 16:42:03
Commandline: apt autoremove
Requested-By: [My Username] (1000)
Remove: librados2:amd64 (19.2.3-0ubuntu0.24.04.1), librdmacm1t64:amd64 (50.0-2ubuntu0.2), bridge-utils:amd64 (1.7.1-1ubuntu2), lxc:amd64 (1:5.0.3-2ubuntu7.2), fakechroot:amd64 (2.20.1+ds-15), librbd1:amd64 (19.2.3-0ubuntu0.24.04.1), libfakeroot:amd64 (1.33-1), lxcfs:amd64 (5.0.4-1), arch-test:amd64 (0.21-1), libsubid4:amd64 (1:4.13+dfsg1-4ubuntu3.2), liblxc-common:amd64 (1:5.0.3-2ubuntu7.2), genisoimage:amd64 (9:1.1.11-3.5), libllvm19:amd64 (1:19.1.1-1ubuntu1~24.04.2), libboost-iostreams1.83.0:amd64 (1.83.0-2.1ubuntu3.1), libpmemobj1:amd64 (1.13.1-1.1ubuntu2), libfakechroot:amd64 (2.20.1+ds-15), qemu-utils:amd64 (1:8.2.2+ds-0ubuntu1.11), libfile-fcntllock-perl:amd64 (0.22-4ubuntu5), debootstrap:amd64 (1.0.134ubuntu1), libaio1t64:amd64 (0.3.113-6build1.1), cloud-image-utils:amd64 (0.33-1), libdaxctl1:amd64 (77-2ubuntu2), libboost-thread1.83.0:amd64 (1.83.0-2.1ubuntu3.1), libdistro-info-perl:amd64 (1.7build1), liburing2:amd64 (2.5-1build1), mmdebstrap:amd64 (1.4.3-6), uidmap:amd64 (1:4.13+dfsg1-4ubuntu3.2), libdpkg-perl:amd64 (1.22.6ubuntu6.5), libpam-cgfs:amd64 (1:5.0.3-2ubuntu7.2), qemu-block-extra:amd64 (1:8.2.2+ds-0ubuntu1.11), libndctl6:amd64 (77-2ubuntu2), lxc-templates:amd64 (3.0.4.79.g84b0597-1), python3-gbinder:amd64 (1.3.0), liblxc1t64:amd64 (1:5.0.3-2ubuntu7.2), libpmem1:amd64 (1.13.1-1.1ubuntu2), fakeroot:amd64 (1.33-1), libglibutil:amd64 (1.0.80), libiscsi7:amd64 (1.19.0-3build4), libgbinder:amd64 (1.1.43)
End-Date: 2026-01-22 16:42:31

Start-Date: 2026-01-23 16:43:31
Commandline: packagekit role=‘remove-packages’
Requested-By: [My Username] (1000)
Remove: libxnvctrl0:amd64 (510.47.03-0ubuntu4), libnvidia-common-580:amd64 (580.95.05-0ubuntu0.24.04.3), libnvidia-fbc1-580:amd64 (580.95.05-0ubuntu0.24.04.3), linux-modules-nvidia-580-open-generic-hwe-24.04:amd64 (6.14.0-37.37~24.04.1), libnvidia-gl-580:amd64 (580.95.05-0ubuntu0.24.04.3), libnvidia-gl-580:i386 (580.95.05-0ubuntu0.24.04.3), libnvidia-extra-580:amd64 (580.95.05-0ubuntu0.24.04.3), nvidia-compute-utils-580:amd64 (580.95.05-0ubuntu0.24.04.3), libnvidia-encode-580:amd64 (580.95.05-0ubuntu0.24.04.3), nvidia-utils-580:amd64 (580.95.05-0ubuntu0.24.04.3), xserver-xorg-video-nvidia-580:amd64 (580.95.05-0ubuntu0.24.04.3), pkgconf:amd64 (1.8.1-2build1), libnvidia-decode-580:amd64 (580.95.05-0ubuntu0.24.04.3), libnvidia-egl-wayland1:amd64 (1:1.1.13-1ubuntu0.1), libnvidia-egl-wayland1:i386 (1:1.1.13-1ubuntu0.1), nvidia-kernel-common-580:amd64 (580.95.05-0ubuntu0.24.04.3), linux-modules-nvidia-580-open-6.14.0-37-generic:amd64 (6.14.0-37.37~24.04.1), nvidia-kernel-source-580-open:amd64 (580.95.05-0ubuntu0.24.04.3), nvidia-prime:amd64 (0.8.17.2), screen-resolution-extra:amd64 (0.18.3ubuntu0.24.04.1), nvidia-settings:amd64 (510.47.03-0ubuntu4), pkg-config:amd64 (1.8.1-2build1), nvidia-driver-580-open:amd64 (580.95.05-0ubuntu0.24.04.3), libnvidia-cfg1-580:amd64 (580.95.05-0ubuntu0.24.04.3), pkgconf-bin:amd64 (1.8.1-2build1), libpkgconf3:amd64 (1.8.1-2build1), libnvidia-compute-580:amd64 (580.95.05-0ubuntu0.24.04.3), nvidia-firmware-580-580.95.05:amd64 (580.95.05-0ubuntu0.24.04.3)
End-Date: 2026-01-23 16:44:10

Start-Date: 2026-01-23 16:44:36
Commandline: packagekit role=‘install-packages’
Requested-By: [My Username] (1000)
Install: libxnvctrl0:amd64 (510.47.03-0ubuntu4, automatic), libnvidia-common-590:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), libnvidia-fbc1-590:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), libnvidia-fbc1-590:i386 (590.48.01-0ubuntu0.24.04.1, automatic), libnvidia-gl-590:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), libnvidia-gl-590:i386 (590.48.01-0ubuntu0.24.04.1, automatic), libnvidia-extra-590:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), nvidia-compute-utils-590:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), linux-modules-nvidia-590-open-generic-hwe-24.04:amd64 (6.14.0-37.37~24.04.1+2), nvidia-kernel-source-590-open:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), libnvidia-encode-590:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), libnvidia-encode-590:i386 (590.48.01-0ubuntu0.24.04.1, automatic), nvidia-utils-590:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), xserver-xorg-video-nvidia-590:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), nvidia-driver-590-open:amd64 (590.48.01-0ubuntu0.24.04.1), pkgconf:amd64 (1.8.1-2build1, automatic), libnvidia-decode-590:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), libnvidia-decode-590:i386 (590.48.01-0ubuntu0.24.04.1, automatic), libnvidia-egl-wayland1:amd64 (1:1.1.13-1ubuntu0.1, automatic), libnvidia-egl-wayland1:i386 (1:1.1.13-1ubuntu0.1, automatic), nvidia-kernel-common-590:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), nvidia-prime:amd64 (0.8.17.2, automatic), nvidia-firmware-590-590.48.01:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), screen-resolution-extra:amd64 (0.18.3ubuntu0.24.04.1, automatic), nvidia-settings:amd64 (510.47.03-0ubuntu4, automatic), pkg-config:amd64 (1.8.1-2build1, automatic), linux-modules-nvidia-590-open-6.14.0-37-generic:amd64 (6.14.0-37.37~24.04.1+2, automatic), libnvidia-cfg1-590:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), pkgconf-bin:amd64 (1.8.1-2build1, automatic), libpkgconf3:amd64 (1.8.1-2build1, automatic), libnvidia-compute-590:amd64 (590.48.01-0ubuntu0.24.04.1, automatic), libnvidia-compute-590:i386 (590.48.01-0ubuntu0.24.04.1, automatic)
End-Date: 2026-01-23 16:45:35

Start-Date: 2026-01-23 17:19:45
Commandline: apt upgrade
Requested-By: [My Username] (1000)
Upgrade: libxml2:amd64 (2.9.14+dfsg-1.3ubuntu3.6, 2.9.14+dfsg-1.3ubuntu3.7), libxml2:i386 (2.9.14+dfsg-1.3ubuntu3.6, 2.9.14+dfsg-1.3ubuntu3.7)
End-Date: 2026-01-23 17:19:50

uusijani · January 25, 2026, 3:46pm

Thanks. I had hoped for either some correlation with my history.log, or something connected to drawing/rendering the desktop, but nothing jumps out from those, alas. The nvidia/libnvidia-* ones from the 23rd would be the obvious suspect, except you had already posted about the problems (above) when those packages were getting installed.

The apparmor denials for Firefox seem to be a known issue. I don’t use Firefox (and back when I did, I used the Mozilla PPA version instead of the snap), but I suspect they’re not related to the freeze. At least not unless you’re running particularly low on memory.

anonymousdormouse · January 25, 2026, 3:56pm

Yes, I saw that thread too. The apparmor denials look like they’re happening to most if not all of the apps installed through the App Center, so I suspect that’s not the issue either since it’s not all of the programs that cause freezes (as far as I know at this time).

anonymousdormouse · January 27, 2026, 12:06pm

To be clear, I’m not running Windows when these issues happen, I’m on Ubuntu. I have Windows installed on a completely separate drive, as outlined in my initial post. I’ve been monitoring my system when the crashes happen, and there’s no unusual stress on memory or CPU, and the temperatures have been well within normal range. My data is backed up, since I did that when installing Ubuntu now in January, and I’ve backed up again since.

Since last I’ve moved to using flatpak applications instead of snaps to see if the apparmor errors were the cause, and it did let me use my PC without issues yesterday. However, today I had another crash. According to the log, the last errors before the crash were of the following types:

13:09:14 gnome-shell: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x9600003
13:09:14 gnome-shell: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x9600003
13:09:01 gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).

And a lot more variations of these. ^

13:08:29 tracker-miner-f: Could not execute sparql: Constraint would be broken: UNIQUE constraint failed: rdfs:Resource.ID

This one also occurred periodically. ^

13:06:51 Discord: 13:06:51.493 › The resource https://discord.com/assets/dd24010f3cf7def7.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.

This one occurred a couple of times. ^

Seeing as gnome and tracker-miner-f messages are almost always around when the crashes happen I suspect the issues lie around there, but I don’t understand what these errors really are and looking them up doesn’t really explain them to me. Most threads I find either end with some kind of update solving the OP’s issues or the thread just gets closed due to inactivity.

Aside from not using snap applications, the one difference between the successful session yesterday and the crash today would be that the software and game I played yesterday were installed on the same drive as Ubuntu, whereas the software I used today was installed on the drive that’s been getting issues due to the crashes. However, they also used to run fine before the crashes started happening, and some of the crashes occurred without that drive being mounted at all, so while something about connecting to that drive might trigger more frequent crashes (?) it doesn’t seem to me like that’s the cause.

EDIT: Another difference between yesterday and today is that yesterday I closed most programs to help the game run better, while today I had more windows open while running a less resource heavy game. If the window manager warnings are related to the crashes, that could be relevant. It would also be annoying, though, since I often want to run several applications at once.