Game crashes after a few minutes - Hotfix 02/05 completely broken

Technical Help
1

  • Game Version: 20260502.12303.W (Hotfix 02/05/2026)

  • Platform: Steam Windows

  • Mods: (Choose one: never used / removed / active)
    Removed :round_pushpin: Previously had 18 mods installed, but disabled and tested with ALL mods removed.
    (Previously active mods: KJ_No_Auto_Change_Clothes_SS, StudioBakery_ATO_Curvy_Chair, MA_OpenShirt, Hair_Minho, NOORA_Emmy_Dressing_Table_Deco, and 13 others)

  • Hardware Specifications & Operating System (OS version, CPU, GPU, RAM, storageā€¦):

    • OS: Windows 11 (25H2) [10.0.26200.8117] 64-bit - CPU: AMD Ryzen 7 5700X 8-Core Processor - GPU: XFX RX 9060XT Swift OC 16GB VRAM - GPU Driver: AMD Software Adrenaline Edition 26.3.1 - RAM: 32GB DDR4 3200MHz - Storage: 500GB NVMe SSD - Monitor: 1080p 165Hz

  • Issue Date: 30/04/2026 (started with first hotfix, persists through 02/05 hotfix)

  • Error Message: Silent GPU crash - RHIInterruptThread crash Game closes without error dialog Crash Log Hash: 17A4424B0A584655CABB15A2816975345FD0C52D (See attached crash dump files for full details)

  • Details: RHIInterruptThread (thread de comunicaĆ§Ć£o da GPU) estĆ” causando a falha.

THE PROBLEM

After the 02/05 hotfix, the game closes by itself after ~2-5 minutes of gameplay. It happens EVERY SINGLE TIME I launch the game.

MY SETUP

CPU: AMD Ryzen 7 5700X GPU: XFX RX 9060XT Swift OC 16GB RAM: 32GB DDR4 3200MHz Storage: 500GB NVMe SSD Monitor: 1080p 165Hz OS: Windows 11 (25H2) GPU Driver: AMD Adrenaline 26.3.1 (FULLY UPDATED)

WHAT Iā€™VE ALREADY TRIED

:white_check_mark: Disabled ALL mods - Renamed entire mods folder

:white_check_mark: Updated GPU driver - Installed AMD Adrenaline 26.3.1 (latest version)

:white_check_mark: Cleaned shader cache - Deleted entire ShaderCache folder and recompiled

:white_check_mark: Validated game integrity - Steam verified all files

:white_check_mark: Engine.ini set to vanilla - Using default game configuration

:white_check_mark: Lowered graphics settings - Ray Tracing disabled, everything on minimum

:white_check_mark: Disabled DirectStorage - Removed storage optimization features

:white_check_mark: Disabled AsyncCompute - Removed GPU parallel optimization

NOTHING fixed it - the game still keeps crashing!

TIMELINE

Date What happened
29/04 Game running PERFECT on UE 5.6.0 - 219+ FPS, zero crashes
30/04 Hotfix released - game started crashing
01/05 New hotfix attempted fix - still crashing
02/05 Hotfix v0.7.2 - STILL CRASHING

HOW THE CRASH HAPPENS

  1. Launch the game

  2. Play normally for 2-5 minutes

  3. Out of nowhere: SILENT CRASH (no error message, just closes)

  4. Back to desktop

This happens 100% of the time.

WHATā€™S ACTUALLY HAPPENING

From analyzing the crash log files (crash XML), the issue is:

RHIInterruptThread (GPU communication thread) is crashing.

This means the graphics card is receiving an invalid command from the engine and fails silently.

The 02/05 hotfix must have changed how the engine communicates with the GPU and broke something fundamental.

EVIDENCE

I found in the forum that there are 285+ people reporting the same problem in the thread: ā€œInZOI Wonā€™t Launch After Hotfix v0.7.2ā€

Status: UNDER INVESTIGATION - you guys already know thereā€™s a bug!

WHAT I NEED

  1. When is the next hotfix coming? I need to play againā€¦

  2. Is there anything else I can do while waiting? Iā€™ve tried everything I know.

  3. Should I downgrade to the previous version?

CRASH FILES

I have 2 crash dump files (XML) if you need them for investigation:

  • First crash: ~140 seconds after launching

  • Second crash: ~287 seconds after launching (same error)

I can provide them if it helps with the investigation.

2

(post deleted by author)

3

@marcus1993.ms7 ,

So sad to hear about your crashes.

This is good investigation and an excellent report. I donā€™t have a solution, but I do have a few suggestions.

(a) Attach the crash reports to the main topic.

(b) Add to the Details sentence, your observation ā€œRHIInterruptThread (GPU communication thread) is causing the crash.ā€

(c) Change the category of this topic from Tech Help to Bug Reports.

This is because the AR moderators do not and cannot help with Tech Help posts. (Tech Help is only peer help. Regarding this topic, all are in the same crashed boat here.).

Devs and QA do not read the forums. There are too many bug posts to have a reasonable manual process to read and prioritize.

Most likely, bug report posts are read (and translated into Korean) by an AI bot to speed up the read-recognize-register-reassign-resolve process.

Bug reports with short accurate titles and details with just 2-3 sentences with 8 to 12 words per sentence are likely to be read and recognized faster.

AI bots do not read and understand the entire report like humans. So better to be short and accurate in the title and details. (Hence my suggestion to add your observation in details. Else it could get lost).

The moderators will likely merge this post with the other crash reports. (The hotfix 0.7.2 topic, with now an incorrect title, has become a dumping thread and a mess). And there is no tag for ā€œCrashesā€ under Bug Reports !!

Hope your investigation and attached crash reports help in resolving these crashes.

4

Hi @marcus1993.ms7 ,

Since youā€™re dealing with game crashes, Iā€™ve moved your post over to Technical Help as itā€™s the category for game-breaking issues such as the crashes that youā€™re experiencing.

5

Hi @Michael ,

Sorry to jump in, but I think this topic is more of a bug report than a tech help, based on the investigation and report by the OP @marcus1993.ms7 . I could be wrong, but I donā€™t think we can give any tech help here. All steps usually suggested in tech-help sub-forum have already been done and no solution obtained.

See from the original post, observation about the error:

If left in Tech-Help sub-forum, the crash reports from this particular crash may not reach the Developers, while when the topic is considered as a Bug Report, the crash files would be useful.

Hence the request that this be considered as a Bug Report along with the other crash reports.

I also recommend that a separate category called Crash Reports be opened on these forums till we get to the 1.0 release.

Thanks!