02f0:cpu id: A7 no microcode update loaded for alternate processor

Dear Sir..  I am facing problem in my L420 model laptop..  that is the above mentioned 02f0:cpu id: A7 no microcode update loaded for alternate processor  error code appearing.. the problem is i cant access any bootable device if i try to put new bios its not supporting os cd and any other bootable devices.. so kindly guide me to solve the issues.. how i can put new bios version or tell me the solution for login bios?

is your CPU the original one shipped with your ThinkPad?
Regards,
Jin Li
May this year, be the year of 'DO'!
I am a volunteer, and not a paid staff of Lenovo or Microsoft

Similar Messages

  • 2 updates loading for hours. I can't stop it, quit, escape...

    Software update popped up and I started it which restarted my Macbook as usual, but it has been loading for a couple of hours. In the meantime, I've tried turning my Macbook off and on to no avail, it stays in loading status (gray screen, small apple and the spinning gear). I've tried escaping, command shift Q, everything! 

    General advice on updating:
    It is worth noting that it is an extreme rarity for updates to cause upsets to your system, as they have all been extensively beta-tested, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
    So before you do anything else:
    If you can, make a full backup first to an external hard disk. Ideally you should always have a bootable clone of your system that enables you to revert to the previous pre-update state.
    Turn off sleep mode for both screen and hard disk.
    Disconnect all peripherals except your keyboard and mouse.
    1. Repair Permissions (in Disk Utility)
    2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
    At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
    3. Download the correct version of the COMBO update from the Apple download site. If your car runs on gasoline you would not want to fill the tank with diesel, so don’t try to install the PPC updater on an Intel Mac!
    The 10.4.11 Combo Updater for PPC Macs is here:  http://support.apple.com/kb/DL170
    And for Intel Macs here:  http://support.apple.com/kb/DL172
    If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
    Full details about the 10.4.11 update here:  http://support.apple.com/kb/TA24901?viewlocale=en_US
    More information on using Software Updater here:
    http://support.apple.com/kb/TA24901?viewlocale=en_US
    Using the Combo updater ensures that all system files changed since the original 10.4.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.4.10 to 10.4.11. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
    Now proceed as follows:
    4. Close all applications and turn off energy saving and screensaver.
    5. Unplug all peripherals except your keyboard and mouse.
    6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
    7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
    8. Once your Mac is awake, repair permissions again, and you should be good to go!
    If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
    9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them compliant with the latest version of your operating system. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 3.
    N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
    Lastly, Apple's own article on the subject of Software Update may also be useful reading:
    http://docs.info.apple.com/article.html?artnum=106695
    [b]If you are updating Safari (or just have):[/b]
    Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up.  If you have installed an OS update and Safari is crashing, the very [i]first[/i] thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
    So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 used Safari 3.0.4 which was [i]not[/i] a beta. If Safari 3.1.2 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
    Moreover, trying to revert to Safari 3.0.4 (or worse still, version 2) when running 10.4.11 or 10.5 can have repercussions, as Safari 3.1.1 uses a completely different webkit on which other applications like iChat, Mail and Dashboard Widgets etc also rely, and may entail you having to reinstall an earlier operating system.
    [b][i]Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on.[/b][/i] Two such add-on that have been frequently mentioned here for causing such problems are Piclens and Pithhelmet. If you have them, trash them.
    Additional tips on software installation here:
    http://docs.info.apple.com/article.html?artnum=106692
    To reiterate, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for  problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must decide. If the functionality of a specific Input Manager or set thereof is really important to you, you may well choose to assume the associated risk.
    Again, the advice is to remove all Input Managers from the following directories:
    /Library/InputManagers
    ~/Library/InputManagers
    especially prior to system updates (they can always be added back one-by-one later).

  • 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.

  • [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.

  • 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)

  • [SOLVED] Intel microcode not loaded - already available in the bios?

    I'm getting ready to the linux 3.17 release and thought I should manually install the Intel microcode.
    I noticed that I didn't even have the package installed, so that was my first stop.
    After doing the steps outlined in the wiki, I'm not sure it's actually loaded.
    The `sig` and `revision` in the available patch and the kernel output is the same.
    Does this mean I already have the microcodes updated through the BIOS, or is this irrelevant?
    And if it's irrelevant, any idea what I'm doing wrong?
    $ uname -a
    Linux simendsjo-t520 3.16.7-1-ck #1 SMP PREEMPT Fri Oct 31 13:09:18 CET 2014 x86_64 GNU/Linux
    $ dmesg | grep microcode
    [ 0.521721] microcode: CPU0 sig=0x206a7, pf=0x10, revision=0x29
    [ 0.521739] microcode: CPU1 sig=0x206a7, pf=0x10, revision=0x29
    [ 0.521764] microcode: CPU2 sig=0x206a7, pf=0x10, revision=0x29
    [ 0.521783] microcode: CPU3 sig=0x206a7, pf=0x10, revision=0x29
    [ 0.521894] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    The initrd lines in grub.cfg has been changed (not showing entire config, but it's on each non-fallback initrd line)
    (But this should matter yet anyway as I'm on 3.16..?)
    # grep intel /boot/grub/grub.cfg
    initrd /boot/intel-ucode.img /boot/initramfs-linux-ck.img
    initrd /boot/intel-ucode.img /boot/initramfs-linux.img
    But iucode_tool says an update is available (ref: https://wiki.archlinux.org/index.php/Microcode)
    # bsdtar -Oxf /boot/intel-ucode.img | iucode_tool -tb -lS -
    iucode_tool: system has processor(s) with signature 0x000206a7
    selected microcodes:
    001: sig 0x000206a7, pf mask 0x12, 2013-06-12, rev 0x0029, size 10240
    Last edited by simendsjo (2014-11-05 20:12:36)

    kokoko3k wrote:
    I think iucode_tool is just saying that an update has been released for your cpu model.
    But yout particular cpu has already it in place.
    I don't know if it is the bios to update the microcode or your cpu has been shipped with the new firmware.
    Thanks! I don't really care As long as I haven't failed the installation process, I'm happy.

  • 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-...

  • 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)

  • Xw6200 1801 microcode update error

     Hi I have recently upgraded my xw6200 workstation cpu from 2 x intel xeon 2.8 ghz to 2 x inel xeon 3.6 ghz. the problem is when i but up my pc i get a error "1801 microcode update error" and give me the option to boot by pressing f1 and the it boots up no problem apart from the fans are a lot noisier. is there a way to solve this error every time i boot up. its not a massive problem as windows runs fine after i press F1 but any help would be appreciated thanks.

    Unfortunately, the latest  version of the installed BIOS version is as good as it gets.
    The BIOS family 786B7, which your BIOS is a member of,  was last updated in 2006.
    Unless a microcode update can be found through Windows update or at Intel for the installed operating system, this may be an issue that I am unable to help you resolve.
    Normally a BIOS update is the answer, but no more exist.
    ****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
    2015 Microsoft MVP - Windows Experience Consumer

  • How can I fix "1801 microcode update error" I have a hp compaq dc5700. I replaced my processor

    how can I fix "1801 microcode update error" I have a hp compaq dc5700. I upgraded my processor to "core2Duo 2.6MHz, e4700"

    Hi MOndo7299:
    Thank you for your post. I am glad to help!
    I assume that the P in the your post is for Processor. The "1801Mocrocode update error" is telling you to update the CPU.  There is more then one way to do this. You can do this by downloading and running the HP Support Assistant.  click here, to aid in updating drivers and resolving issues. You can update from Device Manager. Open Device Manager, right click on the processor and you should see an option to update. You could also check the manufacturer's site for any updates. For your convenience I am sending documentation on "Downloading or Updating Software and Drivers for HP Computers"  click here. If you require further assistance would you please provide your exact model number, and what changes you have  made. How Do I Find My Model Number or Product Number?  click here.
    Sparkles1
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

  • Does anybody know why when I aTrying to edit my yahoo profile using Firefox certain elements do not show up such as update "Load Photo" on the avatar page.

    Trying to edit my yahoo profile using Firefox and certain elements do not show up such as update "Load Photo" on the avatar page.
    If I use Explorer it allows me to see all the links and can edit my profile but not in Firefox.
    I am not sure the URL will let you in as is a private link.

    '''Try the Firefox SafeMode''' to see how it works there. <br />
    ''A troubleshooting mode, which disables most Add-ons.'' <br />
    ''(If you're not using it, switch to the Default Theme.)''
    * You can open the Firefox 4.0+ SafeMode by holding the '''Shft''' key when you use the Firefox desktop or Start menu shortcut.
    * Or use the Help menu item, click on '''Restart with Add-ons Disabled...''' while Firefox is running. <br />
    ''Don't select anything right now, just use "Continue in SafeMode."''
    ''To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before using the Firefox shortcut (without the Shft key) to open it again.''
    '''''If it is good in the Firefox SafeMode''''', your problem is probably caused by an extension, and you need to figure out which one. <br />
    http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes
    ''When you figure out what is causing that, please let us know. It might help other user's who have that problem.''

  • Can't add music my iPhone from iTunes.  When I try to drag a song over to my phone, I get the circle w/ the syncing line through it, but it does not update/load.  [Manually manage music and videos] is checked. And, this is the only Mac I have ever used to

    Can't add music my iPhone from iTunes.
    When I try to drag a song over to my phone, I get the circle w/ the syncing line through it, but it does not update/load.
    [Manually manage music and videos] is checked. And, this is the only Mac I have ever used to add music to my phone.
    Also, just updated the phone's software today, and iTunes' software is already up to date.

    Hi Gregg,
    Have you tried resetting the device (nothing will be lost): Hold down the Home and Power buttons at the same time and continue to hold them down until the Apple appears (up to 30 seconds). Once the Home screen redisplays, see if your Music app is behaving normally.
    Cheers,
    GB

  • I cant update ios7 to apple tv it load for a time than a message that it is not completed

    i cant update ios7 to apple tv it load for a time than a message that it is not completed

    Welcome to the Apple Community.
    If your problem persists get yourself a micro USB cable (sold separately), you can restore your Apple TV from iTunes:
    Remove ALL cables from Apple TV. (if you don't you will not see Apple TV in the iTunes Source list)
    Connect the micro USB cable to the Apple TV and to your computer.
    Reconnect the power cable (only for Apple TV 3)
    Open iTunes.
    Select your Apple TV in the Devices list, and then click Restore.
    (You may already have a micro USB cable if you have a camera or other digital device)

  • Critical update won't load for office 2011 released 2.10.15

    A critical update appears  for Office 2011   released 2.10.2015   14.4.8  113.6 MB
    This update fixes critical issues.
    As soon as it goes through all the install process, it says it was successful, Then it immediatlely shows up as a critical update needed AGAIN.
    I can't figure why it will load.
    Thanks

    Does the ext directory have the php_oci8.dll? In the original steps the PHP dir is renamed. In the given php.in the extension_dir looks like it has been updated correctly. Since PHP distributes php_oci8.dll by default I reckon there would be a very good chance that the problem was somewhere else. Since this is an old thread I don't think we'll get much value from speculation.
    -- cj

Maybe you are looking for