go for 4 tbh
"people in ny have a general idea of how to drive. one of the pedals goes forward the other one prevents you from dying"
maybe...haffeysucks wrote:
go for 4 tbh
Just set it to 3.0GHz, setting it on a 30 minute test to see if it's stable..
orthos or prime95?Jenspm wrote:
maybe...haffeysucks wrote:
go for 4 tbh
Just set it to 3.0GHz, setting it on a 30 minute test to see if it's stable..
"people in ny have a general idea of how to drive. one of the pedals goes forward the other one prevents you from dying"
prime..haffeysucks wrote:
orthos or prime95?Jenspm wrote:
maybe...haffeysucks wrote:
go for 4 tbh
Just set it to 3.0GHz, setting it on a 30 minute test to see if it's stable..
OK, set it to 3.3GHz, and got an error instantly in 3/4 cores.
What now?
What now?
A little more VCore, 0.05v or so.Jenspm wrote:
OK, set it to 3.3GHz, and got an error instantly in 3/4 cores.
What now?
The idea of any hi-fi system is to reproduce the source material as faithfully as possible, and to deliberately add distortion to everything you hear (due to amplifier deficiencies) because it sounds 'nice' is simply not high fidelity. If that is what you want to hear then there is no problem with that, but by adding so much additional material (by way of harmonics and intermodulation) you have a tailored sound system, not a hi-fi. - Rod Elliot, ESP
ok.Freezer7Pro wrote:
A little more VCore, 0.05v or so.Jenspm wrote:
OK, set it to 3.3GHz, and got an error instantly in 3/4 cores.
What now?
I set it down it 3.2GHz, and everything is stable (1 hour), but core #2 errored out after 7 minutes...
Will add more VCore.
Added 0.1 VCore...
All cores get the following error within a minute:
FATAL ERROR: Rounding was 0.5, expected less than 0.4
All cores get the following error within a minute:
FATAL ERROR: Rounding was 0.5, expected less than 0.4
0.1v!? Freezer said 0.05v - and that's pretty solid advice...tone your VCore down a *lot*!
I did, but it didn't help at all, so I asked max and he said anything between 0.15 and 0.2 is ok in most cases...kylef wrote:
0.1v!? Freezer said 0.05v - and that's pretty solid advice...tone your VCore down a *lot*!
also,
It's now at 3.22 and hasn't errored yet (10 minutes). 3.22GHz @ +0.05 VCore errored after ~5Aries wrote:
Also note that our motherboard is bent as shit in supplying the voltage you set in the bios, mine is set at 1.4V but I get 1.36 in reality, which then drops to 1.34 under load (this is due to something called vdroop and is probs why your system fails stability tests). Therefore set it +0.05v over the voltage you want.
Last edited by Jenspm (2008-05-21 11:07:12)
***UPDATE***
This is what I've done so far:
Changed Ram timings to 5-5-5-15 with 1:1 ratio (2.0 multiplier)
Upped VCore by 0.1V - Now at 1.3500V
Upped FSB to 430 (CPU now at 3.22GHz)
Results:
1 core errored Prime95 after 2 hours, other one 15min. later. Both the others "survived" 4 hours before I stopped it.
Load temps dropped from 69*c to 56*c (I assume it's the thermal paste melting in).
Now, my goal was 3.5GHz. Next I'm planning on upping the NB core a little (How much?). Also, Aries' picture says that the FSB voltage should be +0.1V if FSB is raised over 400. Should I do this?
Suggestions pl0x.
This is what I've done so far:
Changed Ram timings to 5-5-5-15 with 1:1 ratio (2.0 multiplier)
Upped VCore by 0.1V - Now at 1.3500V
Upped FSB to 430 (CPU now at 3.22GHz)
Results:
1 core errored Prime95 after 2 hours, other one 15min. later. Both the others "survived" 4 hours before I stopped it.
Load temps dropped from 69*c to 56*c (I assume it's the thermal paste melting in).
Now, my goal was 3.5GHz. Next I'm planning on upping the NB core a little (How much?). Also, Aries' picture says that the FSB voltage should be +0.1V if FSB is raised over 400. Should I do this?
Suggestions pl0x.
Last edited by Jenspm (2008-05-21 15:03:02)
I have my FSB voltage at +0.2 or +0.3 V and my FSB is 389...Jenspm wrote:
***UPDATE***
This is what I've done so far:
Changed Ram timings to 5-5-5-15 with 1:1 ratio (2.0 multiplier)
Upped VCore by 0.1V - Now at 1.3500V
Upped FSB to 430 (CPU now at 3.22GHz)
Results:
1 core errored Prime95 after 2 hours, other one 15min. later. Both the others "survived" 4 hours before I stopped it.
Load temps dropped from 69*c to 56*c (I assume it's the thermal paste melting in).
Now, my goal was 3.5GHz. Next I'm planning on upping the NB core a little (How much?). Also, Aries' picture says that the FSB voltage should be +0.1V if FSB is raised over 400. Should I do this?
Suggestions pl0x.
up NB voltage couple steps. +0.1-0.15V
Also up FSB voltage +0.2
Also up FSB voltage +0.2
Last edited by GC_PaNzerFIN (2008-05-21 15:13:12)
3930K | H100i | RIVF | 16GB DDR3 | GTX 480 | AX750 | 800D | 512GB SSD | 3TB HDD | Xonar DX | W8
Panzer was born inside a computer.
Wow you've managed one hell of a performance boost from very little voltageJenspm wrote:
***UPDATE***
This is what I've done so far:
Changed Ram timings to 5-5-5-15 with 1:1 ratio (2.0 multiplier)
Upped VCore by 0.1V - Now at 1.3500V
Upped FSB to 430 (CPU now at 3.22GHz)
Results:
1 core errored Prime95 after 2 hours, other one 15min. later. Both the others "survived" 4 hours before I stopped it.
Load temps dropped from 69*c to 56*c (I assume it's the thermal paste melting in).
Now, my goal was 3.5GHz. Next I'm planning on upping the NB core a little (How much?). Also, Aries' picture says that the FSB voltage should be +0.1V if FSB is raised over 400. Should I do this?
Suggestions pl0x.
Yes the fsb will definitely need to go up at least a notch, and after fsb of 440 or so you may need to up the northbridge as well which is the thing called (G)mch. Make sure you keep an eye on the mobo temps, they shouldnt go up much if your case is well ventilated bu just something to keep in mind
Last edited by Aries_37 (2008-05-21 15:15:35)
oh fucks, I forgot to say that I already have upped the FSB and NB with 0.1.
So plan for tomorrow morning:
- Up FSB from +0.1 to +0.3
- Up NB from +0.1 to +0.2
- Set FSB to 440 (3.3 GHz)
- Run PRIME95
- If it doesn't error within 15 minutes: leave it running while at school (6 hours)
- If it does error within 15 minutes: I dunno, you tell me.
Sounds like a good plan? (in the plan, all will be done at once)
So plan for tomorrow morning:
- Up FSB from +0.1 to +0.3
- Up NB from +0.1 to +0.2
- Set FSB to 440 (3.3 GHz)
- Run PRIME95
- If it doesn't error within 15 minutes: leave it running while at school (6 hours)
- If it does error within 15 minutes: I dunno, you tell me.
Sounds like a good plan? (in the plan, all will be done at once)
up the cpu voltage as well. lets say 1.375VJenspm wrote:
oh fucks, I forgot to say that I already have upped the FSB and NB with 0.1.
So plan for tomorrow morning:
- Up FSB from +0.1 to +0.3
- Up NB from +0.1 to +0.2
- Set FSB to 440 (3.3 GHz)
- Run PRIME95
- If it doesn't error within 15 minutes: leave it running while at school (6 hours)
- If it does error within 15 minutes: I dunno, you tell me.
Sounds like a good plan? (in the plan, all will be done at once)
3930K | H100i | RIVF | 16GB DDR3 | GTX 480 | AX750 | 800D | 512GB SSD | 3TB HDD | Xonar DX | W8
roger that.GC_PaNzerFIN wrote:
up the cpu voltage as well. lets say 1.375VJenspm wrote:
oh fucks, I forgot to say that I already have upped the FSB and NB with 0.1.
So plan for tomorrow morning:
- Up FSB from +0.1 to +0.3
- Up NB from +0.1 to +0.2
- Set FSB to 440 (3.3 GHz)
- Run PRIME95
- If it doesn't error within 15 minutes: leave it running while at school (6 hours)
- If it does error within 15 minutes: I dunno, you tell me.
Sounds like a good plan? (in the plan, all will be done at once)
If it still fails after that up the vcore a tiny bit more, the vdroop should keep you in a safe zone. But tbh you're shooting for a huuge overclock, massive volts and reduced lifespans will have to be accepted as worthwhile collateralJenspm wrote:
oh fucks, I forgot to say that I already have upped the FSB and NB with 0.1.
So plan for tomorrow morning:
- Up FSB from +0.1 to +0.3
- Up NB from +0.1 to +0.2
- Set FSB to 440 (3.3 GHz)
- Run PRIME95
- If it doesn't error within 15 minutes: leave it running while at school (6 hours)
- If it does error within 15 minutes: I dunno, you tell me.
Sounds like a good plan? (in the plan, all will be done at once)
EDIT:panzer @ pr0 posting speed
Last edited by Aries_37 (2008-05-21 15:27:43)
hrm, how redused lifespan?Aries_37 wrote:
If it still fails after that up the vcore a tiny bit more, the vdroop should keep you in a safe zone. But tbh you're shooting for a huuge overclock, massive volts and reduced lifespans will have to be accepted as worthwhile collateralJenspm wrote:
oh fucks, I forgot to say that I already have upped the FSB and NB with 0.1.
So plan for tomorrow morning:
- Up FSB from +0.1 to +0.3
- Up NB from +0.1 to +0.2
- Set FSB to 440 (3.3 GHz)
- Run PRIME95
- If it doesn't error within 15 minutes: leave it running while at school (6 hours)
- If it does error within 15 minutes: I dunno, you tell me.
Sounds like a good plan? (in the plan, all will be done at once)
EDIT:panzer @ pr0 posting speed
Also, I think I might stop at 3.3
longer than the time you'd normally replace a CPUJenspm wrote:
hrm, how redused lifespan?Aries_37 wrote:
If it still fails after that up the vcore a tiny bit more, the vdroop should keep you in a safe zone. But tbh you're shooting for a huuge overclock, massive volts and reduced lifespans will have to be accepted as worthwhile collateralJenspm wrote:
oh fucks, I forgot to say that I already have upped the FSB and NB with 0.1.
So plan for tomorrow morning:
- Up FSB from +0.1 to +0.3
- Up NB from +0.1 to +0.2
- Set FSB to 440 (3.3 GHz)
- Run PRIME95
- If it doesn't error within 15 minutes: leave it running while at school (6 hours)
- If it does error within 15 minutes: I dunno, you tell me.
Sounds like a good plan? (in the plan, all will be done at once)
EDIT:panzer @ pr0 posting speed
Also, I think I might stop at 3.3
"people in ny have a general idea of how to drive. one of the pedals goes forward the other one prevents you from dying"
Hes faster than a pigeon shitting poop on your shoulder. ---no wait, that doesn't make any sense. I'll leave it anyway.Aries_37 wrote:
If it still fails after that up the vcore a tiny bit more, the vdroop should keep you in a safe zone. But tbh you're shooting for a huuge overclock, massive volts and reduced lifespans will have to be accepted as worthwhile collateralJenspm wrote:
oh fucks, I forgot to say that I already have upped the FSB and NB with 0.1.
So plan for tomorrow morning:
- Up FSB from +0.1 to +0.3
- Up NB from +0.1 to +0.2
- Set FSB to 440 (3.3 GHz)
- Run PRIME95
- If it doesn't error within 15 minutes: leave it running while at school (6 hours)
- If it does error within 15 minutes: I dunno, you tell me.
Sounds like a good plan? (in the plan, all will be done at once)
EDIT:panzer @ pr0 posting speed
Yup it's normally like 10 years --> 4-5 years at the very worst.haffeysucks wrote:
longer than the time you'd normally replace a CPUJenspm wrote:
hrm, how redused lifespan?Aries_37 wrote:
If it still fails after that up the vcore a tiny bit more, the vdroop should keep you in a safe zone. But tbh you're shooting for a huuge overclock, massive volts and reduced lifespans will have to be accepted as worthwhile collateral
EDIT:panzer @ pr0 posting speed
Also, I think I might stop at 3.3
oh, ok, bring the volts, I say!Aries_37 wrote:
Yup it's normally like 10 years --> 4-5 years at the very worst.haffeysucks wrote:
longer than the time you'd normally replace a CPUJenspm wrote:
hrm, how redused lifespan?
Also, I think I might stop at 3.3
delete/edit button is useful tbh.Sup wrote:
Hes faster than a pigeon shitting poop on your shoulder. ---no wait, that doesn't make any sense. I'll leave it anyway.Aries_37 wrote:
If it still fails after that up the vcore a tiny bit more, the vdroop should keep you in a safe zone. But tbh you're shooting for a huuge overclock, massive volts and reduced lifespans will have to be accepted as worthwhile collateralJenspm wrote:
oh fucks, I forgot to say that I already have upped the FSB and NB with 0.1.
So plan for tomorrow morning:
- Up FSB from +0.1 to +0.3
- Up NB from +0.1 to +0.2
- Set FSB to 440 (3.3 GHz)
- Run PRIME95
- If it doesn't error within 15 minutes: leave it running while at school (6 hours)
- If it does error within 15 minutes: I dunno, you tell me.
Sounds like a good plan? (in the plan, all will be done at once)
EDIT:panzer @ pr0 posting speed
"people in ny have a general idea of how to drive. one of the pedals goes forward the other one prevents you from dying"