Solved Wake from Hibernate - Mysterious Intel Management Engine Interface

Sorry for the long & rambling post but I thought if anyone was having this issue my story might help. This post concerns the System #2 in the My Computers below.

I have had a minor irritating issue for the past few months or so. My ASUS desktop hiccups when I move the mouse to wake it out of Hibernation. Moving the mouse should awaken the PC obviously, but what would result is the Power LED lights, I hear a fan whirring, but no awakening. If I didn't move the mouse and just pressed the Power button to wake the machine the problem still occurred. So I'd do a hard reset and it would take a few seconds of me holding in the Power button and it would shut off then I'd immediately push and release the button and the machine would start normally. This problem would occur intermittently. Sometimes the PC would start normally without the hiccup, but recently this hiccup would be the nor.

Since the cure was simple I didn't pursue research into the problem until it happened to my wife and then I knew I had to do something. I just figured there was an issue with the power button switch, dust or something interfering with the contacts. But I reasoned this couldn't be as the LED lit up and pushing the Power button still worked. I was going to remove the front panel to access the button. But I was in the Device Manager for something else and noticed an orange triangle on the Intel Management Engine Interface entry under System. Exploring this revealed the statement: Intel Management Engine interface - code 10. There were no events recorder because it showed that the module never started. The driver for this was TeeDriverW8x64.sys

I thought there must be a connection between my problem and this driver, TeeDriverW8x64.sys, file version: 11.7.0.1045 Driver Date Oct 3, 2017 signed by Microsoft Windows Hardware Compatibility.

Turning to Google I found dozens of people back in the mid 2010s had a problem with the Intel Management Engine Interface causing virtually all of them to have the Blue Screen Of Death, and none of them posted about my issue. No one could advise a cure. All the suggestions about getting an updated driver from their motherboard manufacture, or their system's manufacturer, failed to resolve their problem. A couple users said they disabled the driver and that did solve their problem, but deleting the module or driver was not possible.

Since my system is from August of 2015 the ASUS web site didn't recognize this driver. The Motherboard is H81M-E/M51AD/DP_MB. Intel's web site was of no help either, they only suggested the ideas above.

I was a tad concerned about disabling the driver not having a solid understanding about the function of the Intel Management Engine Interface was. But I took the leap and disabled the driver. And that worked! I have yet to find any problems in disabling the driver. From what I've read the module is only important for things like remote access and that kind of communication with one's PC.

There are some posts on this forum about the IMEI but none directly addressed by "wake from hibernation" issue.

I am seeing hints that my system has not even been using the module, since the driver reported that it has never started in the first place.

I am also guessing that Windows Update had installed the Intel driver so time back. I have recently blocked driver updates using the tutorial Enable or Disable Include Drivers with Windows Updates in Windows 11

Anyone have this issue?
John

oops, looks like the issue is not resolved! The awake-from-hibernation is back. Dang, maybe I'll have to do a repair in-place upgrade with the Win10 22H2 iso.

So, after a Repair Install In-Place Upgrade the Intel Management Engine Interface still reports the error:
This device cannot start. (Code 10)
STATUS_DEVICE_POWER_FAILURE

It looks like, from the Event Viewer details that it first had a problem starting, then was configured, then was deleted. It must have tried again because it then reports the same attempt, it had a problem starting, was configured, then was migrated. It finally gives the notation: requires further installation. But there's no hint as to how to do that.

Attached is a text file of the Event Viewer notes with a jpg of the Viewer. I'll have to see in the morning if Google comes up with anything further I can use. I'm assuming that the hiccup in the awakening from Hibernation is going to continue.
John

starchase said:

Intel Management Engine

Click to expand...

So, I don't know when this article was written but, you might want to look at it.
Don't know if it is important or not:


Again, I don't know how relevant this is either:

Thanks, I will look further on this page.

starchase said:

Thanks, I will look further on this page.

Click to expand...

I have edited my comment . Look at the other site (Asus)

Thanks, I'll keep that link to Asus at hand. But I tried working with the IEMI updates but found I already have the latest driver, and even installing the previous driver gave me the same warning symbol in Device Manager showing the same message:
This device cannot start. (Code 10)
STATUS_DEVICE_POWER_FAILURE

The UEFI entry for ME FW Version shows N/A in my Advanced area! I think I'm going to try uninstalling the Intel Management Engine Interface from the Device Manager and see if that resolves the issue. I'm seeing hints that it was there because of Windows 8.1 which was the original OS when I bought the machine.

I did successfully wake the machine out of Hibernation this morning. But that may not mean anything, as occasionally it would do that anyway!

I'm also thinking of installing Windows 11 23H2 using the In-Place Upgrade Repair, to see if that shows a change in the ImeI installation. I can always restore the Win10 image I'll make just prior.

starchase said:

Moving the mouse should awaken the PC obviously

Click to expand...

Incorrect. When in Hibernation, the system is completely shut down. In that regard, it is no different than performing a shutdown. What is different is that prior to shutting the system down, the system will save the contents of memory to a hibernation file, then it performs the final shutdown. Upon starting the system back up it reads the contents of the hibernation file and puts you right back where you left off. The advantage of hibernation is that the system is using zero power in this state because it is completely shut down. As a result, a system can remain in hibernation indefinitely.

In fact, a typical behavior is for a system in sleep, or extremely low power available, to transition to Hibernation so that no data is lost when the battery is depleated.

If the system behaves any differently, for example if it does react to the keyboard or mouse, this indicates a problem and signifies that the system has not fully entered hibernation (shut down).

One of the first things that I always look at for these types of problems is Fast Startup. Check to see if Fast Startup is enabled. If so, disable it and then see if you have better results. To disable Fast Startup:

Control Panel > Power options > Choose what the power buttons do > TURN OFF fast startup

