i was ocing an e6600 on an evga 680i with a 74gb raptor and 4gb of ram for my uncle's server. we had to install windows server edition 2003 which sucked.
anyway, i started ocing and had had to raise the vcore to 1.3 from 1.28 and i cruised from an fsb of 1066 to 1511 in no time. it was a walk in the park
then i tried 1600 and it didnt boot. so i raised the voltages and etc. and it still didnt boot. i highest i raised my voltage was to 1.35v even though i have read many places that people had raised it to 1.45 and stuff for the speeds i was getting.
you think raising it to 1.4 would solve the stuck at 1600fsb problem?
because it was much stabler at 1.35 and i imagine it would only continue to get stable until it worked good in the low 1.4s
1.3v to 1511 and <1.4v 1600 and higher?
could this be the problem?
anyway, i started ocing and had had to raise the vcore to 1.3 from 1.28 and i cruised from an fsb of 1066 to 1511 in no time. it was a walk in the park
then i tried 1600 and it didnt boot. so i raised the voltages and etc. and it still didnt boot. i highest i raised my voltage was to 1.35v even though i have read many places that people had raised it to 1.45 and stuff for the speeds i was getting.
you think raising it to 1.4 would solve the stuck at 1600fsb problem?
because it was much stabler at 1.35 and i imagine it would only continue to get stable until it worked good in the low 1.4s
1.3v to 1511 and <1.4v 1600 and higher?
could this be the problem?