Screen went black while playing a game, pc still on and running, how to diagnose?

[shadybk]

I was playing xcom 2 when all of a sudden the screen went black, my monitor didn't say no signal, it just went black, my pc was still on and running but no picture or sound.

I turned it off using the power button and when I turned it back on everything was working just fine, I was able to play xcom 2 for about another hour.

I went to view the reliability history in windows 10 and it said there was a hardware failure when the screen went black. How serious can this hardware failure be if my pc is up and running now? What should I do to diagnose what the problem could be?

 

[DRagor]

If it happened only once, it could be just coincidence or game's fault. Unless it repeats there is nothing to worry (and you just can't sensibly diagnose problem that does not manifest itself on regular basis).

 

[shadybk]

If it happened only once, it could be just coincidence or game's fault. Unless it repeats there is nothing to worry (and you just can't sensibly diagnose problem that does not manifest itself on regular basis).

Just happened again, same error in the reliability history, since my monitor lost signal that probably means it has something to do with the gpu because if any other part caused the crash then I would have seen a bsod instead of a no signal right?

 

[DRagor]

If it happened only once, it could be just coincidence or game's fault. Unless it repeats there is nothing to worry (and you just can't sensibly diagnose problem that does not manifest itself on regular basis).

Just happened again, same error in the reliability history, since my monitor lost signal that probably means it has something to do with the gpu because if any other part caused the crash then I would have seen a bsod instead of a no signal right?

Not necessarily, there is lot of errors that don't generate BSOD. Can you share a picture with error(s) details?

 

[shadybk]

If it happened only once, it could be just coincidence or game's fault. Unless it repeats there is nothing to worry (and you just can't sensibly diagnose problem that does not manifest itself on regular basis).

Just happened again, same error in the reliability history, since my monitor lost signal that probably means it has something to do with the gpu because if any other part caused the crash then I would have seen a bsod instead of a no signal right?

Not necessarily, there is lot of errors that don't generate BSOD. Can you share a picture with error(s) details?

Here is the info from the reliability history when my pc crashed at 11:23pm
Source
Windows

Summary
Hardware error

Date
‎1/‎21/‎2018 3:16 PM

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffffd686144294a0
Parameter 2: fffff80aae61f818
Parameter 3: 0
Parameter 4: 1140
OS version: 10_0_15063
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.15063.2.0.0.768.101
Locale ID: 1033


Here is the same crash recorded by the event viewer
Log Name: System
Source: Display
Date: 1/21/2018 11:23:23 PM
Event ID: 4101
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Shady
Description:
Display driver amdkmdap stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Display" />
<EventID Qualifiers="0">4101</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-01-22T04:23:23.106657100Z" />
<EventRecordID>13970</EventRecordID>
<Channel>System</Channel>
<Computer>Shady</Computer>
<Security />
</System>
<EventData>
<Data>amdkmdap</Data>
<Data>
</Data>
</EventData>
</Event>

the event viewer says the display stopped working and mentions amd drivers (I am using an amd gpu), so the first thing I did was update my drivers through windows driver manager, should I do a clean install of the amd drivers manually?

Both times my pc crashed yesterday the reliability history and event viewer say the exact same thing for both instances

 

[DRagor]

Read this thing: https://answers.microsoft.com/en-us/windows/forum/windows_10-update/bcc116-bcc117-your-video-driver-has-stopped/fba02c53-7796-4166-83a2-9c44865c13af

In short, it's either driver problem (so switching to another driver version can help - and if you roll back to older version, it is always recommended to do clean install), overheating problem or GPU starting to fail.

 

[Kingster160]

I have the same issue. I built my PC a few days ago and don't know what to do. It's not overheating. I have an and Vega 56 GPU. What GPU do you have? Have you found a solution?