Hardocp also reported on that, they were able to run prime for hours then launching a benchmark or something would bsod the system. Bit weird.
VERY! you would think that prime95 or other stability tests would bsod.
Anyone know how to cure it?
-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
~~~~~IMPORTANT SANDYBRIDGE OC INFO: Voltages & OC Guide!!~~~~~
- Thread starter Gibbo
- Start date
VERY! you would think that prime95 or other stability tests would bsod.
Anyone know how to cure it?
what shall i set it to? and what does it run @ on auto?
I have bought the ripjaw x cas 6 kit and it seems that the ram will not run at rated settings 6-8-6-24 @ 1.50v it will only do 6-8-6-24 @ 1.65v.
Im seriously thinking of sending all this gear back, Its so annoying how i can actually stress the system hours on end with no issues but still get code 124 BSOD at random times but quite often when not stressing?
I have bought the ripjaw x cas 6 kit and it seems that the ram will not run at rated settings 6-8-6-24 @ 1.50v it will only do 6-8-6-24 @ 1.65v.
Im seriously thinking of sending all this gear back, Its so annoying how i can actually stress the system hours on end with no issues but still get code 124 BSOD at random times but quite often when not stressing?
Last edited:
Real world very little. There was a thread around here linking to a tests done with Sand Bridge adn different spped/latency ram.
I've come to always use blend to test SB stability, I've got a feeling only running small FFT's doesnt hammer the mem controllers and as soon as you try something else it falls over. I have no idea why, im no expert on the internals and can only comment on my own experiances but once mine was prime blend stable, everything was.
Should the default clock speeds on 2600k not be 3300 and 3800 turbo? Max i can reach on default for turbo is 3500 :s
Put every back to default right now may reinstall windows to see if thats giving off the code 124 error as im really confused about that one!
Put every back to default right now may reinstall windows to see if thats giving off the code 124 error as im really confused about that one!
Last edited:
Thats because the default 4 core turbo ratio is 35, 3 core=36, 2 core=37, 1 core=38. Remember turbo boost 2.0 can indepentantly turbo 1-4 cores not just the whole cpu.
You need to change the turbo ratio's per core. set each of them to the speed you actually want to hit. cant remember exactly what the options on the asus are to do it, but basically on this MSI I dont change the multi at all - thats set at 34 (the default clock) and I just change my requested turbo multi per core to 46 for each of them, then adjust voltages and leave all the power saving/speedstep stuff on for the best of both worlds.
I actually have the same board as you lol, Im having a bad time with it though... All stability programs are saying that im stable. I have been running prime95 torture test for over 8 hours all came back fine, even blend. linx, intel burn test. But i keep getting BSOD code 124 at random times while browsing web or on idle. No idea why and i cant cure it!
Last edited:
ha, ok... I should really do some screens of my settings in that case, see if your's is any better, mine has been rock solid since I stopped fiddling and settled at 4.6 1.34v.
In the OC menu leave multi at 34 and then go to CPU features and set the bottom 4 mutlipliers from 38,37,36,35 etc all to 45/46 whatever you want to try go stable at, then make sure you're "long and short duration" power limit wattage is 200. I set Load Line Calibration to "auto" or "low"(if thats an option on your bios version id recommend 1.8b6) also im using the XMP memory profile and auto voltages for everything except vcore, dram and PLL. PLL should be 1.81-1.82v to compensate for a little droop, 1.572 seems to be the sweetspot for my mem (rated 1.65 under XMP), yours may be different, and vcore is dependant on your individual CPU/frequency obviously.
Have a fiddle with that and if you're still struggling i'll get some screenies up for other settings. I'll always suspect voltage if an OC is unstable before a borked win 7 install etc and i've got a sneaking suspition that you're long duration load wont be upped from the default 95w to near 200 meaning its power starved and potentially bsod's...
Last edited:
Thats great mate, nice one for that if you could get some screenies up then i can go by them and see exactly what should be on and what should not be on... As the term names in bios are different from what people say if that makes sense.
I am on 1.8b6
So for that turbo thing then i should set 1,2,3,4 all to 48? and leave the actual mutli to default 34!
I will await your screenshots
You could send them via email if you wanted if it would be better for you?
I think with the issues im getting your the last hope!
i7 1366 i never found as hard to overclock as this :s
Last edited:
Right, these are my settings for a conservative 4.6, safe, stable OC on the MSI. Dont worry about it saying 3400mhz in the first screen, under turbo(load) it does 4.6 and is happy at 1.34 as read from cpu-z in prime95 blend. (Notice all power saving and speedstep is on and its using the turbo feature to reach requested clocks while saving power while idle). Only setting you wont need on is virtualization tech. im running a stack of VM's but normally its not needed.
Voltages will differentiate based on individual setups, stick to the guidelines in Gibbos OP.
Main OC screen
_DSC0025 by rustEswan, on Flickr
CPU Features
_DSC0026 by rustEswan, on Flickr
On this second shot, pay attention to the long and short load duration power - can be 200 for both, i've just lowered the short, while fiddling, not sure it makes a huge difference in this exact config but at default it'll be 95w and possibly impacting stability if its lacking power for the requested frequency. Oh and disable overspeed protection as long as your cooling is good otherwise it'll clock back after a few minutes load.
Voltages will differentiate based on individual setups, stick to the guidelines in Gibbos OP.
Main OC screen
_DSC0025 by rustEswan, on Flickr
CPU Features
_DSC0026 by rustEswan, on Flickr
On this second shot, pay attention to the long and short load duration power - can be 200 for both, i've just lowered the short, while fiddling, not sure it makes a huge difference in this exact config but at default it'll be 95w and possibly impacting stability if its lacking power for the requested frequency. Oh and disable overspeed protection as long as your cooling is good otherwise it'll clock back after a few minutes load.
Last edited:
Hmm what about EIST should that be on or off.
And it seems currently running prime95 It won't go up to 4800 in turbo only 3400
followed everything there aswell in your pictures....If you've checked and double checked the settings in those two screens, then theres only a couple of other things i can think to check, and this is clutching at straws, thats exactly my setup above...
"Green Power, Phase Control= APS Mode" and "settings, advanced, integrated peripherals, HPET=enabled" (i really dont know what impact this had but sure I read something about it impacting oc's?!)
Basically as yours is sticking at 3.4 it looks like it isnt turbo enabled, probably through a power saving/speedstep/EIST setting you missed from the above config im guessing...
"Green Power, Phase Control= APS Mode" and "settings, advanced, integrated peripherals, HPET=enabled" (i really dont know what impact this had but sure I read something about it impacting oc's?!)
Basically as yours is sticking at 3.4 it looks like it isnt turbo enabled, probably through a power saving/speedstep/EIST setting you missed from the above config im guessing...
It is working now mate 
thanks very much.
gives me a different route to go down as not having much look with the other overclocking route...
if i prime stable again like i did on my other overclocking route and still get random BSOD code 124 on idle and web browsing what shall i start to change to solve it?
thanks very much. gives me a different route to go down as not having much look with the other overclocking route...
if i prime stable again like i did on my other overclocking route and still get random BSOD code 124 on idle and web browsing what shall i start to change to solve it?
Not sure exactly, only had limited time with a specific set of hardware, but, update you're sig with specs, especially memory - if the asus was anything to go by these p67's or the current bioses are very funny about memory/memory controllers as far as i can tell.
And, this is purely anecdotal, required voltage for a given stable frequency seems to be lower using my method above(auto voltages for most and speed/power saving tech on), rather than setting the base multi higher. General stability seems to be better aswell.
See how you get on and let us know how it goes.
EDIT - side note, after every 100mhz jump I let it burn in for 2-3 hours of prime blend, right from 3.9ghz up when it got unstable I made a single vcore adjustment and started again, once that did 2-3 hours i notched the 4 mutli's by one and repeated - its the long winded way but seems to have paid off in hepling find the sweet spot. I will at some point try going for a little higher but my vcore/temp/frequency balance im happy with so whatever it ends up capable of, this will prob be my 24/7 config.
And, this is purely anecdotal, required voltage for a given stable frequency seems to be lower using my method above(auto voltages for most and speed/power saving tech on), rather than setting the base multi higher. General stability seems to be better aswell.
See how you get on and let us know how it goes.
EDIT - side note, after every 100mhz jump I let it burn in for 2-3 hours of prime blend, right from 3.9ghz up when it got unstable I made a single vcore adjustment and started again, once that did 2-3 hours i notched the 4 mutli's by one and repeated - its the long winded way but seems to have paid off in hepling find the sweet spot. I will at some point try going for a little higher but my vcore/temp/frequency balance im happy with so whatever it ends up capable of, this will prob be my 24/7 config.
Last edited:
Will do mate running linX right now on 25 runs see how it goes. Im fine running stability programs and passing them its just on idle or web browsing that i get BSOD