Yellow-Dog-Man
Random crash (5 min – 1 h after launch) – possible RenderTexture / D3D11 device-lost loop
Describe the bug?
A small group of users (about six of us so far) are seeing Resonite hard-crash at apparently random moments between ~5 minutes and 1 hour after launching the client.
The Windows crash dialog always points to d3d11.dll → D3DKMTOpenResource or nvwgf2umx.dll with 0xC0000005 (ACCESS_VIOLATION).
The Player.log just before the crash repeatedly prints
Releasing render texture that is set as Camera.targetTexture!
UnityFrooxEngineRunner.RenderTextureConnector.Unload()
followed by a flood of 0x887A0005 (DXGI_ERROR_DEVICE_REMOVED) messages.
Using DDU to fully wipe and reinstall GPU drivers (several different recent Studio & Game-Ready versions) did not noticeably improve stability.
We are stuck since the client may crash in the middle of a session without warning.
To Reproduce
Launch a clean Resonite install
Join any public or private world (VR or Desktop, doesn’t matter).
Wait (typically 5 min–1 h).
Client freezes and Windows crash dialog appears.
We have not found a 100 % reliable click-by-click repro; simple idling is enough on affected machines.
Reproduction Item/World
N/A – happens in multiple unrelated worlds, including an empty home space.
Expected behavior
Resonite should remain stable
Screenshots
No response
Resonite Version Number
2025.1.3 — also confirmed on 2025.1.5 Beta.
What Platforms does this occur on?
Windows
What headset if any do you use?
Desktop or VR
Log Files
ukiwa's log: Player-prev (6).log Player (5).log
sawaden's log: Player-prev (6).log Player (5).log DESKTOP-BVK8H9J - 2025.5.23.1096 - 2025-05-28 00_16_02.log Player (4).log
Additional Context
No response
Reporters
No response
This is a bizarre one, with a lot of history and finger-pointing on the cause. In one case, there was a forum post going back 12 years.
Various fixes found include:
- Disabling frame generation //probably isn't this, unless the issue is hitting other games too.
- Adjusting GPU timeout detection with the
TdrDelayandTdrDdiDelayregistry keys //Also not likely, unless your CPU is good enough to make the GPU your bottleneck. - Cutting back any factory provided overclocks //Possible, but that's really bad luck on the silicon lottery.
- Reseating and testing RAM //Also possible, instability and corrupted data there could cascade to the GPU.
- (OPTIONAL, personal experience suggestion) If using Ryzen, adjust the VDDCR_SOC up a tiny bit //This is the voltage for all the non-processor stuff, like the memory and PCIe controllers. YMMV with this one, but it fixed memory instabilities with my system.
A sanity check - do they have latest GPU drivers? Usually this kind of error is a GPU driver crash caused by something.
@Frooxius I instructed all of them to update their drivers. Additionally, I had them reinstall the drivers using DDU just to be safe. After reinstalling the drivers with DDU, it seems like the issue has been slightly mitigated, but the same problem still occurs with the same log. Strangely, this only seems to affect some users, but when it does, it happens quite frequently. Perhaps if a recovery mechanism could be implemented in the splittening process to handle crashes, we might be able to work around this issue temporarily. Considering that this issue only occurs for some users, it’s likely that the problem lies with their individual PCs. However, the frequency and number of affected users is high, and since we still don’t know a clear workaround or direct cause, it’s been quite a challenge.
NVIDIA System Information 05-29-2025 15-30-06.txt
NVIDIA System Information 05-30-2025 02-30-11.txt
Two of them gave me the driver information.
It finally happened to me — I encountered the same bug.
RABBUTTZHOUSE - 2025.6.4.1085 - 2025-06-05 17_42_16.log
error.log Player.log （No dump files found.）
I am reporting this because a similar phenomenon occurred in my environment. Please check the attached data.
========================1st crash.dmp error.log Player.log
========================2nd crash.dmp error.log Player.log
This hasn't happened to me yet, but I think it could be something like Windows Update that's causing it.
