BSODs started happening 1-2 weeks ago :(

[kmsi063]

I have windows 7 ultimate x64, a custom built pc, it has been fine for about 3 years, but ever since about one or two weeks ago i just kept getting bsods every so often. Here are the files attached, if if you want any other information i will tell you anything you need! i wish i could pay some of you back somehow, it is so great you help people like this! it is really annoying, i use my pc for file sharing, and when it bsods, i can't access it anymore..
i do often have 4 usb hard drives plugged in at the same time, via a usb hub, and firefox/chromium for some reason always dies on facebook and youtube (maybe other site, but none i came came across) firefox just freezes up and crashes, and chromium just tells me the tab is frozen and tells me to 'kill' it. i have no idea if this happens for the same reason, but it started happening around the same time as the bsods. (chromium did let me go on facebook/youtube for a day or two, i installed it because i couldn't access them via firefox anymore, but then after 2 days they stopped working in chromium as well..) it is a mystery to me.
thanks for all of your help!

 

[yowanvista]

Bugcheck 101 is mainly caused by a defective CPU or outdated BIOS

Details about this bugcheck:
http://www.sevenforums.com/crash-loc...tml#post567135

Win 7 A Clock Interrupt... BSOD (101 Error)

   Information

Go to your motherboard's website and check your version of your BIOS. See if there are any problems you are having that are solved by a a later version. I do not often recommend flashing the BIOS because there is a risk involved. If there is problem addressed by a BIOS that applies to your computer, consider flashing your BIOS to the latest version. If you choose to do this, flash you BIOS outside of Windows.

Run Prime 95 again to test your CPU and your ram. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.

   Information

ASACPI.sys the 2005 version is a huge cause of BSOD's
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

   Warning

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.

[B][COLOR=Red]ASACPI.sys[/COLOR][/B]        fffff880`03dec000    fffff880`03df4000    0x00008000    0x42476c4c    [COLOR=Red][B]28/03/2005[/B][/COLOR] 06:30:36

[COLOR=Red][B]sptd.sys[/B][/COLOR]        fffff880`01008000    fffff880`0112e000    0x00126000    0x4ad24632    12/10/2009 00:55:14

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

Use !analyze -v to get detailed debugging information.

BugCheck 101, {61, 0, fffff880009e8180, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

CLOCK_WATCHDOG_TIMEOUT (101)
[COLOR=Red]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: 0000000000000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e8180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

Debugging Details:
------------------


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`009a9768 fffff800`02c77443 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009e8180 : nt!KeBugCheckEx
fffff880`009a9770 fffff800`02cd35f7 : 00000004`00000000 fffff800`00000001 00000000`00002710 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`009a9800 fffff800`02c1a895 : fffff800`02c3f460 fffff880`009a99b0 fffff800`02c3f460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`009a9900 fffff800`02cc73f3 : 00000000`06dd6e96 fffff800`02e43e80 fffff6fc`40004308 fffff880`009e8180 : hal!HalpHpetClockInterrupt+0x8d
fffff880`009a9930 fffff800`02d005a3 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`009a9ac0 fffff800`02cd8e2c : 00000000`00000000 fffff6fc`40004308 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x93
fffff880`009a9b00 fffff800`02d126b9 : fffff6fc`40004308 00000000`0000000c fffff800`02e43e80 00000000`00000010 : nt!KeFlushMultipleRangeTb+0x28c
fffff880`009a9bd0 fffff800`02d1228f : 00000000`00055d00 00000000`0000000f 00000000`00000000 00000000`00000000 : nt!MiZeroPageChain+0x14e
fffff880`009a9c10 fffff800`02f6e166 : fffffa80`018bf5b0 00000000`00000080 fffffa80`018bfb30 fffff800`02ca9479 : nt!MmZeroPageThread+0x7da
fffff880`009a9d40 fffff800`02ca9486 : fffff800`02e43e80 fffffa80`018bf5b0 fffff800`02e51c40 30300080`129c00db : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

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