Hey, can you send your player.log please?
@Crowned_PVP @DDIV as well if you can provide your player logs please
wdym? i already did
it seems you rly don’t give a damn on reading
k there u go once again
@Steve_Jewer here’s the original message that i provided all logs as per the bug report template
reports
datastore.zip
Hey, just another option for people to try. I found a similar set of issues, although the game wasn’t really freezing it was black screening after a few seconds of running. Oddly, if I alt tabbed I could sometimes see the game rendering, but when giving focus back to the game it would be black again. I discovered the same issue on Jotunnslayer.
What fixed it for me was simply exiting discord. It looks like sometimes discord overlays interfere with rendering in Unity games. Hope this is a simple option that helps some people!
1 Like
Added this file to the link.
Black screen after moon logo and ambient on the background.
At this point i am not sure where i supposed to report about this problem. Game does not work for several days. I’m not alone in it. You completely ignore all us. The topic is marked as solved. While it’s not even close to it. Silence in email. Silence in forum.
Don’t ask us to reboot windows or send you logs. We already did it and much more by ourselves. Nothing works. I understand that the problem could be a difficult one but the way you treat us with complete ignore and silence is not acceptable. Just say that’s in progress and we are fine. I am very close to demand for a refund. Very sorry.
Is that enough for solving problem?
1 Like
@Steve_Jewer As I see in Discord @kuro just leave until 9 Feb. I can’t wait for so long. Can u plz check the problem?
After the Moon Studios logo I just get stuck on a black screen and hearing what is probably a menu music background or something, i can’t get through it. I’m trying already some of the possible fixes here and nothing is working so far, can anyone explain me how to get my logs to post here so I can get better help for my issue? I just saw that people are complaining about the same issue since 2024, if the same issue still a problem in 2026 thats very disappointing, I bought the game on steam yesterday but I can’t play it.
1 Like
We apologize for the delay, we implemented a fix for this in the latest hotfix but it has not fixed it for everyone, we are investigating the newest logs now.
1 Like
How can I get my logs to post here?
Instructions on where and how to retrieve the logs can be found here: How to Properly Report Bugs! - #18
If you already have those, but the forum doesn’t let you post them, follow this guide: If you cannot create a bug report due to the check failing
2 Likes
UE5 caused short GPU load spikes during the loading screen, triggering Windows TDR (2-second timeout) and resulting in VIDEO_TDR_FAILURE / Kernel-Power 41. (in my case)
Increasing the Windows TDR delay (TdrDelay = 8 in the registry) gives the GPU enough time to complete the workload and prevents the driver reset.
This is an OS-level fix, not a hardware issue or game modification, and completely resolved the crashes for me.
Disclaimer: I’m not a technical expert myself. This solution was worked out step by step together with ChatGPT through troubleshooting, log analysis, and testing. I’m sharing the results as a potential fix, not as an authoritative diagnosis.
UE5 Crashes During Loading Screen – Troubleshooting, Root Cause, and Fix
The game was consistently crashing during the first loading screen and often caused a full system reboot.
Windows Event Viewer showed Kernel-Power 41 along with VIDEO_TDR_FAILURE (Bugcheck 0x119) and
Event ID 10 (Display / GPU driver). Despite this, the system remained completely stable in stress tests such as
Cinebench (CPU) and FurMark (GPU), and temperatures and power draw were within normal limits.
This strongly indicated that the hardware itself was not faulty.
Further investigation showed that the crashes occurred independently of DirectX version or graphics settings.
The key clue was the repeated TDR-related events in the Windows logs.
TDR (Timeout Detection & Recovery) is a Windows mechanism that monitors GPU responsiveness.
By default, Windows expects the GPU to respond within 2 seconds. If it does not,
Windows assumes the GPU has hung and forcibly resets the graphics driver.
UE5 loading screens can generate very short but extremely heavy GPU workloads
(shader compilation, texture streaming, VRAM allocation).
On some systems, these spikes exceed the default TDR timeout even though the GPU is functioning correctly.
As a result, Windows triggers a driver reset, which can escalate into a system reboot.
The solution was to increase the TDR timeout in the Windows registry by setting:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
TdrDelay (DWORD 32-bit) = 8
Optional: TdrDdiDelay (DWORD 32-bit) = 8
This change gives the GPU additional time to complete heavy workloads before Windows intervenes. Importantly,
this does not increase GPU voltage, clocks, or temperatures, and all hardware safety mechanisms remain active.
Since applying this fix, the game has launched reliably without further crashes or Kernel-Power 41 events.
(post deleted by author)
1 Like
my solution that worked for me:
The game was optimized by Nvidia App. After i cancel optimization it works fine now.
I recommend to try set everything default in nvid control panel + disable hdr
1 Like
I tried every possible fix I found ad it worked, not sure which one fixed the issue but it worked. I’m enjoying the game a lot, i does need more optimization but this is just an early access so its fine, and I’m playing the game using an HD, I’m gonna move it to an SSD for a better experience and I’ll gonna bring feedback in another topic, thank you.
I have a problem: every time I launch the game, it automatically closes within the first 5 seconds of loading.
1 Like
How to check if the GPU driver crashed (Windows – beginner friendly)
If a game crashes, the screen goes black, or the PC restarts, it is not always obvious whether the GPU driver is the cause. Windows does record this information — you just need to know where to look.
Step 1 – Open Windows Event Viewer
- Press Win + X
- Click Event Viewer
- In the left panel, open:
Windows Logs → System
Step 2 – Look for critical or error events
On the right side, click Filter Current Log… and check:
- Critical
- Error
Then press OK.
Now look for events that happened at the exact time of the crash or reboot.
Step 3 – Common events that indicate a GPU driver crash
If the GPU driver was involved, you will usually see one or more of these:
Kernel-Power – Event ID 41
- Description: “The system has rebooted without cleanly shutting down”
- Meaning: Windows lost stability, often after a driver reset
(This does not mean the power supply is bad.)
Display – Event ID 4101 or 10
- Description: “Display driver stopped responding and has recovered”
- Meaning: Windows detected that the GPU driver became unresponsive and tried to reset it
→ This is classic TDR behavior
BugCheck – Event ID 1001
- Description includes:
VIDEO_TDR_FAILURE- Error codes like
0x116or0x119
- Meaning: The GPU driver reset failed or escalated into a system crash / reboot
Step 4 – How to interpret this (simple explanation)
- If you see Display driver errors + BugCheck 1001 → GPU driver timeout
- If you see Kernel-Power 41 right after → system reboot caused by the driver reset
- If stress tests run fine but games crash → not faulty hardware
This means:
Windows thought the GPU was “stuck” for too long and reset the driver.
What this does not mean
GPU is broken- Power supply is failing
- CPU overheating
It usually means:
A very heavy GPU workload exceeded Windows’ default timeout.
If this is TRUE
Step 1 – Open the Registry Editor
- Press Win + R
- Type
regedit - Press Enter
- Confirm the UAC prompt
Step 2 – Navigate to the GraphicsDrivers key
Go to:
HKEY_LOCAL_MACHINE
└ SYSTEM
└ CurrentControlSet
└ Control
└ GraphicsDrivers
Step 3 – Create the TDR delay value
- Right-click in the empty area on the right side
- Select New → DWORD (32-bit) Value
- Name it exactly:
TdrDelay
- Double-click
TdrDelay - Set:
- Base: Decimal
- Value data:
8
- Click OK
(Optional but recommended)
Repeat the same steps and create:
TdrDdiDelay = 8
Step 4 – Restart your PC
The change only takes effect after a reboot.
1 Like