Same when I play Dragon's Dogma 2 (RE Engine specific??) on Fedora 43 using Proton Experimental. No launch options or mods. Vanilla install. Crashes occur randomly. Could be 10 minutes or 10 hours of game play. Usually I can get 1+ hours regularly, but about 10% of the time I get the same crash within the first hour.

System Information:

OS: Fedora Linux 43 (KDE Plasma Desktop Edition) x86_64
Kernel: Linux 7.2.4-100.fc43.x86_64
DE: KDE Plasma 6.7.5
WM: KWin (Wayland)
CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz
GPU 1: AMD Radeon RX 6750 XT


Steam Beta Branch:  Stable Client
Steam Version:  1788652215
Steam Client Build Date:  Wed, Sep 2, 2026 8:32 PM UTC -08:00
Steam Web Build Date:  Sat, Sep 5, 2026 6:13 PM UTC -08:00
Steam API Version:  SteamClient023

GPU + Driver

# lspci -vnn | grep -A3 VGA
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] [1002:73df] (rev c0) (prog-if 00 [VGA controller])
        Subsystem: Tul Corporation / PowerColor Device [148c:2419]
        Flags: bus master, fast devsel, latency 0, IRQ 108, IOMMU group 15
        Memory at f800000000 (64-bit, prefetchable) [size=16G]

# glxinfo | grep "OpenGL version"
OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.3.6

Initial logs. I'll try VKD3D_CONFIG=retain_descriptor_heaps, RADV_DEBUG=hang, and PROTON_LOG=1 launch options next time I play.

coredumpctl list --reverse
TIME                           PID  UID  GID SIG     COREFILE     EXE                                                           >
Sun 2026-09-13 00:59:02 CDT  21667 1000 1000 SIGABRT present      /usr/bin/plasma-keyboard                                      >
Sun 2026-09-13 00:44:28 CDT  21263 1000 1000 SIGABRT present      /usr/bin/Xwayland                                             >
Sun 2026-09-13 00:27:14 CDT   3718 1000 1000 SIGABRT present      /usr/bin/plasma-keyboard                                      >
Sun 2026-09-13 00:27:00 CDT   3943 1000 1000 SIGABRT present      /usr/libexec/org_kde_powerdevil                               >
Sun 2026-09-13 00:27:00 CDT   3730 1000 1000 SIGABRT present      /usr/bin/Xwayland                  

journalctl -k --since "2026-09-13 00:25" --until "2026-09-13 00:45" | grep -iE "amdgpu|gpu|reset|hang|fault|error"   
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:606)
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:  Process DD2.exe pid 14376 thread vkd3d_queue pid 14455
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:   in page starting at address 0x0000800052347000 from client 0x1b (UTCL2)
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501431
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:          Faulty UTCL2 client ID: SQC (data) (0xa)
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:          MORE_FAULTS: 0x1
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:          WALKER_ERROR: 0x0
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:          PERMISSION_FAULTS: 0x3
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:          MAPPING_ERROR: 0x0
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:          RW: 0x0
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:606)
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:  Process DD2.exe pid 14376 thread vkd3d_queue pid 14455
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:   in page starting at address 0x0000800052347000 from client 0x1b (UTCL2)
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:606)
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:  Process DD2.exe pid 14376 thread vkd3d_queue pid 14455
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:   in page starting at address 0x0000800052347000 from client 0x1b (UTCL2)
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:606)
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:  Process DD2.exe pid 14376 thread vkd3d_queue pid 14455
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:   in page starting at address 0x0000800052347000 from client 0x1b (UTCL2)
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:606)
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:  Process DD2.exe pid 14376 thread vkd3d_queue pid 14455
Sep 13 00:26:51 reddevil kernel: amdgpu 0000:03:00.0:   in page starting at address 0x0000800052347000 from client 0x1b (UTCL2)
Sep 13 00:26:53 reddevil kernel: amdgpu 0000:03:00.0: Dumping IP State
Sep 13 00:26:53 reddevil kernel: amdgpu 0000:03:00.0: Dumping IP State Completed
Sep 13 00:26:53 reddevil kernel: amdgpu 0000:03:00.0: [drm] AMDGPU device coredump file has been created
Sep 13 00:26:53 reddevil kernel: amdgpu 0000:03:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Sep 13 00:26:53 reddevil kernel: amdgpu 0000:03:00.0: ring gfx_0.0.0 timeout, signaled seq=32029962, emitted seq=32029965
Sep 13 00:26:53 reddevil kernel: amdgpu 0000:03:00.0:  Process DD2.exe pid 14376 thread vkd3d_queue pid 14449
Sep 13 00:26:53 reddevil kernel: amdgpu 0000:03:00.0: Starting gfx_0.0.0 ring reset
Sep 13 00:26:53 reddevil kernel: amdgpu 0000:03:00.0: Ring gfx_0.0.0 reset failed
Sep 13 00:26:53 reddevil kernel: amdgpu 0000:03:00.0: GPU reset begin!. Source:  1
Sep 13 00:26:53 reddevil kernel: amdgpu 0000:03:00.0: MODE1 reset
Sep 13 00:26:53 reddevil kernel: amdgpu 0000:03:00.0: GPU mode1 reset
Sep 13 00:26:53 reddevil kernel: amdgpu 0000:03:00.0: GPU smu mode1 reset
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: GPU reset succeeded, trying to resume
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: [drm] PCIE GART of 512M enabled (table at 0x0000008000F00000).
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: VRAM is lost due to GPU reset!
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: PSP is resuming...
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: reserve 0xa00000 from 0x82fd000000 for PSP TMR
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: RAS: optional ras ta ucode is not available
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: SECUREDISPLAY: optional securedisplay ta ucode is not available
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: SMU is resuming...
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: use vbios provided pptable
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: SMU is resumed successfully!
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: kiq ring mec 2 pipe 1 q 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: [drm] DMUB hardware initialized: version=0x02020022
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring comp_1.0.0 uses VM inv eng 4 on hub 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring comp_1.1.0 uses VM inv eng 5 on hub 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring sdma0 uses VM inv eng 13 on hub 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring sdma1 uses VM inv eng 14 on hub 0
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: ring jpeg_dec uses VM inv eng 5 on hub 8
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: GPU reset(2) succeeded!
Sep 13 00:26:54 reddevil kernel: amdgpu 0000:03:00.0: [drm] device wedged, but no recovery needed

Can confirm the same SQC (data) GPUVM protection fault on a different SKU (RX 9070 XT, Navi48/RDNA4, not Navi31), so this doesn't seem to be confined to one architecture generation.

Setup: AMD RX 9070 XT (gfx1201, RDNA4), Mesa/vulkan-radeon 26.2.3, CachyOS kernel 7.2.6-1, Monster Hunter Wilds AppID 2246340.

Reproduced on BOTH Proton Experimental (11.0-20260910b), GE-Proton 11-7

Variables ruled out via controlled testing:

Mods: the crash is reproduced on a completely vanilla install when launched via Steam (No mod manager involved). Also, reproduced with Fluorine (an MO2-style mod manager) plus REFramework with around 45 mods active. There was no difference in fault signature or frequency either way, so I want to say mods are not a factor and can be ruled out entirely.

Graphics settings tier: Reproduced identically at the Highest and Medium Graphic Settings, with all settings scaled down accordingly at Medium. Lowering the settings did not reduce frequency or change the fault signature, so this does not seem to be a load, timing, or thermal issue tied to render complexity.

RT, Upscaling, and Frame Generation: all three explicitly disabled in every single test run as they've been the cause of crashes in Windows and Linux in the past. None of the three is the trigger.

VKD3D_CONFIG=retain_descriptor_heaps did not prevent the crash and did not shift the fault client. It stayed SQC (data) every time, unlike the shift to TCP that was reported in issue #3047 for a different title.

Shader cache: cleared the Mesa shader cache, the vkd3d-proton cache, and the REFramework shader cache between test runs, with no effect on recurrence or timing of the crash.

Trigger surface appears to be much broader than just heavy combat VFX. One crash occurred mid-animation while sharpening a weapon with a whetstone, after hunting a Qualmatrice. Separately, on a fully vanilla install, another crash occurred while simply riding a Seikret across the map and gathering plants and crafting materials, this was done in the Plains area (not lush, the weather with a lot of honey) with no monsters, no combat, no hit effects, and no dense particle systems anywhere near the player. Given that this is one of the least demanding, lowest-intensity gameplay states in the entire game, this strongly suggests the fault is not related to GPU load, scene complexity, or combat intensity at all, but rather to some specific asset, material, or shader state transition that happens to occur during these seemingly unrelated activities, whether that is a gathering-interaction shader, a mount-riding animation blend, a whetstone-specific effect, or some shared underlying system all three momentarily touch.

Consistent fault every time, byte for byte identical in structure regardless of what the player was doing when it happened:

amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:X pasid:XXX)
amdgpu: in page starting at address 0x0000000000000000 from client 10
amdgpu: Faulty UTCL2 client ID: SQC (data) (0xa)
amdgpu: PERMISSION_FAULTS: 0x3
amdgpu: ring gfx_0.0.0 timeout

Have 4 saved devcoredump captures and multiple in-game contexts (combat, whetstone sharpening, mount riding/gathering). Hopefully, these are useful for debugging.

amdgpu-coredump-20260919_154302.txt
amdgpu-coredump-20260919_155136.txt
amdgpu-coredump-20260919_210927.txt
amdgpu-coredump-20260919_212512.txt

Edit
I set my graphical settings to max, ray tracing to highest, and added this paragraph of Launch Options on GE-Proton11-7 and was able to hunt a tempered rathian and frog without crashing:

VKD3D_CONFIG=dxr,no_upload_hvv,retain_descriptor_heaps RADV_DEBUG=no_nggc PROTON_FSR4_UPGRADE=1 PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 WINEDLLOVERRIDES="dinput8.dll,dstorage.dll,dstoragecore.dll=n,b" %command% /WineDetectionEnabled:False

I've had moments over the past few days where the crash just happens randomly, so this might be the case, but I thought I would flag this as the Rathian fight has a lot of particle effects involved and this fight took place in the plains biome.

Yeah, since you mentioned the outdated Launch Option, I figured some of the other Launch Options may had issues or were no longer necessary. I haven't played Monster Hunter in about a year. I deleted all shader caches and changed my Launch Options to:

WINEDLLOVERRIDES="dinput8.dll,dstorage.dll,dstoragecore.dll=n,b" %command% /WineDetectionEnabled:False

Then recompiled shaders and haven't had issues since. Was able to complete 10+ Hunts on Medium Settings and another 10 hunts with all the settings maxed out.

So I might've just been unlucky while compiling shaders or the Launch Options were at fault. Fought Tempered Arkveld and a few other demanding hunts and went up about ten Hunter Ranks.

Experienced this crash with the same setup while hunting Seregios near the end of the hunt in multiplayer, the crash is just super inconsistent.

Follow-up since my last comment (2026-09-23). Still hitting this consistently. (Every launch, sometimes within minutes of loading in, sometimes a few hunts in.)

Setup (updated):

• AMD RX 9070 XT (gfx1201, Navi48/RDNA4)
• Mesa/vulkan-radeon 26.2.3-1
• Kernel: CachyOS 7.2.7-1-cachyos
• Tested on both GE-Proton11-7 (stock) and a self-built vkd3d-proton from current master (commit 472989aa, includes 5505762a6 "Fix a signal ordering bug with racy GPU signals")

Variables/tweaks tested:

1. Filesystem (BTRFS/CoW) — full non-reflink copy to a fresh chattr +C (nodatacow) directory, verified attribute stuck. Crashed on first load, identical fault. Crashed again on a second run a few checkpoint saves in. Not the cause.
2. vkd3d-proton signal-ordering fix — built master (472989aa) from source, swapped DLLs into the live prefix (MD5-confirmed). Crash still occurred, identical fault. Doesn't touch this bug.
3. Discord GPU acceleration — disabled hardware accel entirely (--use-gl=disabled confirmed in process args). Crash still occurred, identical fault.
4. Launch Options Tested after crawling protondb again: WINEDLLOVERRIDES="dinput8.dll,dstorage.dll,dstoragecore.dll=n,b" VKD3D_CONFIG=descriptor_heap PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command% /WineDetectionEnabled:False
5. Game was launched via steam without custom DLLs, etc.

System changes since comment 5 days ago:
linux-cachyos kernel: 7.2.6-1 to 7.2.7-1 (2026-09-23) possibly relevant, I only see vesa-dsc-bpp, hdmi, and cgroup-vram changes?
Wine: 11.17-1.1 to 11.18-1.1 (2026-09-23): shouldn't be an impact to GE-Proton, right?
No Mesa, vulkan-radeon, or libdrm updates

Fault signature — byte-for-byte identical across every variable change: address always 0x0, client always SQC (data), PERMISSION_FAULTS: 0x3, same ring-reset pattern. That consistency across filesystem, driver build, background processes, mods, settings, and gameplay context reads as a deterministic code path, not a race — likely RADV/Mesa on RDNA4 rather than vkd3d-proton, though that's a hunch not a diagnosis.

Attaching a fresh devcoredump from today. Happy to test anything specific — repro rate is fast enough for quick turnaround.
amdgpu-coredump-20260925_133137.txt

Otherwise I am going to swap to Proton Experimental and keep trying to play the game lol.