Archived from groups: alt.comp.periphs.mainboard.asus (
More info?)
nospam@needed.com (Paul) wrote in message news:<nospam-2607041043270001@192.168.1.177>...
> In article <fe318e80.0407252008.60ac73da@posting.google.com>,
> ambini2001@yahoo.com (ambini) wrote:
>
> > just wondering how to overclock this. what do i change in the bios. my
> > ddr ram is pc2100. video card is geforce 3 ti 500. stock intel fan. is
> > this possible? TIA.
>
> CPU Speed [Manual]
> CPU External Frequency [CPU_clock/PCI_clock]
>
> You can find overclocking data here. Look up your processor in
> the Intel section:
>
>
http://cpudatabase.com/CPUdb
>
> Based on the overclock data, it looks like some users
> have managed to take their 2.2GHz/FSB400 processor to
> FSB533. This would require the [133/33] setting for
> external frequency, and is pretty ambitious (i.e. not
> likely to work).
>
> Your biggest challenge, will be the fact that the BIOS
> doesn't have the ability to change Vcore. Vcore powers
> the processor core, and to overclock, you would normally
> need a bit of a voltage boost. If the BIOS doesn't
> support voltage boost, the only other thing to try is
> modifying the VID code coming from the processor to the
> Vcore regulator. That requires some knowledge of hardware
> and electronics. If the VID code was 11010, for example,
> you can only change the logic "1" bits, to logic 0, via
> a grounding wire on that logic bit. There is no way to
> change a logic 0 to a 1, unless you cut or insulate a
> VID pin on the processor (very messy). In any case, this
> is not a procedure for newbie overclockers.
>
> You can see here:
>
>
http://processorfinder.intel.com/scripts/details.asp?sSpec=SL6PL&ProcFam=483&PkgType=ALL&SysBusSpd=ALL&CorSpd=ALL
>
> that in the example, the processor uses 1.53 volts, and yet on
> the CPUdb web page, the overclockers used 1.75 or 1.8 volts
> to reach high overclocks.
>
> Below are some sample external frequency choices. For a FSB400
> processor, the normal value is [100/33]. You can try any choice
> where the second (PCI_clock) does not exceed 37.5MHz. So, 38MHz
> PCI clock values or higher, are not recommended, as they cause
> IDE disk corruption. Without a Vcore modification, you might
> make it to 110/37 before it crashes. You cannot try 113/38, and
> the next valid speed would be 120/30, as at 120, the 1/4 divider
> cuts in, and reduces the PCI clock to a safe value.
>
> If you could modify the voltage, then you could go all the
> way to 133/33. Watch the processor temperatures while doing
> this.
>
> 100/33 114/38 128/32 142/36 156/39
> 101/34 115/38 129/32 143/36 157/39
> 102/34 116/39 130/33 144/36 158/40
> 103/34 117/39 131/33 145/36 159/40
> 104/35 118/39 132/33 146/37 160/32
> 105/35 119/40 133/33 147/37 161/32
> 106/35 120/30 134/34 148/37 162/32
> 107/36 121/30 135/34 149/37 163/33
> 108/36 122/31 136/34 150/38 164/33
> 109/36 123/31 137/34 151/38 165/33
> 110/37 124/31 138/35 152/38 166/33
> 111/37 125/31 139/35 153/38
> 112/37 126/32 140/35 154/39
> 113/38 127/32 141/35 155/39
>
> You should not be booting into Windows while overclocking. Get
> a copy of memtest86, from memtest.org. The executable contains
> a floppy disk formatter, and when used with a blank floppy
> diskette, it will make a bootable system disk for you. The
> floppy will not be readable in Windows, as it doesn't have
> a normal file system on it. Set the boot order so that the
> floppy is loaded first. Overclock the computer, then let the
> memtest floppy boot the computer. Run a couple of passes of
> memtest, before trying to boot Windows. This procedure will
> reduce the chances of corrupting your hard drive. If memtest
> is error free, then you stand a better chance of booting
> into Windows.
>
> If the computer crashes, and after resetting or powering
> down, the computer won't POST, you will need to use the
> "clear the CMOS" procedure. Unplug the computer before
> doing this procedure. Look for "Clear RTC RAM (CLRTC1)"
> in the manual. You will have to re-enter your custom
> BIOS settings after doing this.
>
> HTH,
> Paul
Whew, that was quite comprehensive and i guess i need to research more
on this. Thanks Paul,
