[ny_driver]

I have never had an Intel before, and it seems like there is a lot more to it than with AMD.

Anyways, right now I'm just trying to see if I can get a good cpuz run.

I set the vcore to 1.35v for a test run and left everything else on auto because I don't really know what else to do. I disable HT, overspeed protection, and c-state, and I set it to 1 core.

It crashed at like 3.3GHz, which just made me feel confused and clueless. I guess I need some coaching here.

Thanks!!

[Mr.Scott]

You're just confusing yourself. Everything OC's the same way......just the nomenclature is different.

[ny_driver]

Maybe I am, and it probably is mostly a terminology issue, but I still need help.

[Splave]

dont set it to 1 core

turn off all the crap and ht, disable speed step and all c states.

uncore multi must be x2 ram multi or higher, up to 1.55vtt seems to be okay, up to 1.6vcore is okay.

[Hondacity]

bclk starts @ 133

go to 136 - 139 - 142 etc.. - ....using just bios...

[ny_driver]

OK thanks Splave. I just gotta get SetFSB to OC with I guess. I really wish there was a handy program for remotely overclocking/monitoring like on ASUS.

[Witchdoctor]

BIOS does a fine job

just got to play with it a bit

[Hondacity]

Originally Posted by ny_driver

OK thanks Splave. I just gotta get SetFSB to OC with I guess. I really wish there was a handy program for remotely overclocking/monitoring like on ASUS.

gigabyte ...doesn't have one...

[ny_driver]

I honestly thought I was done having to constantly go into the BIOS to make adjustments unless it crashes.

[Kal-EL]

Wait, wut hardware we talking about specifically?