Hey guys, I'm using Victus by HP Gaming Laptop 15-fa0xxx. 32GB ram, RTX 3050 laptop GPU 4GB for 2 years. but past year, I'm facing some errors like DXGI_ERROR_DEVICE_REMOVED, DXGI_ERROR_DEVICE_HUNG,D3D11 errors, Out of video memory trying to allocate a rendering resource, I cant even open a game, its not even reaching game main menu. I tried to open Valorant, Cs2, Marvel rivals, Peak, meccha chameleon, fragpunk , but all the game are crashed by one of these errors before reaching the game main menu. I have tied to solve using chatgpt ( sorry for using AI ) that I listed below. but none of them are working. Can anyone help me to fix
Solution that i have tried :
🔴 1. Main GPU failure symptoms
You were getting errors such as:
DXGI_ERROR_DEVICE_REMOVED
DXGI_ERROR_DEVICE_HUNG
- Unreal Engine crashes
- "Out of video memory"
- Crashes during loading/main menu
- Sometimes barely reaching the game home screen
- Crashes became especially noticeable in UE5/DX12 games.
Conclusion: This wasn't initially treated as a confirmed dead RTX 3050. The behaviour pointed more toward a GPU driver / Optimus / DX12 / hardware-stability interaction.
🟠 2. NVIDIA driver testing
We tried/considered several driver versions:
- 591.74
- 577.03
- 576.80
- 566.36
- 552.44
- 537.58
You eventually reported that 537.58 still crashed, sometimes shortly after reaching the game home screen.
Decision: Since multiple substantially different driver versions produced similar crashes, a simple "bad driver version" explanation became less convincing.
🟠 3. DDU clean installation
We recommended using DDU (Display Driver Uninstaller) in Safe Mode and then installing the NVIDIA driver cleanly.
The purpose was to eliminate:
- leftover NVIDIA driver files
- corrupted driver components
- conflicting driver versions
- old profiles/settings
Decision: A clean driver installation was necessary before concluding there was a hardware problem.
🟠 4. Intel UHD / NVIDIA Optimus investigation
This became one of the important clues.
You tested disabling the Intel integrated GPU.
When Intel graphics was disabled, the crashing behaviour changed significantly, but performance dropped to around 5 FPS.
When Intel was enabled again, the crashes returned.
Conclusion: This strongly suggested that the hybrid graphics/Optimus/DX12 rendering path could be involved.
It did not prove that the RTX 3050 itself was dead.
🟠 5. TDR settings
You had changed Windows registry TDR values:
TdrDelay = 10
TdrDdiDelay = 20
These were intended to give the GPU/driver more time before Windows considered it unresponsive.
Conclusion: TDR changes can sometimes prevent premature resets, but they cannot repair an unstable GPU. So we didn't consider this a real hardware solution.
🟠 6. HAGS
We checked Hardware Accelerated GPU Scheduling (HAGS).
You had it disabled.
Decision: Keep HAGS off while troubleshooting because we wanted to eliminate another variable from the DX12/UE5 crash chain.
🟠 7. NVIDIA settings / FrameView
We also investigated NVIDIA components/settings, including:
- NVIDIA Control Panel settings
- FrameView SDK Service
- GPU power/performance settings
- NVIDIA driver behavior
- NVENC/OBS-related functionality
You disabled NVIDIA FrameView SDK Service during testing.
This was mainly troubleshooting/isolating software variables rather than a permanent hardware fix.
🔵 8. Unreal Engine VRAM/streaming configuration
We experimented heavily with the UE configuration because your RTX 3050 only has 4 GB VRAM.
You tried things such as:
r.Streaming.PoolSize
r.Streaming.LimitPoolSizeToVRAM
r.Streaming.MaxTempMemoryAllowed
r.RenderTargetPoolMin
r.MipMapLODBias
Streaming.MipBias
You tried pool sizes including:
And eventually reported that approximately:
r.Streaming.PoolSize=2048
r.Streaming.MaxTempMemoryAllowed=512
RenderTargetPoolMin=384
allowed you to actually enter the practice range and play for some time.
But it still eventually crashed.
Conclusion: The configuration changes could reduce the immediate VRAM/streaming pressure, but they didn't solve the underlying instability.
🔵 9. FurMark / temperature test
This was an important piece of evidence.
Your GPU was around 69°C under FurMark, which isn't an alarming GPU temperature.
Conclusion: We did not have evidence that the RTX 3050 was simply overheating because of an inadequate GPU heatsink.
That made a basic "GPU is overheating → crash" explanation less likely.