hsehestedt said:

Incorrect. When in Hibernation, the system is completely shut down. In that regard, it is no different than performing a shutdown. What is different is that prior to shutting the system down, the system will save the contents of memory to a hibernation file, then it performs the final shutdown. Upon starting the system back up it reads the contents of the hibernation file and puts you right back where you left off. The advantage of hibernation is that the system is using zero power in this state because it is completely shut down. As a result, a system can remain in hibernation indefinitely.

In fact, a typical behavior is for a system in sleep, or extremely low power available, to transition to Hibernation so that no data is lost when the battery is depleated.

If the system behaves any differently, for example if it does react to the keyboard or mouse, this indicates a problem and signifies that the system has not fully entered hibernation (shut down).

One of the first things that I always look at for these types of problems is Fast Startup. Check to see if Fast Startup is enabled. If so, disable it and then see if you have better results. To disable Fast Startup:

Control Panel > Power options > Choose what the power buttons do > TURN OFF fast startup

Click to expand...

Thanks for the information. I used Hibernation for the reasons you state, but I didn't correlate the relationship between using the mouse to arouse the machine from its Hibernation. And, yes, I do have Fast Start enabled, so I will change that and see if there are any changes.
Many thanks.

Whenever you set up a new machine the most important command is:
cmd (admin)
powercfg /h off

POLYSIUS said:

Whenever you set up a new machine the most important command is:
cmd (admin)
powercfg /h off

Click to expand...

In your opinion! Can you please explain why?

POLYSIUS said:

Whenever you set up a new machine the most important command is:
cmd (admin)
powercfg /h off

Click to expand...

I'm using Hibernate on purpose, so I disagree with you. I prefer this to Sleep since it saves the work and doesn't use power.

And to address the other question above (If the system behaves any differently, for example if it does react to the keyboard or mouse, this indicates a problem and signifies that the system has not fully entered hibernation (shut down), my mouse does permit me to wakie the machine:

@starchase, now that I think about it, I may be incorrect on that point (mouse not being able to wake system from Hibernate). I recall now that there are BIOS settings on some systems that allow this.

If your mouse can wake the system from a shutdown, then it can also do so from Hibernate.

My apologies for that error.

BTW, like you, I rather like Hibernation (on some systems). I use it fairly regularly on some of my systems. I sometimes will be in the middle of researching something and I have a dozen or more Windows and apps running. Suddenly I will realize that the sun is starting to rise and it's time to get an hour or two of sleep. Hibernation makes so easy to just save everything as it so I can resume from exactly that point when I get back up again.

Well, I've done all I can do, but I think the error that had been occurring has stopped. I think it may have been the Fast Boot. I disabled that (now boot time is 90 seconds to log in, and a little more till all is loaded in the Desktop). Thanks #hsehestedt for the suggestion.

I also decided to Google the error statement in the Event Viewer under Log Name: Microsoft-Windows-Kernel-PnP/Device Configuration 411, and a page from MiniTool came up . I tried the Clean Boot like it suggests but the 411 error still appeared at the 2:13:30 time stamp, but does not appear at my most recent boot at 3:55PM today. So I have hope!


So I then disabled Fast Boot (reportedly Fast Boot helps start you PC faster after a shutdown, Restart isn't affected).

Anyway, the hiccup has actually disappeared before these solutions were implemented, so I don't know for sure if the fix is completely gone. Time will tell. Thanks for all your suggestions.
John

So, a day later and after numerous times of waking up from Hibernate I haven't seen the hiccup, so I'll call this solved and hope it never comes back. I think the Fast Boot may have done it (I now have it disabled) or uninstalling the device in Device Manager, the Driver tab of the Intel Management Engine Interface Properties dialog - one of these 2 things. After a month or so I'll probably enable Fast Boot and see what happens.

starchase said:

So, a day later and after numerous times of waking up from Hibernate I haven't seen the hiccup, so I'll call this solved and hope it never comes back. I think the Fast Boot may have done it (I now have it disabled) or uninstalling the device in Device Manager, the Driver tab of the Intel Management Engine Interface Properties dialog - one of these 2 things. After a month or so I'll probably enable Fast Boot and see what happens.

Click to expand...

I wish I had kept the thread on another forum that did mention that, IME was at fault for some problems and they advised to uninstall it
and delete the driver in Device Manager as well. I'll try to retrace my steps and find that post again.

Actually I did delete the device itself today. Curiously the result in the Device Manager was that while the entry for the IME was gone a new entry appeared under Other Devices, an orange triangle with PCI Simple Communications Controller, with no driver showing for it! So it became Wack-A-More. Either way there was an entry to deal with - or ignore. And deleting the PCI SCC device just reappeared on reboot. So I reinstalled the IME. Weird.

Could you take a look at this page ?

Yes, from that page I've obtained the Intel (R) Management Engine Interface V11.0.0.1155 which I used today to reinstall the IMEI as well as reflashing the BIOS, ver. 0802 which I've had on my machine for a while now. I thought I'd go ahead and reflash it just to make sure it installed everything it was supposed to. But it didn't change anything on the PC except to engage again Fast Boot, which brought back the restart hiccup on the restart after the reflash, which had me a bit nervous thinking of the possibility of me having to do a Hard Power Off right after the BIOS flash ended. But I didn't brick the machine, thank God! I did go ahead though and disable Fast Boot, and the couple times I rebooted after that it powered off and on OK. So I think I'm OK now.

I had previously thought about downloading the Intel (R) Chipset Driver V10.1.1.8 on that page but I don't know how to confirm which current chipset version this PC is on now, or where it is installed to look at it.

starchase said:

current chipset version this PC is on now,

Click to expand...

Again, I don't know how much help this will be but: