The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Problem with msi gt62 vr. -Request MeSpilock Failed-

    Discussion in 'MSI' started by Mauwi, Oct 7, 2016.

  1. Mauwi

    Mauwi Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    Hi! Could someone help me with this problem, i just cant find the solution on google!!.

    I recently bought an MSI gt 62vr and from the time i recieved it to now it has just been awesome!.

    But today I played a game (the Witcher 2) and after that i restart the Notebook.
    The problem comes when it just simply dont restart normally.

    I waited for about 15 minutes and the screen with the restart message did not change a bit.
    So I press the power button and wait the notebook to shut off.

    Then the notebook took a long time initiate (about 6 minutes) and a black screen showing the following message:

    (A7) Me FW Downgrade - Request MeSpilock Failed

    When it finally appears the windows screen I checked the device manager and I saw something strange.

    The intel managment engine interface appears with an alert sign and a message appears when I click on it and it says:

    This device cannot start. (code 10).
    STATUS_DEVICE_POWER_FAILURE

    The notebbok is just 2 weeks old (from when I recieved It) and now it takes an about of 4 minutes to start (It should not because it has a samsung 950 pro, and before this problem, the notebook's time to start was an about of 12 seconds.)

    Could someone help me to fix this.
     
    Mauwi, Oct 7, 2016
    #1
  2. t456

    t456 1977-09-05, 12:56:00 UTC

    Reputations:
    1,959
    Messages:
    2,588
    Likes Received:
    2,048
    Trophy Points:
    181
    Translation:
    The system tried to revert to an older version of the ME, but it could not lock the SPI eeprom in order to do so. So ... Windows 10? Could also be a very nasty virus, trying to insert itself in a very dark, ominous place.

    Either way, reflashing the latest bios should clear it. Alternatively, since you don't really need Intel ME, just de-install the device (although that may not remedy the delayed start). Could also use this work-around, but that may actually result in a successful downflash (or rootkit install). Think flashing the bios should be the first attempt.
     
    t456, Oct 7, 2016
    #2