Windows 10: Pc crashing - black screen with inverted colours, attached a crash log file

Pc has been appearing to run fine when gaming, cpu temps around 70c and gpu at 50c. Then the pc will freeze, screen turns black, colors look inverted and then a full pc restart. Has been happening consistently with diablo 4 and a couple times with destiny 2. I have attached the minidump file for the crash. Any help?

:)

 

Help understanding log file and game crash.

I have recently been experiencing crashes in FF14 dx11 mode, and I wanted to be sure it wasn't a hardware failure issue causing the crash. I have a lenovo y510p with the SLI 755ms. I'm keeping both cards temps at 70c or below, and I do have the SLI activated. The crashes occur randomly, and I get the error Final Fantasy XIV has stopped working. As far as I can see my display drivers are not crashing, but I was hoping somebody could take a look at this log file and see if there is anything unusual. The log files shows me playing the game until crash. Also, sometimes when the game crashes I get a black screen, but I can still hear the game in the background.

 

black screen - need help by interprate my logs

thx for answer -> the logs i attached are the LAST logs before the black screens appears. and i restart the pc.

 

Crash/blue screen

Hi

I assume from the title of your post Crash/Blue Screen that the PC has crashed and produced a *BSOD=[Blue Screen Of Death] =Blue Screen; and that the PC recovered from this; if and when you see the Blue Screen write the Stop Code down; recover the PC or use one that is working to access the net and look up the Stop Code.

nb: You may be able to view this with a [*BlueScreenView] application, google for this.

Edit Link - Blue screen of death (STOP error) information in dump files.

Description
===========

BlueScreenView scans all your minidump files created during 'blue screen
of death' crashes, and displays the information about all crashes in one
table. For each crash, BlueScreenView displays the minidump filename, the
date/time of the crash, the basic crash information displayed in the blue
screen (Bug Check Code and 4 parameters), and the details of the driver
or module that possibly caused the crash (filename, product name, file
description, and file version).
For each crash displayed in the upper pane, you can view the details of
the device drivers loaded during the crash in the lower pane.
BlueScreenView also mark the drivers that their addresses found in the
crash stack, so you can easily locate the suspected drivers that possibly
caused the crash.

atb

Law-II