Forum - RE: ME N/A at Z97 ASUS Maximus Hero VII

Win-Raid Forum (Drivers - Firmware - Modding) � Special Topics � Intel Management Engine � ME N/A at Z97 ASUS Maximus Hero VII

Page 11 of 11 � Page 1 ... 6 7 8 9 10 11 Page �

Topic settings

Print view

Jump to forum

General & Forum related Topics News / Announcements Forum-related Questions & Suggestions Off Topic Important Drivers (AHCI/RAID, NVMe, USB etc.) General: Storage Drivers (AHCI/RAID, NVMe and USB) Specific: Intel AHCI/RAID Drivers Specific: NVIDIA nForce Chipset Drivers (incl. AHCI/RAID) Specific: NVMe Drivers Other Drivers System Performance RAID Performance AHCI/NVMe Performance Solid State Drives BIOS Modding BIOS Modding Guides and Problems BIOS modules (PCI ROM, EFI and others) BIOS Modding Requests Reports: BIOS Modding Results Offers: Already modded special BIOSes Special Topics Intel Management Engine CPU Microcodes NVMe Support for old Systems Other Tools (not BIOS modding related) Interesting PC Hardware & Software OS related Topics Windows 11 Windows 8-10/Server 2012-2019 Windows 7/Vista/Server 2008 Windows XP/2000/Server 2003 DOS/Windows 3.X/9X/ME - Retro Gaming Other Operating Systems

#151 | RE: ME N/A at Z97 ASUS Maximus Hero VII datum

Sun Jan 24, 2021 9:24 am (Last edited: Sun Jan 24, 2021 10:26 am)

MEInfo -fwsts givies out :
+ verbose :

Intel(R) MEInfo Version: 9.1.45.3000
Copyright(C) 2005 - 2017, Intel Corporation. All rights reserved.

FW Status Register1: 0x00003406
FW Status Register2: 0x00080000
FW Status Register3: 0x00000000
FW Status Register4: 0x00000000
FW Status Register5: 0x00000000
FW Status Register6: 0x00000000

CurrentState: Disabled and waiting to timeout
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: Transitioning
InitComplete: Initializing
BUPLoadState: Failure
ErrorCode: Image Failure
ModeOfOperation: Normal
Phase: ROM/Preboot
ICC: No valid OEM data, ICC not programmed
ME File System Corrupted: No
PhaseStatus: FIND_IMAGE

HECI device is found to be disabled.

Error 9256: Communication error between application and Intel(R) ME module (FW Update client)

Error 0099: Unknown error code

Error 9256: Communication error between application and Intel(R) ME module (FW Update client)

Error 0099: Unknown error code

Error 9256: Communication error between application and Intel(R) ME module (FW Update client)

Error 0099: Unknown error code

Windows OS Version : 6.2.9200 ""
OS BIOS Support : Legacy

SMBIOS Table Data
SM BIOS Spec Version : 2.8
Starting address: 0x ECF30
Table Size in Bytes: 3729 ( 0xE91 )
Number of Table Entries: the 87 ( 0x57 )

Virtual mapping of complete Table: 2 4kB Pages
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes

Windows OS Version : 6.2.9200 ""
OS BIOS Support : Legacy

SMBIOS Table Data
SM BIOS Spec Version : 2.8
Starting address: 0x ECF30
Table Size in Bytes: 3729 ( 0xE91 )
Number of Table Entries: the 87 ( 0x57 )

