Please explain what all you need. Sorry, I am not familiar with everything currently needed for hackintosh
1. CPU Microcodes.
2. MSR 0xe2 - PMPatch or UEFIPatch? From the guide you linked, it sounds like this is already user editable within the BIOS, correct? If yes, then mod not needed for this.
3. ?
4. ?
etc.

@Lost_N_BIOS I want 1 and 2 , the rest is not important for me.
thank you very much!

OK, I will try to do, but would like to hear back from @Sylar76 first, so I do not use same method he used which caused brick. Hope you are OK to wait on his reply first, thanks!
Ohh! And so, am I correct, you only need #1 - since MSRx02 is changeable in the BIOS? It's mentioned in that guide you linked, he said Asus already set to user can adjust, unless I misunderstood what he meant?

Zitat

---

Within ASUS Prime X299 Deluxe BIOS firmware 1301 and 1401, ASUS now allows upon my user request for the first time to manually unlock the MSR 0xE2 register within the most recent BIOS settings. This makes the ASUS BIOS firmware patching obsolete.

---

I'll look at BIOS settings now and see

in this link,@kgp give out the tool and patcher.txt
https://www.tonymacx86.com/threads/how-t...d-guide.227001/
thought he said our 1401 need not patch, but unpatched bios 1401 can't work as well as patched bios 1301.

I have the tools to do already, but was reading it's not needed so wasn't sure what was going on since you linked me to the article saying not needed due to visible BIOS option for user to set.

1401 not working "as well as" 1301 is BIOS version differences, this is a strictly yes/no patch, it can either work or not, it can't work semi-better in one BIOS vs another. Correct?
So in 1401 it must already be patched (disabled) and or user accessible to set enable/disabled, otherwise you could not boot to hackintosh w. 1401 due to MSR0xe2 locked correct??

I can run the patch, but seems unnecessary since there is a BIOS option for you to set enabled/disabled correct?

What is your CPUID or CPU model, so when I do the microcodes I be sure that one is updated - Never mind, I see only two need updated anyway

my cpu is i7-7800x（3.5GHz）
i'm sure that the bios "enable/disabled" is correct

Thanks! OK, since MSR0xe2 has a BIOS enable/disable setting, there is no need for the MSR0xE2 mod/patch, you can disable or enable when you need in the BIOS before booting to system.
I can still do the patch, but I don't see a reason to risk further BIOS mod when you have this as a BIOS option to set easily in BIOS GUI.

For CPU microcodes, I am waiting to do the mod until Sylar76 replies, so I don't do it the same way he is. I assume I wont be doing the same he did though, since I've came here now to ask you this question and he didn't
Since you already had one brick BIOS test, I'd like to keep the microcode file the same size it currently is, so less possible issue or failures. Can you do without one of these CPUID's (ie can I remove one, if yes which one)

MSR Lock Control: Disabled（enbale/disabled) if is it ok ?

@Lost_N_BIOS

I've extracted GUID CPU Microcodes and used hex editing. I've always used this technique on my Asus Rampage V Extreme motherboard (x99) as well as on other
motherboards (see my other posts) successfully, so I'm sorry for @zz309 to see his motherboard bricked.

That MSR setting you see in BIOS correct? If yes, then the guide you linked is correct, and no need for anyone to modify the BIOS with MSR0xE2 patches, you can set manually either way in BIOS.

Please let me know about above CPUID question, I can give you test BIOS soon as you reply, since I'm sure this method is not how Sylar76 did the mod that bricked.
Unless he made both files containing the microcodes larger, and if he did, I'm not so either way I think my method would not be same he used since he didn't ask you to drop a CPUID

For hex editing I mean to extract cpu microcodes with UEFITOOL, working via hex editing and replacing the whole microcode body file inside bios.

Maybe this method does not work on any motherboard.

Yes, that's what I planned as well, but possibly different way than you since you didn't ask him same stuff I did. I sent you a PM about this, hopefully we can figure it out for him. You said "File" there is two microcode files, did you see that? I assume so, but since you said file asking to be sure, if you only edited one maybe this is the problem

If my mod with UEFITool fails too, we'll try MMTool for extrac/insert next time, good thing is he can recover easily I think.

@Lost_N_BIOS my cpu ID is BFEBFBFF00050654
@ Sylar76 it dosn't matter, "brick" is my wrong spelling. x299 is very strong to flash again and again

I need to know which microcode you don't care about, don't ever need in the near future. I want to remove one CPUID Microcode

@Lost_N_BIOS ... i really don't known what to choose
so let you make any choice for me