System Summary:
OS: CachyOS rolling (last updated today)
Bootloader: Limine
Dekstop Enviornment: KDE Plasma 6.6.3-2.1 (Wayland)
Kernels: 6.19.9-1-cachyos, 6.18.19-1-cachyos, 7.0.rc4-1-cachyos
Storage: Crucial P310 4TB (BTRFS+LUKS)
Host: Framework 13 7040 Series
CPU: AMD Ryzen Ryzen 5 7640U 6c/12t@4.97GHz
iGPU: AMD Radeon 760M
eGPU: AMD Radeon RX 9070 XT (Gigabyte 9070 XT GAMING OC)
eGPU Dock: Razer Core X V2 (Thunderbolt 5 Dock)
RAM: Crucial 2x48GB 5600MHz soDIMM DDR5
Internal Display: 2256x1504@60hz
External Display (connected directly to the eGPU via Displayport): MSI MPG 491CQPX - 5120x1440@240Hz
Firmware info: fwupdmgr get-devices reports system firmware version 0.0.3.18, full command output at bottom of post.
Dmesg output after a GPU crash: 5caba09
Cachy built in bug report command on next boot (running it directly after the crash resulted in it just hanging): e6a4921
I recently (I say recently, this has been ongoing for over a month at this point) purchased a Razer Core X v2 and a 9070 XT to connect to my laptop, after using ewagner12/all-ways-egpu to set the boot_vga and KDE compositor variables to eGPU I managed to get everything running on it.
This resulted in severe instability initially, I was able to partially curb this with the following kernel cmdline parameters:
amdgpu.dcdebugmask=0x12 pcie_aspm=native
amdgpu.pcie_gen_cap=0x40000 amdgpu.runpm=0 pci=realloc=on amdgpu.fw_load_type=1 amdgpu.gfxoff=0
Other things I’ve tried:
- Using the other USB4 port - no impact
- Reseating the GPU - no impact
- Switching between Stable / LTS / RC kernels - no impact
- A myriad of cmdline options, although I can’t remember all of them. I do remember amd_iommu=off and iommu=soft though these either resulted in the system not booting at all or didn’t fix the issue.
Unfortunately, this didn’t completely resolve the issue and it’s ongoing. Though the dmesg log above reveals an interesting crash reason that I wasn’t expecting; The “dev sda” device that is failing is a pseudo storage device built into the monitor, presumably as a target for firmware updates. This is completely independent of the eGPU, plugged directly into the laptop via a USB A expansion card, meaning the issue isn’t isolated to the GPU.
Having realised this I began to recall several USB related issues I’d had with this laptop that I had just chalked up to general instability:
- Before the purchase of my eGPU I had a dock that I plugged my displays into directly, occasionally this would just bug out and not pick up my displays properly, even after several reboots resulting in me having to switch to using the other USB4 port located on the other side of my laptop - for a long time I was just switching back and forth.
- When I upgraded to my current drive I copied over data from my old drive and another I had prior to consolidate my data. After some time (10-15mins) this would result in the transfer failing with rsync outputting “I/O error” for every remaining file. At the time I blamed the enclosure, as it seemed significantly more likely.
Picture of the screen after a crash below, occasionally it would partially recover but never fully, most times it just stayed like this until a force power down:
Sometimes I can switch to another TTY with the built in keyboard, which only appears on the internal display and has been useful for gathering logs after the event.
Additionally, the laptop never shuts down normally, requiring a force shutdown to stop and sometimes fails on boot, typically in 1 of 3 ways:
- The CachyOS logo animation will finish and it will just hang
- The card isn’t detected, shows up in boltctl but not as a PCIe device
- The card is detected but the external display
I also sometimes see some kind of log reporting the failure of /dev/sda though I can ctrl+c out of that and resume normal boot.
This USB revelation took longer than I care to admit to figure out, so here’s some more info specifically about the GPU crashing that I gathered:
The most reproducible crash I’ve found is starting a match of Who’s your Daddy, but I’ve also had crashes in Dark Souls 3, Cyberpunk 2077 (always while in menus like my inventory or visiting a ripperdoc), Drive Beyond Horizons Demo, RV There Yet and Detroit Become Human (rarely), any website with too many images also causes frequent crashes (the easiest example is image searching).
Stress tests with Furmark run perfectly fine so it’s not just a case of the GPU failing under load.
I’ve tested this on a fresh Windows 11 enterprise N LTSC install and it all works flawlessly after installing adrenalin.
It’s also worth noting I had the same issue on Fedora 43’s KDE Spin before switching to CachyOS on the 22nd of Feb.
It’s really difficult to say whether it’s a hardware fault that Windows is handling more gracefully or a driver issue on the Linux side, but if it were the latter I’d imagine there would be more reports of it, though I’ve seen none.
Thank you in advance for any help on this, let me know if I missed any info that would be beneficial to diagnostics. 
Firmware info:
$ fwupdmgr get-devices
Framework Laptop 13 (AMD Ryzen 7040Series)
Unknown Device:
Device ID: e8c00d3909edc557a6d6401f8abff30590abb50b
Vendor: PNP:MSI
GUID: 064e84b0-c513-5c57-822f-0932c3b9c38c ← DRM\VEN_MSI&DEV_4FA8
Unknown Device:
Device ID: c98a8aa6aae9d4dedaaaea3e6cea9f4abeea16bc
Current version: 1539
Vendor: Genesys (USB:0x05E3)
GUIDs: 33bf0d51-f87e-54a0-bbfc-efb323601e31 ← BLOCK\VEN_05E3&DEV_0749
a3a4cb07-8f50-594c-abf0-aa474a03dd94 ← BLOCK\VEN_05E3&DEV_0749&VER_15&CID_E3054907
Device Flags: • Updatable
• Cryptographic hash verification is available
• Unsigned Payload
• Can tag for emulation
CT4000P310SSD8:
Device ID: 03281da317dccd2b18de2bd1cc70a782df40ed7e
Summary: NVM Express solid state drive
Current version: V8CR010
Vendor: Micron/Crucial Technology (PCI:0xC0A9)
Serial Number: 25395336D047
GUIDs: c5d4beb4-6903-5a8c-b6c2-12f5f3cf2ce3 ← NVME\VEN_C0A9&DEV_5426
858d2566-307b-562c-a694-6aff10416e75 ← NVME\VEN_C0A9&DEV_5426&SUBSYS_C0A94100
c3d86786-7f7d-5236-a4ef-07fe661d79ce ← CT4000P310SSD8
Device Flags: • Internal device
• Updatable
• System requires external power source
• Needs a reboot after installation
• Device is usable for the duration of the update
• Can tag for emulation
Optix Driver:
Device ID: 770b0d59988fef96bfe22e1c9c2ec487734a5040
Summary: SCSI device
Current version: 1.00
Vendor: MSI (USB:0x1462, SCSI:MSI)
GUIDs: 5d48d4da-4011-537d-8153-60ab70986c45 ← BLOCK\VEN_1462&DEV_3FA4
b116a97e-5d0e-5de6-bd41-a696a83ce4c3 ← SCSI\VEN_MSI&DEV_Optix-Driver
d9171856-08d1-55b4-b837-83f22cbda7cc ← SCSI\VEN_MSI&DEV_Optix-Driver&REV_1.00
Device Flags: • Can tag for emulation
PIXA3854:00 093A:0274:
Device ID: 2555c513c826db32fa938b47ca1eeace640bbaa1
Summary: Touchpad
Current version: 0x0704
Vendor: Pixart Imaging, Inc. (HIDRAW:0x093A)
GUID: 2a62ed27-652b-5223-8a24-53e40176e152 ← HIDRAW\VEN_093A&DEV_0274
Device Flags: • Updatable
• Unsigned Payload
• Can tag for emulation
Ryzen 5 7640U w/ Radeon 760M Graphics:
Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027
Current version: 0x0a70410a
Vendor: AMD
GUIDs: 2a1df9de-fe02-59c8-8af1-32c8bb011f94 ← CPUID\PRO_0&FAM_19&MOD_74
5a4bca32-6547-584f-bb36-920d9adede25 ← CPUID\PRO_0&FAM_19&MOD_74&STP_1
Device Flags: • Internal device
Radeon 760M Graphics:
Device ID: 83eba1fa14bdefee1f6b4bcf06069b298e1c338f
Summary: AMD AMD_PHOENIX_GENERIC
Current version: 1
Vendor: AMD (PCI:0x1002)
GUID: 4a1501b7-b500-5255-9d9c-41d652a4d5bc ← AMD\113-PHXGEN
Device Flags: • Internal device
• Can tag for emulation
NE135FBM-N41:
Device ID: aec1a869eb0df71b7cea6b3ac71d39b830faf164
Vendor: PNP:BOE
GUID: 95f797c4-9a98-5557-b59b-ad2aa4f3f166 ← DRM\VEN_BOE&DEV_095F
Secure Processor:
Device ID: c54ab0237d7a8db8c717b68e0be78e4374a2a079
Summary: AGESA PhoenixPI-FP8-FP7 1.2.0.0e
Current version: 00.2d.00.88
Bootloader Version: 00.2d.00.88
Vendor: AMD (PCI:0x1022)
GUID: 9eb6a793-7f97-5fb5-b49c-139d2ce3ee46 ← PCI\VEN_1022&DEV_15C7
Device Flags: • Internal device
• Can tag for emulation
System Management Unit (SMU):
Device ID: db0330716216c629bb2c07256e5d018f499eb6ce
Summary: Microcontroller used within CPU/APU program 0
Current version: 76.101.0
Vendor: AMD
GUID: 3ac3159e-6eef-5f6b-bc8d-67686b238747 ← /sys/devices/platform/AMDI0009:00
Device Flags: • Internal device
• Can tag for emulation
TPM:
Device ID: 1d8d50a4dbc65618f5c399c2ae827b632b3ccc11
Current version: 6.4.1.383
Vendor: Microsoft (TPM:MSFT)
GUIDs: 2a65d4b6-60a0-5e8c-acfa-d86cc3cbe4c3 ← TPM\VEN_MSFT&DEV_0001
31a7bb1b-f5e1-53ff-b0e5-8692a21caed6 ← TPM\VEN_MSFT&MOD_Pluton.TPM.A
5bea8d58-c840-513e-a5ad-0184cbaa9821 ← TPM\VEN_MSFT&DEV_0001&VER_2.0
e02519c6-9139-5de8-89d4-9dca2f5c3b66 ← TPM\VEN_MSFT&MOD_Pluton.TPM.A&VER_2.0
Device Flags: • Internal device
• System requires external power source
• Needs a reboot after installation
• Device can recover flash failures
• Signed Payload
• Can tag for emulation
System Firmware:
Device ID: 1e4fa9cea0b89e613370cf9657ffa0b6d3f37fec
Summary: UEFI System Resource Table device (Updated via capsule-on-disk)
Current version: 0.0.3.18
Minimum Version: 0.0.3.6
Vendor: Framework (DMI:INSYDE Corp.)
Update State: Success
GUID: b5f7dcc1-568c-50f8-a4dd-e39d1f93fda1
Device Flags: • Internal device
• Updatable
• System requires external power source
• Supported on remote server
• Needs a reboot after installation
• Cryptographic hash verification is available
• Device is usable for the duration of the update
Device Requests: • Message
Platform Key:
Device ID: 6924110cde4fa051bfdc600a60620dc7aa9d3c6a
Summary: UEFI Platform Key
Current version: 2026
Vendor: Unknown
GUID: 4f874a00-f6bc-5b80-a04d-61d53a67c5e3 ← UEFI\CRT_F9BE19CDED1C73EC91188D812AAEC4FA7B428326
Device Flags: • Internal device
UEFI Key Exchange Key:
Device ID: 2a4c23bfb79b5dabe474cb7b1b3e604645d6f9c6
Device Flags: • Internal device
KEK CA:
Device ID: b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7
Current version: 2023
Vendor: Microsoft (UEFI:Microsoft)
GUIDs: 814e950f-1449-566a-a190-42c9d3a3a2df ← UEFI\VENDOR_Microsoft&NAME_Microsoft-KEK-CA
cd94ec34-7163-5f27-8549-1bd4b7872ae8 ← UEFI\CRT_DEC64D7746D983DB3774829A00BF829D9F19E9CF
Device Flags: • Internal device
• Updatable
• Needs a reboot after installation
• Device is usable for the duration of the update
• Signed Payload
• Can tag for emulation
Key Exchange Key:
Device ID: 7227626d9209595851b3840e3d626601a375ce2d
Current version: 2026
Update Error: No vendor ID set
GUID: 93273a34-4f65-58f7-9e55-1e02a2a33969 ← UEFI\CRT_C0085D2F64C0A53D47E25C5F551A62CD10F8ED9B
Device Flags: • Internal device
• Needs a reboot after installation
• Device is usable for the duration of the update
• Updatable
• Signed Payload
• Can tag for emulation
UEFI Signature Database:
Device ID: 0352a8acc949c7df21fec16e566ba9a74e797a97
Device Flags: • Internal device
Database Key:
Device ID: 0e3b4bfc8e1d26fa79855e17c4a13e4f4ddf316f
Current version: 2026
Update Error: No vendor ID set
GUID: 1e7ac361-a049-5d3d-9c0b-218f23c63fe4 ← UEFI\CRT_087616B061C20613A7976907FE487CCEA10C8EF1
Device Flags: • Internal device
• Needs a reboot after installation
• Updatable
• Signed Payload
• Can tag for emulation
Option ROM UEFI CA:
Device ID: 92120fc1a625f725901333cbfec152b8d6e42d43
Current version: 2023
Vendor: Microsoft (UEFI:Microsoft)
GUIDs: ca4668d9-734f-5b2b-aae8-8120b196f659 ← UEFI\VENDOR_Microsoft&NAME_Microsoft-Option-ROM-UEFI-CA
965d1919-0e18-5b63-9ebd-e5d122cd11df ← UEFI\CRT_F45B559FC1C60F31B3071021298D5ED7D77280B0
Device Flags: • Internal device
• Updatable
• Needs a reboot after installation
• Signed Payload
• Can tag for emulation
UEFI CA:
Device ID: 5bc922b7bd1adb5b6f99592611404036bd9f42d0
Current version: 2023
Vendor: Microsoft (UEFI:Microsoft)
GUIDs: 26f42cba-9bf6-5365-802b-e250eb757e96 ← UEFI\VENDOR_Microsoft&NAME_Microsoft-UEFI-CA
308281c7-d0c5-52e0-8c1a-810540de03df ← UEFI\CRT_7CD7437C555F89E7C2B50E21937E420C4E583E80
Device Flags: • Internal device
• Updatable
• Supported on remote server
• Needs a reboot after installation
• Signed Payload
• Can tag for emulation
Windows UEFI CA:
Device ID: d31da5f926c6d962ed810b284fab5a2ef623007b
Current version: 2023
Vendor: Microsoft (UEFI:Microsoft)
GUIDs: 914015a8-9d92-5462-9a9b-f2b361e4faae ← UEFI\VENDOR_Microsoft&NAME_Windows-UEFI-CA
89a825bf-78b5-5f1c-905b-e982b2f02584 ← UEFI\CRT_A794240D25F0CCB2EC8142DC2F7411890717DEAD
Device Flags: • Internal device
• Updatable
• Needs a reboot after installation
• Signed Payload
• Can tag for emulation
UEFI dbx:
Device ID: 362301da643102b9f38477387e2193e57abaa590
Summary: UEFI revocation database
Vendor: Microsoft (UEFI:Microsoft)
Install Duration: 1 second
GUIDs: e9da603f-619c-5e1b-8573-48afde905498 ← UEFI\CRT_1B3B6ADBF6EC5B6E58FDCAC989037C1644101FD7F63D01490CF8E0A243D540C7&ARCH_X64
f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
d07ff664-b0e1-5f4e-a723-d7fbcbfcb94f ← UEFI\CRT_3CD3F0309EDAE228767A976DD40D9F4AFFC4FBD5218F2E8CC3C9DD97E8AC6F9D&ARCH_X64
Device Flags: • Internal device
• Updatable
• Supported on remote server
• Needs a reboot after installation
• Device is usable for the duration of the update
• Only version upgrades are allowed
• Signed Payload
• Can tag for emulation
USB3 HUB:
Device ID: b46022468451d79b1c327f101949ab71372371b6
Current version: 59.82
Vendor: Intel (USB:0x8087)
GUID: 2ede67ed-35a0-5e45-91d7-cb699b570d2f ← TBT-0127000c
Device Flags: • Updatable
• Signed Payload
• Can tag for emulation