Attach the current system dump, we should try to clean the ME region first. However, I don't like the "VSCC_FAILURE" error. It probably indicates that the system uses a different SPI chip from the one it originally shipped with.

Ah, that was not a good idea from his part. He should have chosen the exact same chip or at least one that is very similar. The ME stores firmware at the SPI chip and needs to read and write to that region, the "ME Region" as we call it. The OEM is responsible for adding the required VSCC entries at the Flash Descriptor (and BIOS? - not sure) so that the ME can work with the SPI chip the system ships with. In your case, the ME cannot communicate/work with that different SPI chip, cannot initialize and thus the "VSCC_FAILURE" error. Two options, either use the original 8MB chip (or a new one which is identical to the original) or edit the VSCC entries at FITC to accommodate that new chip and then reflash the SPI image with the modified FD + cleaned-up ME. Problem is, I don't really know how to add these VSCC entries other than the fact that they can be found at FITC > Descriptor Region > VSCC Table. Should be easy enough I suppose if you know the three values that FITC can adjust. Maybe the chip's datasheet can be of help in such case. Either way, there is no reason to cleanup or reflash the ME until it can work with the SPI chip (without VSCC failure).

You must be doing something wrong, I didn't face any error. I followed the cleanup guide with FITC v9.0 and also changed the "VSCC Device 3" entry from 0x17 to 0x18 so now it's what you want, meaning 0xEF , 0x40 and 0x18. Flash the provided SPI image with "fptw -f ge60_dmp_fix.bin" followed by "fptw -greset" command and let me know how it goes after the reset. I'm interested to see if fixing the VSCC problem is that easy and hopefully not BIOS-dependent at all.

So fixing the VSCC Failure error is easy enough. This "Error 9271" might indicate that the VSCC is also checked from the BIOS. Not sure how to alter that but at least the ME now works. The gpu issue, whatever that is, has nothing to do with the ME. It's normal for MEManuf -EOL to show that error since your Flash Descriptor is currently unlocked. Bare MEManuf (no -EOL) should report Operation Passed in green. If you want to lock the Flash Descriptor then use Flash Programming Tool with "fptw -closemnf" command.