Computer screen goes black, computer non-responsive

paulog16

Reputable
Jul 4, 2014
22
0
4,510
Hi all,

I built a new pc in August. Everything ran well up until recently. My computer screen turns off, the sound goes away from headset, but my computer is seemingly still running (all lights on computer are running, fans are running, mouse etc is still on). The off button doesn't respond too and I have to turn off the switch at the PSU. I thought it was my overclocks failing, but even after resetting everything, it is still happening. It is seemingly random, it can be middle of a game, or it can happen when I'm afk and computer is idle. All GPU and CPU drivers are up to date, and so is my motherboard. My computer specs are:

R7 1700
GTX 1070 ROG Strix
Asus x370-f Gaming
16GB DDR4 TridentZ RGB Ram
thermaltake toughpower grand 650w RGB
Windows 10 pro version 1709
 
Solution
Some users have reported system crashes, after that December Windows update was pushed out, so it is definitely a possible cause.

Even the Spectre vulnerability patch that was released, a couple of weeks back, caused some systems to spontaneously reboot or lock up.

paulog16

Reputable
Jul 4, 2014
22
0
4,510
Hey, so I did a custom view, filtering for 'critical' and 'The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.' event ID 41. Doesn't say too much
 


You need to look at the event(s) that happened just before the red error event. Event ID 41 happens after the event that actually caused the black screen.
 

paulog16

Reputable
Jul 4, 2014
22
0
4,510
There is nothing really helpful. They all say 'A connection to the Windows Update service could not be established' or 'The Network List Manager reports no connectivity to the internet'. One Error occured before the critical event 'The previous system shutdown at 01:31:37 on ‎19.‎01.‎2018 was unexpected.' and one after 'Audit events have been dropped by the transport. 0' and after that there is a weird warning:

'Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Not Tested
User has logged on with AAD credentials: No
Windows Hello for Business policy is enabled: Not Tested
Local computer meets Windows hello for business hardware requirements: Not Tested
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Not Tested
Machine is governed by none policy.
See https://go.microsoft.com/fwlink/?linkid=832647 for more details.'

This pattern of errors and that warning above occurred every time there was a critical event ID 41
 

paulog16

Reputable
Jul 4, 2014
22
0
4,510
Interestingly, the last major update for windows on 7th of December (version 1709), would be when the shutdowns would have started. I left for christmas on the 16th of December, so the problems could be stemming from the update?
 

paulog16

Reputable
Jul 4, 2014
22
0
4,510
There are hundreds of errors occurring on the 7th of December, the first critical event ID 41 occurred on the 9/12. Most of the errors look like this 'Performance power management features on processor 2 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.', event ID 35

Is there anyway I can send you the event history?
 
Some users have reported system crashes, after that December Windows update was pushed out, so it is definitely a possible cause.

Even the Spectre vulnerability patch that was released, a couple of weeks back, caused some systems to spontaneously reboot or lock up.
 
Solution