Vista Tutorial - I7 920 overclock

I recently overclocked my cpu from the stock 2.67 to 3.8
Bclk 194
cpu volt 1.4
Dram bus volt 1.50
Qpi/dram core volt 1.375
Temperature was fine
Which ran fine gave it a few tests (prime95) which was all good, but there was a problem with the sleep function if i did it a second time vista would not boot, i would just get a black screen, and twice when i turned the computer on it gave me a overclock failed message, if i restarted it all was good but i was unsure so now im running it stock.

My first question in what went wrong,
secondly i have been getting a few errors with various programs (java, call of duty 5, crysis) they have been crashing from time to time, the solution centre found a problem and gave me this message

"This problem was caused by a compatibility issue between this version of Windows and a chipset in your computer. The chipset was created by Intel Corporation. The model name of the chipset that caused this problem is Intel QuickPath Architecture I/O Hub."


The link was to an older driver than the one that came pre-installed and a few people that have also had this problem said the old driver did not fix the problem, or did not support the motherboard (thats what i got even though i have the same board, ASUSTeK Computer Inc.-Forum- P6T - Which Intel INF driver to use?)


Anyone have any ideas??


Specs:
Intel i7 920, Asus P6t motherboard, Gigabyte 9500gt 1gb, Seagate es2 barrcuda, 2gb ddr3 ram (jetram, transmedia), trition 81 cpu fan + 4 case fans



thanks

I am having the same problem...same error message. Wondering if the sleep state is making the voltage too low, so when it tries to wake up the system fails.

have you disabled C1E and EIST?

Archie...sorry to noob out, but I have no idea what those abbreviations stand for. Please explain.

C1E - Enhanced Halt State

"Whenever the OS executes the halt instruction, the CPU enters what is known as the halt state. Architecturally, what's going on in a halt state is the clock signal is shut off to the CPU for some period of time. With no clock signal, none of the logic in the chip will do anything and thus power consumption is reduced. Performance is also significantly reduced; however, the halt instruction isn't usually called during application usage, so the performance aspects of the halt state aren't very important.

The problem with the halt state is that it does nothing to reduce voltage, only current draw by stopping clocks from going to the CPU. Since Power varies linearly with both current and voltage (P = I * V), you're effectively only addressing half of the problem. The Enhanced Halt State, as Intel calls it, does two things: it reduces the clock speed of the CPU by decreasing the clock multiplier down to its minimum value (on the EE 965 series, that's 14x, or 2.8GHz), then reducing the voltage. The clock speed is reduced and then the voltage is dropped, to maintain stability.

Intel insists that the enhanced halt state is a significantly lower power state than the conventional halt state, thanks to the reduction in voltage in addition to the reduction in clock speed. While the standard halt state causes a linear reduction in power, Intel's enhanced halt state causes an exponential decrease in power, potentially offering better power savings than the standard halt state. The real world impact obviously depends on how idle your system happens to be."

EIST:

"What EIST does is very similar to AMD's Cool'n'Quiet. It is demand based reduction in CPU clock speed and voltage. Using the same mechanism of adjusting clock speed and voltage, based on the application demand, the processor will dynamically increase/decrease its clock speed between its minimum clock and its normal operating frequency, as well as voltage, in order to optimize for power consumption.

Because of the way EIST (and AMD's Cool'n'Quiet) works, there's inherently a drop in performance. The idea is this: if you're performing a task that's not using 100% of the CPU, the CPU will operate at a slightly reduced frequency in order to conserve power. So, while some tasks will require that the system run at full speed, others will run at lower speeds. "

what he said ^^^^^

im wondering if your bluescreens on wakeup are due to low voltage to the cpu , normally not a problem unless its overclocked

if your overclocking its generally a good idea to turn these options off in your bios they can play havoc with your oc

So how exactly do you enact, or turn off, the above power states?

Also...I would definitely trade an OC that ran a little cooler but that did not use the reduced power modes (that drop cpu multiplier) if it meant more stability and no wonkiness on wake up. I may give that a try also. I;m running a 940 @ 3.52 ghz (x160) with 1.2v to cpu, 1.25 to QPI, and 1.64 on Ram. Using ASUS P6T6 WS Revolution board in SLI.

its just a suggestion mate it may not work , but its worth a shot , its a good idea to turn them off anyway if your overclocking , you'll find the settings in your bios , you'll have to look them up in your mobo book or just have a poke around your bios its not hard to find

Another thing with an overclocked rig if your not bothered about the noise its also a good idea to run your cpu cooler at full speed , disable its auto setting again in bios , this keeps your idle temps down , its up to you