Unpredictable BlackSOD (keyboard and mouse stops lighting up too)

[ZeroAccess]

Hello, really wasnt sure if I should put this under BSOD or not but anyways I have an odd problem. Since the beginning of April at random times something happens to my computer that causes not only a black screen but my keyboard and mouse to not light up as well and my CPU fans are at full speed.

(And its not the type of black screen that people normally get with the white mouse cursor on the screen. Its a complete loss of signal between my graphics card and my monitor.) This has happened a lot and amazingly every single time when I was away from my computer so I cant pin point exactly what causes it.

The only thing I can say is that I am usually running 2 problems when it happens. VMware + Web browser w/Sandboxie. I am sure I have a lot of other conflicting software as well but I didn't install anything new other than Microsoft updates and these programs worked before in the past without any problems.

My graphics driver was up to date when this happened, so I downgraded and it still happens... I ran stress tests, though maybe not long enough? I feel like this is a driver issue/software conflict more than anything unless my graphics card is going but it is pretty new. It wouldnt be the HDMI cable because then why would my keyboard and mouse stop lighting up and my fans race?

I am extremely well informed in the malware area so I highly doubt its that. I uploaded the log information.
The only error that happens in "Event Viewer" is this:

'Faulting application name: csrss.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc115
Faulting module name: sxs.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c9cc
Exception code: 0xc0000005
Fault offset: 0x0000000000011b2f
Faulting process id: 0x36c
Faulting application start time: 0x01d082916e7f280f
Faulting application path: C:\Windows\system32\csrss.exe
Faulting module path: C:\Windows\system32\sxs.dll
Report Id: 572eaebf-ee90-11e4-a669-005056c00008'

I also get a lot of side by side errors if that has anything to do with it and this: "Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards."

Other than that this is really hard to diagnose. This happens like once every day or so, doing a clean boot
would take forever. If anyone can help me with this I would appreciate it a lot.

 

[ICIT2LOL]

Hello Zero Access mate if you have not done so already I would try these first
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
http://www.sevenforums.com/tutorials/433-disk-check.html < if necessary include the /f and /r in the command line as per Option2
if you have or they do nothing for the problem then lets get to the very basic stuff and try my ditty

Using HW Info
PART A:
You can test the volts on the PSU with HW Info HWiNFO, HWiNFO32/64 - Download < download the right bit version and close the right hand window select Sensors and scroll down to the power section where you will see what the volts are doing see my pic. In my pic the section (Nuvoton) with VBATT is a dead give away you are in the section for the rail voltages. There are other section titles and one that pops up often is ITE
Now the voltage on the different rails have to be within 5% =+/- of what is required or the machine will not work properly if at all.
See this for the rail voltage info
http://www.tomshardware.com/reviews/power-supply-specifications-atx-reference,3061.html (Section 2.)
The original right hand window shows the machine running and is handy for that but for looking at the components in some detail close it and use the main left hand side panel
FOR OTHER COMPONENTS
PART B:
Open each small square with + in it on the section the components are in and then click on the individual component/s (it will highlight in blue) - in the right hand side will appear all sorts of details including brands speeds and other essential info that particular device. See pic for example.

PS should have said use PART A: