Did you reflash with command I gave at post #14 now, and all was OK? Yes, I see so in your image. And, ME FW was done first, before this, correct?
If yes, you can try this and see if it helps, doubt it, but try, close all apps because reboot coming >> FPTw.exe -greset

Yes, once you have programmer we can fix!

@Lost_N_BIOS went ahead and restart the pc one again, the problem persists.
Will wait for the programmer, thank you !

Yes, I assumed it would remain, not sure why/how that's possible, but I think it's due to something in the ME FW doesn't get corrected when updating it with ME FW update tool.
I can't remember if FPT flash of ME FW can help fix it, it should with -rewrite since all is erased, but most users cannot flash ME FW with FPT anyway without doing pinmod first and unlock FD, or having flash programmer to unlock FD (so at that point, might as well correct all with programmer anyway)

Tomorrow morning my programmer will arrive.
Can you guide me with the necessary steps in order to get this working?
I would like to have the knowledge to do this so i dont havr to wait tomorrow for your respone if possible.

Here is guides, sadly the one with most images to show how to use has all the images missing due to photobucket/tinypic are crap photo hosts these days
[GUIDE] Flash BIOS with CH341A programmer
[Guide] Using CH341A-based programmer to flash SPI EEPROM
[GUIDE] The Beginners Guide to Using a CH341A SPI Programmer/Flasher (With Pictures!)

Main thing, open software (all versions) and on the "Auto" Function, uncheck erase and blank check. That way nothing gets erased accidentally.
Then dump BIOS by >> Read, verify, and if chip/buffer match then save. Then do nothing, send me that to check and to grab your details from to put in new BIOS, this way you know you have a good backup before you erase or write anything, this also lets you know what version software works or not for your chip.
Give me your BIOS chip ID, in case I need to tell you use a certain version or certain software, or other than exact ID

Here is general CH341A software package - http://s000.tinyupload.com/index.php?fil...695330485827902

Once confirmed you have good backup, I will make you new BIOS to program in.

Did all the steps, verified and saved backup https://imgur.com/a/DEK7Zdn

This is the backup you asked for http://s000.tinyupload.com/index.php?fil...391871230658092

https://imgur.com/a/l36KUDA

@alekskz - that was quick, didn't think it would arrive for another day or two! This is why I asked you for chip ID. For W26Q64FV you need to use software 1.30 or 1.34 and W25Q64BV ID
Otherwise writes will fail. Usually though, read is OK, so you may be fine to not do another dump, but be sure when you write back you use BV ID otherwise writes will always fail.

Do erase, then blank check, then open file and hit auto (read/verify). Then, if power cables not removed from board already, disconnect the 8 and 24 pin, press and hold the case power on button for 10-15 seconds or short pins for that long, then let it sit without power for one minute.
This will reset ME FW state. Then connect all cables, boot to BIOS, load defaults sand save/exit, reboot back to BIOS, make some changes and away you go

I tried to preserve your NVRAM, but in case it's part of the issue I also included BIOS without your original NVRAM only stock one.
Fix.bin has your NVRAM, try first. Then if no luck, use FixNoNV.bin
http://s000.tinyupload.com/index.php?fil...667319442917178

https://imgur.com/a/W3JZ9EI

All done, everything is working as it should be
you are a great human being, thanks for your help!

@alekskz - Great to see!! So, did first one Fix.bin work fine? You're welcome!

Wait, Image says bad write? What happened? Did you have to use FV on your board instead of BV like I suggested? If yes, maybe it's only certain boards or certain batches of those FV that need to use BV?

The fix.bin worked
First time it said bad write and i tried again and it worked and said something like "...it matches"
Either way, i can now oc my cpu and ram, the per core option is there as it should
Thanks !

I wonder why it failed first time? Did you forget to erase/blank check maybe? If not, then maybe cable just jiggled loose a little bit or something.
Yes, chip and buffer match = good to go

Thanks for confirmation on which BIOS worked, now I know, at least sometimes, when this happens it's not a problem in the NVRAM area.
I think some bytes at ME FW aren't able to get fixed with the ME FW update tool, so ME FW re-write with FPT and unlocked FD via pinmod, or full BIOS re-write via flash programmer is only way to fix this.

Good to hear your can OC now and all the per core stuff is back too! Told you we'd get it fixed in a hurry once you had a programmer

Now that you have that, you can always recover any board from bad BIOS flash too, and you can make/test risky BIOS edits anytime you want, because you can always recover, such a lifesaving tool for such a small amount of $$

Zitat von Lost_N_BIOS im Beitrag #26

---

I wonder why it failed first time? Did you forget to erase/blank check maybe? If not, then maybe cable just jiggled loose a little bit or something.
Yes, chip and buffer match = good to go

Thanks for confirmation on which BIOS worked, now I know, at least sometimes, when this happens it's not a problem in the NVRAM area.
I think some bytes at ME FW aren't able to get fixed with the ME FW update tool, so ME FW re-write with FPT and unlocked FD via pinmod, or full BIOS re-write via flash programmer is only way to fix this.

Good to hear your can OC now and all the per core stuff is back too! Told you we'd get it fixed in a hurry once you had a programmer

Now that you have that, you can always recover any board from bad BIOS flash too, and you can make/test risky BIOS edits anytime you want, because you can always recover, such a lifesaving tool for such a small amount of $$

---

It happens! Plus, those clips are a major pain to get perfect, I fought one with a board tonight for about 20 attempts, and then had to do it all over again to put back the BIOS I wanted after done testing and bricking on purpose

haha lol

Normally I can use other tool I have instead of using clip, I have a PCB with pins underneath that site on top of / jumpers over BIOS in place, but on MSI boards this doesn't work properly due to some resistor on the PCB (That or I haven't tried exact same chip on that board yet)
So of course, have to be the mos difficult way to do it on the most difficult board to recover = brick testing on purpose. If I wasn't testing something that bricked on purpose, then it would have been some other board I could recover much easier, always my luck