No one has been able to prove that a "burn-in" is beneficial. IMO, I would run it for about 2-3 days at 100% cpu usage, just to make sure it's stable, then start cranking the fsb up, in slow increments.
Cpu Burn In Time??
Any consensues on how long one should let the system run stock before getting into the clock settings???
I have the system all set up ( except crappy ram right now ), and am itching to start fudging in the BIOS.
1 day? 2 days? 1 week? ( all these times are with 24 hrs of folding
![]()
I have the system all set up ( except crappy ram right now ), and am itching to start fudging in the BIOS.
1 day? 2 days? 1 week? ( all these times are with 24 hrs of folding
1 - 8 of 8 Posts
I crank em up on the first boot
![]()
2
Quote:
haha same here, I think my frist boot on this rig was 230x10
![]()
Originally Posted by Crash I crank em up on the first boot
|
3
Quote:
Hey Gibant I just noticed XMS passed you by 25mhz
![]()
. Remeber when I warned you about it
![]()
. Either way, you're both
![]()
Originally Posted by gibant1 Some of the big overclockers leave memory in folding machines for months before steadily raising the clocks. I myself go for it straight away, always checking temps of course. But they do get higher O/C than myself so who knows? |
3
Quote:
I can get 4384Mhz @ 1:1. Dont think my memory can go any higher and I'm not using a divider. Unfortunately the amount of juice I have to put through at that level (1.85v Cpu, stock 1.55v) makes me nervous even though my temps are still sub zero.
To be honest when you have a machine with a Raptor raid array thats over 3.4Ghz nothing slows them down anyway. I run @ 4.2 but it wouldn't matter if I was a bit less.
To XMS... Keep it coming boy ha ha
Originally Posted by Evil XP2400 Hey Gibant I just noticed XMS passed you by 25mhz
|
To be honest when you have a machine with a Raptor raid array thats over 3.4Ghz nothing slows them down anyway. I run @ 4.2 but it wouldn't matter if I was a bit less.
To XMS... Keep it coming boy ha ha
1 - 8 of 8 Posts
