Inexplicable "overclocking failed" message

G

Guest

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

So I upgraded my A7V+AthlonXP to a K8V+Athlon64 last week.

I am having some extremely strange problems.

Problem #1:

While a cold boot succeeds, a reboot after a successful boot (whether
initiated in software or using the reset button) results in a
long-short-short beep code which if I recall correctly should be a video
error, and nothing appears on screen. The only way to get it to reboot at
this point is to switch the power supply off and on again. This boot
succeeds. But another subsequent reboot and it's back to a blank screen
with a long-short-short beep code (though HDs seem to be spinning up
successfully). I've tried two different video cards and insured that the
first, a Radeon 9700 Pro, had its PSU connector successfully seated (the
latter, a Geforce 4 4200, requires no PSU power) and both produce identical
results.

Then more weirdness proceeds:

After powering off the PSU and booting, I will receive an "overclocking
failed" error message. I have not overclocked the system and have gone to
great pains to make sure CPU temperature and case temperature are ideal
(this is a very well cooled system). The BIOS reports the CPU as
automatically clocking itself at 1800MHz, which is correct, being an Athlon
64 2800+. I have subsequently tried manually setting the memory clock, with
exactly the same results. Same problems.

I have tried four different DIMMs (paired as well as single) in the
following configurations:

2x512MB DDR400 DIMMs
1x512MB DDR400 DIMMs
2x512MB DDR266 DIMMs
1x512MB DDR266 DIMMs

And no dice. I have also run exhaustive Memtest86 tests on both pairs and
they produce no errors. The DDR 266 pair has functioned perfectly well on
my A7V for the last year. The DDR400 pair is new.

That's Problem #1

_____________________

Problem #2:

On a successful cold boot, installation of WinXP fails miserably. No matter
what drive it's installing from (I've tried straight from HD as well as from
two different CD drives) or installing to (tried two different HDs), it
can't find many of the files on disk (files which I have verified are there
on the drive on separate boots and perfectly readable on another computer)
and fails to install successfully.

The weird thing is, it always can't find the SAME files, the first of which
is tahoma.ttf, even though they're on a hard drive and accessible or on an
equally accessible CD, and no matter which drive they're installing from. I
can conceive of no rational explanation for how this can be. I think I'm
living in an alternate universe.

That's Problem #2.

Sheesh.

Any thoughts?
 

Paul

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

In article <1q9Zc.3877$RP5.813@fe51.usenetserver.com>, "Jurgen Chiang"
<screwballicus@hotmail.com> wrote:

> So I upgraded my A7V+AthlonXP to a K8V+Athlon64 last week.
>
> I am having some extremely strange problems.
>
> Problem #1:
>
> While a cold boot succeeds, a reboot after a successful boot (whether
> initiated in software or using the reset button) results in a
> long-short-short beep code which if I recall correctly should be a video
> error, and nothing appears on screen. The only way to get it to reboot at
> this point is to switch the power supply off and on again. This boot
> succeeds. But another subsequent reboot and it's back to a blank screen
> with a long-short-short beep code (though HDs seem to be spinning up
> successfully). I've tried two different video cards and insured that the
> first, a Radeon 9700 Pro, had its PSU connector successfully seated (the
> latter, a Geforce 4 4200, requires no PSU power) and both produce identical
> results.
>
> Then more weirdness proceeds:
>
> After powering off the PSU and booting, I will receive an "overclocking
> failed" error message. I have not overclocked the system and have gone to
> great pains to make sure CPU temperature and case temperature are ideal
> (this is a very well cooled system). The BIOS reports the CPU as
> automatically clocking itself at 1800MHz, which is correct, being an Athlon
> 64 2800+. I have subsequently tried manually setting the memory clock, with
> exactly the same results. Same problems.
>
> I have tried four different DIMMs (paired as well as single) in the
> following configurations:
>
> 2x512MB DDR400 DIMMs
> 1x512MB DDR400 DIMMs
> 2x512MB DDR266 DIMMs
> 1x512MB DDR266 DIMMs
>
> And no dice. I have also run exhaustive Memtest86 tests on both pairs and
> they produce no errors. The DDR 266 pair has functioned perfectly well on
> my A7V for the last year. The DDR400 pair is new.
>
> That's Problem #1
>
> _____________________
>
> Problem #2:
>
> On a successful cold boot, installation of WinXP fails miserably. No matter
> what drive it's installing from (I've tried straight from HD as well as from
> two different CD drives) or installing to (tried two different HDs), it
> can't find many of the files on disk (files which I have verified are there
> on the drive on separate boots and perfectly readable on another computer)
> and fails to install successfully.
>
> The weird thing is, it always can't find the SAME files, the first of which
> is tahoma.ttf, even though they're on a hard drive and accessible or on an
> equally accessible CD, and no matter which drive they're installing from. I
> can conceive of no rational explanation for how this can be. I think I'm
> living in an alternate universe.
>
> That's Problem #2.
>
> Sheesh.
>
> Any thoughts?

