Getting a "a Clock Interrupt was not received..", "IRQL_NOT_LESS_THAN_OR_EQUAL", "System Service Exception" error.

[Fenriss]

first my setup info:

QX6850 w/ Coolermaster Gemini (2 X Aerocool 120mm fan)
EVGA 680i SLI
2GB Buffalo DDR2 PC8000
XFX 8800GTX
4 X Raptors in Raid0
PCP&C 1KW PS connected to an APC 1100va
winXP pro SP2
system is run @ stock speed and never OCed.

started getting "IRQL_NOT_LESS_THAN_OR_EQUAL" BSOD and crashes after i updated my EVGA 680i SLI bios' to P31. i rolled back to P27 (bios i had before the update. system was stable prior to update) but the random crashes still happens.
installed Vista home prem and started getting the "a Clock Interrupt was not received.." BSOD along w/ the IRQ... and other BSOD crashes.
tested the mems w/ memtest, 12 passes w/out errors. swapped it w/ a US mod DDR21066 and ran memtest w/ 10 passes w/out errors. loaded windows and still the BSOD occurs.
temp for the CPU never go beyond 55 and the 8800gtx beyond 70 during load.

any ideas?

 

[myocardia]

99% of all BSOD's are caused by RAM. Assuming you're giving your RAM enough vdimm, and have the timings set correctly, it sounds like you may have a problem with your motherboard.

edit: Although, almost all of these types of errors are user error.

 

[VirtualLarry]

Checked your northbridge temps recently?

 

[RanDum72]

I'm getting the same with my MSI P6N Diamond
CPU - C2D E6550 (1333mhz FSB)
RAM - 2gb OCZ DDR2-800 (Running at stock 5-5-5 20 (2T) timings.
Ran memtest for 4 hours without an error.
EVGA - 8800GT 512mb
Coolermaster 650w PSU, good rails
WinXP SP2

All temps are below normal (meaning they run cool) at idle and at load. I tried Corsair Dominator DDRII-800's and the same result. It seems tobe more stable with the OCZ's although it still happens occasionally. I have some OCZ DDR2-1066 sticks coming in that are supposedly SLI certified but I doubt the memory is the problem. I'm guessing its the chipset (680i) not playing nice with 8800-series video cards. I have tried an ATI X1650 video card and it doesn't seem to have the errors.

 

[CTho9305]

Did you happen to update to newer video card drivers when you updated the BIOS? Most BSOD's that aren't hardware-related are caused by drivers.

 

[Fenriss]

temps seems fine. although i just got some Thermalright Ultra 120 extreme, HR03 and HR05 SLI and will install 'em sometime this week just to be sure. i also got a Prelude to replace the onboard sound. since one of the crashes i'm getting during gaming is the Screen freeze w/ the looping sound. googled this error and it supposed to be a Bad pool mem error related to realtek drivers.

BSOD appear w/ equal regularity when i adjust the Mem vdimm to V2.1 or when i run the bios @ default. i had the mems @ default Vdimm prior to flash w/out any issue.

i should stress that all my probs started when i flashed the bios and rolling back didn't help. i'm getting another LGA775 mobo to test.

 

[imported_amod]

Hi,
Have you installed any new hardware recently ?
That might be one of the issues.

Also check your partition with paging file and OS partition for bad sectors. An autochk with repair option should do the job.
I was having this problem till abt 2 weeks back.
I found bad sector in my paging file while scanning last week. Then I moved by OS partition to another harddisk and send the harddisk for replacement.

No BSOD's after that.

Cheers
Amod

 

[Fenriss]

no new hardware. i ran a windows Diskcheck and it gave no errors.

 

[imported_amod]

Hi,

From the BSOD message, can you write down the second line..
The one which looks like 'ERROR XXXXXX - (Some description)'

That normally talks abt the error description.

Cheers
Amod

 

[The-Noid]

Seems like bad power supply or bad motherboard at this point.

 

[RanDum72]

Got some PC1066 DDRII to test with my mobo. Unstable at 1066 speeds. upped the voltage, relaxed timings. still unstable. Clocked the memory down to 800 and all of a sudden, peace and quiet! I think the 680i chipset, while supposedly able to run 1333FSB CPU's, are very picky with the memory you pair it with.

 

[BonzaiDuck]

I got a similar BSOD with my 680i-based system while fiddling with SpeedStep and Control-Panel "Power Options." I'd worry that it was related to hardware, but I've pretty much confirmed that the settings in BIOS and OS didn't play well together. I've put it through all kinds of stress, and it's rock solid.

You might want to look and see what you have enabled in BIOS.

On the high-end stock memory speeds, it looks as though some folks still want to use a memory divider to run the memory faster. I've argued that it still introduces wait-states into the mix between the processor and memory, even if it speeds up memory operations internally. IF you can tie down the latencies to CAS 3 and pre-charge delay of half the spec, you're almost cutting an average memory operation's clock-cycles in half, and if your improvement in speed is equivalent to looser timings under high-Megahertz, why not use that approach -- especially if you seem to be getting instability with other than 1:1 dividers?

That's my 2-cents-worth . . .

 

[RanDum72]

Thats exactly what I did. Lower 800mhz speed but really tight timings (4-4-4-10). I have T at auto although I may try 1T just for the heck of it. But for now, just enjoying a nice, stable setup. After a week, when I get bored, I might screw around with the settings.

 

[BonzaiDuck]

Mine are running at 712 Mhz, with timings 3,4,4,8. I was running a 1T command rate -- very reliable with these Crucial Ballistix -- until I added an additional 1GB kit so I could have 3GB total. The fact is -- I never attempted to run the 3GB at 1T or even test it yet. Setting the command rate to "Auto" with the 2GB kit alone would default to 1T, and the Auto setting with all slots filled defaulted to 2T.

Do you have Everest benchmarks?

 

[soccerballtux]

ALL YOUR BASE ARE BELONG TO MOTHERBOARD

is what this means. GG.

 

[Fenriss]

i ran my mems @ mobo default. it was stable prior to the bios update. then after when the system started crashing i upped the vdimm to the rated volts but that didn't help. also reset all the mobo setting to default. also didn't help.