Windows 10: Meix64

Ich hab den Fehler gerade bekommen kann mir einer helfen oder Erklären warum dieser Fehler kommt?

:)

 

Intel Management Interface driver causes constant MEIx64 errors in WIndows Event Log

Windows Update just installed this update:

Inter-Other Hardware- Intel(R) Management Engine Interface

Successfully installed on 8/20/2015

This update causes constant MEIx64 Event Codes 1,3 and 4 to be written to the System Event Log. I am running a clean install of Windows 10 on a Dell XPS 8700 computer. I noticed this problem last week while installing these drivers from the Dell website
so I reinstalled WIndows 10 purposely avoiding this update. I reported the problem to Dell but I think they ignored it. How can I remove this update.

Windows Update doesn't give me the option to remove it.

 

Very slow boot-up time (over three minutes)

Hi,

There was many events that was dropped during the boot trace, but there is enough data to undertake a troubleshooting.





First, the majority of the delay happens in the Session init phase. in this phase the OS primarily load and initialize drivers.

I have identified two suspect drivers:

• NoMachine Hub that causes a boot delay of 12s. Windows try to reload the catalog to check the code integrity for this driver because it's a non-embedded-signed driver. So try to upgrad to the latest version of NoMachine application.

• But the biggest delay is caused by Intel Management Engine driver ( 90 s)

you have the version 11.7.0.1057. There is a newer version available on the Intel website Download Intel® Management Engine Consumer Driver for Intel® NUC Kit NUC7i3DN

Update this driver and see if that help.

Finally take another boot trace.

 

Windows 10 with Bitlocker - April 2018 Windows update causes Audio and other devices to fail

We've installed the April 2018 Windows updates for Windows 10 Pro 1709 on several laptops, and the laptops no longer appear to have any audio devices, and other devices are marked as failed. All laptops have Bitlocker enabled on all internal disks.

The laptops are a variety of Dell laptops (a mixture of XPS 15s and Inspiron 15s) with RealTek audio soundcards, which were working prior to installing these updates. All of the laptops have Bitlocker-encrypted disks and have the latest BIOS and driver updates
applied.

According to winver, the O/S build is now 16299.371, and the following updates were installed:

• KB4093112
• KB4018350
• KB4018347
  
• KB4018288
• KB4018330
• KB4093110

The following issues were found in Device Manager:

• The entire Sound controller subtree is missing
• Under "Human Interface Devices", the
  • "I2C HID Device" has the status "This device cannot start. (Code 10). {Device Timeout} The specified I/O operation on %hs was not completed before the time-out period expired."
    • Under "Resources", IRQ is set to 0x33, and there are no conflicts.
• Under "System devices", the
  • "Intel(R) Management Engine Interface" has the status "This device cannot start. (Code 10). STATUS_DEVICE_POWER_FAILURE"
    • Under "Resources", it reports that "This device isn't using any resources because it has a problem."
  • "Intel (R) Smart Sound Technology (Intel(R) SST) Audio Controller" has status "This device cannot start. (Code 10). STATUS_DEVICE_POWER_FAILURE"
    • Under "Resources", it reports that "This device isn't using any resources because it has a problem."

The System event log reports a repeating series of the following 3 events:

• Source: IntcAudioBus, Event ID: 2, Level: Error, Description: "The description for Event ID 2 from source IntcAudioBus cannot be found. ..." (the rest of the standard text that occurs when no description is available has been omitted as there was no additional
  information)
• Source: MEIx64, Event ID: 3, Level: Error, Description "Intel(R) Management Engine Interface driver has failed to perform handshake with the Firmware (FWSTS0: 0x94000245, FWSTS1: 0x80118306)."
• Source: MEIx64, Event ID: 4, Level: Error, Description "The Intel(R) Management Engine Interface is being disabled."

The latter two events occur 15 seconds after the first, and typically we get 5 of these sequences after booting up, spaced about 15-30 seconds apart.

To see if it is related to Bitlocker, we provisioned a new laptop without drive encryption and applied the patches to update it to the same level as the other laptops. The audio device remained available, even after power cycling. After we encrypted the drives
with Bitlocker, the audio device disappeared.

Is this a known issue with one of the patches, and if so, does anyone know when can we expect a fix for it?