#Crash to desktop #2

8 messages · Page 1 of 1 (latest)

hazy rampart
mental quiver
#

woah, what happened here? it froze, and the app restarted?

#

latest version logs have a GPU driver crash, but it should not restart like that

 at C:\TheoryCraft\build-staging\Engine\Source\Runtime\D3D12RHI\Private\D3D12Submission.cpp:1013 
 with error DXGI_ERROR_DEVICE_REMOVED with Reason: DXGI_ERROR_DEVICE_HUNG

[2025.05.19-13.40.13:929][853]LogD3D12RHI: Error: [GPUBreadCrumb] Last tracked GPU operations:
[2025.05.19-13.40.13:929][853]LogD3D12RHI: Error: [GPUBreadCrumb]    3D Queue 0

[2025.05.19-13.40.13:934][854]LogD3D12RHI: Error: [GPUBreadCrumb]    Copy Queue 0

[2025.05.19-13.40.13:945][854]LogD3D12RHI: Error: [GPUBreadCrumb]    Compute Queue 0

[2025.05.19-13.40.13:957][854]LogD3D12RHI: Error: DRED: Last tracked GPU operations:
[2025.05.19-13.40.13:957][854]LogD3D12RHI: Error: DRED: No command list found with active outstanding operations (all finished or not started yet).
[2025.05.19-13.40.13:957][854]LogD3D12RHI: Error: DRED: PageFault at VA GPUAddress "0xFFFF00015000"
[2025.05.19-13.40.13:957][854]LogD3D12RHI: Error: PageFault: PageFault at VA GPUAddress "0xFFFF00015000" (GPU 0)
[2025.05.19-13.40.13:957][854]LogD3D12RHI: Error: PageFault: Last completed frame ID: -1 (cached: 176099) - Current frame ID: 176102
[2025.05.19-13.40.13:957][854]LogD3D12RHI: Error: PageFault: Logging all resource enabled: No
[2025.05.19-13.40.13:957][854]LogD3D12RHI: Error: PageFault: Found 0 active tracked resources in 16.00 MB range of page fault address
[2025.05.19-13.40.13:957][854]LogD3D12RHI: Error: PageFault: Found 0 active heaps containing page fault address
[2025.05.19-13.40.13:957][854]LogD3D12RHI: Error: PageFault: Found 0 released resources containing the page fault address during last 100 frames
[2025.05.19-13.40.13:957][854]LogD3D12RHI: Error: Memory Info from frame ID -1:
[2025.05.19-13.40.13:957][854]LogD3D12RHI: Error:     Budget:       0.00 MB
[2025.05.19-13.40.13:957][854]LogD3D12RHI: Error:     Used:       0.00 MB
[2025.05.19-13.40.13:967][854]LogD3D12RHI: Error: GPU Crashed or D3D Device Removed.```
hazy rampart
# mental quiver woah, what happened here? it froze, and the app restarted?

No that's just Steam Recording picking up back after re-launching the game

My driver didn't crash - I'd get Adrenalin crash report, my iCUE would stop working (it stops displaying stuff on my cpu cooler after driver crash) and, most of all, I'd get the black screen for a second. I didn't get it there!
That recording with mouse getting multiplicated a'la Solitaire - also I didn't see that, my game was just normally working, no lag, no stutter, no mouse freeze. I was just playing and boom, I'm on desktop rocketW
What could also count for the engine as a driver crash, that's not a driver crash?

#

not even in the event viewer!

#

Hmm, there is something in application log however..

#

Yep it's driver timeout... Just a weirder one that didn't follow 'normal' crash routine.
I wonder why. I had my 'classic' driver timeout last week and everything was as always there - freeze, black screen, adrenalin crash detection, iCUE sensors frozen etc. Why did this crash just go straight to desktop without anything else happening susfrog ...