Computer Black Screen

I normally leave my computer run 24/7 but lately the computer has to be rebooted daily because it does the following:

• Becomes unresponsive with a black screen
• Network link goes down when this happens
• Computer can't be revived and simply has to be rebooted.

Event logs show NOTHING when this happens and I know the rough time when it happens because I have nagios monitoring my network including this computer and it tells me when it looses internet, etc.

I've replaced the video card with a brand new one yet this still happens. I'm thinking it has to be a bad PSU or mainboard but I'm unsure what to do to resolve it.

I'll try that driver verifier you mentioned. No I'm not overclocking.

When there is a black screen click the following 4 keys simultaneously and report what you see and hear into the thread:
Windows logo key + Ctrl + Shift + B
(you can practice when there is no black screen)

There are log collectors used in another forum room.
Run each V2 and DM and upload results into this thread:
BSOD - Posting Instructions

List the antivirus software in use on the computer.

Running driver verifier simply causes the computer to BSOD with the error
Stop code: DRIVER VERIFIER IOMANAGER VIOLATION
What failed: Wdf01000.sys

Trying to revert to the restore point I created before enabling driver verifier as it's in a bsod loop now.

- - - Updated - - -

I got the computer booted again from my restore point. Running sfc /scannow atm

That may be good news (a driver is causing BSOD).

See post #4.

zbook said:

That may be good news (a driver is causing BSOD).
See post #4.

I'm working on the logs now. It's been at the point where it says "compressing folder" for a while now.

When using Windows driver verifier the tutorial displays methods to turn off or recover from using the tool.
The commands should be used.
If the commands fail then use system restore.

Sometimes when system restore is used the dump files do not appear.
Without dump files little progress is made in the troubleshooting.
If there are dump files after a system restore then they can be debugged but please use the reset and bootmode commands to increase the likelihood that there will be dump files for debugging.

zbook said:

When using Windows driver verifier the tutorial displays methods to turn off or recover from using the tool.
The commands should be used.
If the commands fail then use system restore.

Sometimes when system restore is used the dump files do not appear.
Without dump files little progress is made in the troubleshooting.
If there are dump files after a system restore then they can be debugged but please use the reset and bootmode commands to increase the likelihood that there will be dump files for debugging.

You are right about the restore trashing the dump logs as there aren't any. This log tool also never finishes "compressing folder" been running like that for over an hour now. I tried the tool again and again it's stuck at "compressing folder"

There are two log collectors.
See if you can run the other and upload results.

Which AV are in use on the computer?

Place the computer in clean boot then run the V2 log collector to see if it makes any difference.

Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

If not then place the computer in safe mode then run the V2 log collector to see if it makes any difference.

Boot into Safe Mode on Windows 10