VIDEO_DXGKRNL_FATAL_ERROR indicates that the Microsoft DirectX graphics kernel subsystem detected a violation. Given that this happens mainly during games, with screen blinking, audio buzzing, and then a crash, the most relevant path is graphics-driver and graphics-stack troubleshooting.
Since resetting Windows, reinstalling games, and reinstalling the latest display drivers were already tried, focus on these steps:
- If a driver name appears on the blue screen or in the stop message, disable that driver or get an updated version from the laptop manufacturer.
- Make sure all graphics-related software is current, including DirectX and OpenGL components, and ensure the affected games are fully patched.
- Check whether any recently added hardware or peripherals are involved, and confirm they are compatible with the installed Windows version.
- Use Safe Mode to isolate whether the issue is tied to a full graphics driver stack:
- Open Settings → Update and Security → Recovery
- Select Advanced startup
- Go to Troubleshoot → Advanced Options → Startup Settings → Restart
- After restart, choose option 4, 5, or 6 for Safe Mode If the system is stable there, that points more strongly to a driver or related software issue.
- Run Windows Memory Diagnostics:
- In Control Panel search, type Memory
- Select Diagnose your computer's memory problems
- After the test, open Event Viewer → System log
- Look for MemoryDiagnostics-Results
- Run the hardware diagnostics provided by MSI for the laptop.
Relevant background: Windows uses Timeout Detection and Recovery (TDR) for GPU hangs. During heavy graphics workloads, the system can appear frozen while the GPU is busy. If recovery succeeds, Windows can show that the display driver stopped responding and recovered; if recovery fails, bug checks such as video TDR failures can occur.
If the crashes are limited to only a few specific games, also check whether those games have known issues or patches. There is also a documented Windows known issue where certain games crash or restart systems because of RGB-related drivers with names similar to inpoutx64, not because of Windows itself. If RGB control software or related device drivers are installed on the laptop, that is worth checking.