ASUS Update -> Boot disk failure

G

Guest

Guest
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Hello!

I have an ASUS A7V8X-X motherboard and I have updated ASUS in order to get a
higher CPU frequency to set for my CPU (My CPU is clocked with 2400 MHZ, my
BIOS only let me set at maximum 2100 MHZ).

After the update, booting is not possible anymore. I always get the error
message "Boot disk failure". I'm able to boot from CD-Rom, but my harddisk
seems not to be detected.

What could be the problem?

Regards,
Robert
 

Paul

Splendid
Mar 30, 2004
5,267
0
25,780
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

In article <eqoqd.53104$ha.37981@news.chello.at>, "Robert Wehofer"
<thalion77@graffiti.net> wrote:

> Hello!
>
> I have an ASUS A7V8X-X motherboard and I have updated ASUS in order to get a
> higher CPU frequency to set for my CPU (My CPU is clocked with 2400 MHZ, my
> BIOS only let me set at maximum 2100 MHZ).
>
> After the update, booting is not possible anymore. I always get the error
> message "Boot disk failure". I'm able to boot from CD-Rom, but my harddisk
> seems not to be detected.
>
> What could be the problem?
>
> Regards,
> Robert

First of all, the core frequency is not the same thing as the
AMD P.R. (performance rating).

The "CPU Clock" times the Multiplier value, gives the Core
Frequency. The P.R. rating is how fast an equivalent Intel
Pentium would need to run, to give the same performance as
the AMD. Running at 2400MHz is an overclock higher than
anything in this table. 2400MHz is not the same thing as
2400+ .

Family Core P.R. Pkg CPU Cache Mult Core Tmax Power
Freq Clk Volts

XP Model 10 2200 (3200+) OPGA 200 512 11x 1.65V 85oC 60.4W
Barton 2100 (3000+) OPGA 200 512 10.5x 1.65V 85oC 53.7W

XP Model 10 2167 (3000+) OPGA 166 512 13x 1.65V 85oC 58.4W
Barton 2083 (2800+) OPGA 166 512 12.5x 1.65V 85oC 53.7W
1917 (2600+) OPGA 166 512 11.5x 1.65V 85oC 53.7W
1833 (2500+) OPGA 166 512 11x 1.65V 85oC 53.7W

XP Model 8 2167 (2700+) OPGA 166 256 13x 1.65V 85oC 62.0W
Thoroughbred 2083 (2600+) OPGA 166 256 12.5x 1.65V 85oC 62.0W

XP Model 8 2133 (2600+) OPGA 133 256 16x 1.65V 85oC 62.0W
Thoroughbred 2000 (2400+) OPGA 133 256 15x 1.65V 85oC 62.0W
CPU ID 0681 1800 (2200+) OPGA 133 256 13.5x 1.60V 85oC 57.0W
1733 (2100+) OPGA 133 256 13x 1.60V 90oC 56.3W
1667 (2000+) OPGA 133 256 12.5x 1.60V 90oC 55.7W
1533 (1800+) OPGA 133 256 11.5x 1.60V 90oC 55.7W
1467 (1700+) OPGA 133 256 11x 1.60V 90oC 55.7W

XP Model 8 1800 (2200+) OPGA 133 256 13.5x 1.65V 85oC 61.7W
Thoroughbred 1733 (2100+) OPGA 133 256 13x 1.60V 90oC 56.4W
CPU ID 0680 1667 (2000+) OPGA 133 256 12.5x 1.65V 90oC 54.7W
1667 (2000+) OPGA 133 256 12.5x 1.60V 90oC 54.7W
1600 (1900+) OPGA 133 256 12x 1.50V 90oC 47.7W
1533 (1800+) OPGA 133 256 11.5x 1.50V 90oC 46.3W
1467 (1700+) OPGA 133 256 11x 1.50V 90oC 44.9W

XP Model 6 1733 (2100+) OPGA 133 256 13x 1.75V 90oC 64.3W
Palomino 1667 (2000+) OPGA 133 256 12.5x 1.75V 90oC 62.5W
1600 (1900+) OPGA 133 256 12x 1.75V 90oC 60.7W
1533 (1800+) OPGA 133 256 11.5x 1.75V 90oC 59.2W
1467 (1700+) OPGA 133 256 11x 1.75V 90oC 57.4W
1400 (1600+) OPGA 133 256 10.5x 1.75V 90oC 56.3W
1333 (1500+) OPGA 133 256 10x 1.75V 90oC 53.8W

Notice in the clock menu, how there are two numbers, like "100/33".
The first number is the front side bus clock ("CPU clk"), and
100 ==> FSB200 while 200 ==> FSB400. The second number, the 33,
is the PCI clock. You can have problems reading from an IDE disk,
if the second number is higher than 37.5MHz. Operating the disk
while the clock is higher than 37.5MHz can even result in corrupting
the disk, such that it won't boot. (This is why motherboards
with a "clock lock" are prized, because they keep the PCI and
AGP bus at their normal 33 and 66MHz frequencies, no matter
how the bus clock is set. Older motherboards use an integer
divider between the bus clock and the PCI and AGP clocks, and
some BIOS clock settings are not recommended while running an
IDE disk.)

To start with, return the bus clock to a safe number like 100/33.
Then see if the computer can boot. If it cannot, you may need
to restore the disk from a backup. It could be that all that
is wrong, is something with the MBR. (I'm no disk expert and
don't know how to fix broken disks.)

HTH,
Paul