Virtual mapping of complete Table: 2 4kB Pages
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes
Table Type 1 ( 0x 01 ) found, size of 27 (0x 1B ) bytes
Table Type 2 ( 0x 02 ) found, size of 15 (0x 0F ) bytes
Table Type 3 ( 0x 03 ) found, size of 25 (0x 19 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 10 ( 0x 0A ) found, size of 6 (0x 06 ) bytes
Table Type 11 ( 0x 0B ) found, size of 5 (0x 05 ) bytes
Table Type 12 ( 0x 0C ) found, size of 5 (0x 05 ) bytes
Table Type 24 ( 0x 18 ) found, size of 5 (0x 05 ) bytes
Table Type 32 ( 0x 20 ) found, size of 20 (0x 14 ) bytes
Table Type 34 ( 0x 22 ) found, size of 11 (0x 0B ) bytes
Table Type 26 ( 0x 1A ) found, size of 22 (0x 16 ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 28 ( 0x 1C ) found, size of 22 (0x 16 ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 27 ( 0x 1B ) found, size of 15 (0x 0F ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 27 ( 0x 1B ) found, size of 15 (0x 0F ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 29 ( 0x 1D ) found, size of 22 (0x 16 ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 26 ( 0x 1A ) found, size of 22 (0x 16 ) bytes
Table Type 28 ( 0x 1C ) found, size of 22 (0x 16 ) bytes
Table Type 27 ( 0x 1B ) found, size of 15 (0x 0F ) bytes
Table Type 29 ( 0x 1D ) found, size of 22 (0x 16 ) bytes
Table Type 39 ( 0x 27 ) found, size of 22 (0x 16 ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 139 ( 0x 8B ) found, size of 54 (0x 36 ) bytes
Table Type 16 ( 0x 10 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 40 (0x 28 ) bytes
Table Type 17 ( 0x 11 ) found, size of 40 (0x 28 ) bytes
Table Type 17 ( 0x 11 ) found, size of 40 (0x 28 ) bytes
Table Type 17 ( 0x 11 ) found, size of 40 (0x 28 ) bytes
Table Type 19 ( 0x 13 ) found, size of 31 (0x 1F ) bytes
Table Type 20 ( 0x 14 ) found, size of 35 (0x 23 ) bytes
Table Type 20 ( 0x 14 ) found, size of 35 (0x 23 ) bytes
Table Type 20 ( 0x 14 ) found, size of 35 (0x 23 ) bytes
Table Type 20 ( 0x 14 ) found, size of 35 (0x 23 ) bytes
Table Type 4 ( 0x 04 ) found, size of 42 (0x 2A ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 136 ( 0x 88 ) found, size of 6 (0x 06 ) bytes
Table Type 13 ( 0x 0D ) found, size of 22 (0x 16 ) bytes
Table Type 221 ( 0x DD ) found, size of 12 (0x 0C ) bytes
Table Type 221 ( 0x DD ) found, size of 26 (0x 1A ) bytes
Table Type 221 ( 0x DD ) found, size of 68 (0x 44 ) bytes
Table Type 221 ( 0x DD ) found, size of 54 (0x 36 ) bytes
Table Type 221 ( 0x DD ) found, size of 12 (0x 0C ) bytes
Table Type 14 ( 0x 0E ) found, size of 20 (0x 14 ) bytes
Table Type 127 ( 0x 7F ) found, size of 4 (0x 04 ) bytes

Error 9256: Communication error between application and Intel(R) ME module (FW Update client)

Error 0099: Unknown error code

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

reply

#152 | RE: ME N/A at Z97 ASUS Maximus Hero VII datum

Sun Jan 24, 2021 2:47 pm

Did you flash the proper/stock/healthy ASUS SPI image with the programmer before running MEInfo -fwsts? It shows firmware corruption.

reply

#153 | RE: ME N/A at Z97 ASUS Maximus Hero VII datum

Sun Jan 24, 2021 3:43 pm

yes, i just redid it again to be sure it was the clean unmodified image from asus site, extracted with uefi tools from "MAXIMUS-VII-RANGER-ASUS-3503.CAP"
same output on meinfo -fwsts or -verbose

reply

#154 | RE: ME N/A at Z97 ASUS Maximus Hero VII datum

Sun Jan 24, 2021 3:50 pm

How did you check that your flash was succesfull?

reply

#155 | RE: ME N/A at Z97 ASUS Maximus Hero VII datum

Sun Jan 24, 2021 3:53 pm

with the CH341A Programmer , after clicking program and writing the file i clicked Verify and it said chip and buffer are the same.

reply

#156 | RE: ME N/A at Z97 ASUS Maximus Hero VII datum

Sun Jan 24, 2021 7:41 pm

Well MEInfo indicates that the firmware is corrupted, it cannot be read properly. Dump the SPI chip with the programmer, compress and attach/link to the result here to double check. Maybe the SPI chip has gone bad?

reply

#157 | RE: ME N/A at Z97 ASUS Maximus Hero VII datum

Sun Jan 24, 2021 8:15 pm

had to leave for work, i wont have access to the system for couple of days, will dump it as soon as i get back, i think something else on the motherboard is faulty, since i got 2 extra SPI chips and they behave the same,
brand new ordered from bios-chip24.com, came pre-flashed with the oficial asus bios, 1 of them i kept in original state for comparison , the other i tried to flash with diferent combos of edited bios in fitc,
i also tried fully unlocked FD and flashed the chip in the actual system, without the programmer .. all same rezults

reply

#158 | RE: ME N/A at Z97 ASUS Maximus Hero VII datum

Sun Jan 24, 2021 9:24 pm (Last edited: Sun Jan 24, 2021 9:25 pm)

Ah yes, if other SPI chips behave the same then the problem is hardware-related and elsewhere. Probably motherboard, meaning Chipset/PCH, where the ME co-processor is located. If it was memory it should have gone away when you swapped the DIMMs because it's unlikely that both are bad. No need to upload a dump anymore.

reply

#159 | RE: ME N/A at Z97 ASUS Maximus Hero VII datum

Sat Jan 30, 2021 6:30 pm

ok, problem solved, got a new motherboard, tested ram and cpu all ok

reply

Optiplex 7010 and VPro/AMT/ME � � TXE 1 clean dump problem

Page 11 of 11 � Page 1 ... 6 7 8 9 10 11 Page �

Please enter a reason for warning.