Monster Hunter Wilds AT Arkvild Crash During Fight PC

What is the AT Arkvild Crash?

The Arch-Tempered Arkvild quest, added to Monster Hunter Wilds in the late-May 2026 title update, ships a new arena, two new VFX layers (volumetric ember + screen-space ash), and a dynamic weather transition mid-fight. The combination overwhelms several specific GPU/driver combos and produces a hard crash to desktop — usually as Arkvild enrages or as the storm rolls in around the 70% HP mark. The crash is fight-specific: the same hunter can play every other AT quest without issue.

When does it occur?

• During the cutscene that introduces Arkvild's enrage
• When the dynamic weather (storm) layer activates mid-fight
• On the arena transition from outer ring to inner crater
• When DLSS Frame Generation or FSR Frame Gen is enabled with ray tracing on
• During the final phase QTE with multiple particle systems on screen
• On loading back into the quest after a failed attempt

Common causes

• VRAM oversubscription on 8 GB cards (RTX 4060, RTX 5060, RX 7600)
• RTX 50 series Video Engine timeout under sustained encoder load (NVIDIA driver 575.xx series)
• AMD Adrenalin 26.4.x ray-tracing regression on RDNA 4 (RX 9070, RX 9070 XT)
• Frame Generation buffer corruption when arena transition fires mid-frame
• Texture streaming pipe stalling on slow SATA SSDs during the weather change
• HAGS (Hardware-Accelerated GPU Scheduling) conflict with the new volumetric pass
• REFramework / mods left active after the title update (frequent crash source)

Step-by-step fixes

1. Update GPU drivers to the Arkvild-ready branch: NVIDIA 581.42 Game Ready or newer (Capcom-validated), AMD Adrenalin 26.5.2 or newer. The Arkvild-specific game profile lives only in these branches.
2. Disable Frame Generation for this quest only: pause → Options → Graphics → Frame Generation → Off. Capcom acknowledged on the official forums that the FG buffer is mistimed during the storm transition.
3. Lower Texture Quality one notch: 8 GB cards must run at most "High" (not "Highest"). Watch dedicated VRAM in Task Manager → Performance → GPU during a non-AT fight; if it sits above 7.4 GB, lower further.
4. Disable HAGS: Settings → System → Display → Graphics → Default graphics settings → turn off "Hardware-accelerated GPU scheduling" → reboot. Re-test only this quest.
5. Use the "load before transition" workaround (community-validated): when Arkvild reaches ~75% HP, force a save by camping briefly at the tent, then re-engage. Pre-warms the storm assets in VRAM and avoids the mid-fight streaming spike.
6. Remove REFramework and all mods: delete dinput8.dll, the reframework folder, and any natives/STM/ overrides from the install directory. Verify integrity via Steam afterward.
7. Move the game to NVMe: SATA SSDs (especially older Crucial MX500 / Samsung 870 EVO) cannot keep up with the burst read during the weather transition. Move via Steam → Properties → Installed Files → Move install folder.
8. Vendor-specific tweak: On RTX 50 series, disable Shader Execution Reordering in NVIDIA Control Panel → Manage 3D Settings → Program Settings → MonsterHunterWilds.exe. On RX 9000 series, disable AMD Anti-Lag+ for this title in Adrenalin.

If it still doesn't work

If you crash inside the first 30 seconds of the quest, the cause is almost always shader cache — close the game, delete %LOCALAPPDATA%\CAPCOM\MonsterHunterWilds\shader_cache\, and let the engine recompile. If you crash specifically when DLSS/FSR is on with Ray Tracing High, you are hitting the same root cause as the [DLSS Frame Gen crash](/en/errors/monster-hunter-wilds-dlss-frame-gen-crash-pc); follow that guide and disable RT until Capcom's next hotfix.

RTX 50 owners seeing "Video Engine has timed out" in Event Viewer should treat this as the broader [RTX 50 driver crash](/en/errors/nvidia-rtx-50-series-driver-crash-video-engine-timeout) and apply the TDR registry workaround. For early-boss black-screen behaviour rather than crash-to-desktop, see [MH Wilds black screen crash](/en/errors/monster-hunter-wilds-crash-black-screen-pc).