OC beginner looking for some feedback on results

sef24

sef24

New Member
Well tonight I started to read up on Overclocking, taking notes and reading carefully so that I wont make any mistakes.

My specs are in the sig.
I had disabled turbo boost as well as CIE and EIST in the bios

My normal bus speed was at 133 and I had increased it to 160 with a x25 multiplier.

After some tests, I kept getting windows startup crashes -> blue screen
I slowely up'd the voltage little by little till I was able to boot stable.

I ran ORTHOS stress test while keeping up CPU-Z and SpeedFan to watch temps.

My currently clock speed is now ~ +/- 4Gz. I up'd the core volatage to 1.35 but cpu-z reads it as 1.296.
ORTHOS gave me 1 error during a test, I reran it without a reboot and after 14 minutes of stress, I did not get any errors

Core0 and Core1 temps are 57-59C, but I never seen it go higher then that while stressed.
While idle they are about 38C.

With my current temps, are they cool enough to not worry about?
As my first OC ill prob keep it at whatever state without pushing it higher than 4gz but, do you think I could push it farther without problems? (future)
Also what is up with cpu-z reading my core volt at 1.296? and not the 1.35 that I set it to.

Anything else I should know about? I changed some of the memory settings, such as setting the DRam timings to quick, making sure they ran at my current ram speeds (9-9-9-24), disabled XMP, and changed preference enhance to standard.

Cant wait to see how bad or well I did?
 
Here is a few pics of my results, I also see the core voltage changed a bit during this pic

cpuz.png


speedfan.png
 
Last edited:
Aastii said:
Those are very good temperatures, however, I would stress test for much longer, especially as you got an error. I would also use Prime 95 to stress test, and wouldn't use Speedfan to measure temps, I would use HWMonitor.

Prime 95: http://www.mersenne.org/freesoft/

HWMonitor: ftp://ftp.cpuid.com/hwmonitor/hwmonitor_1.17-setup.exe
Click to expand...

+1 to basically everything he said. Most people would stress test for at least 12 hours before calling an overclock truly stable. You'll also find your temps will slowly creep up after the 14 minute mark too, so it helps get a more accurate feel as to where your temps are sitting. You have pretty good temps so you don't need to worry about heat for a little bit yet.
 
oh wow, didnt think I need to stress test that long hehe.

Ill go ahead and do that, and ill use those apps during the tests.

While using it today I seem to be getting more failure, as in firefox not responding and had to restart my browser. This rarely happens but I am assuming its because of the OC.

During a long stress test, is it ok to have other apps running? Mostly just microsoft word (to work on a paper).
 
What temps would you suggest as being too high?

With these two apps I am currently getting
core0 max 70c, usually stays around 68c
core2 max 63c

This has only been an hour of straight stress

cpuid.png
 
Last edited:
Well you have to keep in mind that during a stress test your temps will be higher than pretty much anything else you do. My temps hit low-mid 50's during Prime95, but my most demanding games only get it to about 45*c, and I've got a 1055T, which has a much lower TJMax than intel's CPUs.

I don't think it matters if you use other programs while testing, but I really don't know I've just done it. As far as overclocking making FF lock up, it probably isn't indicative of instability. You'll usually get pretty drastic results if your overclock is unstable. Artifacts, blue screens, hardlocks, etc. Overclocking can make some programs behave funny though. The higher I overclock, the choppier my gameplay gets in Far Cry 2 for example. My FPS is through the roof, but the game just doesn't like the overclock. The list goes on and on. One member's sound would cut out if he overclocked a certain amount, even though his system was completely stable. :P
 
You must log in or register to reply here.
Back
Top