Results 1 to 9 of 9
  1. #1
    New ROGer Array
    Join Date
    Jan 2018
    Reputation
    10
    Posts
    4

    Intel Management Engine causing BSOD?

    Operating System
    ==================
    Windows 10

    Computer Specs (PSU, GPU, CPU, RAM, Motherboard)
    ==================
    Motherboard: ASUS ROG MAXIMUS IX HERO

    CPU: i7 7700K

    BIOS: Version 1203 (Latest)

    RAM: 32GB Corsair DDR4

    GPU: MSI GTX 1080

    PSU: Corsair 600W

    SSD: Samsung 960 EVO 512GB



    Description of problem
    ==================
    Over the last few days my computer's stability has become almost unusable (I believe after a Windows update occurred). I frequently get BSODs with varying error messages such as CRITICAL_STRUCTURE_CORRUPTION and others. Interestingly, I also get an array of error messages regarding the Intel Management Engine whenever I POST (booting proceeds as normal after this). The error messages have changed over the last few days as the BSODs have become more frequent, and the current message it displays every time I boot is:


    "Error sending end of post message to ME: HECI disabled, proceeding with boot"


    Cause/Steps to recreate the issue
    ==================
    Normal use of PC (browsing, etc) randomly causes BSOD. Intensive tasks such as gaming don't seem to increase BSOD frequency. Anywhere from 10 minutes to 12 hours.

    What I've tried so far to resolve the issue
    ==================
    1) Updating my BIOS to the latest, 1203

    2) Antivirus / antimalware checks with Windows Defender, MalwareBytes and HijackThis. All come back clean.

    3) sfc /scannow


    At the moment I'm trying to update the Intel Management Engine to its latest versio (which I meant to do when the vulnerabilities were announced a month or two ago but completely forgot). This is where I'm running into problems.


    ASUS' website says the latest BIOS revision should bring my Management Engine's firmware to the latest version, however when I look in the BIOS, my ME Version is: 11.7.0.1229, which is a version from early 2017. I believe I should be aiming to be on version 11.8.50.3425 here? (According to: https://rog.asus.com/forum/showthrea...E-DRIVER/page7 ).


    ASUS have a bunch of tools and stuff for updating the Management Engine on their website (https://www.asus.com/us/Motherboards...Desk_Download/) and none of them seem to work as expected. The "MEUpdateTool" dated 2017/11/22 (3.71MB) simply tells me "Please check MEI Driver is installed."


    So, I download the "Intel ME V11.7.0.1045" tool (dated 2017/12/26 on ASUS' website) which opens up an Intel application called "Intel Management Engine Components" which tells me "This platform is not supported."


    After some more research, I was told to try running "FWUpdLcl64.exe -FWVER" to get the current firmware version. This returns:


    "Error 8193: Fail to load MEI device driver (PCI access for Windows)

    Above error is often caused by one of below reasons:

    Administrator privilege needed for running the tool

    ME is in an error state causing MEI driver fail

    MEI driver is not installed

    Error 8757: Display FW Version failed."



    I also saw on various forums that people were able to see the Intel Management Engine within Device Manager. I do not have it listed there at all. It is also not listed as an 'Unsupported Device' as if it was missing drivers or anything - Device Manager shows no warnings for any device; the Management Engine simply isn't there.


    I've also tried all of the above while booted into Safe Mode to no avail.


    Any help would be greatly appreciated, I'm sort of at a loss at this point.


    Many thanks in advance.

  2. #2
    ROG Guru: Grand Master Array
    Join Date
    Oct 2012
    Reputation
    339
    Posts
    15,255

    Intel has acknowledged that their Meltdown & Spectre microcode is causing the BSODs. It should be solved in the next BIOS release.

  3. #3
    New ROGer Array
    Join Date
    Jan 2018
    Reputation
    10
    Posts
    4

    Quote Originally Posted by Chino View Post
    Intel has acknowledged that their Meltdown & Spectre microcode is causing the BSODs. It should be solved in the next BIOS release.
    Thanks for your reply Chino. Do you have any links to further reading about this?

  4. #4
    Banned Array JustinThyme PC Specs
    JustinThyme PC Specs
    Laptop (Model)G752VY-DH72
    MotherboardRampage VI Extreme
    ProcessorI9 9940X
    Memory (part number)64GB DDR4 8x8 Corsair Dominator Platinum 3800 MHz @ C17
    Graphics Card #1ASUS Strix 2080Ti O11G @ 2.1GHz
    Graphics Card #2ASUS Strix 2080Ti O11G @ 2.1Ghz
    Graphics Card #3ROG Nvlink
    Graphics Card #4Have to feed animals
    Sound CardExternal Audioengine D1 24 bit 192kbps DAC
    MonitorASUS PG348Q @ 100Hz
    Storage #1Intel 905P 480GB U2 flavor
    Storage #2Samsung 850 EVO 1TB X2 in RAID 0, 960 PRO 1TB DIMM.2_1
    CPU CoolerHeatKiller IV PRO and VRM blocks ,Dual D5 PWM serial, 2X 480, 1X 360 RADS
    CasePhanteks Enthoo Elite 8X LL120 PWM, 3X LL140 PWM, 12 SP120 PWM 1x AF140 PWM
    Power SupplyCorsair AX 1500i
    Keyboard ASUS Claymore
    Mouse ASUS Spatha, Logitech MX Master
    Headset Sennheiser HD 700
    Mouse Pad ASUS ROG Sheath
    Headset/Speakers Audioengine A5+ with SVS SB-1000 Sub
    OS Win10 Pro 1809
    Network RouterNetGear NightHawk X10
    Accessory #1 NetGear Prosafe 10GBe Switch
    Accessory #2 Qnap TVS-682 NAS modded with I7 CPU

    Join Date
    Nov 2013
    Reputation
    144
    Posts
    3,858

    Sorry to hear you are experiencing this after trusting Intel to unscrew their screw up.
    Personally this has been there for a very long time, it was a mistake IMO to go public with this so some butt plug could have their 15 mins of fame. Now its common knowledge and all the hackers know about it. Would have been better addressed by keeping it under wraps until they had a viable solution that would not cause more issues and time to test it. Then go public with it and have the tools to address it at the same time.

  5. #5
    ROG Guru: Orange Belt Array restsugavan PC Specs
    restsugavan PC Specs
    MotherboardRAMPAGE VI EXTREME
    ProcessorCore i9 7980XE
    Memory (part number)64GB GSKILL TRIDENT-Z RGB 3200
    Graphics Card #1ASUS ROG POSEIDON 1080Ti
    MonitorSAMSUNG UD590D
    Storage #1INTEL600P 1TB
    Storage #2WD 4TB External HDD
    CPU CoolerNZXT KRAKEN 62
    CaseCorsair Carbine 540
    Power SupplyCorsair AX1200i
    Keyboard Microsoft
    Mouse Microsoft
    Mouse Pad ASUS
    Headset/Speakers Sony
    OS Windows 10 2019 Insider Preview 19002.1
    Network RouterD-LINK
    restsugavan's Avatar
    Join Date
    Sep 2017
    Reputation
    39
    Posts
    435

    Only Coffeelake and Skylake X were safe.

    https://newsroom.intel.com/news/firm...enter-systems/

    intel lastest found microcode that fixed Spectre for Sandy Bridge Ivy Bridge Skylake and Kabylake also bring system reboot follow Haswell and Boardwell, Next week they’ll release another Beta microcode for test again. There are only Coffeelake and Skylake X were safe within minimal performance hit as seen.

    *https://newsroom.intel.com/wp-conten...load-table.pdf
    Last edited by restsugavan; 01-20-2018 at 02:36 PM.

  6. #6
    New ROGer Array
    Join Date
    Jan 2018
    Reputation
    10
    Posts
    4

    Thanks for the responses guys. For anyone else stumbling across this thread with similar issues, this information might help you:

    I've used Steve Gibson's InSpectre tool (https://www.grc.com/inspectre.htm) to temporarily disable Spectre and Meltdown protection until a better fix is found, so far this seems to have increased system stability a bit; I'm now on 6 hours without a BSOD.

    My issue with Intel Management Engine appears to be unrelated, but according to a user on the Win-Raid forums, my Management Engine Storage is corrupt and needs re-flashing. You can read more about that here:

    https://www.win-raid.com/t596f39-Int....html#msg46661

  7. #7
    New ROGer Array
    Join Date
    Jan 2018
    Reputation
    10
    Posts
    4

    Just as a follow up to all of this - I figured I'd try re-seating my RAM one DIMM at a time. Turns out I have one faulty DIMM. The system wouldn't POST at all with just the faulty DIMM. Removing the faulty DIMM now gets rid of the HECI disabled error and allows me to update the Management Engine as expected. I'm not sure if this has resolved my stability issues - only time will tell.

  8. #8
    ROG Guru: Brown Belt Array MrAgapiGC PC Specs
    MrAgapiGC PC Specs
    MotherboardAsus Maximus XI Code
    Processor9900K
    Memory (part number)CMK32GX4M4B3600C18
    Graphics Card #1STRIX-GTX1080ti-O8G-GAMING
    MonitorAOC AGON AG2701QX (2)
    Storage #1Samsung 960 EVO 256GB
    Storage #2Kingston Savage 500GB
    CPU CoolerNzxt X74 360mm AIO
    CaseNzxt H700
    Power SupplyEVGA 850 G2
    Keyboard Logitech G810
    Mouse Asus Spartha
    Headset Hyper X Cloud Revolver S
    Mouse Pad Hyper X Fury S 900mx420mm
    Headset/Speakers Logitech Z337
    OS Windows 10 64btis
    Network RouterTpLink Archer C9
    Accessory #1 EKWB FANs all of them
    MrAgapiGC's Avatar
    Join Date
    Nov 2011
    Reputation
    17
    Posts
    1,710

    Quote Originally Posted by Chino View Post
    Intel has acknowledged that their Meltdown & Spectre microcode is causing the BSODs. It should be solved in the next BIOS release.
    I know Chino is a problem. but until know i work 4 asus machines 2 7700k and 2 8700k 2 heroIX, 1 Hero X and 1 z370-E and are doing ok. On my Z370-E was the thermal paste of the AIO cooler plate. i as felling like a idiot. but that did the trick!

    Intel really, as we say here, put all 5 legs on the ground. i hope these get fix. i have wird artifacts on boot. and I know is these. since i check. but is stable on my 7700k hero ix

  9. #9
    Administrator Array Silent Scone@ASUS's Avatar
    Join Date
    Mar 2016
    Reputation
    124
    Posts
    1,832

    Quote Originally Posted by GLaDOSDan View Post
    Just as a follow up to all of this - I figured I'd try re-seating my RAM one DIMM at a time. Turns out I have one faulty DIMM. The system wouldn't POST at all with just the faulty DIMM. Removing the faulty DIMM now gets rid of the HECI disabled error and allows me to update the Management Engine as expected. I'm not sure if this has resolved my stability issues - only time will tell.


    It's something in the ucode itself that causes the issues. It's not related to the ME firmware as best to my knowledge.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •