Intel Management Engine Failure
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=3913
Printed Date: 04 Aug 2025 at 3:21am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Intel Management Engine Failure
Posted By: EpsilonZero
Subject: Intel Management Engine Failure
Date Posted: 01 Dec 2016 at 7:02am
|
I have a Fatal1ty X99 Professional Gaming i7 (BIOS 1.40) with a Broadwell-E on Win10x64. I can't get the Intel Management Engine (11.0.0.1181) component to run. It consistently gives this error: This device cannot start. (Code 10) STATUS_DEVICE_POWER_FAILURE Hardware IDs are: PCI\VEN_8086&DEV_8D3A&SUBSYS_8D3A1849&REV_05 PCI\VEN_8086&DEV_8D3A&SUBSYS_8D3A1849 PCI\VEN_8086&DEV_8D3A&CC_078000 PCI\VEN_8086&DEV_8D3A&CC_0780 Compatible IDs are: PCI\VEN_8086&DEV_8D3A&REV_05 PCI\VEN_8086&DEV_8D3A PCI\VEN_8086&CC_078000 PCI\VEN_8086&CC_0780 PCI\VEN_8086 PCI\CC_078000 PCI\CC_0780 I've tried re-installing Windows, uninstalling/reinstalling the IMEI driver, pulling all but 1 stick of ram (and switching it), switching out power supplies, re-seating everything... all with negative results. This RAM worked fine with my previous ASRock board (w/Haswell-E) and is on memory QVL list. My PCIe 1.2TB Intel 750 NVMe SSD isn't on the storage QVL, but it worked fine with my http://www.asrock.com.tw/microsite/Fatal1tyKiller/Fatal1ty%20X99X%20Killer3.1.html" rel="nofollow - Fatal1ty X99X Killer/3.1 . Incidentally, I bought two of these at the same time and built a second system with a new Haswell-E that doesn't have the IMEI problem (on Win7x64). Help?  |
Replies:
Posted By: EpsilonZero
Date Posted: 01 Dec 2016 at 7:09am
|
Also, the time to get to the ASRock splash screen is quite long... boot-up is slower that both my new Haswell-E and my old one on the X99X Killer. |
Posted By: parsec
Date Posted: 01 Dec 2016 at 9:06am
Why are you using that old version of the IME driver, particularly with a Broadwell-E CPU? The version on your board's download pages is 11.0.4.1186: http://www.asrock.com/mb/Intel/Fatal1ty%20X99%20Professional%20Gaming%20i7/#osW1064" rel="nofollow - http://www.asrock.com/mb/Intel/Fatal1ty%20X99%20Professional%20Gaming%20i7/#osW1064 Same IME version for all versions of Windows, and a Broadwell-E compatible UEFI/board. Do you have the correct INF files installed? Version 10.1.2.10? That should be installed before anything else. Your Intel 750 is not the problem. Your other system with a Haswell-E that does not have the problem using the Haswell-E IME version... should not have this problem. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
EpsilonZero wrote:Posted By: EpsilonZero
Date Posted: 01 Dec 2016 at 1:22pm
|
I just re-downloaded and re-installed INF 10.1.2.10 and rebooted. Downloaded the ME (11.0.4.1186) from the support page and ran the install. It says it is successful, but the version went back to 11.0.0.1181. Trying again, the version went to 11.0.5.xxxx (5 not a typo) but it is back to 11.0.0.1181 again after uninstalling and re-detecting hardware. I did try installing other versions at one point, so some of those files still exist on the drive. I can't seem to get the correct version to stick. I originally installed everything using the ASROCK live update utility. |
Posted By: EpsilonZero
Date Posted: 01 Dec 2016 at 1:36pm
|
Tried installing INF again as administrator... rebooted... now ME (11.0.4.1186) says platform not supported when I try to install. |
Posted By: EpsilonZero
Date Posted: 01 Dec 2016 at 1:41pm
|
Uninstalling ME from device manager and deleting the driver each time dropped it to v11.0.0.1157. The v11.0.4.1186 installer ran through this time, but put the version back to 11.0.0.1181 again. |
Posted By: wardog
Date Posted: 01 Dec 2016 at 5:36pm
|
" rel="nofollow - Stop Windows 10 from Windows Update d/l'ing and installing driver updates Control Panel > System and Security > System > Advanced system settings > Hardware tab > Device Installation Settings > "Do you want to automatically download manufacturers apps and custom icons available for your devices?" > Select No, then select Save Changes Now that your versioning is hosed compliments of WU, go back into Dev Mgr and see where rolling back these gets you |
Posted By: EpsilonZero
Date Posted: 02 Dec 2016 at 5:40am
|
" rel="nofollow - Isn't the driver version supposed to be 11.0.0.1181, with the installer version being 11.0.4.1186? I think this is the correct version but it just isn't working for some other reason. |
Posted By: parsec
Date Posted: 02 Dec 2016 at 10:34am
" rel="nofollow -
Yes to both questions, I have exactly that on my X99 Extreme6/3.1 board, just checked on this The installation program is 11.0.4.1186, which appears in Win 10 Programs and Features. The actual driver version in Device Manager is 11.0.0.1181. I also have the same chipset files installed, 10.1.2.10. So where are you at now? IME is still not running on your PC? I have never seen that happen, on my X99 and any other Intel system. I have many of them, too many. You see the error in Device Manager, correct? If you click on the Resources tab in the Device Manager entry, do you see any conflicting devices? Do you have the Intel Turbo Boost Max Technology 3.0 ver:1.0.0.1027 installed? NOT that I know it should or must be installed, I have no idea. I'm desperate for something to tell you. Or the Intel NVMe driver, was that installed? Again, not that I think it is needed for IME. I assume you have restarted the PC a few times since you noticed this situation? IMO, Windows 10 update has not installed anything wrong, and is not the problem. I don't have that option turned off in Windows 10, and I'm not getting any unwanted driver updates. Try starting a command prompt (Admin), and type in msinfo32. In the resulting display, check Hardware Resources, and really everything that might provide a clue. Problem Devices in Components, for example. Did you check any Windows Event and Error logs for clues? ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: EpsilonZero
Date Posted: 02 Dec 2016 at 10:46am
|
Still not running... The PC has been restarted many times. Intel SSD Toolbox is loaded and the latest firmware is installed for the Intel 750 SSD Turbo Boost 3.0 v1.0.0.1027 is installed There are no conflicting resources in device manager because the device isn't running ("has a problem") msinfo32 reports problem devices as: Intel(R) Management Engine Interface PCI\VEN_8086&DEV_8D3A&SUBSYS_8D3A1849&REV_05\3&11583659&0&B0 This device cannot start. system error logs reports: 1. Intel(R) Management Engine Interface driver has failed to perform handshake with the Firmware (FWSTS0: 0x1E000042, FWSTS1: 0x60002106). 2. The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. |
Posted By: EpsilonZero
Date Posted: 02 Dec 2016 at 10:57am
|
" rel="nofollow - That second error looks like RuntimeBroker... which I don't think needs to run at all (metro apps?). |
Posted By: EpsilonZero
Date Posted: 02 Dec 2016 at 11:00am
|
...and a second error (different FWSTS1 by one digit.. maybe due to me trying a different ME version from the other error) Intel(R) Management Engine Interface driver has failed to perform handshake with the Firmware (FWSTS0: 0x1E000042, FWSTS1: 0x66002106). |
Posted By: Roktuk
Date Posted: 03 Dec 2016 at 9:13pm
|
This just happened to me out of the blue, I have a Fatal1ty X99X Killer
bios 3.10, haven't updated anything recently. Reboot took abnormally
long, event viewer gave me this "Intel(R) Management Engine Interface
driver has failed to perform handshake with the Firmware" I tried uninstalling, re-installing management engine, not fixed. New version of ME, not fixed. Tried letting windows update get it, not fixed. I tried re-flashing bios v3.10, not fixed. Tried re-flashing previous bios v1.90, FIXED!!! Went back and re-flashed back to v3.10, still FIXED!!! It's only been a couple of hours, but all seems well. I hope this helps. Edit: I forgot to say that I tried a previous restore point as well with no success. Win10. Just to be thorough. |
Posted By: EpsilonZero
Date Posted: 03 Dec 2016 at 9:41pm
|
" rel="nofollow - I just tried downgrading to BIOS 1.10... ME still broken. Upgrade back to 1.40... ME still broken. Do you have Broadwell-E too? |
Posted By: Roktuk
Date Posted: 03 Dec 2016 at 9:50pm
|
" rel="nofollow - 5820k Haswell-E, If your board has A B bios, maybe try switching, that was gonna be my next step as I've never flashed the B bios. I don't really think this has to do with the software though because for me just posting was slow, somehow the bios got corrupted? I don't know. |
Posted By: EpsilonZero
Date Posted: 04 Dec 2016 at 3:04am
|
Switched to BIOS B and just installed a brand new power supply at the same time. Still broken... |
Posted By: EpsilonZero
Date Posted: 10 Dec 2016 at 9:34pm
|
" rel="nofollow - I suppose we're out of ideas, then. Broken hardware? |
Posted By: UnsungPatriot
Date Posted: 20 Dec 2016 at 1:18pm
|
Been having this problem from the very beginning of building this system. Also having occasional BSODs, not sure if related or not. Leaning towards more and more that it could be. This is what I see in the windows event logger:
Event ID: 3 Source: MEIx64 Intel(R) Management Engine Interface driver has failed to perform handshake with the Firmware (FWSTS0: 0x1E000042, FWSTS1: 0x60002106). In Device Manager: This device cannot start (Code 10) STATUS_DEVICE_POWER_FAILURE (When I look at events Tab in device manager) Device PCI\VEN_8086&DEV_8D3A&SUBSYS_8D3A1849&REV_05\3&11583659&0&B0 had a problem starting. Driver Name: oem93.inf Class Guid: {4D36E97D-E325-11CE-BFC1-08002BE10318} Service: MEIx64 Lower Filters: Upper Filters: Problem: 0xA Problem Status: 0xC000009E More info: Current Intel Management Engine installed on my system Driver Version: 11.6.0.1015 Tried fresh install of Windows 10 Education 3 times, re-flashed the Bios to latest listed on Asrock X99 Fatal1ty support page, uninstalling IME drivers and reinstalling multiple times, the drivers that are on the support website for X99 Fatal1ty Professional Gaming i7 version 11.0.4., as well as the general drivers from Intel website that are version 11.0.6. I'm searched through multiple website forums to find an answer for this and nobody can seem to figure it out. I still have had the same exclamation mark showing in device manager for the Intel Management Engine Interface. I am at a loss as well unfortunately. |
Posted By: stereo55
Date Posted: 05 Apr 2017 at 6:40am
|
Just ran across this thread by googling the/my same problem . In Device Manager: This device cannot start (Code 10) STATUS_DEVICE_POWER_FAILURE Just noticed the above problem when looking for a reason or cause of my slow boot up's . Running : Asrock x99 OC Formula 3.1~ orginal bios 1.20 / 5930k / Samsung Evo 256gig / Windows 10 Tried everything like others thus far, but not a bios change/update (reluctant as I did not care for the newer bios's Ive tried in the past) . Will do a bios update and report back . |
Posted By: parsec
Date Posted: 05 Apr 2017 at 11:50am
" rel="nofollow -
I have many ASRock Intel chipset boards, including an X99 board, and I have never had a failure of the IME software. Frankly I'm fascinated by this issue, since it seems so odd IMO, and I've never experienced it myself. I assume that is the problem you have, although you did not say so specifically. Or is that another device? Did you install the basic drivers for your board? The INF driver ver:10.1.2.10 installer should be run first after any Windows installation, followed by the Intel IME software, the Intel Management Engine driver ver:11.0.4.1186. Both are available on your board's download page (sorry for the text link, the forum's link tool fails with some URLs): http://www.asrock.com/mb/Intel/X99%20OC%20Formula3.1/?cat=Download&os=Win1064 You did not like the newer BIOS updates for your board? Curious, as I always use the latest UEFI/BIOS updates, including those for my X99 Extreme6/3.1 board. If you do install any UEFI version from 3.20 or newer, from your current 1.20 version, you should also run the two installation programs I listed above, in the order described. It seems that some of the UEFI versions that may have been available in the past for your board were removed. While not listed in the descriptions, the IME firmware, which is part of the UEFI/BIOS file, has been updated in the 3.20 or the previous version. The IME firmware is not updated in every UEFI version, so if you go back to an earlier UEFI version after installing a version that updates the IME firmware, that could cause strange behavior. The IME software is not related to your "slow boot up's". In this case we must be more specific about the PC's start up sequence, which includes the POST process, and then the actual loading and running of the OS. If you had a POST beep speaker connected to the board, and the POST beep option enabled in the UEFI/BIOS, you could tell how long the POST process takes, and then how long it takes to boot Windows 10. X99 boards are notorious for their long POST time, for several reasons. X99 boards are the most complex of any PC chipset board. They normally have quad channel memory, eight memory slots, twice that of other boards. More PCIe lanes (40 vs 16) and more PCIe slots. Ten Intel SATA ports instead of six. All of these things are checked during POST. Plus the X99 chipset is related to Intel's enterprise chipsets, which value stability and integrity over saving time during POST. The other hardware connected to your board affects POST time. HDDs slow down post time, and connected USB devices are slow wake up. The more drives, video cards, etc, connected to the board, the longer POST will be. The fastest starting PC I have is my little DeskMini 110W, with a dual core i3 CPU and two SSDs, using integrated graphics.. A very simple platform takes no time to complete POST. You did not describe all your hardware, so it is difficult to comment further. But X99 boards will never be among those that can complete POST quickly. If you value a fast startup, an X99 system is not for you. ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: Kinetic80
Date Posted: 28 Apr 2020 at 9:22pm
|
I'm having the same issue, and I also have a samsung drive (512GB Evo Pro) installed, along with a RAID of 2xSamsung SSDs 250GB. Did you manage the resolve the issue? |