asus P4C800e deluxe new cpu installed

[kLoBy]

Hi,


Well problem is that every boot time i got mesage new CPU installed
run bios to setup ? Then I must go to bios and exit from bios and
everything goes as normal..

I didnt install new cpu ?!

bios ver. that I put now is new one 1023, same thing, I even clear
cmos but nothing. Old bios was 1019 beta..

anyone know solution ?

thnx

 

[GinTonix]

Hi,


Well problem is that every boot time i got mesage new CPU installed
run bios to setup ? Then I must go to bios and exit from bios and
everything goes as normal..

I didnt install new cpu ?!

Check the bios battery. Sometimes, when its lifespan is near to its end,
it could be manifested like this. No specific experience on Asus boards,
but an Intel one used to do this, i.e. no other settings lost but the
CPU info.

bios ver. that I put now is new one 1023, same thing, I even clear
cmos but nothing. Old bios was 1019 beta..

anyone know solution ?

Report if this helped, as I have a similar mobo in the closet waiting
for components and I'd like to know solutions to some (common?) problems
already before I meet them

 

[Paul]

Hi,


Well problem is that every boot time i got mesage new CPU installed
run bios to setup ? Then I must go to bios and exit from bios and
everything goes as normal..

I didnt install new cpu ?!

bios ver. that I put now is new one 1023, same thing, I even clear
cmos but nothing. Old bios was 1019 beta..

anyone know solution ?

thnx

The flash BIOS chip contains more than a simple BIOS program.

It contains at least:

1) Boot block - simple bootstrap loader to configure basic hardware.
2) Main BIOS - takes over after boot block has checksummed the Main
BIOS code.
3) DMI segment
4) ESCD segment - these two segments hold info about what hardware
was present, the last time the computer POSTed.
5) Microcode cache - AFAIK, used for Intel processors. A small cache
in the small KB in size. Contains a copy of the
microcode patch loaded into the processor by the
BIOS. In some cases, can be manually loaded with
CTMC.

DMI/ESCD info seems to be used by large companies for keeping an
inventory of what hardware is connected to the computer. Tools
like "DMI Explorer" can be used to read the info - although
whether this feature is still supported properly by anyone,
is unclear. I think I've seen Asus Probe mentioned as having
a DMI tab in the interface.

It is possible the BIOS doesn't completely support the processor
being used. If the BIOS cannot update the DMI correctly, then each
time it starts, it detects a mismatch between what was written into
DMI the last time, and what CPU it thinks it has got this time.
That could cause the behavior you are seeing.

Possible reasons for this are:

1) BIOS bug. Try another BIOS version.
2) Flash chip is damaged or the area where DMI/ESCD is written,
is locked and cannot be updated.

While the CMOS could be a contributor, I doubt there is room
in there to record much in the way of inventory info.

What exact processor is this ? Do you have an order code or
SSPEC (Slxxx) code ? Have you used CPUID or Everest or the
like, to see what kind of processor is claimed to be present ?

Paul

 

[kLoBy]

Check the bios battery. Sometimes, when its lifespan is near to its end,
it could be manifested like this. No specific experience on Asus boards,
but an Intel one used to do this, i.e. no other settings lost but the
CPU info.

I tried another battery but nothing..

 

[kLoBy]

The flash BIOS chip contains more than a simple BIOS program.

It contains at least:

1) Boot block - simple bootstrap loader to configure basic hardware.
2) Main BIOS - takes over after boot block has checksummed the Main
BIOS code.
3) DMI segment
4) ESCD segment - these two segments hold info about what hardware
was present, the last time the computer POSTed.
5) Microcode cache - AFAIK, used for Intel processors. A small cache
in the small KB in size. Contains a copy of the
microcode patch loaded into the processor by the
BIOS. In some cases, can be manually loaded with
CTMC.

DMI/ESCD info seems to be used by large companies for keeping an
inventory of what hardware is connected to the computer. Tools
like "DMI Explorer" can be used to read the info - although
whether this feature is still supported properly by anyone,
is unclear. I think I've seen Asus Probe mentioned as having
a DMI tab in the interface.

It is possible the BIOS doesn't completely support the processor
being used. If the BIOS cannot update the DMI correctly, then each
time it starts, it detects a mismatch between what was written into
DMI the last time, and what CPU it thinks it has got this time.
That could cause the behavior you are seeing.

Possible reasons for this are:

1) BIOS bug. Try another BIOS version.
2) Flash chip is damaged or the area where DMI/ESCD is written,
is locked and cannot be updated.

While the CMOS could be a contributor, I doubt there is room
in there to record much in the way of inventory info.

