Windows 10: How to fix: video_dxgkrnl_fatal_error? And other issues.

The problem:Whenever I play a game for too long, or play for a specific amount of time in general, I crash. I keep getting a video_dxgkrnl_fatal_error.This happens in nearly every game. What hurts more is the fact that I just got this gaming laptop back from the repair shop. It's an Acer Nitro V-15.Apart from crashers, I'm also having extremely horrible driver issues. Sometimes it sticks, sometimes it flickers, other times it glitches, and it also has this very specific problem. I can only say specific as it's so hard to describe with words, but I was fortunate enough to capture footage of i

:)

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

Scan for hardware changes causes blue screen error VIDEO_DXGKRNL_FATAL_ERROR

Hi,

Thank you for contacting Microsoft Community. I will surely help you to fix the Blue Screen error.

The bug check VIDEO_DXGKRNL_FATAL_ERROR indicates that the Microsoft DirectX graphics kernel subsystem has detected a violation.

To understand the issue better, let me know what is the make and model of the computer?

Method 1:

I suggest you to uninstall and re-install latest graphics driver from the computer manufacturer website and check if it helps.

Method 2:

If the issue persists, I suggest you to try the steps in the following article which will help to fix common Blue Screen errors. Check if it helps.

Resolving Blue Screen errors in Windows - Microsoft Support

Hope this information helps. Reply to the post with an updated status of the issue so that we can assist you further.

 

Programs not working

In post 26 there were steps listed to fix the operating system corruption.
Are you able to follow them?
In post 29 was the suggested dism repair command.