edgy hare
Hardware:
GPU: NVIDIA GeForce RTX 2060 (TU106)
CPU: Intel i7-10700F
RAM: 32 GB
OS: Windows 11 25H2 (10.0.26200.7309)
Drivers / Settings:
NVIDIA Game Ready driver 581.80
Clean install (previously on 591.44)
Tested with all overlays disabled (Discord, Steam, GeForce Experience, Xbox Game Bar, MSI Afterburner)
Tried both DX11 and DX12:
DX11 path: repeated LogD3D11RHI: GetQueryData is taking a very long time followed by DXGI_ERROR_DEVICE_REMOVED / DEVICE_HUNG
DX12 path: LogD3D12RHI: GPU timeout then DXGI_ERROR_DEVICE_HUNG
Repro steps (roughly):
Launch Vein (Steam, Windows 11) with -dx12 launch option.
Game gets to main menu / loading screen.
After a short time, the game crashes with a GPU error.
Key log lines (DX12 crash):
GPU timeout: A payload on the 3D queue has not completed after 5.0007 seconds.
GPU crash detected: Device 0 Removed: DXGI_ERROR_DEVICE_HUNG
Aftermath mini dump says:
Fault Description: A shader instruction caused an MMU fault when accessing memory
Fault Name: MMU Fault Error
Shader name: fragment_02 (pixel/fragment shader)
Device state: Error_DMA_PageFault
VRAM at time of crash:
Local Budget: 5187 MB
Local Used: 1847 MB
Crash dump written to:
Vein\Saved\Logs\D3D12.0.2025.12.06-20.58.39.nv-gpudmp
What I’ve tried:
Clean driver install (581.80 and 591.44)
DX11 and DX12
Lowest graphics settings (shadows, foliage, postprocessing)
Frame cap and VSync
Disabling Discord / Steam / GFE / Xbox overlays
It looks like a shader or rendering bug hitting Turing (RTX 2060) specifically – NVIDIA Aftermath is reporting an MMU page fault in fragment_02. Please let me know if I can provide the full .nv-gpudmp file or additional logs.
fringe zinc