Windows 10: Keep getting VIDEO_DXGKRNL_FATAL_ERROR and restart in past 12 hours

Hi! I facing a problem with my laptop. When I run a program it freezed for about 1-2 sec and crashed. After that my laptop turn bluescreen with the stop code: VIDEO_DXGKRNL_FATAL_ERROR. My laptop detail as belowrocessor IntelR CoreTM i5-8300H CPU @ 2.30GHz 2.30 GHz System type 64-bit operating system, x64-based processor Graphic GTX1050 I tried uninstall and reinstall my graphic driver, and fixed driver with DriverFix. However it since like those method not working. The problem still there

:)

 

Stop code: Video_DXGKRNL_FATAL_ERROR restarting computer





I have a coworker who keeps getting this message and her laptop restarts at seemingly random times. I followed all the steps from www.windows.com/stopcode yet it continues to restart randomly. It is an MSI laptop running Windows 10. I noticed (as in the
image above) that the Stop code is for Video_DXGKRNL_FATAL_ERROR so I both updated the drivers and rolled back video drivers after updating them did not stop this issue. Does anyone have any suggestions?

Moved from: [Windows / Windows 10 / Devices & drivers]

 

Windows 10 stuck after restart on blue screen "getting windows ready" for 12 hours

Few days ago after restarting my Lenovo PC a blue screen with " getting windows ready don't turn off your computer" appeared

and no way to get windows desktop, even restatring again didnt help

had to leave it and wait about 12 hours to get the desktop again

restarting again had this issue all over again (12 hours wait)

I noticed previous failure to install windows update: KB4056887

I run windows update to check for updates and after awhile got the status:" your device is up to date : last checked 12.1.2018" I run it on 16.1.18

tried restarting and still have the issue with blue screen for 12 hours until it comes up to desktop, this is crazy....

Need Help ---- > How can this be fixed?

Thanks!

E

Moved From:

• Windows
  
• /
• Windows 10
  
• /
• Windows update, recovery, & backup
  

 

"Active hours can be set between 1 and 12 hours"?!

Those who are criticizing posters about being unhappy with Windows features seem to be misrepresenting a poster's intent. It appears that posters are simply expressing a belief that Microsoft should have designed
the feature better--not that they do not understand that they are stuck with the software they bought and agreed to.

How could Active Hours be designed better?

• What's the current design? It looks like Microsoft believes it might take up to 12 hours to accomplish an update, so requests that the user specify a period including 12 hour of non-Active Use.
  
  .
• But the biggest fear appears to be that the restart might happen during truly important work, not that the update might possibly still be going on when the user returns to work. Such would be unfortunate but could be worked around, especially if it is
  only a possibility. I have endured some long updates: "Do not turn off the power ..." but it has never taken 12 hours. I am a Win10-Home user.
  
  .
• A Better Design: That Active Hours only govern when the system shall not be restarted. In this case, a period as long as 23 hours would be allowable. If it takes 12 hours to update, so be it--but there is
  no way to prevent that as long as it truly takes MS 12 hours (sometimes). This seems to give Microsoft as much flexibility and the user as much protection as the current design. For example, my desired Active Hours are 10am-3am (17 hours). If I set my AH
  to 4am-3am (23 hours) I get the same protection as now; and Microsoft can restart at 3am and take 12 hours if needed.
  
  .
• But if Microsoft, even today, not do its restart at any arbitrary time within the non-Active Hours, but only at the beginning of it, it would have the same effect as the proposal, and its actions would be very
  predictable. Since users are complaining about unexpected restarts, it appears that Microsoft must be choosing an arbitrary point outside of Active Hours. Is it?