Windows 10: Black Screen

the BSOD happened about an hour or two ago... so i hope that any information is still contained within that zip file for you! Thank you so much for all of your swift responses and help btw! Much MUCH appreciated!

 

There were 2 BSOD mini dump files.
The bugchecks were 101.
The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 32 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Testing 32 GB of RAM at one time may take several days and is ideal testing conditions. If you are unable to be without the use of the computer for this duration of time you can remove 16 GB and test 16 GB at one time. This would enable testing the multichannel capability of the motherboard.
Then perform a 2nd test with the other 16 GB RAM for 8 or more passes.
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take pictures and post images into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials

Code: 12/14/2017 1:01 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 101 P2: 18 P3: 0 P4: ffff98006094b180 P5: 4 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\121417-13343-01.dmp \\?\C:\Windows\TEMP\WER-16953-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER54A7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER54A7.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER54B8.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_101_76cb8ed0d479e58a56bd174d5a93eddd97587_00000000_cab_193c5b9d Analysis symbol: Rechecking for solution: 0 Report Id: f899a357-3668-4c77-baab-13e752d472ae Report Status: 2049 Hashed bucket:[/quote] Code: BugCheck 101, {18, 0, ffff98006094b180, 4} Probably caused by : memory_corruption Followup: memory_corruption CLOCK_WATCHDOG_TIMEOUT (101)An expected clock interrupt was not received on a secondary processor in anMP system within the allocated interval. This indicates that the specifiedprocessor is hung and not processing interrupts.Arguments:Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.Arg2: 0000000000000000, 0.Arg3: ffff98006094b180, The PRCB address of the hung processor.Arg4: 0000000000000004, 0.[/quote]

 

Soo.... it looks like that happened once, correct? I think what ended up happening with that was when I reset the bios, I loaded in the wrong xmp file and the wrong setting for the ram was selected. So, for now ... everything has been running smooth based on what we did thus far. PSU unit is delivered Monday and I will install that and see how she flies before I dive into testing the ram. This is the studio machine and it's gonna be hard to test individual sticks of ram.... they're 8gb sticks not 16. If I still encounter issues I have no other choice. The only thing I have noticed that persists is randomly under loads is the leggy mouse.... and I'm curious to know if this still would b a power consistency issue with that unit that I'll find out after Monday cures, or if it's a driver related issue with the mouse I'm using. I know there a sleu of ppl that suffer from problems with the MX Master mouse from Logitech and I've spent days going around trying to solve that, and I still don't know if it's Logitech or Creators Update issue. The problem did seem to diminish when I isolated the router to 5ghz transmission as opposed to 2.4... but alot of devices in the studio still rely on 2.4 so that solution is impractical. I might try just moving it downstairs away from the machine. The other solution that I've tried is setting full power on usb devices and thought about setting the priority level for it.... but I don't think that setting stays after a reboot or full power down. But ... that's the run down so fsr... I'll keep u updated when the new unit arrives and again thank you for ur persistence in helping!!!

 

Please update the specs in the "My Computer" section:
How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Site Use Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, etc.)

 

Updated all of my info as best possible.

Installed new PSU unit today.

Tried to reproduce the electronic noise upon opening Adobe illustrator, and it occurred again.

Possible software issue?

I updated every driver with Easy Driver....
Uninstalled Adobe illustrator, and reinstalled it.

Tried to duplicate the problem by opening every Adobe software, leaving illustrator till last... while exporting files.... So the system was spiking, 100% cpu and temps at 68 degrees Celsius.... still could not duplicate the issue.

With that said, .... that makes me think a possible software issue cuz if it's hardware.... it should be reproduced when stressing the system like that....

 

When installing drivers the best source is the computer manufacturer / motherboard manufacturer.
The next best source is the component manufacturer (Nvidia, Intel, etc)
The software websites that install drivers can install anything.
Sometimes clean installs are needed after using these websites.
Please uninstall these drivers and use computer manufacturer/ motherboard manufacturer drivers.

For any BSOD please place post a new zip for troubleshooting.

When Memtest86+ version 5.01 has completed 8 or more passes please use a camera to take a picture and post an image into the thread.
Once RAM /DIMM / MB problems are ruled in / ruled out the next test will be CPU.