bsod, clock interrupt not received on secondary processor + 1 other

[pmarquez01]

am getting 2 bsod on computer after installing a printer? was working without flaw up until then. first (and most persistent) is the one on the subject line and the other is "problem has been detected and windows has been shut down to prevent damage"

I've attached photos of both with appropriate minidumps for anyone who would like to give this a shot. I already uninstalled any drivers associated with the printer. I had a video card radeon hd 4670 that I uninstalled and actually got to go 4 hours without a reboot, but it happened anyway. I have bitdefender total home security running, but I have for the better part of a year without any trouble.

Any help is appreciated, thank you.

 

[writhziden]

The following drivers may be outdated:

PS2	fffff880`04366000	fffff880`0436f000	Thu Sep 07 16:49:03 2006 (4500a1df)	0000d72b		PS2.sys
AtiPcie	fffff880`017f8000	fffff880`01800000	Mon Nov 06 09:59:54 2006 (454f6a0a)	000104a1		AtiPcie.sys
rtlprot	fffff880`02c26000	fffff880`02c31000	Fri Apr 20 03:16:48 2007 (46288500)	0000bd49		rtlprot.sys
usbfilter	fffff880`042f8000	fffff880`04302000	Wed May 28 16:54:15 2008 (483de297)	000111b5		usbfilter.sys
Rt64win7	fffff880`02c6f000	fffff880`02ca1000	Thu Feb 26 02:04:13 2009 (49a65b0d)	0002eb30		Rt64win7.sys

PS2.sys
AtiPcie.sys
rtlprot.sys
usbfilter.sys
Rt64win7.sys

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\pmarquez01\022612-20763-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03291e70
Debug session time: Sun Feb 26 00:09:12.889 2012 (UTC - 7:00)
System Uptime: 0 days 3:13:19.406
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80080e8028, b6000000, 181}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80080e8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000181, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  sqlservr.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02f6ca88 fffff800`0301d903 : 00000000`00000124 00000000`00000000 fffffa80`080e8028 00000000`b6000000 : nt!KeBugCheckEx
fffff880`02f6ca90 fffff800`031da293 : 00000000`00000001 fffffa80`080e9d30 00000000`00000000 fffffa80`080e9d80 : hal!HalBugCheckSystem+0x1e3
fffff880`02f6cad0 fffff800`0301d5c8 : 00000000`00000728 fffffa80`080e9d30 fffff880`02f6ce30 fffffa80`0ea52000 : nt!WheaReportHwError+0x263
fffff880`02f6cb30 fffff800`0301cf1a : fffffa80`080e9d30 fffff880`02f6ce30 fffffa80`080e9d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f6cc80 fffff800`03010e8f : fffff880`02f64180 00000000`00000001 fffff880`02f6ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f6ccc0 fffff800`030c2e6c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02f6ccf0 fffff800`030c2cd3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6ce30 fffff800`030ca850 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`08d2d8f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXSave+0xad


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Run these hardware tests to supplement the above informational link:

• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • 
    Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
    
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
  
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Start with http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html and holler if you need any help.



Update the above listed drivers as they are all important to the system running properly.



Also, please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with a full crash report rather than just the .dmp files. While the .dmp files provide nearly 90% of the useful information we use, they do not give the full picture without the rest of the reports and logs.