Blck issues

[Rammsteiner]

Hey guys,

Although Im highly in love with my Bloodrage, somehow I guess that it's limiting my CPU OC though.

Im running 21x200 stable, Ive ran 21x205 stalbe but somehow I probably missed a setting cause I cant really reproduce it. But that doesnt particulary matter since that's the whole issue; Blck.

I tried to boot from 20x210 (yes, I disabled Turbo mode). But apart from actually corrupting a load of drivers it didnt do much for me. Ive tried this;
Vcore, left it alone (I mean, 4.2Ghz is 4.2Ghz).
VTT upto +280mV. Seems like lower VTT had more succes because at 280mV I had looping BIOS speaker beeps but at +180mV it BSOD just before actually getting past log-on (and thus corrupting everything).
CPU PLL from 1.8 to 1.88, no idea if it actually helped.
IOH1.1 and 1.108 VCCA Voltages to 1.2 and 1.25V, nothing.

Also I set my RAM to 6xmulti once as well to 9-9-9-20 timings, didnt help either. I might try one more time to actually use not so much Vdimm cause according to eva2000's findings some CPU's dont like high VTT's. And since Im fine with a 100~120mV+ for 200Mhz Blck and Ive had less bad results with a lower VTT, this might fix it.

Anyway, Im testing memory systems now with specs in BIOS, few more hours to go. I hope you guys could eventually give some feedback in the mean time.

Thx!

[MpG]

Personally, I'd be backing off the CPU multi and verifying that the QPI and Uncore are stable first. And that's assuming that you know the memory's got the headroom (I know, seems like a gimme). Honestly, wouldn't surprise me if you needed a little more than +120mV to hold the CPU at that speed. Yeah, some chips are good like that, but lots of others aren't. I'm assuming you're keeping your temps under control?

[Rammsteiner]

Personally, I'd be backing off the CPU multi and verifying that the QPI and Uncore are stable first. And that's assuming that you know the memory's got the headroom (I know, seems like a gimme). Honestly, wouldn't surprise me if you needed a little more than +120mV to hold the CPU at that speed. Yeah, some chips are good like that, but lots of others aren't. I'm assuming you're keeping your temps under control?

Im trying to find the best settings regarding clocks and Volts now for the current OC, but Im indeed planning to back everything off and start testing purely the Blck.

Temps wise, even at quite some over-Voltage @ 4.3Ghz it didnt hit the 70's at all

Currently it barely hits the 60's, only the first core now and then. But well, EK Supreme + TFC X-Changer 480mm, no other components in the loop

[BenchZowner]

Try setting the CPU Clock skew to 300ps and the NB Clock skew to 100ps

[Rammsteiner]

Try setting the CPU Clock skew to 300ps and the NB Clock skew to 100ps

Ill try that later if current testing results in the usual BSOD's.

