Recent content by CursedMind

looks very solid, I need to do something about my own :( No headroom with voltages here at 3.8oc

Was that Cl 7 DDR3-1600 ? Nice OC. Still know temp on NB after prime ?

I have fixed ram issues with carefully adjusting voltages and latency. Was a bit tricky though, and I don't know why it worked, but it did. But I actually was not able to get much below that 1.4vCore I wanted sadly. It seems pretty stable, 1.32 upwards, but it isn't. Got several bluescreens...

Thanks, yes I see what it does then. I'll leave it untouched for now, because (Oh wonderous things have happen) my PC is actually booting fine, and currently running prime again, with some vCore values that I like much much more then those 1.42V I had. *ggg* I really think turning Spread...

Thanks a lot, I don't think I ever learned that much about hardware in such little time :) Just got a Prime warning, so I'm back to bios. Going to check those settings now, and what room they give me in core voltage.;) one final question: This refers to that "differential signaling...

Could anyone explain to me what I'm doing when I disable CPU &PCIE spread spectrum ? I know where the option is, but I don't switch anything off (or on) when I don't know what I'm doing... :D Ram is fine btw. although its 1333 :p Turbo is off, multiplier locked differential signal on auto...

Currently testing with PLL & QPI voltage that looks a bit more like those that you have, but no screen yet, I'm still not entirely stable, but this is -way- better then when I started considering I have time to write this before prime gives me some blue color all over that screen :D Actually...

Thanks, that looks promising. And I think I know now why I've run into that much trouble on my own... I'll try a little tonight when I'm done working, and post what I get then.

I figure you should be able to see some number in the Bios screen, if not, at least Core voltage is shown in CPU-Z

ignore those old statements above, I was running with near random voltages there. But what you say is entirely correct, as long as you stay at 166 blck theres absolutely nothing to worry about, no matter what you set or don't set. The Ram timings are just something I forgot to undo before...

Screenshot of CPUZ, still running Prime 95 since yesterday to make sure its stable again Another question, If you guys would also think my A-DATA Vitesta+ Triple-Channel Kit 2GB (PC3-12800, CL7). SPD EEPROM 7-7-7-20@1333MHz 1,65V owuld be the limiting factor for sure, and as you can see, I...

As far as I have seen, I cannot set consumption levels for Turbo, and the Bios itself states that Turbo is going to be disabled for clockspeeds beyond 3.6Ghz. But you say nothing is wrong with my numbers ?

sorry for resurrection of this thread. some weeks passed, and I read a lot of people hitting 3.8 on air with stock voltages. I don't even get to 3.6 on stock voltage, one out of 20 tries @3.6 managed to stay stable for 10 minutes of Prime95 before BSODing on me, and I don't consider that...

It was a LOT easier then I thought when I just set those "auto" values manually. Looks like all those problems were caused by the Rampage autovalues. System ran 3.3Ghz with 20 CPU multiplier at 166 Bus speed, 8 MemMulti+16QPI Multi to give me a bit slower but 1328 DDR3 8-9-9-24 clocks wich...

*sigh I think I better wait and read a little more before I try now as I don't think I got all the mechanics involved yet. 3.32 Ghz with 20x mutliplier 166 Bus speed, DDR3 at 996 Clock, thats what I know I've got... Nehalem calculator tells me QPI clock is 2988 and UnCore at 1992, but I...