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

[ers1284]

I've been plagued by BSOD 101 errors (A clock interrupt was not received... blah blah) the last few days. Specs are attached in the report.zip and updated on my profile here. Also attaching the last few dump files. I've analyzed them myself but can't decipher exactly what the problem is. I have a theory it may be related to how I have my HDD's and programs organized... I'm using a 500 GB HDD with just Windows 7, Microsoft Outlook, and a few 'core' apps installed on. Almost everything else (games, Firefox, misc apps) I routed to the 1 TB HDD. I suspect this is a issue because I get alot of BSOD when using Firefox, (using IE8 to type this now), iTunes, or playing various games... all of which are installed to the 2nd HDD.

Also, I was getting alot of random shutdowns when using Vista prior to Win7 install. The shutdowns would happen whenever I was doing anything graphic intensive and the system would just shutdown. No BSOD, no warning, just turned off. After installing Win7, the system would still crash but reboot, however my mouse and keyboard would be locked out unless I powered down the entire system. After eliminating any software issue, I ended up taking everything off the mobo, reseating the mobo to the case, and methodically reseating every piece of hardware carefully as well as doing a fresh Vista-->Win7 install. That seemed to solve the 'random shutdowns' but now i'm getting BSOD all the time.

All drivers are updated, BIOS updated, chipset, etc etc.

Anyway, I hope someone will be able to spot something I've missed... I appreciate any help!

 

[torrentg]

In no particular order:

sfc /scannow should be run from elevated command prompt.

Look into AMD forums or AMD website for "tlb" fix.

Completely uninstall AVG from system. Run memtest for as long as you can stand to.

Scan with Malwarebytes.

Use event viewer to click on links as bottom to get Microsoft's recommendations for each error.

Disable floppy support in bios if not used. Better to completely detach from system. Disable all unused ports in the bios, namely, serial. Disable RAID controller in device manager if not in use. (I see you have no driver installed for it now.)

Unlrelated, but get Bonjour off the system the proper way. Google is helpful here.

 

[ers1284]

sfc /scannow should be run from elevated command prompt.

-I did that, several times before. Scan doesn't find anything.

Look into AMD forums or AMD website for "tlb" fix.

-I reseached that already too. My BIOS has an option to implement TLB fix or leave it disabled by default. It makes no difference if it's on or off.

Completely uninstall AVG from system. Run memtest for as long as you can stand to.

-I don't think AVG has had anything to do with my crashes. I was getting them before I even installed it, and still getting them after uninstalling it. I'm fairly certain my memory isn't the culprit either- I replaced the sticks with 2 others from another computer that is working fine.

Scan with Malwarebytes.

-I don't think it's Malware either. These problems are after fresh installs and I'm pretty diligent about computer security. I have scanned several times before though.

Use event viewer to click on links as bottom to get Microsoft's recommendations for each error.

-Even viewer is about as useful as the minidumps. Just alot of logs about the system shutting down unexpectedly without pointing to any possible causes or suggestions.

Disable floppy support in bios if not used. Better to completely detach from system. Disable all unused ports in the bios, namely, serial. Disable RAID controller in device manager if not in use. (I see you have no driver installed for it now.)

-Did both of those, no change.

Unlrelated, but get Bonjour off the system the proper way. Google is helpful here.

-No change.

 

[torrentg]

Alright. Seems the antivirus suggestion hasn't been tried. It has a decent chance of being the possible solution. I'd try that if all else fails. It's .exe has been mentioned in dumps and for other reasons too.

Only way to be certain about memory is to run memtest for extended periods of time. 5 hours at least. 10 better.

 

[H2SO4]

In addition to the excellent assistance by torrentg...

These types of error messages are relatively simple, from a certain viewpoint: as frequently happens during normal processing, one core (processor) attempted to get the attention of another core, in order to synchronise their activites with respect to an operation that requires processor coordination. Described using "official" terminology:

"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."

The trigger for the crash is the "sender/requestor" processor going "wtf? why is there still no response after almost half a second?!?" Those inter-processor interrupts (IPIs) are some of the most critical activity imaginable, and an unrequited IPI is absolutely lethal - hence the crash.

AMD procs had known issues which manifested themselves in this manner under Vista and Win7. There were/are many possible problem permutations, some solved through BIOS updates, and some necessitating fiddling with the "Translation Lookaside Buffer" (TLB), as per torrentg's suggestion to look up 0x101 and AMD and TLB.

Your real aim is to give yourself the best possible chance of discovering a software cause for the target processor to go unresponsive, and thereby avoid the most obvious conclusion - that the processor is periodically unresponsive because of hardware-level defects

I can confidently tell you that the browsers, apps, and games cannot be the root cause of this problem, even though I don't doubt your observation that the operation of certain software seems to more easily trigger the crash. What you're looking for will be in one of the following categories:

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)

Good luck with it.

 

[usasma]

Your RAID controller is listed as a problem device in the MSINFO32 report:

RAID Controller PCI\VEN_105A&DEV_3F20&SUBSYS_37161462&REV_00\4&15C850D&0&0048 The drivers for this device are not installed.

Please install the proper drivers for it.

You had numerous problems with the XFX Graphics card installer on Nov 1st - what did you do to finally make it work?

Your machine seems to have started spitting out errors in large quantities on Oct 31. Was this the day that you installed Windows 7, or was there something else done on this date?

It seems to start with difficulties installing a Logitech device - what device were you trying to install, and what did you do to finally make it work?

AVG also installs drivers that work on a low level in your system, so I'd suggest that you uninstall it and install a fresh copy.

It all boils down to this (from H2SO4):

What you're looking for will be in one of the following categories:

a) BIOS bug (you have the latest BIOS version installed)
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)