[ASUS TUF Gaming A15] Freeze with kernel dump

[Thegrayjedi]

Distribution (run cat /etc/os-release): NAME="Pop!_OS" VERSION="22.04 LTS" ID=pop ID_LIKE="ubuntu debian" PRETTY_NAME="Pop!_OS 22.04 LTS" VERSION_ID="22.04" HOME_URL="https://pop.system76.com" SUPPORT_URL="https://support.system76.com" BUG_REPORT_URL="https://github.com/pop-os/pop/issues" PRIVACY_POLICY_URL="https://system76.com/privacy" VERSION_CODENAME=jammy UBUNTU_CODENAME=jammy LOGO=distributor-logo-pop-os

Related Application and/or Package Version (run apt policy $PACKAGE NAME): Any application can cause a system freeze or green screen. Freezes are much less common with the c-state fix I implimented, green screens are still frequent.

Issue/Bug Description:

- Nov  2 20:22:33 pop-os kernel: [ 1250.506396] BUG: kernel NULL pointer dereference, address: 0000000000000005
- Nov  2 20:22:33 pop-os kernel: [ 1250.506404] #PF: supervisor write access in kernel mode
- Nov  2 20:22:33 pop-os kernel: [ 1250.506407] #PF: error_code(0x0002) - not-present page
- Nov  2 20:22:33 pop-os kernel: [ 1250.506409] PGD 230858067 P4D 230858067 PUD 273146067 PMD 27337e067 PTE 0
- Nov  2 20:22:33 pop-os kernel: [ 1250.506413] Oops: 0002 [#1] PREEMPT SMP NOPTI
- Nov  2 20:22:33 pop-os kernel: [ 1250.506416] CPU: 2 PID: 8617 Comm: RimWorldWin64.e Tainted: P           OE      6.0.3-76060003-generic #202210211149~1666452039~22.04~1891946
- Nov  2 20:22:33 pop-os kernel: [ 1250.506418] Hardware name: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA506IV_TUF506IV/FA506IV, BIOS FA506IV.320 06/01/2022
- Nov  2 20:22:33 pop-os kernel: [ 1250.506420] RIP: 0010:__smp_call_single_queue+0x9b/0xa0
- Nov  2 20:22:33 pop-os kernel: [ 1250.506425] Code: 89 c7 e9 58 73 04 01 48 89 de 48 c7 c7 80 e8 fd 8a 48 89 55 e0 e8 25 4e 57 00 48 8b 55 e0 eb 9a 66 66 2e 0f 1f 84 00 00 00 00 <00> 0f 1f 40 00 0f 1f 44 00 00 55 bf 01 00 00 00 48 89 e5 e8 cd f0
- Nov  2 20:22:33 pop-os kernel: [ 1250.506426] RSP: 0018:ffffbbbe03f9bc40 EFLAGS: 00010097
- Nov  2 20:22:33 pop-os kernel: [ 1250.506428] RAX: 0000000000004000 RBX: 00000000000312c0 RCX: 0000000000000000
- Nov  2 20:22:33 pop-os kernel: [ 1250.506430] RDX: ffff992e009e4c80 RSI: 0000000000000000 RDI: 0000000000000005
- Nov  2 20:22:33 pop-os kernel: [ 1250.506431] RBP: ffffbbbe03f9bc58 R08: 0000000000000000 R09: 0000000000000000
- Nov  2 20:22:33 pop-os kernel: [ 1250.506432] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000005
- Nov  2 20:22:33 pop-os kernel: [ 1250.506433] R13: 0000000000000005 R14: ffff99350f7712c0 R15: 0000000000000005
- Nov  2 20:22:33 pop-os kernel: [ 1250.506434] FS:  00007f0682d01740(0000) GS:ffff99350f680000(0000) knlGS:0000000067fe0000
- Nov  2 20:22:33 pop-os kernel: [ 1250.506436] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
- Nov  2 20:22:33 pop-os kernel: [ 1250.506437] CR2: 0000000000000005 CR3: 0000000116882000 CR4: 0000000000350ee0
- Nov  2 20:22:33 pop-os kernel: [ 1250.506438] Call Trace:
- Nov  2 20:22:33 pop-os kernel: [ 1250.506440]  <TASK>
- Nov  2 20:22:33 pop-os kernel: [ 1250.506443]  __smp_call_single_queue+0x61/0xa0
- Nov  2 20:22:33 pop-os kernel: [ 1250.506446]  ttwu_queue_wakelist+0x139/0x1c0
- Nov  2 20:22:33 pop-os kernel: [ 1250.506449]  try_to_wake_up+0x1f9/0x660
- Nov  2 20:22:33 pop-os kernel: [ 1250.506451]  ? get_user_pages_fast+0x24/0x60
- Nov  2 20:22:33 pop-os kernel: [ 1250.506454]  wake_up_q+0x50/0xa0
- Nov  2 20:22:33 pop-os kernel: [ 1250.506455]  futex_wake+0x15f/0x190
- Nov  2 20:22:33 pop-os kernel: [ 1250.506457]  do_futex+0xd7/0x230
- Nov  2 20:22:33 pop-os kernel: [ 1250.506459]  __x64_sys_futex+0x78/0x1f0
- Nov  2 20:22:33 pop-os kernel: [ 1250.506461]  ? __secure_computing+0x9b/0x110
- Nov  2 20:22:33 pop-os kernel: [ 1250.506464]  ? syscall_trace_enter.constprop.0+0xb5/0x1c0
- Nov  2 20:22:33 pop-os kernel: [ 1250.506466]  do_syscall_64+0x5c/0x90
- Nov  2 20:22:33 pop-os kernel: [ 1250.506469]  ? filp_close+0x60/0x80
- Nov  2 20:22:33 pop-os kernel: [ 1250.506471]  ? exit_to_user_mode_prepare+0x3b/0xd0
- Nov  2 20:22:33 pop-os kernel: [ 1250.506473]  ? syscall_exit_to_user_mode+0x2a/0x50
- Nov  2 20:22:33 pop-os kernel: [ 1250.506474]  ? do_syscall_64+0x69/0x90
- Nov  2 20:22:33 pop-os kernel: [ 1250.506476]  ? sysvec_apic_timer_interrupt+0x4e/0xb0
- Nov  2 20:22:33 pop-os kernel: [ 1250.506477]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
- Nov  2 20:22:33 pop-os kernel: [ 1250.506480] RIP: 0033:0x7f0682e00acd
- Nov  2 20:22:33 pop-os kernel: [ 1250.506482] Code: bf 0d 00 0f 05 eb a1 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 73 83 0d 00 f7 d8 64 89 01 48
- Nov  2 20:22:33 pop-os kernel: [ 1250.506484] RSP: 002b:000000000017f9e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
- Nov  2 20:22:33 pop-os kernel: [ 1250.506485] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f0682e00acd
- Nov  2 20:22:33 pop-os kernel: [ 1250.506486] RDX: 000000007fffffff RSI: 0000000000000001 RDI: 00007f068122f950
- Nov  2 20:22:33 pop-os kernel: [ 1250.506487] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
- Nov  2 20:22:33 pop-os kernel: [ 1250.506488] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
- Nov  2 20:22:33 pop-os kernel: [ 1250.506489] R13: 000000000017fa00 R14: 0000000000000003 R15: 0000000000000002
- Nov  2 20:22:33 pop-os kernel: [ 1250.506492]  </TASK>
- Nov  2 20:22:33 pop-os kernel: [ 1250.506493] Modules linked in: ntfs3 tls ccm rfcomm snd_seq_dummy snd_hrtimer cmac algif_hash algif_skcipher af_alg bnep nvidia_uvm(POE) snd_sof_amd_renoir snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci iwlmvm snd_hda_codec_hdmi snd_sof intel_rapl_msr snd_sof_utils snd_hda_intel intel_rapl_common snd_intel_dspcfg snd_intel_sdw_acpi binfmt_misc snd_soc_core mac80211 snd_hda_codec snd_usb_audio uvcvideo snd_compress videobuf2_vmalloc snd_hda_core ac97_bus snd_usbmidi_lib videobuf2_memops snd_pcm_dmaengine videobuf2_v4l2 snd_hwdep snd_rpl_pci_acp6x snd_seq_midi videobuf2_common snd_acp_pci btusb nvidia_drm(POE) snd_seq_midi_event btrtl snd_pci_acp6x edac_mce_amd nvidia_modeset(POE) btbcm snd_rawmidi snd_pci_acp5x libarc4 snd_seq nls_iso8859_1 btintel videodev snd_pcm kvm_amd asus_nb_wmi btmtk snd_seq_device nvidia(POE) iwlwifi snd_rn_pci_acp3x asus_wmi joydev mc input_leds snd_timer kvm bluetooth platform_profile snd_acp_config ledtrig_audio snd_soc_acpi
- Nov  2 20:22:33 pop-os kernel: [ 1250.506532]  ecdh_generic serio_raw wmi_bmof snd_pci_acp3x ecc hid_multitouch efi_pstore sparse_keymap snd rapl k10temp ucsi_ccg ucsi_acpi cfg80211 ccp typec_ucsi soundcore typec asus_wireless mac_hid sch_fq_codel kyber_iosched ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear system76_io(OE) system76_acpi(OE) usbhid r8153_ecm cdc_ether usbnet r8152 mii amdgpu iommu_v2 gpu_sched i2c_algo_bit drm_buddy drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt r8169 fb_sys_fops i2c_nvidia_gpu nvme hid_generic crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel ahci aesni_intel crypto_simd cryptd drm nvme_core libahci i2c_piix4 xhci_pci nvme_common xhci_pci_renesas i2c_ccgx_ucsi realtek wmi i2c_hid_acpi i2c_hid video hid
- Nov  2 20:22:33 pop-os kernel: [ 1250.506583] CR2: 0000000000000005
- Nov  2 20:22:33 pop-os kernel: [ 1250.506585] ---[ end trace 0000000000000000 ]---
- Nov  2 20:22:33 pop-os kernel: [ 1250.660316] RIP: 0010:__smp_call_single_queue+0x9b/0xa0
- Nov  2 20:22:33 pop-os kernel: [ 1250.660328] Code: 89 c7 e9 58 73 04 01 48 89 de 48 c7 c7 80 e8 fd 8a 48 89 55 e0 e8 25 4e 57 00 48 8b 55 e0 eb 9a 66 66 2e 0f 1f 84 00 00 00 00 <00> 0f 1f 40 00 0f 1f 44 00 00 55 bf 01 00 00 00 48 89 e5 e8 cd f0
- Nov  2 20:22:33 pop-os kernel: [ 1250.660331] RSP: 0018:ffffbbbe03f9bc40 EFLAGS: 00010097
- Nov  2 20:22:33 pop-os kernel: [ 1250.660334] RAX: 0000000000004000 RBX: 00000000000312c0 RCX: 0000000000000000
- Nov  2 20:22:33 pop-os kernel: [ 1250.660335] RDX: ffff992e009e4c80 RSI: 0000000000000000 RDI: 0000000000000005
- Nov  2 20:22:33 pop-os kernel: [ 1250.660336] RBP: ffffbbbe03f9bc58 R08: 0000000000000000 R09: 0000000000000000
- Nov  2 20:22:33 pop-os kernel: [ 1250.660338] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000005
- Nov  2 20:22:33 pop-os kernel: [ 1250.660340] R13: 0000000000000005 R14: ffff99350f7712c0 R15: 0000000000000005
- Nov  2 20:22:33 pop-os kernel: [ 1250.660341] FS:  00007f0682d01740(0000) GS:ffff99350f680000(0000) knlGS:0000000067fe0000
- Nov  2 20:22:33 pop-os kernel: [ 1250.660343] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
- Nov  2 20:22:33 pop-os kernel: [ 1250.660345] CR2: 0000000000000005 CR3: 0000000116882000 CR4: 0000000000350ee0`

Steps to reproduce (if you know): Just let the machine run any program that barely sips the CPU/GPU

Expected behavior: No crashing

Other Notes: I've already fixed the processor c-states bug, so I'm not sure what caused this freeze. This is the first time the kernel decided to report what happened though.

[Thegrayjedi]

Oh, and a clean Neofetch just in case:

• OS: Pop!_OS 22.04 LTS x86_64
• Host: ASUS TUF Gaming A15 FA506IV_TUF506IV 1.0
• Kernel: 6.0.3-76060003-generic
• Uptime: 18 mins
• Packages: 2528 (dpkg), 45 (flatpak), 9 (snap)
• Shell: bash 5.1.16
• Resolution: 1920x1080
• DE: GNOME 42.3.1
• WM: Mutter
• WM Theme: Pop
• Theme: Pop-dark [GTK2/3]
• Icons: Pop [GTK2/3]
• Terminal: gnome-terminal
• CPU: AMD Ryzen 7 4800H with Radeon Graphics (16) @ 2.900GHz
• GPU: AMD ATI 06:00.0 Renoir
• GPU: NVIDIA GeForce RTX 2060 Mobile
• Memory: 3067MiB / 31515MiB

[Thegrayjedi]

New error that caused a softlock that I couldn't recover from even using a TTY terminal.

• Nov 03 04:19:16 pop-os kernel: watchdog: BUG: soft lockup - CPU#8 stuck for 26s! [Compositor:10468]
• Nov 03 04:19:16 pop-os kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 26s! [IPDL Background:10414]
• Nov 03 04:19:16 pop-os kernel: watchdog: BUG: soft lockup - CPU#11 stuck for 26s! [Softwar~cThread:10453]

[Thegrayjedi]

My last boot log, in case there are some errors in there that may be causing the issue: https://termbin.com/3dxg

[jacobgkau]

A kernel crash would typically either be caused by a bug in the kernel (possibly a driver), or by a hardware defect/failure. What hardware are you using? (Your steps to reproduce, "Just let the machine run any program that barely sips the CPU/GPU," obviously don't work on all systems.)

---

System76 customers can reach out to support for technical assistance. For non-System76 hardware, you can seek community support on Reddit or Mattermost.

[Thegrayjedi]

Is the Neofetch I posted not enough info? It has the CPU, both GPUs, laptop model number, total ram, ect.

[jacobgkau]

Ah, I missed it in the wall of text, sorry. (I just edited your initial description to have a working code block for the log output-- it's three backticks on their own line before and after.)

[Thegrayjedi]

Oh, excellent, thanks. I tried a code entry, but the text all ran together so I tried a bullet point instead.

[jacobgkau]

By "finally" in the issue title, I assume you mean this issue has been occurring for some time (i.e. not just with a recent kernel update?) Or do you suspect it's related to a recent update?

Have you checked if the same issue occurs on any other Linux distributions with the same or different kernel versions? (Assuming you can recreate the issue from a live USB, it sounds like you may be able to check without installing.)

[Thegrayjedi]

So the problems actually started early 2021 with Windows 10. It began with a few occasional BSODs, and graduated with 3-4 BSODs per hour with complete system freezes and sudden shutdowns, nothing being written to crash dumps. I was at a total loss. After tons of research, I determined it was a combination of software and driver issues (Win10 likes to push updates that are incompatible with hybrid-gaming laptops and then MAYBE fix the issue a month later, when they push new updates that cause even more issues.)

So I did the only thing I could think of, I switched to Linux. Right away, I experienced MUCH less crashing, but freezing was still somewhat frequent and Green Screen of Death issues were intermittent. That was on Deepin Linux. I switched to PopOS because it was supposed to handle NVidia Optimus laptops far better (Deepin couldn't handle my graphics switching at all). I noticed a immediate performance increase, but freezing and green screen issues were still around.

After about a month of research, I solved 90% of the freezes by fixing the Processor C-States. However the GSoD still persists. I recently discovered my GPU fan isn't working at all under PopOS because it can not even communicate with it, so I may need to switch to a distro like Nobara that has built-in Asus controller software. However, I confirmed the GSoD isn't heat related. I benchmarked the system, pushing CPU and GPU to 100%, and both thermal throttled like they should to prevent critical heat overload. I'm guessing it is the NVidia drivers causing the issue, as my log shows issues loading the USBC drivers.

Anyway, that is where I currently am, with the Nobara ISO sitting on a Ventoy USB stick waiting for install.

[mmstick]

GPU fans are controlled by firmware, and it should already have a fan curve defined without any OS intervention.

AsusCtl is a Rust application, so it's easy to install in Pop!_OS

sudo apt install cargo libclang-dev libudev-dev
git clone https://gitlab.com/asus-linux/asusctl
make
sudo make install
systemctl daemon-reload
systemctl restart asusd

[Thegrayjedi]

Huh, I'll give it a shot but was told asusctl would not work without patching the kernel, which I can't do.

[mmstick]

Depends on your model. I read that the most recent 2022 models need Linux 6.1.0 to use their MUX switch. Which you can get at https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.1-rc3/ But that might cause issues with the NVIDIA drivers since I'm not sure if it's supported by released drivers yet.

[Thegrayjedi]

Laptop is a 2020 model, GPU switch is software. I wish I had a proper MUX switch, lol. Anyway, build failed. It can't find "fontconfig" even though it is installed. Guessing PoPOS hides it in a unexpected spot or something, and I can't figure out what file to edit to fix it.

[mmstick]

Maybe you just need libfontconfig-dev installed. Pop/Ubuntu doesn't have it in an unexpected location.

[Thegrayjedi]

I'll try that.

Edit: Ok, that worked. Install went smooth as well, and following commands have been run. Now to grab the GUI extension for Gnome and play with this a bit. Thanks, @mmstick I hope this works.

[Thegrayjedi]

Sadly, nothing. No fan control. All I have is the ability to control the battery max charge, and a LED slider that doesn't seem to do anything. Pretty sure I need a kernel patched with ASUS specific tweaks before I'll see the fan controls.

[Thegrayjedi]

So, I still haven't switched to Nobara yet, because something odd has transpired. This morning, I experienced a freeze, and a green screen. Now I've been running a solid 10 hours with neither. I highly doubt my issue is fixed, but it makes me wonder if maybe some driver is failing to load 4 out of 5 times maybe?

Very odd. I'll keep a eye on it.

[Thegrayjedi]

I think I may have isolated another system crash. The text scrolled by really fast (System crashed to a terminal that scrolled text and then auto-rebooted). The majority of errors I saw were NVME related, and since both of my storage drives are NVME m.2 drives, it must have been a driver crash, or possibly a PCIE error. Does anyone know if Linux or PopOS has issues with NVME drives?

[Thegrayjedi]

Just passed nvme_core.default_ps_max_latency_us=0 to the kernel via kernelstub, should disable the power saving feature on the NVME drives, lets see if it was another "device goes to deep sleep and never awakens" issue.

Edit: I've taken to calling this the Sleeping Beauty Syndrome.

[Thegrayjedi]

Nice, deep probe of my system is here now: https://linux-hardware.org/?probe=66b6e49eb5

[mmstick]

You're still having issues after setting that?

[Thegrayjedi]

Not sure why I would stop having issues after seeing the probe? Yes, it lists some hardware with issues, but what can I do about it? Half of that hardware is soldered into the mainboard.

[mmstick]

Nothing besides wait for a future kernel update that may one day fix it.

[Thegrayjedi]

I know at this point I need a new USBC hub and a new WiFi card, that might fix the remaining issues. And I'm happy that with Linux I was able to make my system far more stable than Windows ever was. (Mainly due to Linux logging every tiny action, and Windows only logging something when it feels like it.)

Anyway, I'll keep on top of it. If I manage to find the final culprit, I'll put it here for future FA506IV users, esp since I'm sending a few to PopOS.

[Thegrayjedi]

Found another freeze issue. I started to notice this at the end of my log once in a while:

(root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)

After searching thru the logs, I found out it is a regular thing. However, once in a while, it would run, complete and then the system stops logging anything after that point. Then 3-5 minutes after that, the system would freeze up requiring a power cycle. This seemed unusual to me, so i installed a overlay that monitored CPU, GPU and Ram total use. During one of my games, I noticed everything immediately went to 100% and the system froze. After looking thru the logs, I found that cron job was the last thing to be logged before the freeze. So I did the following:

sudo apt remove sysstat

So far (2 days) I haven't had a repeat of this issue. Thought I'd report it, since I found a few others having a issue with the same program (sysstat), although nobody who reported a issue was using PopOS, just base Ubuntu.

[mmstick]

That's good to know

[Thegrayjedi]

Ok, so today I got another green screen after several un-logged system freezes, and the system rebooted with VERY limited wifi function. Checked the logs and kept seeing communication issues with USB port 5-2, which according to lsusb, was my AX200 wifi card. Had this error many times before, and I have had a suspicion for a while now that the wifi card was the root of the green screen crashing. Attempted a reboot, and the system refused to boot back in. Kept spitting errors on USB port 5-2.

At this point, I cracked the laptop open, yanked out the AX200 and put the old stock wifi card back in (Lesson here kids, save your old parts). System booted fine, and at first there were zero USB errors. Now I'm seeing a new 5-2 error and new errors on 4-1! Starting to think my USB controller in this laptop is having issues. Although, the wifi card is supposed to be PCIe, no idea why they would route it like a USB device. Anyway, errors are below, I'll keep on top of this.

usb usb5-port2: unable to enumerate USB device usb 5-2: device not accepting address 7, error -62

usb usb4-port1: Cannot enable. Maybe the USB cable is bad?

The 4-1 error MIGHT be for the HDD dock I have. It has it's own power source with USB out and a SD Card reader, and I keep it turned off when not in use. Maybe the laptop is suddenly trying to connect it while it is powered off? No idea.

[mmstick]

Maybe you could try disabling system76-power and restarting? It could simply be a firmware problem if it runs fine in Windows. There's still some improvements for ASUS TUF laptops in Linux 6.1.0 that's not quite here yet. I've seen a report of using Ethernet on a similar ASUS TUF laptop causing the firmware to abruptly reboot.

[Thegrayjedi]

Doesn't run windows at all anymore. Before I switched to Linux, I was getting 10 or more freezes and BSODs per day. The reliability monitor was bottomed out, lol. Recently, I did try to do a win10 reinstall, and the system just refused to install it, let alone boot into it.

Not sure what has caused all the issues with this thing, could be a major hardware issue that requires a chip replacement or something. I'll keep updating on it.

[mmstick]

Have you tried blacklisting the ucsi_acpi module?

[Thegrayjedi]

Not even sure how to do that, or how to recover my system should that brick the whole thing.

[Ceikry]

I've been having many similar issues to you, except I'm on a ROG Zephyrus G14. I haven't 100% confirmed it yet, as less than 24 hours have passed since turning the setting on, but I believe there's a significant chance I fixed the Green Screen of Death by changing the PowerMizer settings in nvidia control panel to "Prefer Maximum Performance".

As for the other freezes, I've been dealing with those occasionally as well, and here's some interesting info that was logged just before my most recent freeze, this one featuring still-functional-mouse-movement, but everything else was locked up (and couldn't switch tty's or anything else)

Jan 07 21:21:44 pop-os kernel: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
Jan 07 21:21:44 pop-os kernel: CPU: 14 PID: 1719 Comm: Xorg Tainted: P           OE      6.0.12-76060006-generic #202212290932~1671652965~22.04~452ea9d
Jan 07 21:21:44 pop-os kernel: Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401IH_GA401IH/GA401IH, BIOS GA401IH.212 03/14/2022
Jan 07 21:21:44 pop-os kernel: RIP: 0010:ep_poll+0x35c/0x370
Jan 07 21:21:44 pop-os kernel: Code: 0f 85 47 fd ff ff 48 8b 43 78 48 83 f8 ff 0f 95 c0 0f b6 c0 e9 34 fd ff ff 48 c7 85 78 ff ff ff 00 00 00 00 45 31 f6 e9 04 fd <ff> ff 48 8b 85 70 ff ff >
Jan 07 21:21:44 pop-os kernel: RSP: 0018:ffffb5aa05553dd0 EFLAGS: 00010283
Jan 07 21:21:44 pop-os kernel: RAX: ffff9cb44324e4cd RBX: ffff9cb44324e480 RCX: 0000000000000000
Jan 07 21:21:44 pop-os kernel: RDX: ffff9cb44324e4d0 RSI: 00007ffd4f90d9c0 RDI: ffff9cb44324e480
Jan 07 21:21:44 pop-os kernel: RBP: ffffb5aa05553e60 R08: ffff9cb442879300 R09: 0000000000000000
Jan 07 21:21:44 pop-os kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000100
Jan 07 21:21:44 pop-os kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 00000000ffffffea
Jan 07 21:21:44 pop-os kernel: FS:  00007ffb4bf28a80(0000) GS:ffff9cb75f980000(0000) knlGS:0000000000000000
Jan 07 21:21:44 pop-os kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 07 21:21:44 pop-os kernel: CR2: 00007ff2d0b36000 CR3: 000000011412e000 CR4: 0000000000350ee0
Jan 07 21:21:44 pop-os kernel: Call Trace:
Jan 07 21:21:44 pop-os kernel:  <TASK>
Jan 07 21:21:44 pop-os kernel:  ? _copy_to_user+0x25/0x60
Jan 07 21:21:44 pop-os kernel:  ? __fget_light+0xaf/0x150
Jan 07 21:21:44 pop-os kernel:  do_epoll_wait+0xbd/0xe0
Jan 07 21:21:44 pop-os kernel:  __x64_sys_epoll_wait+0x60/0x110
Jan 07 21:21:44 pop-os kernel:  do_syscall_64+0x5c/0x90
Jan 07 21:21:44 pop-os kernel:  ? syscall_exit_to_user_mode+0x2a/0x50
Jan 07 21:21:44 pop-os kernel:  ? do_syscall_64+0x69/0x90
Jan 07 21:21:44 pop-os kernel:  ? do_syscall_64+0x69/0x90
Jan 07 21:21:44 pop-os kernel:  ? do_syscall_64+0x69/0x90
Jan 07 21:21:44 pop-os kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
Jan 07 21:21:44 pop-os kernel: RIP: 0033:0x7ffb4c325fde
Jan 07 21:21:44 pop-os kernel: Code: 10 89 7c 24 0c 89 4c 24 1c e8 ae aa f6 ff 44 8b 54 24 1c 8b 54 24 18 41 89 c0 48 8b 74 24 10 8b 7c 24 0c b8 e8 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 >
Jan 07 21:21:44 pop-os kernel: RSP: 002b:00007ffd4f90d990 EFLAGS: 00000293 ORIG_RAX: 00000000000000e8
Jan 07 21:21:44 pop-os kernel: RAX: ffffffffffffffda RBX: 00007ffd4f90d9c0 RCX: 00007ffb4c325fde
Jan 07 21:21:44 pop-os kernel: RDX: 0000000000000100 RSI: 00007ffd4f90d9c0 RDI: 0000000000000004
Jan 07 21:21:44 pop-os kernel: RBP: 000056338ab67a00 R08: 0000000000000000 R09: 0000000000000000
Jan 07 21:21:44 pop-os kernel: R10: 00000000ffffffff R11: 0000000000000293 R12: 000056338a6ce851
Jan 07 21:21:44 pop-os kernel: R13: 00007ffb4bf286f8 R14: 00007ffd4f90e614 R15: 0000000000000000
Jan 07 21:21:44 pop-os kernel:  </TASK>
Jan 07 21:21:44 pop-os kernel: Modules linked in: tls ccm rfcomm cmac algif_hash algif_skcipher af_alg snd_seq_dummy snd_hrtimer nvidia_uvm(POE) snd_sof_amd_renoir snd_sof_amd_acp snd_sof_p>
Jan 07 21:21:44 pop-os kernel:  kyber_iosched ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq >
Jan 07 21:21:44 pop-os kernel: ---[ end trace 0000000000000000 ]---
Jan 07 21:21:44 pop-os kernel: RIP: 0010:ep_poll+0x35c/0x370
Jan 07 21:21:44 pop-os kernel: Code: 0f 85 47 fd ff ff 48 8b 43 78 48 83 f8 ff 0f 95 c0 0f b6 c0 e9 34 fd ff ff 48 c7 85 78 ff ff ff 00 00 00 00 45 31 f6 e9 04 fd <ff> ff 48 8b 85 70 ff ff >
Jan 07 21:21:44 pop-os kernel: RSP: 0018:ffffb5aa05553dd0 EFLAGS: 00010283
Jan 07 21:21:44 pop-os kernel: RAX: ffff9cb44324e4cd RBX: ffff9cb44324e480 RCX: 0000000000000000
Jan 07 21:21:44 pop-os kernel: RDX: ffff9cb44324e4d0 RSI: 00007ffd4f90d9c0 RDI: ffff9cb44324e480
Jan 07 21:21:44 pop-os kernel: RBP: ffffb5aa05553e60 R08: ffff9cb442879300 R09: 0000000000000000
Jan 07 21:21:44 pop-os kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000100
Jan 07 21:21:44 pop-os kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 00000000ffffffea
Jan 07 21:21:44 pop-os kernel: FS:  00007ffb4bf28a80(0000) GS:ffff9cb75f800000(0000) knlGS:0000000000000000
Jan 07 21:21:44 pop-os kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 07 21:21:44 pop-os kernel: CR2: 00007fa6927f8000 CR3: 000000011412e000 CR4: 0000000000350ee0

[Ceikry]

Notably our crashes appear to be different, if I'm not mistaken it appears mine originated from Xorg while yours the RimWorld executable.

[Thegrayjedi]

Most of the ASUS laptops are very similar in build quality and parts used. It wouldn't surprise me if some random chip on the mainboard was causing all the issues for these laptops. I'll give the max performance a try, thanks! Are you having any other freezing issues? I've fixed quite a few, and can post those fixes here if you need them.

[Ceikry]

Most of the ASUS laptops are very similar in build quality and parts used. It wouldn't surprise me if some random chip on the mainboard was causing all the issues for these laptops. I'll give the max performance a try, thanks! Are you having any other freezing issues? I've fixed quite a few, and can post those fixes here if you need them.

Other than the one I attached to that post, there's also #2753 which I created a separate issue for as it was certainly a different problem.

If you have a solution for that one (other than the obvious disabling of pop-shop), please respond to it with that info :)

[Thegrayjedi]

The rimworld executable was just the one crash the logs happened to capture. There are tons of crashes that the logs didn't notice, and they happen at the weirdest times. I might minimize my browser, crash. I might close a folder, crash. Open a video, crash. Open a text document, crash. Ect.

[Ceikry]

If it's any comfort to you, I can rule out hardware being the cause of this particular issue. I had switched back to windows for 3-4 months hoping this problem would be fixed when I came back, and alas, it has not! My computer was completely stable on windows with absolutely no changes to any settings at all, indicating that it's almost certainly not a hardware issue.

[Thegrayjedi]

Ahh, thats the major difference. I switched to Linux because I was getting as many as 20 BSODs or Freezes per day on Windows. Very unstable. Linux cleared most of those issues up, and I'm hunting down the rest like Elmer Fudd on drugs.

[Ceikry]

Ah, still might not be a hardware issue. Windows can BSOD over even minor things. I had a similar scenario where Windows would BSOD dozens of times daily on one particular machine, switched to linux and it was completely smooth sailing for the rest of time.

[Thegrayjedi]

I replied to your thread with a question.

[Thegrayjedi]

Here is something interesting. An easily reproducable crash. Simply download any large file on this PC and wait. 85% of the time (Depending on how big it is) the system will lock up and require a power cycle. Weird, right?

[Thegrayjedi]

Most recent errors from the last 3 boots. Ignore anything about the WiFi, I just installed a new card this week, ironing the bugs out.

-- Boot f3cc4a8c378249a48bab4473f1a82008 --
Jan 18 10:59:43 pop-os kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP4.WLAN], AE_NOT_FOUND (20220331/dswload2-162)
Jan 18 10:59:43 pop-os kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
Jan 18 10:59:43 pop-os kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.THRM._SCP.CTYP], AE_NOT_FOUND (20220331/psargs-330)
Jan 18 10:59:43 pop-os kernel: ACPI Error: Aborting method \_TZ.THRM._SCP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Jan 18 10:59:43 pop-os kernel: 
Jan 18 10:59:44 pop-os kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Jan 18 10:59:44 pop-os kernel: ucsi_ccg 4-0008: i2c_transfer failed -110
Jan 18 10:59:44 pop-os kernel: ucsi_ccg 4-0008: ucsi_ccg_init failed - -110
Jan 18 10:59:44 pop-os kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
Jan 18 10:59:45 pop-os kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jan 18 10:59:45 pop-os smartd[1161]: Device: /dev/nvme0, number of Error Log entries increased from 2354 to 2357
Jan 18 10:59:45 pop-os gnome-session-binary[1490]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jan 18 10:59:45 pop-os gnome-session-binary[1490]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jan 18 10:59:45 pop-os pipewire[1460]: mod.x11-bell: XOpenDisplay() failed
Jan 18 10:59:53 pop-os gdm-password][2061]: gkr-pam: unable to locate daemon control file
Jan 18 10:59:53 pop-os pipewire[2742]: mod.x11-bell: XOpenDisplay() failed
Jan 18 10:59:55 pop-os systemd[2732]: Failed to start Application launched by gnome-session-binary.
Jan 18 11:00:01 pop-os gdm-launch-environment][1410]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jan 18 12:45:59 pop-os kernel: usb 3-4: Failed to query (SET_CUR) UVC control 10 on unit 2: -32 (exp. 2).
Jan 18 12:45:59 pop-os kernel: usb 3-4: Failed to query (SET_CUR) UVC control 4 on unit 1: -32 (exp. 4).
Jan 18 12:46:42 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 10 on unit 2: -32 (exp. 2).
Jan 18 12:46:42 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 4 on unit 1: -32 (exp. 4).
Jan 18 12:47:26 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 10 on unit 2: -32 (exp. 2).
Jan 18 12:47:26 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 4 on unit 1: -32 (exp. 4).
Jan 18 12:49:42 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 10 on unit 2: -32 (exp. 2).
Jan 18 12:49:42 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 4 on unit 1: -32 (exp. 4).
Jan 18 12:50:18 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 10 on unit 2: -32 (exp. 2).
Jan 18 12:50:18 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 4 on unit 1: -32 (exp. 4).
Jan 18 12:50:30 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 10 on unit 2: -32 (exp. 2).
Jan 18 12:50:30 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 4 on unit 1: -32 (exp. 4).
Jan 18 12:50:35 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 10 on unit 2: -32 (exp. 2).
Jan 18 12:50:35 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 4 on unit 1: -32 (exp. 4).
Jan 18 12:51:04 pop-os kernel: usb 3-4: Failed to query (SET_CUR) UVC control 10 on unit 2: -32 (exp. 2).
Jan 18 12:51:04 pop-os kernel: usb 3-4: Failed to query (SET_CUR) UVC control 4 on unit 1: -32 (exp. 4).
Jan 18 12:51:29 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 10 on unit 2: -32 (exp. 2).
Jan 18 12:51:29 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 4 on unit 1: -32 (exp. 4).
Jan 18 12:58:04 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 10 on unit 2: -32 (exp. 2).
Jan 18 12:58:04 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 4 on unit 1: -32 (exp. 4).
Jan 18 13:04:54 pop-os kernel: usb 3-4: Failed to query (SET_CUR) UVC control 10 on unit 2: -32 (exp. 2).
Jan 18 13:04:54 pop-os kernel: usb 3-4: Failed to query (SET_CUR) UVC control 4 on unit 1: -32 (exp. 4).
Jan 18 13:12:38 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 10 on unit 2: -32 (exp. 2).
Jan 18 13:12:38 pop-os kernel: usb 3-1.3: Failed to query (SET_CUR) UVC control 4 on unit 1: -32 (exp. 4).
Jan 18 14:18:43 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 14:18:59 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 14:19:04 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 14:19:20 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 14:19:30 pop-os kernel: usb 3-1.3: device not accepting address 10, error -62
Jan 18 14:19:41 pop-os kernel: usb 3-1.3: device not accepting address 10, error -62
Jan 18 14:19:47 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 14:20:02 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 14:20:08 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 14:20:23 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 14:20:36 pop-os kernel: usb 3-1.3: device not accepting address 13, error -62
Jan 18 14:20:47 pop-os kernel: usb 3-1.3: device not accepting address 14, error -62
Jan 18 14:20:47 pop-os kernel: usb 3-1-port3: unable to enumerate USB device
Jan 18 17:28:47 pop-os gdm3[1340]: Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: activation request failed: a conc>
Jan 18 17:28:47 pop-os kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Jan 18 17:28:47 pop-os systemd[2732]: Failed to start Portal service (GTK/GNOME implementation).
Jan 18 17:28:49 pop-os systemd-cryptsetup[79261]: device-mapper: remove ioctl on cryptswap  failed: Device or resource busy
-- Boot ced947157fa6415181b1c5f68d229089 --
Jan 18 17:29:49 pop-os kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP4.WLAN], AE_NOT_FOUND (20220331/dswload2-162)
Jan 18 17:29:49 pop-os kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
Jan 18 17:29:50 pop-os kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.THRM._SCP.CTYP], AE_NOT_FOUND (20220331/psargs-330)
Jan 18 17:29:50 pop-os kernel: ACPI Error: Aborting method \_TZ.THRM._SCP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Jan 18 17:29:50 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 17:29:50 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 17:29:50 pop-os kernel: 
Jan 18 17:29:51 pop-os kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Jan 18 17:29:51 pop-os kernel: ucsi_ccg 4-0008: i2c_transfer failed -110
Jan 18 17:29:51 pop-os kernel: ucsi_ccg 4-0008: ucsi_ccg_init failed - -110
Jan 18 17:29:51 pop-os kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
Jan 18 17:29:51 pop-os smartd[1084]: Device: /dev/nvme0, number of Error Log entries increased from 2357 to 2360
Jan 18 17:29:51 pop-os smartd[1084]: Warning via /usr/share/smartmontools/smartd-runner to root produced unexpected output (183 bytes) to STDOUT/STDERR:
Jan 18 17:29:51 pop-os smartd[1084]: /etc/smartmontools/run.d/10mail:
Jan 18 17:29:51 pop-os smartd[1084]: Your system does not have /usr/bin/mail.  Install the mailx or mailutils package
Jan 18 17:29:51 pop-os smartd[1084]: run-parts: /etc/smartmontools/run.d/10mail exited with return code 1
Jan 18 17:29:51 pop-os smartd[1084]: Warning via /usr/share/smartmontools/smartd-runner to root: failed (32-bit/8-bit exit status: 256/1)
Jan 18 17:29:51 pop-os gnome-session-binary[1473]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jan 18 17:29:51 pop-os gnome-session-binary[1473]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jan 18 17:29:52 pop-os pipewire[1442]: mod.x11-bell: XOpenDisplay() failed
Jan 18 17:30:07 pop-os gdm-password][2847]: gkr-pam: unable to locate daemon control file
Jan 18 17:30:07 pop-os pipewire[2868]: mod.x11-bell: XOpenDisplay() failed
Jan 18 17:30:09 pop-os systemd[2858]: Failed to start Application launched by gnome-session-binary.
Jan 18 17:30:09 pop-os systemd[2858]: Failed to start Application launched by gnome-session-binary.
Jan 18 17:30:09 pop-os systemd[2858]: Failed to start Application launched by gnome-session-binary.
Jan 18 17:30:13 pop-os gnome-session-binary[1473]: GLib-GIO-CRITICAL: g_dbus_connection_emit_signal: assertion 'object_path != NULL && g_variant_is_object_path (object_path)' failed
Jan 18 17:30:13 pop-os gnome-session-binary[1473]: CRITICAL: gsm_client_peek_id: assertion 'GSM_IS_CLIENT (client)' failed
Jan 18 17:30:13 pop-os gnome-session-binary[1473]: CRITICAL: gsm_client_peek_id: assertion 'GSM_IS_CLIENT (client)' failed
Jan 18 17:30:13 pop-os gnome-session-binary[1473]: GLib-CRITICAL: g_hash_table_find: assertion 'version == hash_table->version' failed
Jan 18 17:30:13 pop-os gdm-launch-environment][1392]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jan 18 17:39:19 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 17:39:35 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 17:39:40 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 17:39:56 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 17:40:07 pop-os kernel: usb 3-1.3: device not accepting address 13, error -62
Jan 18 17:40:18 pop-os kernel: usb 3-1.3: device not accepting address 13, error -62
Jan 18 17:40:23 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 17:40:39 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 17:40:44 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 17:41:00 pop-os kernel: usb 3-1.3: device descriptor read/64, error -110
Jan 18 17:41:12 pop-os kernel: usb 3-1.3: device not accepting address 16, error -62
Jan 18 17:41:23 pop-os kernel: usb 3-1.3: device not accepting address 17, error -62
Jan 18 17:41:23 pop-os kernel: usb 3-1-port3: unable to enumerate USB device
-- Boot b0180eab0be7427c8306608708e792d9 --
Jan 18 21:34:23 pop-os kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP4.WLAN], AE_NOT_FOUND (20220331/dswload2-162)
Jan 18 21:34:23 pop-os kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
Jan 18 21:34:23 pop-os kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.THRM._SCP.CTYP], AE_NOT_FOUND (20220331/psargs-330)
Jan 18 21:34:23 pop-os kernel: ACPI Error: Aborting method \_TZ.THRM._SCP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Jan 18 21:34:24 pop-os kernel: 
Jan 18 21:34:25 pop-os kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Jan 18 21:34:25 pop-os kernel: ucsi_ccg 4-0008: i2c_transfer failed -110
Jan 18 21:34:25 pop-os kernel: ucsi_ccg 4-0008: ucsi_ccg_init failed - -110
Jan 18 21:34:25 pop-os kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
Jan 18 21:34:25 pop-os kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jan 18 21:34:25 pop-os smartd[1143]: Device: /dev/nvme0, number of Error Log entries increased from 2360 to 2363
Jan 18 21:34:26 pop-os gnome-session-binary[1481]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jan 18 21:34:26 pop-os gnome-session-binary[1481]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jan 18 21:34:26 pop-os pipewire[1447]: mod.x11-bell: XOpenDisplay() failed
Jan 18 21:34:32 pop-os gdm-password][2026]: gkr-pam: unable to locate daemon control file
Jan 18 21:34:32 pop-os pipewire[2113]: mod.x11-bell: XOpenDisplay() failed
Jan 18 21:34:33 pop-os systemd[2100]: Failed to start Application launched by gnome-session-binary.
Jan 18 21:34:40 pop-os gdm-launch-environment][1398]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

[Thegrayjedi]

Freeze with an error message this time:

Jan 31 19:36:37 pop-os kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
Jan 31 19:36:37 pop-os kernel: BUG: unable to handle page fault for address: ffffffff8a803000
Jan 31 19:36:37 pop-os kernel: #PF: supervisor instruction fetch in kernel mode
Jan 31 19:36:37 pop-os kernel: #PF: error_code(0x0011) - permissions violation

[Thegrayjedi]

Unfortunately, lack of a few specific bits of software for Linux forced me back to Windows 10. This is no longer a PopOS issue, so closing it. Thanks all!