@forceadmin
Have you tried to set 0x2D4 to 0x1 only, then reboot and dump again? (Do not perform -greset).
If still getting that CPU access error, try running the attached MESET utility from CLEVO, which may override the FD after auto reboot, then dump. (meset.exe is for DOS, meset.efi is for EFI Shell, and Wmeset.exe is for Windows)

@ Ferrous:

I set 0x2D4 back to 0x1, rebooted, ran "fptw64 -d spi.bin", and received the same CPU error.

I then ran meset.exe from a DOS boot prompt and received error, This version of Meset.EXE is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher. I am running Windows 10 Pro x64.

You mistaked command prompt for DOS. Try Wmeset.exe or meset.efi instead

@ Ferrous:

Excuse my ignorance. I ran both meset.exe and wmeset.exe from UEFI Win 10 DVD > Repair > Command Prompt. Both gave me the same error.

I am not familiar enough with EFI shell to know how to run meset.efi.

Run it with the first EFI Shell that plutomaniac gave you

@ Ferrous:

Thank you. I ran meset.efi from the EFI shell that Plutomaniac first sent. The message returned is ME Updated sequence, It will be auto-shutdown ,then power on.

However, it has done nothing since. I am unable to run any further commands. It has just been sitting there at that message for the last 10 minutes.

Edit: After waiting approximately 30 minutes with no activity, I pressed the power button and rebooted. I then ran "fptw64 -d spi.bin" and received the same CPU error.

You have out of software solutions. Have to purchase a hardware programmer.

@ Ferrous: @ Plutomaniac:

I appreciate all of your attempts to help me. Unfortunately, I cannot afford to spend any more time on this issue. I'm very disappointed that a $3,000 laptop that is only 3 years old is in such condition.

Will it hurt anything to leave 0x2D4 at value 0x1? The laptop boots much quicker, runs much faster, & behaves as it should from a power management standpoint (sleep, dock/undock, etc.). Otherwise, it reboots every time it comes out of sleep (including when it docks & undocks). That is a very annoying and time-consuming activity.

There is a new version 11.7.0.1028, but cant download it from Station Drivers...

@ Plutomaniac:

Thanks. I don't have a problem opening the laptop as I have done it before. However, I don't know how to "sort 2 pins at the audio chip". Is there an instruction somewhere? My understanding is that doing this unlocks read/write access to the ME region at the BIOS/SPI chip. I would also need to know what software command(s) to run at the next boot. If the probability is high that this would resolve the issue, I would probably try it.

Zitat von harmoonia im Beitrag #1360

---

Hi!

I got a problem with my Laptop. I am suspecting that there is a problem with ME, because its having power loss exactly after 10min of power up. No help updating bios. Still same problem.
Anyway, i tried to follow the guide updating ME firmware but i ran into problem. MeManuf is giving me a following error:

Error 9331: SMBus hardware is not ready

Error 9296: MEManuf Test Failed

Where exaclty i can find out more information about those error codes and more importantly can i ignore those errors and continue with firmware update?

---