DXGI_ERROR_DEVICE_HUNG in logs and silent game crash. Please help!

Technical Help
, , ,
1

  • Game Version:20260902.14983

  • Platform: Steam / Windows

  • Mods: Removed

  • Hardware Specifications & Operating System:

    • OS: Microsoft Windows 11 Pro, Build 26200
    • CPU: AMD Ryzen 7 5700X 8-Core Processor
    • GPU: NVIDIA GeForce RTX 4060, 8 GB VRAM
    • Current GPU Driver: 32.0.16.1664
    • RAM: 31.9 GB (32 GB)
    • Storage:
      • C: 930.6 GB total / 449.4 GB free - system
      • D: 931.5 GB total / 221 GB free - installed here!

  • Issue Date: September 4, 2026

  • Error Message: No visible error message. The attached crash report records GPU Crash dump Triggered and DXGI_ERROR_DEVICE_HUNG.

  • Details:

  • The game repeatedly crashes after approximately 10–15 minutes of gameplay.

    Previously, underclocking both the GPU core and GPU memory helped prevent these crashes. However, after an inZOI update, the crashes returned and underclocking no longer resolves the issue. Mods have been removed.

    The attached crash report is from September 3, 2026. It identifies a DirectX 12 GPU crash with the following information:

    • Crash type: GPUCrash
    • GPU crash reason: DXGI_ERROR_DEVICE_HUNG
    • Time since launch for this particular crash: 380 seconds
    • Map: /Game/Map/Gangnam_Map
    • Last recorded GPU temperature: 66°C
    • Recorded game VRAM usage: approximately 5,459 MB against a 7,080 MB budget
    • Available system RAM at crash: approximately 8.9 GB
    • Out-of-memory flag: MemoryStats.bIsOOM = 0
    • DLSS and Frame Generation were configured as enabled; ray tracing was disabled.
    • The D3D12 diagnostic log reports no breadcrumb head and no page-fault data.

    Please note that the attached crash report records NVIDIA driver 32.0.16.1074 (610.74), whereas my current driver is 32.0.16.1664.

    Could you investigate the attached GPU dump and minidump to determine what caused the GPU hang? Please advise whether this could be related to the recent inZOI update and whether there is a recommended workaround.

UECC-20260902.14983.W-321788-1C36DBEB4FD99B7D13569A81B0B42A97_0000.zip (501.5 KB)

UECC-20260902.14983.W-321788-191472384B7D79FEFAAF5DAE69B572D7_0001.zip (669.5 KB)

2 Likes