New
#11
Haven't have the time to fully set and watch the test, don't want it to run it by itself and it blow up if that the case. GPU and CPU test will happen this evening. Memory test tomorrow morning.
Driver Verifier will be safe to leave running, it's designed to monitor the drivers installed on your system, and create a BSOD if the drivers' behavior meets a certain variable set when configuring Driver Verifier.
All test show that there nothing wrong but it still doing it....mmmmm Any ideas?
The original BSOD from the first post
An expected clock interrupt was not received on a secondary processor in anMP system within the allocated interval.
Ensure you have configured a Kernel Memory dump instead, if a Stop 0x101 is still occurring, a Minidump will not contain enough information - Dump Files - Configure Windows to Create on BSOD
You will need to place the file into a zipped folder, and then upload to a file sharing site such as Dropbox or Skydrive. Make sure the folder is placed in the Public folder if using Skydrive. Post the link to the file afterwards.
Is Driver Verifier still running? Stop 0x101's with Driver Verifier running, indicate more of a hardware related issue.
Here is the BSOD. What going on now is that sometimes the system starts to respond slowly. An example is that the mouse arrow disappear and takes a moment to get caught up with where I'm moving the mouse. Control+Alt+Delete responds slow as well. Only a few moments and then it back to working fully. I check out the processing but couldn't see anything out of the norm. When this is happening I shut down the system and than it all speeds down like it turn off no fans running or CPU spinning away but it still on. I then have to cold boot it to make it turn off. It makes no sense. A full system scan with MSE and other virus and trojan scanners show nothing. :/