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.
← Previous page

    Updating Intel ME Firmware on 15 r2/17 r3 or possibly other BGAs as well

    Discussion in '2015+ Alienware 13 / 15 / 17' started by Vasudev, Feb 19, 2018.

  1. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    12,035
    Messages:
    11,277
    Likes Received:
    8,814
    Trophy Points:
    931
    That's dangerous man you could have killed your mobo. That's the reason I put Beta or untested method before I edited and felt it was safe to use!
    Try downloading intel platform tools from win-raid and use meinfo -verbose output here. Also, download mei inf driver from win-raid.
     
  2. Mofoist

    Mofoist Notebook Geek

    Reputations:
    45
    Messages:
    93
    Likes Received:
    63
    Trophy Points:
    26
    ntel(R) MEInfo Version: 11.8.55.3510
    Copyright(C) 2005 - 2017, Intel Corporation. All rights reserved.




    Windows OS Version : 10.0

    Table Type 54 ( 0x 36 ) found, size of 0 (0x 00 ) bytes
    Table Type 218 ( 0x DA ) found, size of 253 (0x FD ) bytes
    Table Type 218 ( 0x DA ) found, size of 85 (0x 55 ) bytes
    Table Type 0 ( 0x 00 ) found, size of 52 (0x 34 ) bytes
    Table Type 1 ( 0x 01 ) found, size of 83 (0x 53 ) bytes
    Table Type 2 ( 0x 02 ) found, size of 78 (0x 4E ) bytes
    Table Type 3 ( 0x 03 ) found, size of 55 (0x 37 ) bytes
    Table Type 4 ( 0x 04 ) found, size of 186 (0x BA ) bytes
    Table Type 7 ( 0x 07 ) found, size of 29 (0x 1D ) bytes
    Table Type 8 ( 0x 08 ) found, size of 24 (0x 18 ) bytes
    Table Type 9 ( 0x 09 ) found, size of 23 (0x 17 ) bytes
    Table Type 10 ( 0x 0A ) found, size of 44 (0x 2C ) bytes
    Table Type 11 ( 0x 0B ) found, size of 154 (0x 9A ) bytes
    Table Type 12 ( 0x 0C ) found, size of 121 (0x 79 ) bytes
    Table Type 13 ( 0x 0D ) found, size of 39 (0x 27 ) bytes
    Table Type 14 ( 0x 0E ) found, size of 14 (0x 0E ) bytes
    Table Type 218 ( 0x DA ) found, size of 253 (0x FD ) bytes
    Table Type 218 ( 0x DA ) found, size of 85 (0x 55 ) bytes
    Table Type 0 ( 0x 00 ) found, size of 52 (0x 34 ) bytes
    Table Type 1 ( 0x 01 ) found, size of 83 (0x 53 ) bytes
    Table Type 2 ( 0x 02 ) found, size of 78 (0x 4E ) bytes
    Table Type 3 ( 0x 03 ) found, size of 55 (0x 37 ) bytes
    Table Type 4 ( 0x 04 ) found, size of 186 (0x BA ) bytes
    Table Type 7 ( 0x 07 ) found, size of 29 (0x 1D ) bytes
    Table Type 8 ( 0x 08 ) found, size of 24 (0x 18 ) bytes
    Table Type 9 ( 0x 09 ) found, size of 23 (0x 17 ) bytes
    Table Type 10 ( 0x 0A ) found, size of 44 (0x 2C ) bytes
    Table Type 11 ( 0x 0B ) found, size of 154 (0x 9A ) bytes
    Table Type 12 ( 0x 0C ) found, size of 121 (0x 79 ) bytes
    Table Type 13 ( 0x 0D ) found, size of 39 (0x 27 ) bytes
    Table Type 14 ( 0x 0E ) found, size of 14 (0x 0E ) bytes
    Table Type 14 ( 0x 0E ) found, size of 40 (0x 28 ) bytes
    Table Type 16 ( 0x 10 ) found, size of 25 (0x 19 ) bytes
    Table Type 17 ( 0x 11 ) found, size of 112 (0x 70 ) bytes
    Table Type 19 ( 0x 13 ) found, size of 33 (0x 21 ) bytes
    Table Type 20 ( 0x 14 ) found, size of 37 (0x 25 ) bytes
    Table Type 21 ( 0x 15 ) found, size of 9 (0x 09 ) bytes
    Table Type 22 ( 0x 16 ) found, size of 151 (0x 97 ) bytes
    Table Type 32 ( 0x 20 ) found, size of 22 (0x 16 ) bytes
    Table Type 41 ( 0x 29 ) found, size of 26 (0x 1A ) bytes
    Table Type 136 ( 0x 88 ) found, size of 8 (0x 08 ) bytes
    Table Type 176 ( 0x B0 ) found, size of 7 (0x 07 ) bytes
    Table Type 177 ( 0x B1 ) found, size of 14 (0x 0E ) bytes
    Table Type 208 ( 0x D0 ) found, size of 54 (0x 36 ) bytes
    Table Type 212 ( 0x D4 ) found, size of 19 (0x 13 ) bytes
    Table Type 216 ( 0x D8 ) found, size of 11 (0x 0B ) bytes
    FW Status Register1: 0x8030404E
    FW Status Register2: 0x340D0006
    FW Status Register3: 0x00000420
    FW Status Register4: 0x00000000
    FW Status Register5: 0x00000000
    FW Status Register6: 0x00000000

    CurrentState: Unknown (14)
    ManufacturingMode: Disabled
    FlashPartition: Valid
    OperationalState: CM0 with UMA
    InitComplete: Initializing
    BUPLoadState: Success
    ErrorCode: Debug Error
    ModeOfOperation: Normal
    SPI Flash Log: Not Present
    FPF HW Source value: FPF HW Not Set
    ME FPF Fusing Patch Status: ME FPF Fusing patch NOT supported in this FW Version
    Phase: BringUp
    ICC: Valid OEM data, ICC programmed
    ME File System Corrupted: No
    PhaseStatus: CHECK_BUP_OVERRIDE_STRAP
    FPF and ME Config Status: Not committed

    Error 86: Communication error between application and Intel(R) ME module (FWU client)

    Error 81: Internal error (Could not determine FW features information)

    I installed the latest v12 inf as well as ran the setupME using SetupME.exe -tcs -nodrv.
     
  3. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    12,035
    Messages:
    11,277
    Likes Received:
    8,814
    Trophy Points:
    931
    Have you tried installing just inf driver in legacy mode?
     
  4. Mofoist

    Mofoist Notebook Geek

    Reputations:
    45
    Messages:
    93
    Likes Received:
    63
    Trophy Points:
    26
    You mean booting in legacy mode?
     
  5. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    12,035
    Messages:
    11,277
    Likes Received:
    8,814
    Trophy Points:
    931
    yes.
     
  6. Mofoist

    Mofoist Notebook Geek

    Reputations:
    45
    Messages:
    93
    Likes Received:
    63
    Trophy Points:
    26
    Perhaps I'm doing something incorrectly, but I turn secure boot off, swith UEFI to Legacy...then windows fails to load. I moved the hard disk up to #1 in boot order but am still getting a insert bootable media.

    Legacy mode cant read the EFI partition right?
     
    Last edited: Oct 26, 2018
  7. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    12,035
    Messages:
    11,277
    Likes Received:
    8,814
    Trophy Points:
    931
    that's odd, w10 should boot easily. Are you using RAID?
     
  8. Mofoist

    Mofoist Notebook Geek

    Reputations:
    45
    Messages:
    93
    Likes Received:
    63
    Trophy Points:
    26
    Yes. I've tried every possible combination to boot to legacy. Doesn't work.

    Edit: To be clear I'm not sure which legacy you mean.

    First is change UEFI to Legacy which gives me manual control of the boot list. That fails to detect any bootable media.

    2nd is to leave it at UEFI, go secure boot off, and use the "load legacy rom" option. That one begins to load windows, but results in a blue screen with "inaccessible boot device". I have disabled fast startup in windows beforehand.
     
    Last edited: Oct 26, 2018
  9. Mofoist

    Mofoist Notebook Geek

    Reputations:
    45
    Messages:
    93
    Likes Received:
    63
    Trophy Points:
    26
    Ok I got method 2 to work via going into safe mode before switching.

    Right click-installed the latest .inf file and it just immediately pops "operation completed successfully" so same result as before. MEinfo still cant communicate with ME.
     
    Last edited: Oct 26, 2018
    Vasudev likes this.
← Previous page