Archived from groups: alt.comp.periphs.mainboard.asus (
More info?)
With BIOS 1008, I had no problem.
When I flashed the BIOS with 1010, and my computer
almost evrything went fine at first.
But the CPU speed was set at 133 by default.
When I changed it to 166 (333 MHz processor),
I got a warning "Failed because of overclock".
Rebooted, had trouble getting in the BIOS (at least nothing
would appear on the screen). After a few attempts
the BIOS display appeared, but my keyboard
wasnot working, so nothing doing. It turned out the
processor was fried. I won't try another one with
that BIOS for fear of frying another one. Guess
I will have to order a new BIOS,
Using my old mother board for the time being,
with new processor.
"Rivergoat" <goat@goathead.com> a écrit dans le message de
news:63es60h07jvn4eo53tom0fjm6iftrdchaf@4ax.com...
> What's a blue screen? Yeah, and I'm sure Bill Gates sits at his desk
> with his Macintosh laughing at us *

>
> Turns out nothing is wrong with my floppy, it was the keyboard. This
> isn't a new keyboard and the F2 button wasn't working. I brought in
> another keyboard and tested, sure enough worked fine, so I would have
> been able to get to the AWD Flash utility at POST had the key combo
> been working. Figures....
>
> Spent over an hour and a half talking to ASUS tech support today.
> Actually a good guy and quite helpful, although he didn't have any
> definite fixes to some glitches. We both sat at systems and compared
> MS Knowledgebase articles, as well as kicking around scenarios. He
> said there's not been any other reports thus far on BIOS 1010 being a
> problem. Could be I got corrupted d/l, could be vampires for all I
> know. Either way we agreed I don't really need to try it again as 1010
> is basically a memory thing, not to do with other glitches I have. He
> did say some day a whole new BIOS, not just a revision could be
> released, there are some better BIOS in use.
>
> I'm going to consume alcohol now....
>
>
>
> On Fri, 2 Apr 2004 22:10:58 +0100, "Ben Pope" <spam@hotmail.com>
> wrote:
>
> >Rivergoat wrote:
> >> Has anyone had the latest BIOS cause a blue screen crash at startup?
> >
> >Err... whats blue screening? Thats generally a Windows thing.
> >
> >> Typical crash consistent with drive not compatible with BIOS.
> >
> >Drive incompatibilities should be pretty rare, and a failed drive should
not
> >crash the BIOS under any circumstances.
> >
> >> One
> >> shouldn't have to reformat a drive just to update BIOS, cripes, I
> >> never had to in the past!
> >
> >Whats wrong with your floppy? (oo-err..
😛)
> >
> >Ben
>