New build soon

[Mithrandir]

One of two things either 1:2 is actual speed so effectively 1:1 (as DDR is double data rate) so 200x2 = 400MHz or the divider is actually at 1:2 so 200x2=400 then DDR so 400x2=800MHz

If CPUZ says DRAM Frequency is 400MHz then your actually running at 800MHz.

Thanks. That's what I was thinking but I'll need to spend more time with it when I get home.

[Mithrandir]

Had an hour to spare last night so I upped the fsb and set in a divider for the ram.

At fsb 240 = 2.88ghz




At fsb 250 = 3ghz




Ran Orthos for 5 mins (temps topped 51 degrees in a cool room [18 degrees])



I tried fsb 265 but failed to boot.


One thing I'm worried about are the voltages set to auto. Not sure how to set a fixed value on the cpu v. The cpu voltage is on 1.39v at fsb250. I know it's more about the temps but am worried especially when summer comes along.

[CAT-THE-FIFTH]

You should also test the overclock for stability. IntelTestBurn is a very good and quick test. A 7 to 10 test run should be enough to test for stability and should take under an hour.

[Mithrandir]

Just read this usually goes 20 degrees above normal load temps.

Would topping 80 degrees be safe for the cpu?

[Webby]

Any reason you were running 2 Orthos' it is already multi-threaded so on instance is enough to load up up

As to why you didn't boot at 265 that could be either the CPU didn't going that fast, the memory didn't like going that fast (unless you changed the divider again you exceeded 800MHz) or you need more voltage to a component be that CPU, NB or memory.

I am not familiar with Biostar's BIOS so can't help on finding manual control for the voltages sorry although they are normally accessed from the same screen as CPU frequency etc.

[Mithrandir]

Any reason you were running 2 Orthos' it is already multi-threaded so on instance is enough to load up up

As to why you didn't boot at 265 that could be either the CPU didn't going that fast, the memory didn't like going that fast (unless you changed the divider again you exceeded 800MHz) or you need more voltage to a component be that CPU, NB or memory.

I am not familiar with Biostar's BIOS so can't help on finding manual control for the voltages sorry although they are normally accessed from the same screen as CPU frequency etc.

lol. Good point about Orthos. Not sure what I was doing there.


I think it must be the ram holding me back, I'm sure it's running at 1.9v and can go up to 2.1v.

[Mithrandir]

Well I ran IntelBurnTest and max temp I saw was 57 degrees




3DMark06 score on a 250fsb OC (3ghz)



My 250fsb OC seem to fail Orthos though

[Webby]

Well no one program tests in the same ways so its possible for it to pass Orthos and fail IBT or the otherway around although you would normally expect it to fail both try running IBT for 20 rounds rather than 8 and see if it still comes back ok or not, my cpu passed 9 then failed 10 when i was pushing it as far as it will go, Longer is always better in these tests also don't run it in report mode that way you can see whats going on and if it fails you can see and stop the rest of the run rather than having to wait for it to finish.

[CAT-THE-FIFTH]

I usually run 25 iterations of IntelBurnTest. I would also use OCCT CPU for at least 8 hours too. I also would run the OCCT Blend Test for 2 hours also. Then you can try Orthos for at least 12 hours also after that. I would also do a couple of 3DMark06 runs too. Doing a few loops for the Crysis test also is useful.

IntelBurnTest usually detects errors earlier in my experience. I have had OCCT and Orthos stable overclocks which it has detected errors in. The great thing it is the quickest
way to find CPU errors than any other programme I know.

If your PC is stable after this it should be fine for most gaming and encoding sessions for the average user!!

I would rather spend a weekend to make sure the overclock is stable as BSODs later on can be rather annoying!!

[CAT-THE-FIFTH]

Well I ran IntelBurnTest and max temp I saw was 57 degrees




3DMark06 score on a 250fsb OC (3ghz)



My 250fsb OC seem to fail Orthos though

Sorry I thanked you by mistake!!

Sometimes Orthos fails when the maximum temperature it allocates as safe by default is exceeded. I think it is 60C IIRC. You can change this setting if you do not mind your CPU exceeding it!

[Mithrandir]

Sorry I thanked you by mistake!!

Sometimes Orthos fails when the maximum temperature it allocates as safe by default is exceeded. I think it is 60C IIRC. You can change this setting if you do not mind your CPU exceeding it!

lol.

I'll have a look at Orthos settings but I'm sure the temps haven't reached that high (well defo not as high as IntelBurnTest)

Will try a 10 run and then 20 run loop to see how it copes.

[Webby]

If your cooling is stable for 8 runs its not going to matter if it is doing 10 or 100 you will be fine

Anyway do the testing and see what happens testing is fun

Now all I need to do is resist the temptation to buy a new CPU just to see what it can do...

[CAT-THE-FIFTH]

Now all I need to do is resist the temptation to buy a new CPU just to see what it can do...

I need to resist the temptation to buy a new graphics card!! Just dropped my HD3870 when cleaning the dust out of my pc!! Butterfingers!! Managed to knock a single resistor off the back of the card. Luckily I managed to find it!!
Anyway successfully resolder one back onto their card here??

Looks like I will be using my good old trusty x1900gt for the next couple of months!! Anyway I needed a rest from FPS gaming for a while!! Go Star Trek:Lecacy go!