PDA

View Full Version : Mr.B question


Toonarmy
05-17-01, 10:23 AM
ok, as i said in a previous post i am new to o/c'ing etc but i want to make sure i understand what you mean by light, moderate & heavy o/c'ing.

talking from a celeron 600 point of view, i take it that a light o/c is bumping the fsb upto 75mhz, moderate = 83mhz and a heavy =100+mhz yes? or is 83mhz seen to be a light o/c?

cheers for helpin a newbie :)

Super
05-17-01, 12:14 PM
I'm not Mr. B, but I'll tell you this, 75MHz will give you the speed of 675MHz, which is a pretty light oc, (I could do it with my default HSF), 83MHz will give you 750MHz, which is not bad, and still, I did it with def. HSF, but you have to watch your temps.

100MHz (will give you 900MHz) I can do now, but now I have Alpha PAL 6035, and I haven't tried it with def HSF.

When I had def HSF, I went no further than 83MHz, I didn't want to burn the chip. If you have good cooling you can go over 100MHz, and clock your celeron 600 to around 1 gig, which is the average speed for that chip.

Toonarmy
05-17-01, 02:06 PM
yea, cheers for that

i went to 675 with the standard hsf and it played CS no probs for hours, but after been left idle it gave a windows protection error but was fine again after restart. Today i slapped an athlon approved upto 1.3ghz cooler with 60mm fan on it and have had no probs since. Was just wondering if this would handle the 83mhz jump as thats all i'm arsed about for the moment but from what you said it looks promising

Link_flap
05-17-01, 02:26 PM
You really should try to avoid the 83MHz bus. Running the PCI bus that far out of spec can wreak havoc on all devices that depend on the PCI bus clock.

An IDE controller acting up at the wrong time can really ruin a day. Granted the current IDE controllers/HDDs seem to be able to handle it better than those of the days of yore, but I've seen too many cases of busted HDDs/IDEc during the socket7 days to even consider running at 83MHz.

I'll risk electromigration over corrupt data any day

Go for 100fsb its close to a sure thing and it will be easier on the rest of your system than 83MHz. If you don't want to go 100, I'd recommend 75.

/Link_flap

Phil
05-17-01, 03:54 PM
with a celeron 600 aim for 900mhz, it should be able to do that pretty easily, it may need better cooling and a voltage increase but it is rare to see a cpu that won't under any circumstance, a FOP 32 is more than enough to get a celeron to 900mhz and stay under 2v, when I bought my cCO 600 it needed 1.75v to be stable at 900mhz with a FOP, I tryed a burn in and it would then run at 900mhz with 1.55v, but after adding some components it needs 1.65v

Toonarmy
05-17-01, 06:35 PM
Ok, well i really dont want to kill the cpu which is why i have not been to enthusiastic about going to 100mhz (thinking that getting an extra 50% of cpu power will kill it quite quickly). But as i am new to this and i have no reference to get an idea of the life expectancy of the c600 @ 900 could anyone post their results of c600 o/c'ing at 900+, i.e how long it lasted/how long its been running stable at the current speed etc?

cheers

thanks for the responses btw :)

stompah
05-17-01, 07:32 PM
As a newb I'll make a quick comment.

Your 600 celly should handle a 100mhz FSB it seems as if most can handle it (from my research). Like everyone has said cooling is very important. I started off with a GOrb cause it was cheap and I had a hard time choosing what cooler to buy. Now that I have decided I have taken the GOrb off and may never use it again. I bought an Alpha 6035 off of ebay and have been happy (except for the loss of 2 DIMMs on my MB).

The other thing is that since the 600 should handle a a 100mhz fsb and running in the middle will just mess with your PCI/AGP divisors. The best choice you could make is to jump as close as you can to 100mhz and set the divisors accordingly. that way you will be slightly underclocked as opposed to very overclocked.

Good luck

And sorry I thought I would make it quick...

William
05-17-01, 09:35 PM
Super (May 17, 2001 12:14 p.m.):
I'm not Mr. B, but I'll tell you this, 75MHz will give you the speed of 675MHz, which is a pretty light oc, (I could do it with my default HSF), 83MHz will give you 750MHz, which is not bad, and still, I did it with def. HSF, but you have to watch your temps.

100MHz (will give you 900MHz) I can do now, but now I have Alpha PAL 6035, and I haven't tried it with def HSF.

When I had def HSF, I went no further than 83MHz, I didn't want to burn the chip. If you have good cooling you can go over 100MHz, and clock your celeron 600 to around 1 gig, which is the average speed for that chip.

same here, i am running the retail, I think I can get this puppt to a gig, I am running at default voltage now, and that is good. So maybe I can get a new hsf for this puppy and get it to a gig.

Mr B
05-17-01, 10:04 PM
Hey gang....

