Microcode update

hi all help needed please,
have hp small form factor dc 7600 and on start up i have the ollowing message
1801 microcode update error missing or invalid processor microcode update
any ideas?

DANIEL442
If you could please post your product number for your computer. I am linking a document below that will show you how to find your product number. As well if you could indicate which operating system you want change to whether or not it is 32-bit or 64-bit as with this and the product number we can provide you with accurate information.
How Do I Find My Model Number or Product Number?
http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c00033108
Please feel free to re-post once you have the required information.
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
Dunidar
I work on behalf of HP
Find out a bit more about me by checking out my profile!
"Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

Similar Messages

How to fix "1801-Microcode Update Error" in HP Compaq dc7800 Convertible Minitower

I have Intel Core 2 Duo @ 2.93 Ghz. My operating system is Windows 7 Ultimate x64.
This question was solved.
View Solution.

Hi:
The E7500 processor is not supported in the dc7800, which is why you are getting the microcode error.
Below is the list of supported processors.
Intel Core 2 Duo Processors:
Intel Core 2 Duo E4500 Processor (2.20-GHz, 2 MB L2 cache, 800-MHz FSB)
Intel Core 2 Duo E4600 Processor (2.40-GHz, 2 MB L2 cache, 800-MHz FSB)
Intel Core 2 Duo E4700 Processor (2.6-GHz, 2 MB L2 cache, 800-MHz FSB)
Intel Core 2 Duo E6550 Processor (2.33-GHz, 4 MB L2 cache, 1333-MHz FSB)
Intel Core 2 Duo E6750 Processor (2.66-GHz, 4 MB L2 cache, 1333-MHz FSB)
Intel Core 2 Duo E6850 Processor (3.0-GHz, 4 MB L2 cache, 1333-MHz FSB)
Intel Core 2 Duo E7200 Processor (2.53 GHz, 3 MB L2 cache, 1066 MHz FSB)
Intel Core 2 Duo E7300 Processor (2.66 GHz, 3MB L2 cache, 1066 MHz FSB)
Intel Core 2 Duo E8200 Processor (2.66-GHz, 6 MB L2 cache, 1333-MHz FSB)
Intel Core 2 Duo E8300 Processor (2.83-GHz, 6 MB L2 cache, 1333-MHz FSB)
Intel Core 2 Duo E8400 Processor (3.00-GHz, 6 MB L2 cache, 1333-MHz FSB)
Intel Core 2 Duo E8500 Processor (3.16-GHz, 6 MB L2 cache, 1333-MHz FSB)
Inter Core 2 Duo E8600 Processor (3.33-GHz, 6 MB L2 Cache, 1333-MHz FSB)
As a long shot, you can try installing the latest microcode update. You need to use a bootable USB flash drive with dos files so you can run the flashbin.exe command after you copy the microcode update files to your bootable flash drive.
I can't get to the dc7800 support site. When you can, select the microcode update download from 2010 v1.14
If you are unfamiliar with how to make a flash drive bootable, here is a good "how to" article with the files you need.
http://www.techpowerup.com/forums/showthread.php?t=47812
Paul

[SOLVED] AMD Microcode update failed (on Xen host)

I have an Arch system running as a VM Host based on Xen 4.4.1
It is yet unclear to me why the VMHost (Dom0) cannot update the CPU microcode of the AMD Opteron 3365.
The following errors appear.
[ 9.664531] microcode: CPU0: patch_level=0x0600081c
[ 9.664548] microcode: CPU1: patch_level=0x0600081c
[ 9.664566] microcode: CPU2: patch_level=0x0600081c
[ 9.664580] microcode: CPU3: patch_level=0x0600081c
[ 9.664593] microcode: CPU4: patch_level=0x0600081c
[ 9.664607] microcode: CPU5: patch_level=0x0600081c
[ 9.664624] microcode: CPU6: patch_level=0x0600081c
[ 9.664639] microcode: CPU7: patch_level=0x0600081c
[ 9.664723] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
[ 18.344286] microcode: CPU0: update failed for patch_level=0x06000832
[ 18.345579] microcode: CPU1: update failed for patch_level=0x06000832
[ 18.346899] microcode: CPU2: update failed for patch_level=0x06000832
[ 18.348202] microcode: CPU3: update failed for patch_level=0x06000832
[ 18.349488] microcode: CPU4: update failed for patch_level=0x06000832
[ 18.350776] microcode: CPU5: update failed for patch_level=0x06000832
[ 18.352063] microcode: CPU6: update failed for patch_level=0x06000832
[ 18.353352] microcode: CPU7: update failed for patch_level=0x06000832
I am aware that Xen can do some early loading of microcodes, since I have found clues in the Xen git logs.
But I guess Xen does not update the microcode, since the OS in Dom0 believes it is necessary to update the microcode.
Does anybody have a clue why updating the CPU microcode from within Dom0 fails?
Last edited by ArthurBorsboom (2015-01-10 12:45:29)

I have solved the issue by using the Xen early microcode loading with the following changes.
Copy the correct microcode binary to the boot folder.
sudo cp /lib/firmware/amd-ucode/microcode_amd_fam15h.bin /boot
Edit the Xen command line in /etc/xen/grub.conf from
XEN_HYPERVISOR_CMDLINE="dom0_mem=1024M,max:1024M xsave=1"
to
XEN_HYPERVISOR_CMDLINE="dom0_mem=1024M,max:1024M xsave=1 ucode=-1"
Hardcode the /etc/grub.d/09_xen configuration file to load the binary.
From
menuentry "Xen ${XEN_VERSION} / Arch Linux ${_KERNEL_PKG_} kernel" ${CLASS} {
$(save_default_entry)
if [ x\$feature_all_video_module = xy ]; then
insmod all_video
fi
set gfxpayload=keep
insmod ${BOOT_PART_FS}
if [ x\$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root ${BOOT_PART_HINTS_STRING} ${BOOT_PART_FS_UUID}
else
search --no-floppy --fs-uuid --set=root ${BOOT_PART_FS_UUID}
fi
echo '$(printf "Loading Xen %s ..." ${XEN_VERSION})'
multiboot ${REAL_DIR}/${XEN_BASENAME} ${REAL_DIR}/${XEN_BASENAME} ${XEN_HYPERVISOR_CMDLINE}
echo 'Loading Arch Linux ${_KERNEL_PKG_} kernel ...'
module ${REAL_DIR}/${_KERNEL_FILE_} ${REAL_DIR}/${_KERNEL_FILE_} root=${GRUB_LINUX_ROOT_DEVICE} rw ${GRUB_LINUX_PARAMS}
echo 'Loading Arch Linux ${_KERNEL_PKG_} kernel initramfs ...'
module ${REAL_DIR}/${_INITRAMFS_}
To
menuentry "Xen ${XEN_VERSION} / Arch Linux ${_KERNEL_PKG_} kernel" ${CLASS} {
$(save_default_entry)
if [ x\$feature_all_video_module = xy ]; then
insmod all_video
fi
set gfxpayload=keep
insmod ${BOOT_PART_FS}
if [ x\$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root ${BOOT_PART_HINTS_STRING} ${BOOT_PART_FS_UUID}
else
search --no-floppy --fs-uuid --set=root ${BOOT_PART_FS_UUID}
fi
echo '$(printf "Loading Xen %s ..." ${XEN_VERSION})'
multiboot ${REAL_DIR}/${XEN_BASENAME} ${REAL_DIR}/${XEN_BASENAME} ${XEN_HYPERVISOR_CMDLINE}
echo 'Loading Arch Linux ${_KERNEL_PKG_} kernel ...'
module ${REAL_DIR}/${_KERNEL_FILE_} ${REAL_DIR}/${_KERNEL_FILE_} root=${GRUB_LINUX_ROOT_DEVICE} rw ${GRUB_LINUX_PARAMS}
echo 'Loading Arch Linux ${_KERNEL_PKG_} kernel initramfs ...'
module ${REAL_DIR}/${_INITRAMFS_}
echo 'Loading AMD Microcode'
module ${REAL_DIR}/microcode_amd_fam15h.bin
Rebuild the grub configuration file
sudo grub-mkconfig -o /boot/grub/grub.cfg
And reboot
Check with the following command that Xen is running
dmesg | grep xen
Check with the following command that the microcode has the correct version
[arthur@orion1695 ~]$ dmesg | grep microcode
[ 9.379631] microcode: CPU0: patch_level=0x06000832
[ 9.379645] microcode: CPU1: patch_level=0x06000832
[ 9.379662] microcode: CPU2: patch_level=0x06000832
[ 9.379676] microcode: CPU3: patch_level=0x06000832
[ 9.379692] microcode: CPU4: patch_level=0x06000832
[ 9.379710] microcode: CPU5: patch_level=0x06000832
[ 9.379724] microcode: CPU6: patch_level=0x06000832
[ 9.379738] microcode: CPU7: patch_level=0x06000832
[ 9.379823] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
[arthur@orion1695 ~]$
And as you see in this example, there is no attempt to update the microcode anymore, since it is already up-to-date.
I hope this helps other people facing this issue.

Microcode Update Error in HP DC7100 CMT

Hi, I have a hp dc7100 cmt and I have already read other post regarding Microcode Error, but the file that I need ---> http://h20566.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=402165&swItem=ir_63388_1&lang=en&cc=uk <--- isn't available where I can find it?
This question was solved.
View Solution.

Hi:
Here is the link to the file you need...
http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=402164&swItemId=PSG_I23754_109014&swEnvOi...
Reminder that this microcode update will only work by using a floppy disk.
The file will ask you to insert a floppy disk in a FDD and it will create a bootable floppy disk and put the microcode update files on the disk.
Then you boot from the FDD and follow the on screen instructions to update the microcode.

XEN VM - Applying Intel CPU microcode update fails

Hi,
I just installed OEL5 and I get the following message on boot:
Applying Intel CPU Microcode update: FATAL: Module microcode not found.
ERROR: Module microcode does not exist in /proc/modules [Failed]
From my quick Google search this is caused by the XEN virutualization. If you you get the [Failed] message then you have a serious problem.
Any ideas?
Thanks
David

The same happens booting a xen linux kernel on original RHEL and derivatives (such has centos)
I just ignored it, and AFAIK there's no problem with xen.
Just my 2 cents.

Applying Intel CPU microcode update

Hi,
after creating a virtual machine from OEL template, when the I connect to that virtual machine OEL booting process fail to Applying Intel CPU microcode update.
ghassan Hallaq

The same happens booting a xen linux kernel on original RHEL and derivatives (such has centos)
I just ignored it, and AFAIK there's no problem with xen.
Just my 2 cents.

How to fix "1801-Microcode Update Error" in HP Compaq dc7600 Convertible Minitower

Dear Sir,
I am using hp compaq dc7600U with pentium (R) 4 3.00 GHz. processor. When I changed the processor with Pentium D 3.4 GHz. processor I found a message " 1801 Microcode Update error" Press F1 to continue. After pressing F1 computer works normally. I want to know that how I can remove this error message.

Hi:
You need to install the microcode update by using a bootable flash drive with the common MS DOS Command files and the contents of the microcode flash file included on the bootable flash drive.
Then you type Flashbin.exe at the command prompt you get when you boot from the flash drive, and hit the enter key.
Follow the on screen instructions to update the microcode.
I have attached the tool to make a usb flash drive bootable and the MS DOS system files to copy onto the flash drive.
See the 3 files below under Attachments.
Unzip and copy the DOS files without any folders to the flash drive after you run the HP tool to make it bootable.
I have also zipped up and attached the microcode update files.
Unzip them and put them on the flash drive too without any folders after you make the drive bootable.
Attachments:
SP27608.zip ‏1817 KB
Dos System Files.zip ‏243 KB
DOS Flash.zip ‏73 KB

How to fix "1801-Microcode Update Error" in HP Compaq dc7600 Minitower

Dear Sir,
I am using hp compaq dc7600U with pentium (R) 4 3.00 GHz. processor. When I changed the processor with Pentium D 3.4 GHz. processor I found a message " 1801 Microcode Update error" Press F1 to continue. After pressing F1 computer works normally. I want to know that how I can remove this error message.

Please see my reply to your other post at the link below...
http://h30434.www3.hp.com/t5/Desktop-Hardware/how-to-fix-quot-1801-Microcode-Update-Error-quot-in-HP...

How to fix "1801-Microcode Update Error" in HP Compaq dc7700p Convertible Minitower

Hello,
i've been reading and reading this post for a several times and i'm not sure will this work on my PC so i must ask, how to fix "1801-Microcode Update Error" in HP Compaq dc7700p Convertible Minitower i've upgraded it with E7200 instead of the original E6300
here's Product Number: p/n RN120ET#UUZ
I'm able to boot up and start windows i don't know is it working normaly or not, i'm just annoyed with the boot message:
Please HELP and Thank You in advance !!!
This question was solved.
View Solution.

Hi:
You will need to update the BIOS to its latest version to get rid of the microcode error, and the processor will only run at half the FSB speed because the BIOS update was not written to make the E7xxx processors work correctly.
You will need to run this software each time you get into windows and change the multiplier to the max.
Or you can run that batch file listed on the below webpage for it to run automatically.
http://crystalmark.info/software/CrystalCPUID/index-e.html
If I were you, I would just install a Conroe E6700 and have a problem-free upgrade.
You will need to use the DOS based flash because I don't think there is a BIOS update written for W7.

Microcode update error 1801 in hp compaq dc5800 sff

Dear sir,
we have facing a problem like in intial display sowing eror microcode update error 1801 in hp compaq dc5800 sff.
Please find the resulation.

Hi:
Did you install a different processor than the one that came with the PC?
If so, what processor did you install?
A microcode error means there is an unsupported processor installed or you need to install a microcode update to allow for support of the processor you installed if it can be supported in your dc5800.
Paul

How can i fix "invalid processor microcode update" i have a compaq dc7600 cmt C2C6260Q93

My m/c is a HP Compaq dc7600 CC2C6260Q93).
I've replaced the 2.8 processor with INTEL(R) PENTIUM (R) D CPU 3.00 GHZ/4M , during start-up it gives the message "missing or invalid processor microcode update"
My motherboard is HP (C)2005 HP DC

Hi:
Please see my reply to your other post at the link below.
http://h30434.www3.hp.com/t5/Desktop-Operating-Systems-Software-Recovery/how-can-i-fix-quot-invalid-...

How can i fix "invalid processor microcode update" i have a compaq dc7100 cmt

My m/c is a HP Compaq dc7100 CMT(DX438AV).
I've replaced the 2.8 processor with a P4 HT 3.4ghz 1M/800 SL7PY , during start-up it gives the message "missing or invalid processor microcode update"
My motherboard is HP 0968h . My Bios is... Version : 786C1 v01.05
I looked at specs for the board and i think it supports this chip, can anyone help fix this problem
Thanks..
This question was solved.
View Solution.

Hi:
Now that you installed the latest microcode update, may I recommend you install the Pentium 4 650 3.4 GHz?
That processor has double the L2 cache as the one you installed, and you can run a 64 bit operating system on it.
If you have the CMT, you have a pretty wide assortment of video cards you can install so you can run all of the features of Windows 7. The onboard GMA 900 video won't run Aero. Just keep within the power supply limit of 345W
I have W7 x64 on my dc7100 CMT and an ASUS nVidia 8400GS 512 MB fanless video card in mine, and everything works great. Recommended P/S is 300W for the card so I was fine.
The P4 650 is pretty reasonable on eBay. That is where I got mine.
http://computers.shop.ebay.com/CPUs-/164/i.html?CPU%2520Type=Pentium%25204&rt=nc&LH_BIN=1&_nkw=650&_...
Paul

[SOLVED]Can the Intel microcode update(/non-update) brick my computer?

Ref news: https://www.archlinux.org/news/changes- … deupdates/
Related forum posts:
https://bbs.archlinux.org/viewtopic.php?id=188777
https://bbs.archlinux.org/viewtopic.php?id=188252
This news sounds quite scary to me. The big question is if anything I do can brick my computer.
Does doing this on kernels < 3.17.2 brick my computer?
Will upgrading to 3.17.2 without doing this brick my computer?
Last edited by simendsjo (2014-10-23 07:25:02)

Hi,
I have a rather silly question. I can't figure out if I have Intel microcode updates enabled. I have installed the intel-ucode package from [extra] (extra/intel-ucode 20140624-1), and I get this when I check dmesg:
prakhar@sim74stic ~ $ dmesg |grep microcode
[ 11.576665] microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x15
[ 11.709317] microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x15
[ 11.710515] microcode: CPU0 updated to revision 0x1b, date = 2014-05-29
[ 11.710545] microcode: CPU1 sig=0x306a9, pf=0x10, revision=0x15
[ 11.710602] microcode: CPU1 sig=0x306a9, pf=0x10, revision=0x15
[ 11.711282] microcode: CPU1 updated to revision 0x1b, date = 2014-05-29
[ 11.711296] microcode: CPU2 sig=0x306a9, pf=0x10, revision=0x15
[ 11.711341] microcode: CPU2 sig=0x306a9, pf=0x10, revision=0x15
[ 11.712068] microcode: CPU2 updated to revision 0x1b, date = 2014-05-29
[ 11.712080] microcode: CPU3 sig=0x306a9, pf=0x10, revision=0x15
[ 11.712134] microcode: CPU3 sig=0x306a9, pf=0x10, revision=0x15
[ 11.712859] microcode: CPU3 updated to revision 0x1b, date = 2014-05-29
[ 11.712897] microcode: CPU4 sig=0x306a9, pf=0x10, revision=0x15
[ 11.712972] microcode: CPU4 sig=0x306a9, pf=0x10, revision=0x15
[ 11.713683] microcode: CPU4 updated to revision 0x1b, date = 2014-05-29
[ 11.713698] microcode: CPU5 sig=0x306a9, pf=0x10, revision=0x15
[ 11.713736] microcode: CPU5 sig=0x306a9, pf=0x10, revision=0x15
[ 11.714451] microcode: CPU5 updated to revision 0x1b, date = 2014-05-29
[ 11.714469] microcode: CPU6 sig=0x306a9, pf=0x10, revision=0x15
[ 11.714503] microcode: CPU6 sig=0x306a9, pf=0x10, revision=0x15
[ 11.714878] microcode: CPU6 updated to revision 0x1b, date = 2014-05-29
[ 11.714888] microcode: CPU7 sig=0x306a9, pf=0x10, revision=0x15
[ 11.714907] microcode: CPU7 sig=0x306a9, pf=0x10, revision=0x15
[ 11.715282] microcode: CPU7 updated to revision 0x1b, date = 2014-05-29
[ 11.715322] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
My question is, did the microcode update work? And should I add it to mkinitcpio to trigger it early? (sudo modprobe microcode doesn't change the output above).
Last edited by prakharsingh95 (2014-10-23 16:21:56)

Atom PSE erratum detected, BIOS microcode update recommended

This is the information about my Netbook:
Lenovo Ideapad S10
Memory = 995,8 MiB
Processor = Intel® Atom™ CPU N270 @ 1.60GHz × 2
Graphics = Intel® 945GME x86/MMX/SSE2
System base = Arch Linux 32-bit
This is my journalctl:
[root@arch julio]# journalctl
-- Logs begin at jue 2013-09-26 14:43:49 COT, end at mié 2013-10-02 15:36:17 COT. --
sep 26 14:43:49 arch systemd-journal[103]: Runtime journal is using 184.0K (max 49.7M, leaving 74.6M of free 497.7M, current l
sep 26 14:43:49 arch systemd-journal[103]: Runtime journal is using 188.0K (max 49.7M, leaving 74.6M of free 497.7M, current l
sep 26 14:43:49 arch kernel: Initializing cgroup subsys cpuset
sep 26 14:43:49 arch kernel: Initializing cgroup subsys cpu
sep 26 14:43:49 arch kernel: Initializing cgroup subsys cpuacct
sep 26 14:43:49 arch kernel: Linux version 3.11.1-2-ARCH (tobias@testing-i686) (gcc version 4.8.1 20130725 (prerelease) (GCC)
sep 26 14:43:49 arch kernel: Atom PSE erratum detected, BIOS microcode update recommended
sep 26 14:43:49 arch kernel: e820: BIOS-provided physical RAM map:
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009f7ff] usable
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x000000000009f800-0x000000000009ffff] reserved
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x00000000000d2000-0x00000000000d3fff] reserved
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x00000000000dc000-0x00000000000fffff] reserved
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003f6cffff] usable
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x000000003f6d0000-0x000000003f6e1fff] ACPI data
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x000000003f6e2000-0x000000003f6e2fff] ACPI NVS
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x000000003f6e3000-0x000000003fffffff] reserved
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed003ff] reserved
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x00000000fed14000-0x00000000fed19fff] reserved
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed8ffff] reserved
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
sep 26 14:43:49 arch kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
sep 26 14:43:49 arch kernel: Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
sep 26 14:43:49 arch kernel: SMBIOS 2.5 present.
sep 26 14:43:49 arch kernel: DMI: LENOVO 433336U /Kuril , BIOS 14C
sep 26 14:43:49 arch kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
sep 26 14:43:49 arch kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
sep 26 14:43:49 arch kernel: e820: last_pfn = 0x3f6d0 max_arch_pfn = 0x100000
sep 26 14:43:49 arch kernel: MTRR default type: uncachable
lines 1-31
I did what you recommended and this product is the report
https://wiki.archlinux.org/index.php/Microcode
Any idea?

progandy wrote:You'll have to update the bios or use the early microcode update as described here: https://www.kernel.org/doc/Documentatio … rocode.txt
Interesting... perhaps this is handled some how by mkinitcpio? I didn't see anything obvious in the hooks section.
progandy wrote:Edit: You can download the microcode data here: https://downloadcenter.intel.com/Search … crocode%22
This gives the same file that [extra]/intel-ucode uses, but neither the source nor the package provides "GenuineIntel.bin" mentioned in the document.
EDIT: If the info contained in the blog post you referenced is indeed accurate, I fail to see what value the intel-ucore packages provides at all. In other words, it loads the updates after the kernel has already disabled the features the updates are fixing. Seems as though either:
1) The package provides superfluous files.
2) It needs to generate a modified initrc image as described in the early-microcode.txt file you referenced.
3) We are wrong and the package does indeed provide a solution.
EDIT2: http://lists.debian.org/debian-user/201 … 00395.html
Last edited by graysky (2013-10-03 18:27:03)

BIOS Microcode Update?

When I run dmesg after booting up my Dell Mini 9 (With an Atom processor) I get the following:
Atom PSE erratum detected, BIOS microcode update recommended
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003f6d0000 (usable)
BIOS-e820: 000000003f6d0000 - 000000003f6e2000 (ACPI data)
BIOS-e820: 000000003f6e2000 - 000000003f6e3000 (ACPI NVS)
BIOS-e820: 000000003f6e3000 - 0000000040000000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
Any idea on how to update my BIOS microcode?

