I've learned that 1366 can be quite weird when trying to find a stable OC, one day it can be several hour P95 stable and the next it will BSOD every 30mins.
I think your just shooting for too high of an oc off the bat, my X5650 & 5670 do about 4.2 @ 1.35V, 4.5 needs somewhere around 1.45V on both.
FWIW my X5650 has seen up to 1.66V Core, 1.55V VTT & 2.2V Dimm (I don't recommend this of course) all at once and it's still does just the same as when I got it.
I don't use P95 because it puts un realistic stress on the hardware I stick to games and AIDA64 stress test
Sounds about right. I think in my case 4.5G was the line past which OC did more harm than good (clocks went up, but perf went down for some reason, not throttling).
Still did a few benches at 4.7G+, but the best performance in 3DMark and CB15, but results were lower than @4.4G.
I sold my 1366 rig many years ago, but I really miss it. Performance may be lacking on the modern level, but it's the most "fun" platform that ever existed.
ok just got a BSOD while playing doom (driver over ran stack buffer) any suggestions/ I installed the via audio drivers could it be that or voltage related? I'm also thinking it could be memory timings I tightened them up because I'm underclocked on my 1866 3x8 2R dims stock is 10-11-10-27 cr2 I set them to 9-10-9-27 cr1
I haven't touched westmere in awhile, but as far as I remember my Rampage II Gene was very finicky about RAM and Uncore.
My "golden sample" x5650 was running daily 3.7-ish GHz at 1.2V during summer, and 4.2GHz the rest of the year, but in both cases it did not like RAM frequencies higher than 1800MHz: had G.skill DDR3-2133 3x4GB kit which could push 2400MHz on Haswell rig, so the limit was definitely with a board itself or a memory controller. I'd get random BSODs or reboots while watching youtube or doing mundane non-intensive stuff.
Don't forget to tune down uncore to approximately 2x RAM frequency. Also I've never even touched QPI or IOH voltages, but it was still good enough to push over 200MHz BCLK for benching and 180+ for daily.
Basically my rule of thumb was to turn everything down to a minimum, and start cranking up that BCLK until the system becomes unstable. Add core voltage and repeat. 1.4V is probably the highest I'd go for daily, and only if you have a decent cooling solution. On air I wouldn't even dare to go over 1.35V. Power draw starts piling up quite fast once you get past 4GHz. When I finally broke 5G barrier, my UPS was screaming in pain, letting me know that my rig with stock GTX750Ti was pulling over 520W!!! This said, the higher you go - the higher is the probability that something else, totally unexpected, is going to hold you back, like PSU or VRM cooling.
that could be your crashing problem I start by setting the DRAM voltage to 1.5v because I'm use 1866 dims underclocked and QPI/DRAM to 1.3v thats the XMP voltage for these dims, auto settings will overvolt these when overclocking Xenon's, maybe the I7's allowed more voltage I dont know never owned an X58 I7 but I hurt two CPU's IMC doing the same thing it set my QPI/DRAM to 1.38 and DRAM to 1.7v got great bench marks initially but quickly degraded within days of light usage.
DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and BugCheck call is the one that overran its local
variable(s).
Arguments:
Arg1: 00002986679b76b0, Actual security check cookie from the stack
Arg2: 000051eae7abb6ee, Expected security check cookie
Arg3: ffffae1518544911, Complement of the expected security check cookie
Arg4: 0000000000000000, zero
Ok I had set my QPI/DRAM to 1.3v in bios but in order to achieve 1.3v to the motherboard it needs to be set at 1.33v tried running full virus scan and it was not completing and disabling on the way out so I reset to defaults in bios scan completed no threats detected which led me to up the QPI/DRAM voltage and lowered the CPU voltage just under 1.35v ran virus scan again works fine no threats so I decided to run another cinebench to test and wow check the results also AIDA64 is causing a strange hard drive access thing that defender is blocking I'm thinking this was the cause of the crash I noticed there is an update available but I keep declining maybe there is a fix will test soon as it updates I will also be using defender as another level of future stability testing