Had plans w/ the wife this evening....just got on...

Frankly, sounds like you've answered the question. Each chip is different, in regards to vcore required to achieve different bus speeds, so I don't think there's any "set in stone" numbers that you could go by.

75 MHz I would define as "light", 83 I wouldn't run unless I really had to, as the PCI bus is so far outta whack there...90 to 100 I'd call "moderate"

103+ I'd call "heavy". But again, as I said, each chip is different. Some chips will hit 100 FSB at default vcore settings. Therfore, I'd have to say that 100 FSB for this chip is "light". Other chips might need 1.95v to get there....this is closer to "heavy", but at the same bus speed...follow the thought process??

Increasing the vcore will increase the temps, requiring a better than OEM hsf. Heck, if you can get a 66 FSB Celeron to 100 at default, with the intel hsf, at low temps, by all means do it. But if you have to start bumping up the vcore setting, start thinking about a better hsf, too.

Mr B

Rainmaker
05-18-01, 06:23 AM
The new cco celerons are really easy to overclock. Mine can do 1100 at 2.1v with the retail hsf! Have it down to 1035 1.8v now because I'm waiting for an Alpha and I don't want to risk burning it. I would definitely avoid 83mhz fsb. I have had hard disks die on me at this level back when I was still taking a celeron 366 to 550. I still can't play dvds using my decoder at greater than 945.

Toonarmy
05-18-01, 12:50 PM
ok, cheers for the replies been running bang on at 83 mhz the last couple of days with the 1.2ghz athlon approved giant mutha of a hsf and it seems well cool in there at the moment, but thats without upping the core settings, i'll give it a shot at 100fsb see how it goes (if at all). Trying to find the m/b manual as i aint sure if the board will allow me to change the core settings

what is the life expectancy of this celery at 100fsb both with and without changing the vcore settings? a month, a year, 2 years, 5 years??

how long have you been running your c600 @ 1053 for instance?

cheers

Rainmaker
05-18-01, 06:53 PM
I saw a thread here once where somebody estimated that with extreme overclocking a celeron would probably last 5 years minimum. Haven't had a cpu for more than 2 years. I just got my c600 last March. The store that had them had a bunch of exactly the same batch/fpo#. Probably don't know they're sitting on an overclocker's goldmine.

Good luck with your climb to 100.

Newbie_Doo
05-18-01, 08:02 PM
Toonarmy (May 18, 2001 12:56 p.m.):
ok, cheers for the replies been running bang on at 83 mhz the last couple of days with the 1.2ghz athlon approved giant mutha of a hsf and it seems well cool in there at the moment, but thats without upping the core settings, i'll give it a shot at 100fsb see how it goes (if at all). Trying to find the m/b manual as i aint sure if the board will allow me to change the core settings

what is the life expectancy of this celery at 100fsb both with and without changing the vcore settings? a month, a year, 2 years, 5 years??

how long have you been running your c600 @ 1053 for instance?

cheers

The life expectancy under overclocked conditions is longer than your tolerance for slow computers. You will likely upgrade before your chip spits the dummy.

Mr B
05-18-01, 10:31 PM
Hmmmmm...

Toonarmy,

I only ran the chip there for about a month, during which time I got a P/// 600E, an Asus P3C2000 mb, and an Alpha P3125 hsf. I got the P/// running stable at 954 MHz, which blows away a C "1053" all day long.

Rainmaker,

Noticed in your "sig" you run your Celeron on the same mb I ran mine at 1053....Those two (C600 and 6BA+III) seem to work really well together, don't they??

NewbieDoo,

Wow, what a lovely old colloquial phrase! I can't remember the last time I heard something referred to as "Spitting the Dummy" when it dies....lol

Bonus points for you for this one....hehehehe

Mr B

Shadow рс
05-19-01, 02:18 AM
pretty sure I've NEVER heard that saying!

Toonarmy
05-19-01, 05:21 AM
well, i tried 100mhz, thought it was gonna work for a second

posted fine started to boot into windows but locked on the winme bootup screen. The main problem i now have is that the feckin motherboard i got (Gigabyte 6BXC) doesn't allow me to change the vcore of the cpu, any ideas on how to overcome this prob is most welcome

Rainmaker
05-19-01, 06:23 AM
Toonarmy,

Too bad man.Vcore adjustments can be quite helpful. Gigabytes have never been known for being overclocker friendly.


Mr. B,

Soyo sure made pretty good bx boards. Bxboards.com even said that the 6ba+III was the best bx board they had reviewed at that time (mid-98 or so).If I remember right the first review of the p3500e in oc.com was made with a 6ba+IV. Went straight to 150 stable. And with a Soltek slocket.

Super
05-19-01, 09:38 AM
Toonarmy (May 19, 2001 05:21 a.m.):
well, i tried 100mhz, thought it was gonna work for a second

posted fine started to boot into windows but locked on the winme bootup screen. The main problem i now have is that the feckin motherboard i got (Gigabyte 6BXC) doesn't allow me to change the vcore of the cpu, any ideas on how to overcome this prob is most welcome

I have the same problem, I can't boot at anything over 100MHz FSB. My max CV is 1.7V. There is an article in Hard OCP, which tells you how to do the vidpinging trick. You basically connect some CPU pins with a wire, and it gives you better voltage. I haven't tried that yet, but as soon as I learn everything about it, than I'll try. ( I just don't want to loose my chip)

Phil
05-19-01, 03:08 PM
Is the Gigabyte 6BXC a slot 1 or s370 board? if it's a slot 1 then I recomend getting a better slocket, either an asus abit or Iwill with voltage selction jumpers will be fine. if it's an s370 then you will need to do the wire trick mentioned by Super, just be sensible about the voltage you select

Toonarmy
05-19-01, 03:51 PM
yea its a slot 1 motherboard, been hearing about these slockets where can i get a good one from and how much would they cost me? i'm british btw :)

Toonarmy
05-19-01, 03:57 PM
yea its a slot 1 motherboard, been hearing about these slockets where can i get a good one from and how much would they cost me? i'm british btw :)

LutaWicasa
05-19-01, 04:01 PM
Don't forget the MSI 6905 Master ver 2 slotket :)

Mr B
05-19-01, 05:56 PM
Or the Soltek SL02A++ either.....=)

I'd put the Abit !!! at the bottom of the list of slockets mentioned above... I've been reading a lot of not so nice things about them, like stability problems, etc...

I've also seen quite a few posts that say when they've replaced the Abit !!! with another brand, they were able to overclock to a faster setting. I can't vouch for this, as the Abit !!! I have has a C600 that was pre-tested to 945 MHz on it, and from what I've read, the problems start at somewhat faster speeds than this. Let's put it this way (IMHO) ... I'm selling mine in the rig I built for a co-worker. It seems to work fine at the speed the C600 will run at (945 max), so I know it won't screw up on the guy, and I don't have to deal with trying to get it to run with a different chip. Reading all of the bad stuff about them made the decision to pass it along quite easy.....

Mr B

Super
05-19-01, 07:16 PM
Mr B (May 19, 2001 05:56 p.m.):
Or the Soltek SL02A++ either.....=)

I'd put the Abit !!! at the bottom of the list of slockets mentioned above... I've been reading a lot of not so nice things about them, like stability problems, etc...

I've also seen quite a few posts that say when they've replaced the Abit !!! with another brand, they were able to overclock to a faster setting. I can't vouch for this, as the Abit !!! I have has a C600 that was pre-tested to 945 MHz on it, and from what I've read, the problems start at somewhat faster speeds than this. Let's put it this way (IMHO) ... I'm selling mine in the rig I built for a co-worker. It seems to work fine at the speed the C600 will run at (945 max), so I know it won't screw up on the guy, and I don't have to deal with trying to get it to run with a different chip. Reading all of the bad stuff about them made the decision to pass it along quite easy.....

Mr B

So much for that ABIT slogan : "ABIT Takes you to the Top.... Power, Stability, Speed"

Sempei
05-19-01, 10:23 PM
I'll second Mr B's opinion on the Abit sloket. Mine was fine up to 927 but no voltage above it (up to 2.1v)would keep me stable at 1008. Switched to an MSI 6905 Master and all was sweet. 1008 at 1.9v with no instability at all.

Newbie_Doo
05-20-01, 01:03 PM
Mr B (May 18, 2001 10:34 p.m.):
Hmmmmm...

Toonarmy,

I only ran the chip there for about a month, during which time I got a P/// 600E, an Asus P3C2000 mb, and an Alpha P3125 hsf. I got the P/// running stable at 954 MHz, which blows away a C "1053" all day long.

Rainmaker,

Noticed in your "sig" you run your Celeron on the same mb I ran mine at 1053....Those two (C600 and 6BA+III) seem to work really well together, don't they??

NewbieDoo,

Wow, what a lovely old colloquial phrase! I can't remember the last time I heard something referred to as "Spitting the Dummy" when it dies....lol

Bonus points for you for this one....hehehehe

Mr B

It's an Australian phrase, I don't remember when I learned it but here is one of many definitions:

"DUMMY , as in spit the dummy. To spit the dummy is to baulk at, get angry about, or simply, obstinately refuse to do, something. A dummy is what some Americans call a pacifier, and when a baby spits the dummy it just can't be pacified."
(Source: http://goaustralia.about.com/travel/goaustralia/library/weekly/blstrine_d.htm )

When I use it about CPUs, I mean it in the sense that it simply refuses to work anymore.