Well, when we haven't a clue what is wrong, we blame it on the
power supply :)

Does the new system have a power supply with the 2x2 +12V connector
on it ? Does the supply have a decent rating, and give good readings
in the BIOS hardware monitor (+3.3, +5.0, +12.0V within 5% of
their normal value) ?

The "overclocking failed" could be a trick of the BIOS. There must
be a flag somewhere that the BIOS uses to detect whether the last
attempt to boot got past a certain point or not. If the flag is not
set, when the board comes back up, it sees that the last time the system
was powered, the boot sequence didn't run to completion. So, don't
assume an overclocking failed message has anything to do with
overclocking - similarly, if you get a message about the BIOS
being corrupted, that can be caused by the clock to the parts
controlling the reading of the BIOS are running too fast, so
the access time for the flash chip is not being met. On my
P4C800-E, a "corrupt BIOS" message can be cleared by clearing
the CMOS, which returns the clock settings to defaults. There is
no need to try re-flashing the BIOS to fix that. If the "corrupt
BIOS" message continued to come up on the screen, only then would
I consider fixing it by flashing.

Also, I checked here, and the 2800+ on a K8V required BIOS 1003 or
later. What version of BIOS are you running ?

http://www.asus.com.tw/support/cpusupport/cpusupport.aspx

HTH,
Paul
 
G

Guest

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

I had the same problem on my ASUS P5AD2 Premium motherboard. In my
BIOS I have something called "AI Overclocking and Performance mode"; I
set both of them to "Standard" and had no problem ever since.

I'm not sure if you have the exact same option; if you have something
overclock. Try setting it to standard or to a lower value. Don't use
the auto setting.

My comp spec:
Motherboard: ASUS P5AD2 Premium
CPU: 3.2Ghz 1MB L2 Cache /w HT
Hard Drive: Western Digital SATA 10-K RPM /w WinXP Pro
Memory: OCZ Enhanced Bandwidth 1GB dual channel (4-3-3-12)
Video Card: ASUS AX800 XT PE PCI Express (free webcam YAY!)
And a bunch of fans to cool it down.
 
G

Guest

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

Good call. PSU is probably the issue indeed. It's a 450W Enermax, but I
have six hard drives, two CD drives and a high power consumption vid card,
so that's probably putting it over the top.

My theory for why a soft restart results in a video error and "overclocking
failed" (both potentially power related) but a cold boot doesn't is that
given that on a soft restart I have seven drives spun up and consuming power
already at POST, the board's just not drawing enough power to POST on a
restart. Just a theory, but seeing as nothing else makes sense, it's the
best I've got.

- JC

