- Joined
- Jul 12, 2003
I finally got a decent heatsink in my system (vantec aeroflow) and I'm ready to overclock... I was pretty upset that the only way to get stable at 2.2ghz (200 x 11) was to push the vcore up to 1.70, any less and it would crash on the first try of a prime test. so I tried 2.25 ghz with 188 x 12 and with 205 x 11, both times it crashed the whole system within 20 seconds of starting prime torture test. So I push the vcore all the way up to 1.75 and the only thing that changes is that it lasts maybe 40 seconds instead of 20 in prime95. My temps at 2.2ghz are 43c idle/ 48c load... it drops about 5 degrees by leaving my case open cause my airflow in the case sucks, getting more fans next week though, but even with the case open and temps around 38c, I can't get it anywhere near stable past 2.2ghz and I'm afraid to go over 1.75 vcore.
Does my 2500 just plain suck? I've heard many people get theirs to 2.2ghz at stock vcore, some even with stock heatsink, and most everyone here get theirs at least to 2.3 ghz. Is there some trick I'm missing?
Also, I'd like to add that every time I reset the CMOS or put the chip in for the first time, it misreads my chip as a 1.1 ghz duron cause it autodetects the FSB at 100mhz instead of 166mhz, I thought maybe it was just a weird bug with the mobo or something, but do you think it's a result of the suckiness of my chip?
Does my 2500 just plain suck? I've heard many people get theirs to 2.2ghz at stock vcore, some even with stock heatsink, and most everyone here get theirs at least to 2.3 ghz. Is there some trick I'm missing?
Also, I'd like to add that every time I reset the CMOS or put the chip in for the first time, it misreads my chip as a 1.1 ghz duron cause it autodetects the FSB at 100mhz instead of 166mhz, I thought maybe it was just a weird bug with the mobo or something, but do you think it's a result of the suckiness of my chip?