Home

News

Forums

Hardware

CPUs

Mainboards

Video

Guides

CPU Prices

Memory Prices

Shop



Sharky Extreme : December 5, 2008





Regular Sections

- Weekly CPU Prices
- Weekly Memory Prices
- PC Buyer's Guides
- Private Eye
- Forums Spotlight
- The Rear View
- The Silicon Money Pit
- SharkyForums
- Site Info
- Links
- About Us


After mounting the Glaciers onto the Celeron(tm) 400s, we went through our usual overclocking regimen when testing new CPUs: All BIOS settings set to their least dangerous/intrusive, all peripherals save for the video card removed, ambient temperature of the room the machines are in lowered to 64 degrees F, complete removal of the case covers, and finally, the placement of three 8cm high capacity fans within each PC's case.

These aren't normal measures, and to be clear, the benchmarks we obtained for this article at 498MHz with the Celeron(tm) 400 were achieved with just the Glacier 4500C in a normal 72 degree F environment.

Considering all of the precautions we follow, and the extreme cooling methods we employ, you'd figure that overclocking the two retail boxed Celeron(tm) 400s would have been pain-free and relatively easy. It was....to a point. With both of the Celeron(tm) 400 CPUs we tested, neither would come even close to correctly booting into Win95 OSR 2.1 when set to the 6.0 x 100MHz frequency. Even with the Abit BH6's voltage set to a mind-bending 2.6 volts, our Celeron(tm) 400s failed miserably when asked to hit 600MHz. Cooling and voltage didn't seem to be the problems in oursituation, as the CPU and system temperatures were far below the levels that we've seen reliably overclocked systems run at. Disabling the CPUs L2 cache helped the machines boot further into Win95, but ultimately failed before even the desktop would appear.

next page




"our Celeron(tm) 400s failed miserably when asked to hit 600MHz"

Copyright © 2001 INT Media Group, Incorporated. All Rights Reserved. Legal Notices | Licensing , Reprints , & Permissions | Privacy Policy