Mobo and video card capatibility question

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
I've just completed my first pc build and have run into one error.
During boot up, I get an error that says "Intel CPU uCode Loading
error". I then have to hit F1 to continue. It hasn't seemed to cause any
operational problems. I'm able to run anything I want so far. I can even
go into the BIOS to set to ignore this error and continue with startup.
I'm just curious as to what this means, and will it affect something
later on. Here's my computer components:

Video card - EVGA GeForce 8800GTS
Mobo - ASUS P5B Deluxe
CPU - Intel Core 2 Duo E6750
Hard drive - Western Digital Caviar SE16 500GB 7200 RPM
Memory - Crucial Ballistix 2GB (2x1GB) DDR2 800
Power Supply - Antec NeoPower 650W
Operating System - Windows Vista Home Premium

I still haven't loaded any BIOS updates for my motherboards. Also
another person on a forum said he's surprised the mobo worked with that
video card, because "Your motherboard only supports a maximum of 1066
mhz FSB, and the E6750 uses 1333 mhz FSB, so it can't utilise the extra
speed, i am surprised its even working because some computers don't."
Is this an accurate statement?
Thanks for any help.

Tricia in TX

Re: Mobo and video card capatibility question

Quoted text here. Click to load it
It appears you should try for a BIOS update.

Re: Mobo and video card capatibility question

A&T wrote:
Quoted text here. Click to load it

The following page tells you your E6750 is supported with BIOS 1215. That
means your nominal FSB1066 Northbridge is capable of running at FSB1333. The new
BIOS may well include fresh microcode, for that family code/stepping of
(Note - not all chipsets can do this - some that run at FSB1066 really
cannot go any faster, and a BIOS upgrade won't magically make a FSB1333
processor work well. You got lucky :-) )

The BIOS file has microcode for various Intel processors stored in it.
At start up, the BIOS attempts to find a microcode (2KB or a multiple
of that size) and load it into the processor. The processor has a small
RAM that holds the patch. The patch area is used to correct errors in the
processor, and when a brand new processor ships, from day one it will
have microcode to correct known errors. Over the life of
the processor, more errors will be found. Many errors are not
critical, and are only found in artificial instruction sequences
(sequences that a compiler would not normally generate).

To give an example, the microcode patch for the Intel P4 on
my motherboard, is at revision 17 or so. That means Intel has released
that many versions of the microcode patch, to correct errors that
it felt needed to be corrected. If I download and flash upgrade
a later BIOS, I may get an even later version of microcode patch
for the processor.

Generally speaking, for people who experience a problem with
loading a microcode patch (either at the BIOS level, or with
the Microsoft WinXP microcode updater update.sys), they don't
seem to "crash and burn" because of it. But that doesn't mean
it couldn't happen. A BIOS update should fix it all for you.

This is another way that a microcode patch can be distributed.
When Microsoft issues one, it is serious. And since this one
is downloaded with your Windows Update, chances are it will be
available to you, three months before Asus puts that microcode
into a new BIOS file. WinXP has a microcode loader, and if the
BIOS doesn't patch the processor, Windows can. The only
exposure when WinXP patches a broken processor, is if there is
a problem in the boot sequence. The computer has to be able
to boot, to be able to run the Windows update, and the computer
could crash before it got a chance to run the microcode update
at the Windows level. So if a problem happened during the boot
up, the Microsoft way of fixing it would not work. In your
case, you want the BIOS update, mainly for general compatibility
with the FSB1333 processors, and the new microcode you get, is
for free.


Site Timeline