What kind of speeds and stability are you getting out of it? Any special cooling tricks required?
Is celly @900 really better than athlon600 I wonder.
Is celly @900 really better than athlon600 I wonder.
your overclocked Celeron600s going well?
- Thread starter Rigoletto
- Start date
I just recently put together a new system on an Abit BX133-RAID (yes the infamous one), using a Celeron 600. Unfortunately, the maximum voltage allowed by the BIOS for Celemine is 1.75 V, and I've heard many stories of people who need significantly more than that to reach 900 Mhz/100 FSB.
Mine works perfectly well at 1.70 V @819 MHz/91 FSB, no crashes at all in Win2k or Win98 SE. Cooling was with a Golden Orb and the stock square of heatsink putty which my Gorb shipped with, temperature typically reads 34 C with MoboMonitor. However, it tends to crash at 828/92 even at 1.75 V, and will not boot at 93 regardless of any PCI or AGP divider settings. I left it at 801/89 for the time being, just to be on the safe side, and have had no crashes at all for a week. Elsa Erazor X works fine on the 89 MHz overclocked AGP port, PCI is divided to 1/3 speed though, ~30 Mhz.
If Abit updates the BIOS to allow higher voltages (as they do on their other mainboards) then I'll try for 900 Mhz, but I'm pretty happy as it is.
As for the Duron vs Celemine comparison, it might be fairer to rate an unlocked and o/c'ed Duron against the Celeron. I understand that most 600's will easily reach 900 among Durons, but this is rarer with Celeron. If you buy a Celeron I'd personally recommend choosing the 566 or even 533 (with lower multipliers) so you can achieve a high FSB within the limits of your particular chip.
Mine works perfectly well at 1.70 V @819 MHz/91 FSB, no crashes at all in Win2k or Win98 SE. Cooling was with a Golden Orb and the stock square of heatsink putty which my Gorb shipped with, temperature typically reads 34 C with MoboMonitor. However, it tends to crash at 828/92 even at 1.75 V, and will not boot at 93 regardless of any PCI or AGP divider settings. I left it at 801/89 for the time being, just to be on the safe side, and have had no crashes at all for a week. Elsa Erazor X works fine on the 89 MHz overclocked AGP port, PCI is divided to 1/3 speed though, ~30 Mhz.
If Abit updates the BIOS to allow higher voltages (as they do on their other mainboards) then I'll try for 900 Mhz, but I'm pretty happy as it is.
As for the Duron vs Celemine comparison, it might be fairer to rate an unlocked and o/c'ed Duron against the Celeron. I understand that most 600's will easily reach 900 among Durons, but this is rarer with Celeron. If you buy a Celeron I'd personally recommend choosing the 566 or even 533 (with lower multipliers) so you can achieve a high FSB within the limits of your particular chip.
Thanks for so much detail. Pity is that 533 and 566 can't be found right now. They are moving onto the 633 very soon.
I just upgraded my processor to the Celeron 600MHz (retail) on my SY-6VBA133. The highest I can get so far is 750MHz on 83MHz FSB using default 1.52V and the heatsink and fan that came with the Cely.
The SY-6VBA133 requires me to set a dip switch to initially boot to either 66MHz, 100MHz, and 133MHz. If I set the dip switch to 66MHz, then the highest I can overclock on the BIOS is 83MHz, which is what I have now. I would like to try the next higher setting at 90MHz but setting the dip switch to 100MHz would not boot. I hear the drives spinning etc., but no video would come on.
I tried increasing the voltage up to 1.75 on my MSI6905 slocket but still would not boot on 100MHz FSB. I have no indication (since I have no video) that the mobo took the 1.75 setting on my slocket.
The SY-6VBA133 requires me to set a dip switch to initially boot to either 66MHz, 100MHz, and 133MHz. If I set the dip switch to 66MHz, then the highest I can overclock on the BIOS is 83MHz, which is what I have now. I would like to try the next higher setting at 90MHz but setting the dip switch to 100MHz would not boot. I hear the drives spinning etc., but no video would come on.
I tried increasing the voltage up to 1.75 on my MSI6905 slocket but still would not boot on 100MHz FSB. I have no indication (since I have no video) that the mobo took the 1.75 setting on my slocket.
This one still works well:
Abit BH6 1.02
Celeron 600 @ 900MHz 1.8v
Generic Slocket for coppermine
Alpha PEP66 w/ ADDA 28.3CFM fan
Tony
Abit BH6 1.02
Celeron 600 @ 900MHz 1.8v
Generic Slocket for coppermine
Alpha PEP66 w/ ADDA 28.3CFM fan
Tony
I have a Celeron 633@950 out of the box with a Golden Ord+Abit sloket!!!
at 1.7V. This is on a Giga-byte 6BXE with PC66, PC100, and PC133 running together with no problems....
JCruz
at 1.7V. This is on a Giga-byte 6BXE with PC66, PC100, and PC133 running together with no problems....
JCruz
Eug
Lifer
- Mar 11, 2000
- 24,167
- 1,812
- 126
<< I tried increasing the voltage up to 1.75 on my MSI6905 slocket but still would not boot on 100MHz FSB. I have no indication (since I have no video) that the mobo took the 1.75 setting on my slocket. >>
Yes you do. Boot at 66 MHz and see what the voltage is. I'd be surprised if that chip could do 1.75 900. You may need a much higher voltage. Also, are you sure you can do 100 FSB with your memory? (Cas 2 vs. Cas 3). (I believe your AGP should be OK since I think that board autosets the AGP speed - but it's been a while so I'm not 100% sure.)
Edit: I forgot to mention that I'm at 920 (Celeron 533A) at 1.9 V. (I could probably do 1.85 but my older system doesn't recognize that voltage.) 1.8 V is stable at 897 but is ever so slightly unstable at 920 - got one BSOD after a day of use. Rest of setup in sig. I also have Arctic Silver paste and lots of case air flow. YMMV.
Eug, you're absolutely right about the 66MHz 1.75V check -- that never occurred to me! Thanks.
I have since switched my MS6905 with an Asus slocket ? the MS6905 is now in my son?s PC with an older Intel mobo and a 366@550 Cely. I got the Asus because the MS6905 was out of stock at most places and the Asus was available at a local computer merchant.
I've had some success on the 600MHz just now. I am now at 900 MHz at 1.80V. I would not call it stable yet as I get occasional blue screens on WinME. (I have Norton Crashguard so I don?t have to reboot each time.)
At 1.75V I got blue screens. Brought it back to 1.8V. After quite awhile (about 30 mins) the blue screens started reappearing, consistently like every minute. So I suspected a background task that wakes up at regular intervals. When I killed McAfee scheduler (antivirus), the blue screens stopped. On powerdown, though, I got one final blue screen.
Now, I'm back at 1.8V, 900Mhz, have been using for about 1 hour now and only 1 blue screen (yet). The blue screen complained about "vxd pcntn5hl" (???). I also have all my background tasks running again including the McAfee scheduler so I still have some puzzles to solve.
I?ll continue to post my experience here. Thanks again for the tips. I'll keep them in mind.
---
Just read some more of your comments -- yes, the board autosets the AGP speed. I am not using AGP though, I have the PCI Voodoo3 2000. My 2 sticks of 64MB DIMMS are rated at 133Mhz.
I have since switched my MS6905 with an Asus slocket ? the MS6905 is now in my son?s PC with an older Intel mobo and a 366@550 Cely. I got the Asus because the MS6905 was out of stock at most places and the Asus was available at a local computer merchant.
I've had some success on the 600MHz just now. I am now at 900 MHz at 1.80V. I would not call it stable yet as I get occasional blue screens on WinME. (I have Norton Crashguard so I don?t have to reboot each time.)
At 1.75V I got blue screens. Brought it back to 1.8V. After quite awhile (about 30 mins) the blue screens started reappearing, consistently like every minute. So I suspected a background task that wakes up at regular intervals. When I killed McAfee scheduler (antivirus), the blue screens stopped. On powerdown, though, I got one final blue screen.
Now, I'm back at 1.8V, 900Mhz, have been using for about 1 hour now and only 1 blue screen (yet). The blue screen complained about "vxd pcntn5hl" (???). I also have all my background tasks running again including the McAfee scheduler so I still have some puzzles to solve.
I?ll continue to post my experience here. Thanks again for the tips. I'll keep them in mind.
---
Just read some more of your comments -- yes, the board autosets the AGP speed. I am not using AGP though, I have the PCI Voodoo3 2000. My 2 sticks of 64MB DIMMS are rated at 133Mhz.
Got my retailed 633 through buy.com for $83. I have overclocked it to 950 (9.5 x 100) w/ASUS CUV4X and GlobalWin FOP3 and a core voltage of 1.7v. It is very stable except when running Total Annilation, the program crashes sometimes. I am using 256MB of PC-100 SDRAM, so I don't expect it to overclock any higher.
The CPU temperature is no higher than 33c even after intensive game playing. Isn't this a bit too low? The idle temp. is about 27c.
The CPU temperature is no higher than 33c even after intensive game playing. Isn't this a bit too low? The idle temp. is about 27c.
I've gained stability at 900Mhz, 1.80 volts, I think. I say "I think" because I haven't done extensive 3D burn-in tests yet, I just ran QIII demo0001 a couple of times. I won't have time till the weekend. But the PC is used here at home as the ICS server, and no reports of "blue screen" from my "user" when I return home.
I've also done some research on the consistent blue screens I was having the other day. It seems the file pcntn5hl.sys belongs to AMD's phoneline nic drivers. I am not using AMD but I believe all HomePNA chips are made by AMD(?). So the per minute blue screens make sense -- the nic couldn't keep up with the OC'ed proc. If the blue screens return, then I know it's not the proc, the mobo, or WinME.
As a side note, when I upgraded from the 366@550 Cely to the 600 Cely -- no OC yet -- Soundblaster Live would not make any sound. I got blue screens complaining about the "emu---" vxd or something. I downloaded the latest SBLive drivers from CL and it worked again. Pretty strange, the original drivers would not work with the faster proc.
I've also done some research on the consistent blue screens I was having the other day. It seems the file pcntn5hl.sys belongs to AMD's phoneline nic drivers. I am not using AMD but I believe all HomePNA chips are made by AMD(?). So the per minute blue screens make sense -- the nic couldn't keep up with the OC'ed proc. If the blue screens return, then I know it's not the proc, the mobo, or WinME.
As a side note, when I upgraded from the 366@550 Cely to the 600 Cely -- no OC yet -- Soundblaster Live would not make any sound. I got blue screens complaining about the "emu---" vxd or something. I downloaded the latest SBLive drivers from CL and it worked again. Pretty strange, the original drivers would not work with the faster proc.
Rigoletto
Do you realize than the Athlons put out 3 times as much heat as the CIIs? (non-overclocked default voltage)
Do you realize than the Athlons put out 3 times as much heat as the CIIs? (non-overclocked default voltage)
3 times? Why so much? Is it to do with the number of transistors? They all use the same micron process, right?
Rigoletto
I can't remember the reference, but I do remember that one of the Athlons, Maybe a 700mhz used 47 watts while the cIIs used 15 -17 watts(533 to 600mhz???). Remember that AMD requires approved power supplies and MBs and one of their requirements is adequate power.
Someone else could probably correct my figures a little but the difference is heat produced is significant. I think that accounts for the golden Orb being quite popular and capable on the CIIs while it has been found to be somewhat inadequate on the Athlons/T-birds.
I can't remember the reference, but I do remember that one of the Athlons, Maybe a 700mhz used 47 watts while the cIIs used 15 -17 watts(533 to 600mhz???). Remember that AMD requires approved power supplies and MBs and one of their requirements is adequate power.
Someone else could probably correct my figures a little but the difference is heat produced is significant. I think that accounts for the golden Orb being quite popular and capable on the CIIs while it has been found to be somewhat inadequate on the Athlons/T-birds.
A Celly @900 really should perform better than an Athlon 600.
Taking the CPU marks of 3DMark2000 my Celly performs around an Athlon 750.
Depending on your system-config you have to be 100-150MHz over a P3/Athlon with your celly to equal the CPU performance (more or less...).
Taking the CPU marks of 3DMark2000 my Celly performs around an Athlon 750.
Depending on your system-config you have to be 100-150MHz over a P3/Athlon with your celly to equal the CPU performance (more or less...).
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 23K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter