Solved BSOD of indeterminate origin, errors 0x00000101 and 0x0000001e

My computer has been hanging about 2 or 3 times a week without generating a blue screen. The mouse and keyboard fail to respond (including Caps Lock and Num Lock keys). On rare occasions such as last night, I will get a BSOD. I am uploading my files in accordance with the posting instructions and am hoping that someone can give me some insight as to possible resolutions. I have had several issues since purchasing this computer and have almost reached the point of sending it back to the manufacturer (which would result in me losing all my installed programs of course when they wipe the system), but would like to attempt fixing the issues one last time. In addition to the BSOD files, I have added my Event Viewer Logs to this posting.

Thank you to anyone whom can assist in this matter.



My system information is:
System built by CyberPowerPC in November 2011 (7 months old)
Last clean reinstall was around December 15th 2011.

OS: Windows 7 Ultimate-64bit OEM
Motherboard: Giga-Byte GA-970A-D3
CPU: AMD 8150 3.6 GHz(8-core)
RAM: 16 GB DDR3 1600MHz (4 x 4GB)
Video: AMD Radeon 6950 (2GB DDR5) x 2, crossfired
Sound: Creative Labs Audigy SE
OS HD: 60 GB OCZ Agility 3 SATA III SSD
Data HD: 2 TB SATA III
Power Supply: Azza Titan 1000W
Antivirus: Microsoft Security Essentials
Malware: MalwareBytes (does running MSE and MBAM cause a conflict? I thought MBAM was malware only, but have seen posts calling it an antivirus)

Related to VKbms.sys HID mini driver for USB Fx2 Device from Windows (R) Win 7 DDK provider. I would remove to test.


http://www.sevenforums.com/crash-lo..._watchdog_timeout-troubleshtg.html#post567135

In the middle of typing my post, the computer hung again and then would not restart. I had to do a system restore in order to reboot as start-up repair could not fix it.
I have removed 4 instances of VKbms.sys from my computer, all of them were for my Razor Death Adder mouse.

Other items of concern to me are the "Device cannot start" entries listed on the PERFMON report, but I'll try handling those after working on the current attempt at fixing the system. I ran FurMark to test my video cards and allowed them to get to 90 degrees C for over 5 minutes. I will also be running GIMPS to stress test my hardware and see if the error occurs.

In looking at VKbms.sys, I noticed that i had two separate versions of the Black Adder mouse software installed; Black Edition, and regular edition. Black Edition is NOT for my mouse. However, since my mouse will function with Windows drivers, I will be installing both editions of the Black Adder software for testing purposes and see if this corrects my issue. If the issue is resolved, then I will try to install the most current version for the mouse again.

Thank you for your input and help zigzag, I will post to this thread again when I have something substantial to report.

Cody

While running Prime95 aka GIMPS as stated in one of the above linked threads for diagnosing error x0101, I keep getting the following error "ILLEGAL SUMOUT". From looking at this, and additional information, plus the duration and the various BSOD's I have received in the past, along with the fact that logical CPU's 2 through 8 are not getting errors; I am starting to wonder if I am getting the BSOD's and the freezes/hangs due to an actual hardware failure in the CPU. I have one of the very first AMD 8150's (8-core) processors.

I am still willing to attempt to figure out the root cause as I am not completely certain that the theory I currently have is accurate. Feedback would be appreciated though.

I am also attaching the two most recent BSOD's which has occurred since the initial posting of this thread earlier today and occurred within minutes of one another.


[May 26 17:50] Worker starting
[May 26 17:50] Setting affinity to run worker on logical CPU #1
[May 26 17:50] Resuming primality test of M54466201 using AMD K10 FFT length 2880K, Pass1=640, Pass2=4608
[May 26 17:50] Iteration: 9497/54466201, ERROR: FFT data has been zeroed!
[May 26 17:50] Possible hardware failure, consult the readme.txt file.
[May 26 17:50] Continuing from last save file.
[May 26 17:50] Waiting five minutes before restarting.
[May 26 17:56] Resuming primality test of M54466201 using AMD K10 FFT length 2880K, Pass1=640, Pass2=4608
[May 26 17:56] Iteration: 9498 / 54466201 [0.01%].
[May 26 17:56] Possible hardware errors have occurred during the test! 6 ILLEGAL SUMOUT.

Two most recent are the same as the earlier ones.

I didn't realize I had posted them already. Here are 3 of the 4 that occurred while trying to run either GIMPS or Hot CPU Tester Pro. These three gave the x101 BSOD, the last one gave the xF4 BSOD (general hardware failure, I believe), but did not write a dump file.

The three crashes from May 27 are still BCC101, just as before.

I know they are BCC101 also. However, I removed all drivers named VKbms.sys and followed all the testing procedures of
STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg
but I am still getting the same errors.
I suppose my question is at this point, do you believe the error to be a hardware failure? I believe the issue to lie within Core 1 of my 8 core processor. If you do not agree, can you give me any ideas on further diagnosis procedures, or options to try.
I am also going to open a trouble ticket with cyberpowerpc.com since I purchased the system from them.

Throughout this process, I am learning more and more about crash analysis and I appreciate your time and effort.

101 & 124 are general hardware complaints and from this end contain very little information that would help you. The stress tests will tell you more which component is mis-behaving. I think it is a good idea to open that ticket.

Thanks again for all the help zigzag. After all the elimination process we did. I opened a ticket with the manufacturer and have had to ship the PC back to them. They have informed me that either the motherboard or Core 0 of the CPU is bad and they will be doing testing/swapping to repair the issue.

Let us know what they find when you find out. Thanks for posting back and keeping us updated.