my first oc...

[isifgr]

first oc ever i made. I didnt want to push my pc furhter so i stopped to:

amd 64 3000+ venice: 250*9= 2250@ 1.45V
corsair value ram: drop to ddr333, 2.5-3-3-8 1T @2.6V
msi board neo4 platinum
tt big typhoon

now about my temps : CPU: idle 34 load 41....
m/b: idle 35 load 40....
my case i think is not that good (logisys fantom) when i open the panel temp drop to 32... what do u think??? are high??

For first time oc's : The room temps are very important. In the summer my idle was 42... I thought my pc had a problem so i didnt oc. i saw my pc temps to lower 10c because my room got cooler. I see now how critical is the room temp... still though my room is not cold i assume during the winter cpu-m/b temp are going to get lower ( i am student so... my room is not the best in the world..its on the last floor of an old house).

I got nervous, very confused and frustrated when i was trying to oc but now i feel very confortable with it after spending so many hours reading and testing my pc...

Now i can get an X2 3800+...

I wanna see your opinions or suggestions..to get better knoledge about OC.

 

[kyp275]

try to tidy up the wires inside the case if you haven't, it'll help with the airflow inside the case, and maybe you can knock down your case temp a little bit.

Only way to learn is by reading up on the materials and practice, just like everything else

 

[Leper Messiah]

not bad for a first OC. You got decent parts to start with. My first real OC was a PIII slot one 550 to 616. With idles and loads that low, you could easily take another .1vcore which should get you to like 9x270 or 280. Try adding a bit more voltage to the RAM too, CVR should do decently, 220ish or something like that depending on the chips they binned for value.

 

[isifgr]

i am thinking to move to X2 now... can someone tell me are there different cores?? i know there is manchester is there toledo?? some guys were talking about E6 doesnot oc well who does???

 

[DRBaldock]

Originally posted by: isifgr
first oc ever i made. I didnt want to push my pc furhter so i stopped to:

amd 64 3000+ venice: 250*9= 2250@ 1.45V
corsair value ram: drop to ddr333, 2.5-3-3-8 1T @2.6V
msi board neo4 platinum
tt big typhoon
...

Hello "isifgr",

With the Big Typhoon on the MSI K8N Neo4 Platinum, are you able to use all the memory sockets? The Thermaltake web site doesn't seem to have a motherboard compatability chart.

I've got a Thermalright XP-120 on my current Gigabyte motherboard. Their chart says it blocks the first memory socket on the Neo4 Platinum.

Thanks,
David

 

[GuitarDaddy]

Nice conservative first OC, so many people go for broke right off the bat. Then when they hard crash or corrupt their windows install they are ill prepared to trouble shoot it and get it running again.

Your temps look great! As you overclock further the temps will go up but as long as you stay under 60c(summer) load your fine IMO, although I've seen people running 68c. My SD3700+ running 2.8ghz hits 52-53c(summer) after a few hours of Prime95 but the SD's run a little hotter than the Venices. And a true load temp should be recorded after several hours of Prime95 or S&M, too many people run 3dmark for 15mins and call that a load temp. And with dual core chips of course you have to run two instances of the torture test, one on each core.

A word about stability testing:
Torture tests like Prime95, S&M, OCCT and memtest are you best friends when overclocking. I have meet too many people who say "I don't want to torture my rig, and pull all that stress on it" or "I ain't going to spend the elec. to run that all night". The truth is these programs are essential for overclocking. 95% of the problems(data corruption, OS repairs, and reformats) that come from overclocking occur when attempting to boot up to unstable settings. These programs are designed to create stress and detect instability and when instability is detected it creates an error, and they do not cause any harm to your system. All those problems can be avoided if you boot up to a known stable setting then use a program like clockgen to bump your HTT up a few mhz at a time and do rigorous stability testing at each level. The stress programs will detect instability and create an error long before your system becomes unstable enough to hang or crash, so then you can adjust your settings (voltages, timinings, etc..) and resume stress testing.
If you use this simple process there is no reason you can't push your system to its limit with almost 0 chance of messing something up.


Now spank that puppy and lets see what she can do