View Full Version : OC'ing my CPU
Floor66
09-06-2009, 09:19 PM
I'm think about overclocking my processor, but I need some explanation on how to :$ And I don't wanna mess it up x'D
My current specs:
Windows XP SP3
3.0 GB RAM
Intel Core2 Duo E6300 @ 1.86GHz
Everest says:
CPU temp. = 40 Degrees Celsius
CPU #1 / Core #1 temp. = 43 Degrees Celsius
CPU #1 / Core #2 temp. = 39 Degrees Celsius
So is it appropriate for me to do? And what are all the risks?
I know... :google: But I trust SRL's wizzkids over google :<>
Sabzi
09-06-2009, 10:05 PM
I got the same processor!
I love it!
I over clocked it to 2.8 GHz :D, so I may can help you.
I got 2 GB ram.
You don't have to worry under 50 Celsius I would say. I have bought a new cooler, tho.
"So is it appropriate for me to do?"
If you own a C2D E6300 you MUST overclock it.
I have done this about 2 years ago and I haven't done with it anything since that so I forgot this and that.
How you can overclock it is highly depends on your mainboard and your ram too.
When you overclok you must raise the voltage a bit(with E6300 it's not much), and set the multiplier of the ram to fit the new core speed, maybe you have to set the ram frequency too.
I know I haven't provided much knowledge but this may help:
http://www.overclock.net/
You have to google your ram, what properties they suggest for it(Mine is 4-4-4-12, Geil Ultra 800 MHz) and set it to that. And when you overclocking you have to keep the ram frequency within a small range with modifying the multipliers.(For me it's 400 MHz but it counts double for me(I don't really understand this part.)
You don't have to worry, intel processors won't burn in your mainboard. If you don't do something really serious you will just have to reboot and set the things back.
Don't rely on programs that do this things for you after startup. Just set everything with hand in BIOS.
First just give it a small boos. Maybe 1,9 GHz or 2.0 GHz. Don't even bother with other things. Try it. If there is no beeb you are okay :)
You must get CPUZ and some stressing programme(I forgot what I have used) to test the stability of your new setup. Then reboot -> BIOS -> some more MHz, voltage(very little) -> test again. You will have to do some "jumps" though because of the ram frequency so that you can keep it in the small range with changing the multipliers.
For example you want 400 for the ram. As you changing the core speed it will raise too so if it is like 420 change the multiplier so you will have 380. But 380 is low a bit so this is the jump, you boost the core speed a bit more so it will be near 400(the ram).
My mainboard count me the ram frequency, some not, so you may have trouble counting that yourself(I don't know the formulas).
Floor66
09-06-2009, 11:37 PM
First just give it a small boos. Maybe 1,9 GHz or 2.0 GHz. Don't even bother with other things. Try it. If there is no beeb you are okay
Erm you say I should just do this... Without doing all the stuff you post next ("You must get CPUZ and some...")
And how much voltage do you mean by 'very little voltage'?
And a different question;
When running a game really intensive (max settings), is it normal for my ATi Radeon HD 2600 XT's GPU temp to be like 70+ degrees Celsius?
Sabzi
09-07-2009, 12:13 AM
That doesn't matter. GPUs are in that high range. I was talking about just the processor.
It can be 55 or 60 but I like keeping it under 50.
And the first steps are so little you don't have to do anything with other things.
If you got the default cooler I wouldn't go higher then 2.4. Maybe just 2.2 based on the weather there, lol.
Lol I have started to write this a lots of minutes ago. I probably wanted to say something more but I forgot.
EDIT:Oh, yeah I got it! About the voltage ...
I don't know what you got now.
Very little means a few 0.01 maybe 0.1. I forgot a lot since then but if you need help I think I can reveal it.
Floor66
09-07-2009, 01:24 AM
I can't find a way to change the voltages in my BIOS :\
But, no worries. Standing at 2.03GHz atm, and adding 5-10MHz till it wont boot no more.
Temps are still the same.
Sabzi
09-07-2009, 01:35 AM
I can't find a way to change the voltages in my BIOS :\
But, no worries. Standing at 2.03GHz atm, and adding 5-10MHz till it wont boot no more.
Temps are still the same.
That's the way how it goes. But be careful with your ram. If they are on a too high frequency, well it's not good.
But booting is not everything. You may can boot while you can't play because you get a blue screen. You should find the good voltage for the best stability.
There must be something you can set the voltage with, though.
And the real temperature just show itself under work. But as I have mentioned high temperature cause nothing serious to you as far as I know. Intel processors rock. And you mainboard must have something maximum temp too.
Good luck for you!
Floor66
09-07-2009, 01:47 AM
I've got a stress test program thingy and I'll run it for 2 hours later on.
And I accidently put waaaaaaaay to much at the same time and for a moment there I was afraid my PC was dead... But then, technology came to the rescue! :D
It reseted the GHz to 1.86.
bullzeye95
09-07-2009, 01:50 AM
But as I have mentioned high temperature cause nothing serious to you as far as I know.
If the temperature gets too high, it will damage the CPU, no matter what kind of processor it is.
For testing stability, get Intel Burn Test (http://downloads.guru3d.com/downloadget.php?id=2047&file=1&evp=c124b204b68596fcc99d0f9f96c3bb65), and set stress level to maximum. Before you start it, get Real Temp (http://www.techpowerup.com/downloads/1325i/RealTemp_3.00.zip) to monitor your CPU temperature. Start the test, but if the temperature goes over 60C, it's too hot, so stop the test and either downclock until it doesn't get that hot, or get a better heatsink.
Floor66
09-07-2009, 01:52 AM
I've got Everest, and from my expiriences it's way more accurate (aprox. 7 deg. C.) than RealTemp.
ehazel
09-07-2009, 01:54 AM
I'm think about overclocking my processor, but I need some explanation on how to :$ And I don't wanna mess it up x'D
My current specs:
Windows XP SP3
3.0 GB RAM
Intel Core2 Duo E6300 @ 1.86GHz
Everest says:
CPU temp. = 40 Degrees Celsius
CPU #1 / Core #1 temp. = 43 Degrees Celsius
CPU #1 / Core #2 temp. = 39 Degrees Celsius
So is it appropriate for me to do? And what are all the risks?
I know... :google: But I trust SRL's wizzkids over google :<>
what mobo are you running?
Sabzi
09-07-2009, 01:56 AM
I don't got personal experiences, I never let it higher than 55. And 55 is just when I stress it.
Sorry Floor :(
However, my overclocking master friend told me when I asked him about temperature that 60 is not that dangerous high. But it's always better to keep it lower as bullzeye said.
bullzeye95
09-07-2009, 02:02 AM
However, my overclocking master friend told me when I asked him about temperature that 60 is not that dangerous high. But it's always better to keep it lower as bullzeye said.
70C is where it really starts getting dangerous, but keeping it below 60C is generally the rule I've seen, as sometimes it can cause damage (not often at all, but you want to be on the safe side, right?).
@Floor, are you sure that Everest reads 45nm CPU temperatures correctly? I am quite sure that Real Temp does, but if you are sure that Real Temp isn't accurate, I will google around about it.
Floor66
09-07-2009, 02:03 AM
How long does that BurnTest run if you choose it to run once?
EDIT:
and about Everest, the temps in my BIOS are way more similar to the ones Everest gives.
bullzeye95
09-07-2009, 02:05 AM
It's probably different on your computer than mine, but it takes 15-20 minutes for me.
EDIT: Oh, once.. 5 minutes max. You kinda need to run it more than once though (3 times minimum), because it compares the different runs to check stability.
Floor66
09-07-2009, 02:08 AM
I'll run it; 5 times; 2000 MB (more gives a 64-bit error, i have 32-bit).
EDIT:
OK ran it 3 times (cba to wait more ^^) at 2.03GHz, I'm a little confused tho;
My highests:
CPU: 54
Core 1: 61
Core 2: 62
Which one 'counts' here?
Markus
09-07-2009, 02:35 AM
70C is where it really starts getting dangerous, but keeping it below 60C is generally the rule I've seen, as sometimes it can cause damage (not often at all, but you want to be on the safe side, right?)..
Modern CPU's clock down/shut down when the temps go to high. Something like this (http://www.youtube.com/watch?v=Xf0VuRG7MN4) won't happen anymore with modern CPU's (gotta lol at the AMD's at the end xD).
Putting voltage too high, however, can burn up CPUs.
Floor66
09-07-2009, 02:42 AM
Can anyone answer my previous question ;3
And, I can't adjust my voltage in my BIOS, what are my other options to still change it ? :\
bullzeye95
09-07-2009, 02:44 AM
Get a new motherboard.
Markus
09-07-2009, 02:48 AM
Just don't change it, and see how far you can go?
Floor66
09-07-2009, 02:49 AM
Can't afford :\
I could also just stick with 2.10GHz and leave it :p
EDIT:
Markus, my exact thoughts ^^.
Everest says:
- Voltage: CPU Core 1.3v
Sabzi
09-07-2009, 03:25 AM
Can't afford :\
I could also just stick with 2.10GHz and leave it :p
EDIT:
Markus, my exact thoughts ^^.
Everest says:
- Voltage: CPU Core 1.3v
Mine is max 1.35 so that^ should be fine for you.
rogeruk
09-07-2009, 06:05 AM
Use ORTHOS, CoreTemp and CPU-Z.
Floor66
09-07-2009, 12:59 PM
I'll run it; 5 times; 2000 MB (more gives a 64-bit error, i have 32-bit).
EDIT:
OK ran it 3 times (cba to wait more ^^) at 2.03GHz, I'm a little confused tho;
My highests:
CPU: 54
Core 1: 61
Core 2: 62
Which one 'counts' here?
Ok thanks, Rogeruk.
Now please someone still answer this :)
EDIT:
Going any higher FSB than 300 will not boot :\ I'm guessing it's because of the voltages, but hey, 2.10GHz, that's something :D
Sabzi
09-07-2009, 09:39 PM
Use ORTHOS, CoreTemp and CPU-Z.
Ahh, my friend, that's it! I used orthos back then.
But I can't remember CoreTemp, lol.
I have heard about 3+ GHz too. They are crazy. However with a good mainboard/cooler that shouldn't be a problem.
I got a Cooler Master Hyper TX2 if anyone interested.
And yeah it won't boot with low voltage. Your processor is hungry than :D.
Powered by vBulletin® Version 4.2.1 Copyright © 2024 vBulletin Solutions, Inc. All rights reserved.