Gaming PC Randomly Restarting and/or Blacking Out Screen During Use

[Austin311]

My PC has been running exceptionally well for the past several months aside from the occasional viruses that I have had to clean out before. But a few days ago, out of nowhere, my PC began randomly either restarting or making the screen to go black rendering it unusable. This happens after using my PC for an hour, or even just 7 minutes. I have tried scanning it for viruses and it did not detect anything through quick scan, but when I tried using full scan, it would restart before it had the chance to finish the scan, the same thing happened when I tried to defragment the hard drive. I have tried unplugging all of my cables, dusting out my PC, and then plugging all of the cables back in, and it still did not work. I also have not overclocked any of my components manually.

Here are my specs:
GPU - MSI R9 390
CPU - Intel i5 4590
CPU Cooler - Master Hyper 212 EVO
Motherboard - MSI H81M-E34 Micro ATX LGA1150
RAM - Team Elite 8 GB DDR3-1600
Hard Drive - Seagate Barracuda 1TB
PSU - Sentey 850w 80+ Bronze MBP
Case - Sentey Stealth GS-6008 ATX
Monitor - VIZIO E-Series 47” Class LCD Smart TV

 

[JamesSneed]

Check out the event viewer after this occurs. That should point you in the right direction.

 

[Austin311]

How will I know which error will give me the info I need to solve my problem?

 

[Austin311]

I opened the event viewer, it shows a ton of errors related to printer drivers and the computer unexpectedly closing, so what do I do?

 

[Austin311]

Check out the event viewer after this occurs. That should point you in the right direction.

Here is the report from the shutdown:

Log Name: System
Source: EventLog
Date: 8/19/2016 11:27:53 AM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: GAMING-PC
Description:
The previous system shutdown at 11:18:07 AM on ‎8/‎19/‎2016 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-08-19T18:27:53.125614100Z" />
<EventRecordID>16705</EventRecordID>
<Channel>System</Channel>
<Computer>GAMING-PC</Computer>
<Security />
</System>
<EventData>
<Data>11:18:07 AM</Data>
<Data>‎8/‎19/‎2016</Data>
<Data>
</Data>
<Data>
</Data>
<Data>2434</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>E0070800050013000B0012000700DC03E007080005001300120012000700DC03600900003C000000010000006009000001000000B00400000100000000000000</Binary>
</EventData>
</Event>

 

[JamesSneed]

Check out the event viewer after this occurs. That should point you in the right direction.

Here is the report from the shutdown:

Log Name: System
Source: EventLog
Date: 8/19/2016 11:27:53 AM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: GAMING-PC
Description:
The previous system shutdown at 11:18:07 AM on ‎8/‎19/‎2016 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-08-19T18:27:53.125614100Z" />
<EventRecordID>16705</EventRecordID>
<Channel>System</Channel>
<Computer>GAMING-PC</Computer>
<Security />
</System>
<EventData>
<Data>11:18:07 AM</Data>
<Data>‎8/‎19/‎2016</Data>
<Data>
</Data>
<Data>
</Data>
<Data>2434</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>E0070800050013000B0012000700DC03E007080005001300120012000700DC03600900003C000000010000006009000001000000B00400000100000000000000</Binary>
</EventData>
</Event>

Right before this shutdown was issued is where you would want to look for errors. Work back from this point.

The printer driver errors seem unlikely to be the cause but I would fix them first. The easiest thing to do is to go download new drivers from the vendors site that match your OS / 32bit/64bit size.

If that doesn't point you to the right direction and things son't seem to be moving along here I would take a look at http://www.techsupportforum.com/ as this type of issue is there specialty. You will be getting into the lang of analyzing core dumps if the printer driver inst the main culprit.