Forum Discussion

09SADEK's avatar
09SADEK
Newcomer
1 day ago

Crash on match start (DXGI_ERROR_DEVICE_HUNG) — Intel Iris Xe

System:

  • Laptop: ASUS Vivobook K5504VA (BIOS updated to latest)
  • GPU: Intel Iris Xe Graphics, driver 32.0.101.7088 (confirmed current/latest for this GPU family via Device Manager and Task Manager)
  • OS: Windows 11, version 25H2, build 26100.1.amd64fre.ge_release.240331-1435

Issue:
FC 27 crashes every time I start a match, at the loading screen right before kickoff. It's 100% reproducible — happens every single attempt, regardless of graphics settings.

  • On DirectX 12: the entire system fully freezes/hard-locks, requiring a forced reboot.
  • On DirectX 11: the game throws a recoverable crash instead of freezing the whole system:

Direct function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG ("The GPU will not respond to more commands"). GPU: "Intel(R) Iris(R) Xe Graphics", Driver: 32.0.101.7088.

Troubleshooting already completed (issue persists through all of this):

  • Clean driver reinstall via DDU in Safe Mode, followed by a fresh install of the latest official Intel driver (32.0.101.7088) directly from intel.com
  • Updated laptop BIOS to the latest version (this fixed a separate full-system-freeze/firmware-throttling issue, but not this crash)
  • Verified/repaired game files through the EA App
  • Fully uninstalled the game and deleted all leftover config/cache folders (Documents, AppData, LocalAppData, ProgramData) before a clean reinstall
  • Tested both DirectX 11 and DirectX 12
  • Set all graphics settings to their lowest possible values (Graphics Preset 0, Graphics Quality 0, all individual quality sliders at 0, 720p/1080p tested, render scale 0.5, borderless windowed mode, VSync off, dynamic resolution off, FPS capped at 30)
  • Increased the Windows TDR timeout delay (TdrDelay/TdrDdiDelay) — no change
  • Disabled overlay software and tested with a clean boot (only essential services running)
  • Ran the game as administrator

None of the above resolved the crash. Attaching the Windows crash dump (.mdmp) from a DX11 crash — analysis of it shows the exception occurs at the boundary between the game's Engine.Render.Core2.PlatformPcDx12.dll render layer and Intel's DX12 driver stack (igd12um64xel.dll, igc1464.dll shader compiler), consistent with a GPU command hang rather than a hardware or driver-version issue.

crashing

Recent Discussions