"Paul" <nospam@needed.com> wrote in message
news:nospam-0109040344420001@192.168.1.177...
> In article <1q9Zc.3877$RP5.813@fe51.usenetserver.com>, "Jurgen Chiang"
> <screwballicus@hotmail.com> wrote:
>
> > So I upgraded my A7V+AthlonXP to a K8V+Athlon64 last week.
> >
> > I am having some extremely strange problems.
> >
> > Problem #1:
> >
> > While a cold boot succeeds, a reboot after a successful boot (whether
> > initiated in software or using the reset button) results in a
> > long-short-short beep code which if I recall correctly should be a video
> > error, and nothing appears on screen. The only way to get it to reboot
at
> > this point is to switch the power supply off and on again. This boot
> > succeeds. But another subsequent reboot and it's back to a blank screen
> > with a long-short-short beep code (though HDs seem to be spinning up
> > successfully). I've tried two different video cards and insured that
the
> > first, a Radeon 9700 Pro, had its PSU connector successfully seated (the
> > latter, a Geforce 4 4200, requires no PSU power) and both produce
identical
> > results.
> >
> > Then more weirdness proceeds:
> >
> > After powering off the PSU and booting, I will receive an "overclocking
> > failed" error message. I have not overclocked the system and have gone
to
> > great pains to make sure CPU temperature and case temperature are ideal
> > (this is a very well cooled system). The BIOS reports the CPU as
> > automatically clocking itself at 1800MHz, which is correct, being an
Athlon
> > 64 2800+. I have subsequently tried manually setting the memory clock,
with
> > exactly the same results. Same problems.
> >
> > I have tried four different DIMMs (paired as well as single) in the
> > following configurations:
> >
> > 2x512MB DDR400 DIMMs
> > 1x512MB DDR400 DIMMs
> > 2x512MB DDR266 DIMMs
> > 1x512MB DDR266 DIMMs
> >
> > And no dice. I have also run exhaustive Memtest86 tests on both pairs
and
> > they produce no errors. The DDR 266 pair has functioned perfectly well
on
> > my A7V for the last year. The DDR400 pair is new.
> >
> > That's Problem #1
> >
> > _____________________
> >
> > Problem #2:
> >
> > On a successful cold boot, installation of WinXP fails miserably. No
matter
> > what drive it's installing from (I've tried straight from HD as well as
from
> > two different CD drives) or installing to (tried two different HDs), it
> > can't find many of the files on disk (files which I have verified are
there
> > on the drive on separate boots and perfectly readable on another
computer)
> > and fails to install successfully.
> >
> > The weird thing is, it always can't find the SAME files, the first of
which
> > is tahoma.ttf, even though they're on a hard drive and accessible or on
an
> > equally accessible CD, and no matter which drive they're installing
from. I
> > can conceive of no rational explanation for how this can be. I think
I'm
> > living in an alternate universe.
> >
> > That's Problem #2.
> >
> > Sheesh.
> >
> > Any thoughts?
>
> Well, when we haven't a clue what is wrong, we blame it on the
> power supply :)
>
> Does the new system have a power supply with the 2x2 +12V connector
> on it ? Does the supply have a decent rating, and give good readings
> in the BIOS hardware monitor (+3.3, +5.0, +12.0V within 5% of
> their normal value) ?
>
> The "overclocking failed" could be a trick of the BIOS. There must
> be a flag somewhere that the BIOS uses to detect whether the last
> attempt to boot got past a certain point or not. If the flag is not
> set, when the board comes back up, it sees that the last time the system
> was powered, the boot sequence didn't run to completion. So, don't
> assume an overclocking failed message has anything to do with
> overclocking - similarly, if you get a message about the BIOS
> being corrupted, that can be caused by the clock to the parts
> controlling the reading of the BIOS are running too fast, so
> the access time for the flash chip is not being met. On my
> P4C800-E, a "corrupt BIOS" message can be cleared by clearing
> the CMOS, which returns the clock settings to defaults. There is
> no need to try re-flashing the BIOS to fix that. If the "corrupt
> BIOS" message continued to come up on the screen, only then would
> I consider fixing it by flashing.
>
> Also, I checked here, and the 2800+ on a K8V required BIOS 1003 or
> later. What version of BIOS are you running ?
>
> http://www.asus.com.tw/support/cpusupport/cpusupport.aspx
>
> HTH,
> Paul
 
G

Guest

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

Perhaps Power Supply?? Had similar Probs with another M/B A7N8X-X
turned out to be the power supply, replaced that and no probs. Worth a
try.
 
G

Guest

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

I had the same "overclocking failed" message, twice,
after I made some changes in the BIOS that had nothing
to do with overclocking. It hasn't happened again.



my system:

Windows 2000 Professional w/ service pack 3
ASUS P4P800-E DELUXE mainboard
P4 2.8EGHz
1GB Geil Dual Channel PC3200
Thermaltake 420 watt psu
WD 80 GB hard drive
ATI 7200 LE 32MB video card
+

Johnny Asia, Guitarist from the Future
http://johnnyasia.info