Frequent and Various BSODs while installing/updating and on Youtube.

[Skyde]

Computer Specs:
CPU: AMD FX(tm)-8150 Eight-Core Processor
Motherboard: Gigabyte Technology Co., Ltd. GA-970A-D3
BIOS: Award Modular BIOS v6.00PG
RAM: 16.00 GB
HDD: ST2000DM001-9YN164 ATA Device
Sound Card: (1) ATI HDMI Audio (2) Realtek High Definition Audio
Graphics Card: AMD Radeon HD 6800 Series
OS: Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1

I purchased this computer in March and since around Day 4 of ownership it has been giving me frequent blue screens. The most common is STOP Error 0x00000101 but I have received a wide variety of other kinds. They happen pretty much daily with as much as 5 a day. I finds they happen most often when installing or updating games on my computer or while watching YouTube. Only once have I ever actually had a BSOD while playing a game. Around the end of July I tried a fresh install of Windows and updated my BIOS using a program on a disc that came with the computer. A little after that I had an issue where my power supply failed and I needed to send the PC in for repairs and I made them aware of the blue screens. They replaced the power supply and Graphics Card but I am still receiving the blue screens. I would like to figure out the blue screen issue so that I do not need to waste another $80 sending the computer in for repairs and possibly having nothing fixed. Thanks for any future help.

 

[koolkat77]

Welcome

For an insight on the 101 bug check, go through this thread:
:ar: http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

This most of the time indicates problem with the CPU/Processor of the computer.

Let us know if your computer is under warranty and what you try from the guide.

We'll enable driver verifier seeing the various bug checks you got.

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Driver Verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier and press Enter
- Select Create custom settings (for code developers) and click Next
- Select Select individual settings from a full list and click Next
- Select everything EXCEPT FOR Low Resource Simulation and click Next
- Select Select driver names from a list and click Next
Then select all drivers NOT provided by Microsoft and click Next
- Select Finish on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR="red"]BugCheck 101[/COLOR], {19, 0, fffff88002fd7180, 3}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="red"]CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.[/COLOR]
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002fd7180, [COLOR="Red"]The PRCB address of the hung processor.[/COLOR]
Arg4: 0000000000000003, 0.

 

[Skyde]

Sorry about how long it had taken me to respond. So I tried to run Driver Verifier and after the screen with the windows logo I immediately received a BSOD. I tried to restart 4 more times and each time resulted in the same thing. Checking my minidump folder afterwards it only left 1 minidump even though I experienced 5 BSOD's. Enclosed in the zip is that one minidump, as well as two minidumps unrelated to the driver verifier that have happened since the last post.

 

[koolkat77]

I have seen the dumps, the one with driver verifier does not reveal much just something related with USB but I doubt thats the issue. The other two give the same bug check = 101

Did you do a clean install on this system after you purchased it?

Recently it was found (here: http://www.sevenforums.com/crashes-...0x00000101-stop-0x0000009c-3.html#post1869800 ) that a wipe and reinstall of Windows fixed a STOP 0x101 problem. I'd have to recommend at least running SFC.EXE /SCANNOW on any PC that has this problem (simply because it's too easy easy to do and it may fix things). Thanks to writhziden for pointing this out!

 

[Skyde]

I did a clean install around the end of July.

 

[koolkat77]

Okay, did you take the tests from the link on post #2?