I decided to leave IOH just at stock, use a bit more Vdimm (1.7V), +160mV VTT, +200mV (what the heck, ain't hitting 70C with that) and 1.87V PLL. It looks like it's going at 205Mhz Blck.

Anyway, before I ramp Blck up and eventually try those skew options to your recommended settings, what exactly is it for? Could it possibly cause dmg if you use too much ps? Maybe stupid question but Ive no single clue what the hell this might be for

[BenchZowner]

No it cannot damage your hardware.
Try it, it'll more than likely cut it ( if not with some additional Vtt )

[dengyong]

Hey guys,

Although Im highly in love with my Bloodrage, somehow I guess that it's limiting my CPU OC though.

Im running 21x200 stable, Ive ran 21x205 stalbe but somehow I probably missed a setting cause I cant really reproduce it. But that doesnt particulary matter since that's the whole issue; Blck.

I tried to boot from 20x210 (yes, I disabled Turbo mode). But apart from actually corrupting a load of drivers it didnt do much for me. Ive tried this;
Vcore, left it alone (I mean, 4.2Ghz is 4.2Ghz).
VTT upto +280mV. Seems like lower VTT had more succes because at 280mV I had looping BIOS speaker beeps but at +180mV it BSOD just before actually getting past log-on (and thus corrupting everything).
CPU PLL from 1.8 to 1.88, no idea if it actually helped.
IOH1.1 and 1.108 VCCA Voltages to 1.2 and 1.25V, nothing.

Also I set my RAM to 6xmulti once as well to 9-9-9-20 timings, didnt help either. I might try one more time to actually use not so much Vdimm cause according to eva2000's findings some CPU's dont like high VTT's. And since Im fine with a 100~120mV+ for 200Mhz Blck and Ive had less bad results with a lower VTT, this might fix it.

Anyway, Im testing memory systems now with specs in BIOS, few more hours to go. I hope you guys could eventually give some feedback in the mean time.

Thx!

Do you have the qpi multi at x18 and the uncore multi at x16 ?

[Rammsteiner]

No it cannot damage your hardware.
Try it, it'll more than likely cut it ( if not with some additional Vtt )

Is it recommendable to set these values anyway? No matter if Im stable or not? Or does it come with slight drawbacks as performance loss or anything?

Otherwise Ill just set it when I restart and leave it there

Just finished a 25 run of Intelburn Test 64b with 205Mhz Blck, now testing 207Mhz (without the skew adjustments that is). Not hitting 70C yet with +200mV @ 4.35Ghz. If I could get only to 210Mhz Blck it would be 4.4Ghz, now that would be awesome for 24.7 Well, if it doesnt need much more Volts though. Although Im within Intel's specs, what's the point if got to RMA it every 2 months due to degradation

[BenchZowner]

It doesn't have any real-life drawbacks.
It might help you stabilize your system at higher Bclks than without adjusting them manually ( if you leave it at auto, the board automatically configures these values, and auto doesn't pick the best values everytime )
As long as you keep your CPU under 75C @ full load, and you're not feeding your CPU ( retail hopefully ) with voltages higher than 1.7Vqpi ( Vtt ), Vcore higher than 1.45V, and Vmem higher than 2.25V ( you have to keep the Vmem - Vtt difference at or under 0.5V ) your CPU will be fine.

[Rammsteiner]

It doesn't have any real-life drawbacks.
It might help you stabilize your system at higher Bclks than without adjusting them manually ( if you leave it at auto, the board automatically configures these values, and auto doesn't pick the best values everytime )

K, thx.

I just got a weird thing though, since I read a bit into wtf skew is in the first place but I never used that before it's hard for me to understand whether some error/issue might be related to 'non-skewing'. As I bumped Blck to 207Mhz and started to test with Intel Burn Test I got an error after about 10 succesfull runs. Not an error in the program showing instability, no instead it simply stopped responding according to Vista Is this a 'sign' of frequencies starting to run out of sync?

As long as you keep your CPU under 75C @ full load, and you're not feeding your CPU ( retail hopefully ) with voltages higher than 1.7Vqpi ( Vtt ), Vcore higher than 1.45V, and Vmem higher than 2.25V ( you have to keep the Vmem - Vtt difference at or under 0.5V ) your CPU will be fine.

I might want to try to reduce Vcore then, it's pretty much at 1.44/1.456V according to CPU-Z, for the rest, Im miles away from those Voltages

[Rammsteiner]

Do you have the qpi multi at x18 and the uncore multi at x16 ?

Yep, read some sort of guide which said to have them in a ~8:9 ratio, although it might not be needed, just incase.

However, I decided to stick with 4.2Ghz, but 20x210 is more preferable than 21x200 IMO, so Ill still try to reach 210Blck

[Rammsteiner]

Oh bah, I think it's my Uncore I could boot into Windows with RAM and Unc at a respectively 6x and 12x, but when I boosted Uncore back to 16x it started to crap around, short beeps when powered up with C1 error.

Ive tried upto 1.4VTT, IOH Voltages, Vcore/VTT ratio's, skewing etc, nothing helped.

Oh well, 4.2Ghz is good enough, it's sad I cant run 20x210 but well, nothing to do about

Thx for your help guys!