MEInfo -fwsts

Here, in case of any future problems with Intel tools (meinfowin, FW Update, FPTw), be sure you are using the ones included in this package, as I mentioned the FTK may be outdated - https://mega.nz/#!CF1l1LJK!K2l6_74FPsGig...Rvp8Efj8a5drZSc

On meinfowin -verbose - You must press a key to continue, to show rest of report, before it gives you the prompt back, it will be 2-3x longer than the current shown image results.

The MEInfo -fwsts output doesn't look correct either? Please download the tools above and use those instead of anything in FTK package.

Thanks Lost_N_BIOS,

this is the output of -fwsts and -verbose:

You're welcome! All looks good to me, I can't see the issue, hopefully plutomaniac will be able to spot the problem.

Thanks plutomaniac! Ray, go ahead and order a CH341A programmer, might as well since they are so cheap. I would suggest this over new BIOS chip too, that way you'll have it for any future BIOS issues with this board or others.

FPT is blocked by FD to writing ME region, so FPT wont help. FWUpdate tool we already used, that leaves only CH341A flash programmer to redo the ME region of the BIOS, unless you want to short pins?
If you want to short pins, method is shown in this guide (Section E/E1) [Guide] Unlock Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing

You can try re-writing the BIOS region with FPT (Without unlock needed), that could fix it since ME appears to be OK right now, but it may be ME issue we can't see and we can't fix that with FPT unless you do the above short.
fptw -rewrite -bios -f Z77EXT43.00

If you do the above short and unlock FD, run these commands after it's unlocked and before rebooting (Use the ME mod BIOS I sent you for all these above and below)
fptw -rewrite -f Z77EXT43.00
fptw -rewrite -me -f Z77EXT43.00
fptw -greset

thanks for your advice.
I will order a CH341A programmer. There is a specific version i need to buy or any CH341A programmer it's ok?

when i buy it, i need to do pinmod and after that fptw -rewrite -bios -f Z77EXT43.00 with your bios modified? These are the steps?

Any will be OK, cheaper usually is longer wait, but you can find seller closer to you usually for $8-12 if you are in a major hurry. Black/gold one seems to read/write a bit faster.

When you have programmer no pins mods or anything is needed, you'll pull BIOS get a verified backup and copy that to upload here, someone can copy over your board specific details (Serial, UUID, LAN MAC ID etc) and put into new BIOS.
Then you simply write that to your BIOS chip and your done.

Pin mod is only necessary for now, without programmer. You can do the FPTw command you mentioned now without pin-mod, that is only writing to the BIOS region which is unlocked.
Pin mod is necessary to write to ME usually, with FPTw, FW update tool can write to it without pin-mod which you already did and that updated the ME but did not seem to fix the issue.

If you do the pin-mod, the last three fptw commands I mentioned above apply, because then your FD will be unlocked and you'll be able to write to the ME with FPTw

So, to clarify -

This can be done now, without pin-mod, this will only rewrite the BIOS region. This might help, but we think the issue is ME region not BIOS region, but always worth it to try this since you can.
fptw -rewrite -bios -f Z77EXT43.00

Pin-mod is required to do the below commands, these will first rewrite entire BIOS, second rewrite ME region only, third reset ME state.
fptw -rewrite -f Z77EXT43.00
fptw -rewrite -me -f Z77EXT43.00
fptw -greset

fptw -rewrite -bios -f Z77EXT43.00

all clear! GBE and PDR region not found. At the end a message show me "bios are identical". Rebooting -> load defaults settings -> the problem still remains...

OK, looks like ME region is the issue as suspected. You can try again using the FW Update tool and ME I posted in post #8, be sure to use fwupdlcl from the package I linked in post #18

Try with this command this time instead
fwupdlcl -f me.rgn -allowsv -forcereset

now i've used your package...
fwupdlcl -f me.rgn -allowsv -forcereset works fine in ~15 seconds.
At the end of the procedure it rebooting the pc. -> the problem still remains.
I have cleared CMOS using the jumper -> the problem still remains.


EDIT:

this guy resolve the problem with a SPI programmer: https://forums.tweaktown.com/asrock/5406...red-bios-2.html

Hoped the FW update tool would fix a second time around, but hopes weren't too high since it didn't the first time.
You probably will have to get programmer as we mentioned, or do the pin mod (that will allow full FPT -rewrite which is same as having a programmer)

Ok than i will order a CH341a programmer:

- pull off bios chip from the motherboard
- insert the chip on the CH341a's socket
- load the bios and make a backup of it
- clear all bios and reprogram with your bios v3.00 custom update
- insert the bios chip on the motherboard and boot pc

these are the steps?

Yes, that is close. Few things to be aware of, first pay attention to the direction the BIOS chip is in now, there is a notch/half circle on the BIOS and matching notch on the socket, same notch will be on controller socket, these always have to line up.
Second, when pulling the BIOS chip out, if you did not get a chip puller, be very careful because they legs bend super easy especially the closer you get to having the chip fully removed.
Wiggle up upward little at a time from one side then the other, sort of rocking with upward motion, for that use some type of hard sturdy plastic wedge if you can find something like that, so you don't scratch or crack the chip.
If you can't find something like that, use tiny flat screwdriver with some black tape or something over the tip so it's not at hard on the chip
And as mentioned the closer you get to having it out be more and more careful. Once it's out, you can put it into the programmer halfway or so, you don't have to push all the way down, that way it's easier to remove once you are done.

Also, when making your backup, make 100% sure after you load and read the BIOS, before hitting save, that you use verify and it says buffer/memory and chip match, that way you are certain you have a verified backup before you write anything to the chip.
If you are unsure, send the backup here for checking before writing anything to the BIOS, or you might loose your board specifics. Sometimes you may have to use a few versions of the program before finding one that works perfect for your chip.
Here's several versions, and the driver needed - https://www.sendspace.com/file/gtcmvd

And, no on the BIOS to use. You will upload BIOS backup from the programmer here, so we can then edit your board details back into a stock clean BIOS, then you'll flash that back into the board.
You can go ahead and program in the current 3.00 BIOS and see if it fixes your issue, which it should, but you might loose windows activation, and LAN MAC ID due to all details missing.
But we can do the fixed BIOS later after that w/ details from your backup once you're back up and running again (That can be reflashed or programmed)