Need help Intel blames MS and Corsair for BSOD's

I am running w7 Ultimate x64 and keep getting this BSOD:


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


Loading Dump File [C:\Users\Joseph\Documents\My Received Files\050510-24632-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03414000 PsLoadedModuleList = 0xfffff800`03651e50
Debug session time: Wed May 5 07:23:27.091 2010 (UTC - 4:00)
System Uptime: 0 days 0:27:46.215
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff880009b1180, 4}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

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.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b1180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: d

STACK_TEXT:
fffff800`00b9bfb8 fffff800`03432443 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`009b1180 : nt!KeBugCheckEx
fffff800`00b9bfc0 fffff800`0348ccf7 : 00000000`00000000 fffff800`00000004 00000000`000030d4 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff800`00b9c050 fffff800`039fa895 : fffff800`03a1f460 fffff800`00b9c200 fffff800`03a1f460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00b9c150 fffff800`03480af3 : fffff880`100ca352 fffffa80`06e14101 00000000`046c6b64 fffff800`00b9c200 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00b9c180 fffff800`03446173 : fffff800`035fee80 fffffa80`03cf4b60 fffff800`035fee80 00000000`00000004 : nt!KiInterruptDispatchNoLock+0x163
fffff800`00b9c310 fffff800`0348d2a9 : 00000000`00000002 fffff800`03610000 fffff880`00000005 00000000`000000ff : nt!KxWaitForSpinLockAndAcquire+0x23
fffff800`00b9c340 fffff880`04612f3a : 00000000`00000001 fffff800`03629600 fffff800`00b9c430 fffffa80`06e131a0 : nt!KeAcquireSpinLockRaiseToDpc+0x89
fffff800`00b9c390 fffff880`046144a1 : fffffa80`06e131a0 fffffa80`06e04050 fffff800`00b9c430 fffffa80`06e041a0 : USBPORT!USBPORT_AcquireEpListLock+0x2e
fffff800`00b9c3c0 fffff880`0461c259 : fffffa80`06e041a0 fffffa80`06e041a0 00000000`00000003 fffffa80`06e131a0 : USBPORT!USBPORT_ProcessNeoStateChangeList+0x39
fffff800`00b9c430 fffff800`0346f493 : 00000000`00000000 00000000`00000000 00000000`00000001 fffffa80`04e689f8 : USBPORT!USBPORT_DM_IoTimerDpc+0x29
fffff800`00b9c460 fffff800`034906a6 : 00000000`00000002 fffff800`00b9c6a8 00000000`00000000 00000000`00000000 : nt!IopTimerDispatch+0x132
fffff800`00b9c570 fffff800`0348fa26 : fffffa80`08e71e50 fffffa80`08e71e50 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`0349057e : 00000003`dc3eca1e fffff800`00b9cc58 00000000`00019f29 fffff800`036017a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`0348fd97 : 00000001`023faccb 00000001`00019f29 00000001`023faceb 00000000`00000029 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`0348cdfa : fffff800`035fee80 fffff800`0360cc40 00000000`00000000 fffff880`10114ea0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


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_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner

I have received this 5 times in the last 7 days, and Intel has been of no help. They said that Corsair is to blame as the memory isn't compatible. Corsair faxed me the spec sheet they got from Intel concerning the memory and even highlighted where they said it was compatible. After the 3rd BSOD, I got testy with the Intel tech who said it was a windows issue. So now I'm coming here for help. If anyone can help with this. I would be extremely happy, as nobody so far can point to where this is coming from. Each of the last 5 BSOD's are identical.

John, thanks for that info. I have more than adequate cooling for my machine. She's liquid cooled, except for the NB heatsink which is left to the air movement from the chasis fans. I am planning on adding that waterblock in the coming days, after I get back the memory from Corsair. My cpu temps under liquid cooling is around 34*c. I haven't even overclocked this cpu yet, as I'm still trying to chase down the BSOD's. After several chats with Intel and Corsair, Corsair is the only one willing to RMA their products. Also, I have talked with a local comp tech and he thinks maybe the MB might be the problem. I had the comp stress tested before, per Intel's pushing, and they said they tried to kill it. Nothing they could do would get my rig to die. It passed with no problems. He was very impressed with the way my rig is set up. They had it for almost a week. I have read that ASUS has had problems with the MB in the past, and I'm trying to rule out everything else before I ask ASUS to step in and help. Of all the rig's I've put together in the past 15 years, this is teh first one that is driving me crazy with all the BSOD's. I did swap out the video card into my wife's comp just to see if it would cause a bsod over there, and it ran fine with no problems. But as her's is an AMD rig, running on ddr2 memory, that's about as far as I can go with swapping out hardware in house. I may take it back down to the tech and tell him to start swapping out components until he can narrow it down. I still believe it's a cpu issue, but Intel is giving me a bunch of crap about it. I'll keep you posted.

You can try underclocking the memory.

It will make ZERO noticable perfomance difference.

My (now older) rig had a 1066 mhz bus and I bought 1066 mhz ram but running it at that clock speed heated the ram up so much I couldn't even touch the heat sinks. I knew the ram wouldn't last long at those temps so I under clocked it to 800 mhz and the machine has been rock solid for years now. Knocks maybe 0.5 fps off of games :/ I was then able to overclock the CPU in winter months by 15% and THAT give an exact 15% increase in frame rates. CPU speed is everything, memory speed is nothing.

The tolerances on todays MB's and RAM are tighter than ever. Easing back on the "stress" on the RAM may make it work a lot more reliably and you won't notice the difference at all. Will make overclocking the CPU more possible as well and then you'll end up with more performnce in the end.

Thanks for the reply. I was told by Corsair that I shouldn't do that. I'll try that when I get me memory back from them. Sent them in for RMA, and just received an email from them. It'll take an extra 5 business days to get them back. This to me is unacceptable, considering I had to pay to have them sent back. So now it's gonna be at least 2 weeks before I get them back. I will try lowering them and see what happens. I was able to get the cpu up to 4.2GHz with only a 5*C raise in temp. I still need to get a NB waterblock tho, as those temps are a little high for my comfort zone. I will keep you guys updated as we progress along.