It is simple. download the latest BIOS from http://support.asus.com/download/Dow...Language=en-us
for your specific Motherboard. copy it to a floppy or CD.
Insert CD/floppy and start the computer.
Press ALT + F2 at booting and relax. the ezflash program on the ROM does everything for you.
I am using P5GPL-x Asus mainboard.
At first I used CPU pentium iV 2.8GHZ, when I boot up system, an error message "CPU ucode loading erros" appeared , ...press F1 to continue... When I pressed F1, system boot up normally.
After that I upgrade newest bios from ASUS web site ( 0407 version), , I've resolved problem with pentium iv 2.8GHZ
But when I've changed other CPU - Pentium IV - 3.0 , that error appear again, then to continue boot up system, I had to press F1.
No new Bios version higher until now than 0704 version.
But when looking in the Bios configure menu, , under Boot menu when I change "wait for F1 if error" menu from Enable to Disable, I still see CPU ucode loading erros message, but I don't have to press F1 again.
So if you don't want press F1 when Switch power on, just try disable this menu.
Hope this help.
I also have a problem.. same as Intel CPU uCode Loading Error,
I have this specs Motherboard: P5VD2-VM SE
Processor: Intel Dual Core E2160, LGA775
1.80 GHz, 1MB L2 Cache, 800 MHz-FSB
Memory: Kingston 512 DDR2
Harddisk: 80 GB SATA Seagate
I am trying to install windows XP sp2, but this error appears after post.
I am using the built in vga board. It's strange that after booting from the cd.. then windows setup starting.. it then appears a blue screen and it tells me to try to use other video adapters or update my bios.. what should i do? i dont want to update the bios since it was risky thing. appreciate your help sir.. thanks
Thanks for posting the solution to this problem. I just purchased 2 ASUS 5PL2D SE motherboards (one to use and one as a spare) These are for direct replacement in a business critical computer and I wanted to replace with the exact motherboard. Upon installing the uCode error came up. Upgrading to the latest BIOS made the problem go away.