Re: P4P800-E: Getting Goofey After New Memory Install?



(PeteCresswell) wrote:
Old Memory: two 512-meg Crucial DDR 400

New Memory: four 1-GB Crucial DDR UNBUFF DIMM 128mx64

At initial boot with the new memory the MB issued something about
not buying the existing over clocking settings (which I never set
- I assume there was something set at the factory).

I hit F2 "To restore defaults" and it booted ok and Windows XP
Pro started up.

Ran a benchmark before/after and the numbers were slightly worse
*after*.

Then, at a subsequent Windows XP Pro startup, it began throwing a
Found New Hardware Wizard for "RAID Controller".

Anybody got an idea of what might be going on?

An "overclocking failure", is the BIOS using a flag to detect
a previous crash. When you start the computer, the BIOS at
some point is supposed to clear a flag in hardware. If, during
a subsequent POST, the flag is still set, the BIOS concludes
that the computer crashed during the previous session. The message
indicates an "overclocking failure", but in fact it can be caused
by any crash event, that prevents the flag from being cleared
before the next session. The response, when that happens, is
to *reset* all the BIOS settings to defaults. (The detection
and resetting feature is designed to help overclockers while
they are experimenting, but for the inexperienced user, the
feature tends to "shoot them in the foot". The error message
should have been changed, to indicate "some kind of crash
happened, so I'm resetting your settings".)

This was pretty annoying on my P4C800-E, because I had some
non-default settings at one time, for the disk interfaces.
For example, the Promise controller has some options that
I had to restore, every time this happens.

If the BIOS decides to reset the settings, on some occasion,
then the result can be a refusal to boot. Entering the
BIOS, and restoring the disk related settings, and the boot
order, may be all that is needed to set it right.

You can use CPUZ to verify what the BIOS settings are with
two sticks versus four sticks. If the motherboard decided to
use a different memory clock divider, for the heavier loading
case, that might be why the benchmark is different. With
FSB800, the memory can run at DDR400, DDR320, or DDR266.
CPUZ will help you verify what is going on. It could
even be, that the new memory has a higher stock CAS value.

http://www.cpuid.com/cpuz.php

Paul
.



Relevant Pages

  • Re: Memory Problem w/ASUS A7V133 MB in XP Pro - repost
    ... Yes, the first time around, and all my bios settings are correct. ... "sced13ri" wrote in message ... The problem begins when I try to upgrade the memory using 512MB ... it would not boot with one 256 + one512. ...
    (microsoft.public.windowsxp.hardware)
  • Re: P4P800se and populating all memory slots?
    ... memory manually, but it always kicked me back to 266mhz 2-2-2. ... and take me back to the bios screen). ... I'd start by looking at the SPD contents. ... If you use manual memory settings, you can override some of the ...
    (alt.comp.periphs.mainboard.asus)
  • Re: Problem reinstalling Windows - think its a hardware issue
    ... I have a Seasonic 380 watt power ... I don't know how to change my memory ... make me feel safe to change the settings. ... *promise* me you won't flash the BIOS? ...
    (microsoft.public.windowsxp.hardware)
  • Re: problems with booting fedora core 4 ...
    ... BIOS Version/Date Award Software International, Inc. 4.0h, 12.6.2005 ... Total Physical Memory 1 536,00 MB ... how to boot Fedora properly? ... This can be circumvented by creating a boot partition at the beginning ...
    (Fedora)
  • Re: Bios says PC6400 running at 5300 on a P5WD2 Premium
    ... the bios show it as PC5300. ... It says "Provided for Overclocking Purposes ... >settings other than 5-5-5 if your memory supports that. ... >how much of an impact optimizing these settings would have. ...
    (alt.comp.periphs.mainboard.asus)