@SK - nothing will happen since your CPU's microcode from the latest version hasn't changed. I did the experiment on my Atom 330 based machine.
thestinger wrote:Ah, it's possible that's the newest microcode for that CPU, I wouldn't worry about it .
You're right I think...
On my X3360:
microcode: CPU0 sig=0x10677, pf=0x10, revision=0x705
microcode: CPU1 sig=0x10677, pf=0x10, revision=0x705
microcode: CPU2 sig=0x10677, pf=0x10, revision=0x705
microcode: CPU3 sig=0x10677, pf=0x10, revision=0x705
microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
microcode: CPU0 updated to revision 0x70a, date = 2010-09-29
microcode: CPU1 updated to revision 0x70a, date = 2010-09-29
microcode: CPU2 updated to revision 0x70a, date = 2010-09-29
microcode: CPU3 updated to revision 0x70a, date = 2010-09-29
On my E5200:
microcode: CPU0 sig=0x1067a, pf=0x1, revision=0xa07
microcode: CPU1 sig=0x1067a, pf=0x1, revision=0xa07
microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
microcode: CPU0 updated to revision 0xa0b, date = 2010-09-28
microcode: CPU1 updated to revision 0xa0b, date = 2010-09-28
On my Atom 330:
microcode: CPU0 sig=0x106c2, pf=0x8, revision=0x20d
microcode: CPU1 sig=0x106c2, pf=0x8, revision=0x20d
microcode: CPU2 sig=0x106c2, pf=0x8, revision=0x20d
microcode: CPU3 sig=0x106c2, pf=0x8, revision=0x20d
microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
microcode: CPU0 updated to revision 0x219, date = 2009-04-10
microcode: CPU1 updated to revision 0x219, date = 2009-04-10
microcode: CPU2 updated to revision 0x219, date = 2009-04-10
microcode: CPU3 updated to revision 0x219, date = 2009-04-10
Last edited by graysky (2011-02-27 12:16:29)

Microcode update

Similar Messages

Maybe you are looking for