Laptop restarting automatically, video_dxgkrnl_fatal_error

Meganle7

Commendable
Aug 26, 2016
1
0
1,510
I bought the new MSI63vr laptop last week, specs:
16gb ram
geforce gtx 1060
i7 - 6700HQ quad core 2.6 ghz
1000 GB HHD, 128 GB SSD

My problem is, the power button is badly placed(on the side of the laptop), and i accidentally hit it while playing Rise of the Tomb Raider, and the laptop completely shut off while the cpu and gpu were at 5000 rpm and round 70 C. I immediatly turn it back on to a blue screen, saying the computer is checking for errors and the fans are makng a grinding noise. The computer restarts, and as soon as I sign in it blue screens and shows the error "video_dxgkrnl_fatal_error" and restarts. this happens about 7 times in a row. Eventually, it doesn't blue screen and I'm able to turn the game back on. Everything runs great, seems like it's all ok. So I turn the game off, and then it blue screens showing the same error. I turned it back on after that, turned the game back on, it all seems fine and I played it for quite a bit, turned off the game, and then turned off the computer with no blue screen. It seems ok now, but what is causing the blue screen? Is it something I can fix or should I just go return the laptop?
 
Solution
Well you could return it, if it is giving you errors that quickly. Personally I would be feeling that way as well.

However, that said, it could just be the way that system was trying to address the errors caused by the improper shut down. When something like that happens it is always best to run checks on the system to make sure nothing was damaged, lost, etc. New computer or not. You don't want the error to repeat nor have any permanent damage to your system.

Again, I do agree, it should not react so badly when new, but for future reference, if it gets shut down improperly, then run system checks and repairs before continuing to use the system as normal.
Well you could return it, if it is giving you errors that quickly. Personally I would be feeling that way as well.

However, that said, it could just be the way that system was trying to address the errors caused by the improper shut down. When something like that happens it is always best to run checks on the system to make sure nothing was damaged, lost, etc. New computer or not. You don't want the error to repeat nor have any permanent damage to your system.

Again, I do agree, it should not react so badly when new, but for future reference, if it gets shut down improperly, then run system checks and repairs before continuing to use the system as normal.
 
Solution