I hope this information will be useful for you and help you identify the problem faster. Here is a report of my observations and system configuration
configuration:
GPU: AMD Radeon RX 7800 XT (RDNA3)
Driver: Adrenalin 26.2.1
OS: Windows 11 25H2
Minecraft: 1.21.4
Fabric Loader: (0.18.4)
Fabric API: (0.111.0+1.21.4)
Radiance: (windows.jar build)
Multi-monitor setup: Yes (2 displays)
HAGS (Hardware Accelerated GPU Scheduling):
ON → full display engine reset (one monitor loses signal)
OFF → no display loss, but still driver timeout
TDR: default (TdrDelay = 2)
No overclock / no undervolt
Overlays disabled
Description:
The game crashes immediately after entering a world.
Behavior:
World loads.
Player joins successfully.
First frame starts rendering.
Only a partially rendered frame is visible (top portion rendered, rest black).
GPU driver times out.
Minecraft closes.
When HAGS is enabled:
One monitor consistently loses signal (display engine reset).
Manual recovery (Win+Ctrl+Shift+B does not restore it).
When HAGS is disabled:
No display engine death.
Still results in AMD “driver timeout”.
Minecraft terminates.
Minecraft logs do not show a Vulkan error or stacktrace. latest.log ends abruptly without a graceful shutdown message.
Additional Observations
Crash happens exactly at the moment of first world render.
Appears to coincide with initial RT pipeline / TLAS build / first dispatch.
Increasing allocated RAM has no effect.
Disabling overlays has no effect.
Also changing in dynamic pipeline settings has no effect
Issue is fully reproducible.
latest.log
I hope this information will be useful for you and help you identify the problem faster. Here is a report of my observations and system configuration
configuration:
GPU: AMD Radeon RX 7800 XT (RDNA3)
Driver: Adrenalin 26.2.1
OS: Windows 11 25H2
Minecraft: 1.21.4
Fabric Loader: (0.18.4)
Fabric API: (0.111.0+1.21.4)
Radiance: (windows.jar build)
Multi-monitor setup: Yes (2 displays)
HAGS (Hardware Accelerated GPU Scheduling):
ON → full display engine reset (one monitor loses signal)
OFF → no display loss, but still driver timeout
TDR: default (TdrDelay = 2)
No overclock / no undervolt
Overlays disabled
Description:
The game crashes immediately after entering a world.
Behavior:
World loads.
Player joins successfully.
First frame starts rendering.
Only a partially rendered frame is visible (top portion rendered, rest black).
GPU driver times out.
Minecraft closes.
When HAGS is enabled:
One monitor consistently loses signal (display engine reset).
Manual recovery (Win+Ctrl+Shift+B does not restore it).
When HAGS is disabled:
No display engine death.
Still results in AMD “driver timeout”.
Minecraft terminates.
Minecraft logs do not show a Vulkan error or stacktrace. latest.log ends abruptly without a graceful shutdown message.
Additional Observations
Crash happens exactly at the moment of first world render.
Appears to coincide with initial RT pipeline / TLAS build / first dispatch.
Increasing allocated RAM has no effect.
Disabling overlays has no effect.
Also changing in dynamic pipeline settings has no effect
Issue is fully reproducible.
latest.log