What exact processor is this ? Do you have an order code or
SSPEC (Slxxx) code ? Have you used CPUID or Everest or the
like, to see what kind of processor is claimed to be present ?

Paul

first thnx for the info.

My CPU is intel P4 2.4C model. see attachment

 

[kLoBy]

The flash BIOS chip contains more than a simple BIOS program.

It contains at least:

1) Boot block - simple bootstrap loader to configure basic hardware.
2) Main BIOS - takes over after boot block has checksummed the Main
BIOS code.
3) DMI segment
4) ESCD segment - these two segments hold info about what hardware
was present, the last time the computer POSTed.
5) Microcode cache - AFAIK, used for Intel processors. A small cache
in the small KB in size. Contains a copy of the
microcode patch loaded into the processor by the
BIOS. In some cases, can be manually loaded with
CTMC.

DMI/ESCD info seems to be used by large companies for keeping an
inventory of what hardware is connected to the computer. Tools
like "DMI Explorer" can be used to read the info - although
whether this feature is still supported properly by anyone,
is unclear. I think I've seen Asus Probe mentioned as having
a DMI tab in the interface.

It is possible the BIOS doesn't completely support the processor
being used. If the BIOS cannot update the DMI correctly, then each
time it starts, it detects a mismatch between what was written into
DMI the last time, and what CPU it thinks it has got this time.
That could cause the behavior you are seeing.

Possible reasons for this are:

1) BIOS bug. Try another BIOS version.
2) Flash chip is damaged or the area where DMI/ESCD is written,
is locked and cannot be updated.

While the CMOS could be a contributor, I doubt there is room
in there to record much in the way of inventory info.

What exact processor is this ? Do you have an order code or
SSPEC (Slxxx) code ? Have you used CPUID or Everest or the
like, to see what kind of processor is claimed to be present ?

Paul

Intel(R) Processor Identification Utility
Version: 2.5.20050912
Time Stamp: 2005/10/26 16:43:18
Number of processors in system: 1
Current processor: #1
Processor Name: Intel(R) Pentium(R) 4 CPU 2.40C GHz
Type: 0
Family: F
Model: 2
Stepping: 9
Revision: 2E
L1 Trace Cache: 12 Kµops
L1 Data Cache: 8 KB
L2 Cache: 512 KB
Packaging: FC-PGA2
EIST: No
MMX(TM): Yes
SIMD: Yes
SIMD2: Yes
SIMD3: No
Enhanced Halt State: No
Execute Disable Bit: No
Hyper-Threading Technology: Yes
Intel(R) Extended Memory 64 Technology: No
Expected Processor Frequency: 2.40 GHz
Reported Processor Frequency: 2.40 GHz
Expected System Bus Frequency: 800 MHz
Reported System Bus Frequency: 800 MHz

 

[Paul]

Intel(R) Processor Identification Utility
Version: 2.5.20050912
Time Stamp: 2005/10/26 16:43:18
Number of processors in system: 1
Current processor: #1
Processor Name: Intel(R) Pentium(R) 4 CPU 2.40C GHz
Type: 0
Family: F
Model: 2
Stepping: 9
Revision: 2E
L1 Trace Cache: 12 Kµops
L1 Data Cache: 8 KB
L2 Cache: 512 KB
Packaging: FC-PGA2
EIST: No
MMX(TM): Yes
SIMD: Yes
SIMD2: Yes
SIMD3: No
Enhanced Halt State: No
Execute Disable Bit: No
Hyper-Threading Technology: Yes
Intel(R) Extended Memory 64 Technology: No
Expected Processor Frequency: 2.40 GHz
Reported Processor Frequency: 2.40 GHz
Expected System Bus Frequency: 800 MHz
Reported System Bus Frequency: 800 MHz

That is a Northwood 2.4C/FSB800/512KB cache. Nothing unusual
about that. The microcode revision indicates you are using
BIOS 1018 or later. (Since 1017 is missing from my collection,
I don't know whether it had 0F29 rev 2E in it or not.) Even the
latest 1024 BIOS still has microcode 2E revision. In fact,
I have a Northwood 2.8C in my P4C800-E, and have never had
the problem you are describing.

About all I can suggest, is flashing the BIOS. Flashing the
BIOS is never without risk, so only consider flashing the
BIOS, if the benefit of fixing this problem outweighs
the risk of not being able to boot the computer. If you
have already succeeded in upgrading the flash on this
computer before, then go right ahead. What should happen,
is the DMI/ESCD from the flash file, should overwrite what
is already in the flash chip, and perhaps that will fix it.

As I mentioned before, I don't think the CMOS has room to
record this kind of info, and DMI/ESCD is the only other
area I know of.

Paul