Who can help me successfully overclock this rig?
- Thread starter swambast
- Start date
Always learning new stuff daily around here. Imaginary mod reps for XMS!
I'm an Intel n00b, lolYep...
OK, YES DAVE, you were right. Ran Prime for 1 hr 5 mins, no errors LOL
I'll up the AGP voltage again to 1.6, just to be on the safe side. Looks like, so far, it will hold steady at 3.09 Ghz.
Here is one problem I've experienced in the past though. I had Prime run for over 7-8 hours without any errors. BUT, when I would fire up a heavy hard-hitting game like IL2 Forgotten Battles or Call of Duty, the system would instantly crash to death... So, part of my testing has to include "game testing" in order for me to really call it stable...
After I confirm this is stable with the games, I'll try juicing up the FSB more. I have to believe at this point, that manually changing those memory timings has made all the difference...
OK, YES DAVE, you were right. Ran Prime for 1 hr 5 mins, no errors LOL
I'll up the AGP voltage again to 1.6, just to be on the safe side. Looks like, so far, it will hold steady at 3.09 Ghz.
Here is one problem I've experienced in the past though. I had Prime run for over 7-8 hours without any errors. BUT, when I would fire up a heavy hard-hitting game like IL2 Forgotten Battles or Call of Duty, the system would instantly crash to death... So, part of my testing has to include "game testing" in order for me to really call it stable...
After I confirm this is stable with the games, I'll try juicing up the FSB more. I have to believe at this point, that manually changing those memory timings has made all the difference...
More...
OK, here's an update. I set the FSB to 224, Memory Speed 448 giving a 3.14 Ghz - would not load/boot into Windows.
Stepped down the FSB to 222, Memory Speed 444, giving a 3.11 Ghz - did successfully boot/load into Windows. Temps are starting to really get up there now, 44C under load, 39 Case... yikes!
Obviously I'm reaching some kind of threshold now. What might I try next? Should I prime this out, or will it check out OK? I think maybe the next step might be to start upping the voltage on the CPU/DDR?
OK, here's an update. I set the FSB to 224, Memory Speed 448 giving a 3.14 Ghz - would not load/boot into Windows.
Stepped down the FSB to 222, Memory Speed 444, giving a 3.11 Ghz - did successfully boot/load into Windows. Temps are starting to really get up there now, 44C under load, 39 Case... yikes!
Obviously I'm reaching some kind of threshold now. What might I try next? Should I prime this out, or will it check out OK? I think maybe the next step might be to start upping the voltage on the CPU/DDR?
correct sir, you are getting the hang of this!
up the cpu voltage by one notch. it should be called vcore. really only do this by one notch atm. if at 224 ane +1notch vcore it still doesnt boot into windows then you can try upping vcore again. Remember when upping vcore to continually check your temperatures.
up the cpu voltage by one notch. it should be called vcore. really only do this by one notch atm. if at 224 ane +1notch vcore it still doesnt boot into windows then you can try upping vcore again. Remember when upping vcore to continually check your temperatures.
Safe Temps...?
OK, what is a safe temp under load?
Stepped down the FSB to 222, Memory Speed 444, giving a 3.11 Ghz - did successfully boot/load into Windows. Temps are starting to really get up there now, 44C under load, 39 Case... yikes! And that's on a "not so demanding" game (Steam/Day of Defeat).
OK, what is a safe temp under load?
Stepped down the FSB to 222, Memory Speed 444, giving a 3.11 Ghz - did successfully boot/load into Windows. Temps are starting to really get up there now, 44C under load, 39 Case... yikes! And that's on a "not so demanding" game (Steam/Day of Defeat).
Guys, what is the best way to test "under load" temps? I typically run the game, and then after letting it play or playing it for an hour (or more), exit out of the game and immediately check MotherBoard Monitor 5 for readings. Is this more/less accurate than getting the readings directly from the BIOS? Reason I'm asking is that once I exit back, the system quickly jumps back to 31-32 CPU Idle temps within seconds. By the time I rebooted the computer and checked the BIOS, I think it might reflect lower temps than "under load" temps...?????
name='swambast' said:
prime 95's tortue test
direct link http://mersenne.org/gimps/p95v238.exe
http://www.mersenne.org/freesoft.htm
install P95 then change the settings to run the torture test :evil: exactaly what it says on the tin
this gives ur processor massive calculatiobs to perform AND detects processing errors(if u r online while running the test) so it allows you to sucessfully gauge the load temp & the quality of the OC; most OCers run this program for hours (usually around 6 ) to proove their systems are stable
FarFarAway
New member
name='swambast' said:
Use these tests:
memory Prime95 on the torture test "blend" lost of memory used.
General: download the F@H client here and use that...it stresses out your CPU
Graphics:
Run: RTHDRIBL to strees out your GPU. Also heats up your system nicely.
Close to giving up now
Well guys, no luck at all 3.10 Ghz running games. Played a game for 1.5 hours, and without warning, the computer crashed and reset.
Dropped proc down to 3.0 Ghz, and after 2 hours, same thing, computer crashed and reset.
Both times temp showed 44C on the CPU under load, and that seems fine...
I don't know - I think I'm just going to give up now. No matter what I try, or with all the help I get, no one's quite been able to get this rig O/C - NOT EVEN A LITTLE BIT!
Resetting everything back to defaults, and I guess I really don't have much more choice but to just be happy with my 2.8 GHz.
This rig just does not want to budge, I guess.
:damn:
Thanks for all the advice, time and insight you've all provided, I really appreciate it, really. :worship:
Well guys, no luck at all 3.10 Ghz running games. Played a game for 1.5 hours, and without warning, the computer crashed and reset.
Dropped proc down to 3.0 Ghz, and after 2 hours, same thing, computer crashed and reset.
Both times temp showed 44C on the CPU under load, and that seems fine...
I don't know - I think I'm just going to give up now. No matter what I try, or with all the help I get, no one's quite been able to get this rig O/C - NOT EVEN A LITTLE BIT!
Resetting everything back to defaults, and I guess I really don't have much more choice but to just be happy with my 2.8 GHz.
This rig just does not want to budge, I guess.
:damn:
Thanks for all the advice, time and insight you've all provided, I really appreciate it, really. :worship:
swambast said:Well guys, no luck at all 3.10 Ghz running games. Played a game for 1.5 hours, and without warning, the computer crashed and reset.
Dropped proc down to 3.0 Ghz, and after 2 hours, same thing, computer crashed and reset.
Both times temp showed 44C on the CPU under load, and that seems fine...
I don't know - I think I'm just going to give up now. No matter what I try, or with all the help I get, no one's quite been able to get this rig O/C - NOT EVEN A LITTLE BIT!
Resetting everything back to defaults, and I guess I really don't have much more choice but to just be happy with my 2.8 GHz.
This rig just does not want to budge, I guess.
:damn:
Thanks for all the advice, time and insight you've all provided, I really appreciate it, really. :worship:
sounds like memory errors run Memtestx86 to findout (run it for a while 2+ hours)
if it is due to a memory error you may need to experiment with the following
Loosening memory timings;
increasing Northbridge Voltage or
Increaseing memory voltage (you may ned to do these in a combination)
edit thanx for votin .. most peeps love that bear
FragTek
New member
swambast said:Well guys, no luck at all 3.10 Ghz running games. Played a game for 1.5 hours, and without warning, the computer crashed and reset.
Dropped proc down to 3.0 Ghz, and after 2 hours, same thing, computer crashed and reset.
Both times temp showed 44C on the CPU under load, and that seems fine...
I don't know - I think I'm just going to give up now. No matter what I try, or with all the help I get, no one's quite been able to get this rig O/C - NOT EVEN A LITTLE BIT!
Resetting everything back to defaults, and I guess I really don't have much more choice but to just be happy with my 2.8 GHz.
This rig just does not want to budge, I guess.
:damn:
Thanks for all the advice, time and insight you've all provided, I really appreciate it, really. :worship:
Time to go :amd:
FarFarAway
New member
name='FragTek' said:Time to go :amd:
Yep....prettty much!
Well, I'll be damned! This is interesting, but certainly not positive news.
I tested MemTest on my memory, with the memory running at a mere 402 Mhz from the standard 400 Mhz. It failed within 35 minutes.
I then tested MemTest on the memory, this time, with the memory running at the default 400 Mhz. It's been over 3 hours, and not a single error being reported so far (test is still running).
Ah, at this point in time, this leads me to one conclusion - can you confirm for me if you think this is correct:
This memory SUCKS TOTAL SHIT.
Would that be a correct assumption, or could it still be something else?
BTW, again thanks to everyone so far for your continued support. I want to especially commend sai_jao - you just seem to really know how to call these problems right on...
I tested MemTest on my memory, with the memory running at a mere 402 Mhz from the standard 400 Mhz. It failed within 35 minutes.
I then tested MemTest on the memory, this time, with the memory running at the default 400 Mhz. It's been over 3 hours, and not a single error being reported so far (test is still running).
Ah, at this point in time, this leads me to one conclusion - can you confirm for me if you think this is correct:
This memory SUCKS TOTAL SHIT.
Would that be a correct assumption, or could it still be something else?
BTW, again thanks to everyone so far for your continued support. I want to especially commend sai_jao - you just seem to really know how to call these problems right on...
