1.Extract SiInitPreMem，GUID:A8499E65-A6F6-48B0-96DB-45C266030D83. 2.Search "C786....000000....00"，".." is any HEX value. 3.The first place of “....” is not important，the second place of "...." will show "8000" or "0001" , "8000" means maximum 64GB , and "0001" means maximus 128GB. 4.Replace "8000" with "0001" , and you can use 128GB on it.
I can see the same hex pattern in Z170/Z270 BIOS , but I don't know whether SKL/KBL can support 128GB or not. Most MSI Z370 motherboard already have "0001" in their latest BIOS , so they should be ready for 128GB RAM.
@Lost_N_BIOS The "Mod all" including "Invalid BIOS" , but not include "OEMID mismatch". "Invalid BIOS" will show when BIOS were modified. But sometime Gigabyte change OEMID, so "Invalid BIOS" bypass can not bypass OEMID check.
@Lost_N_BIOS I use that version to avoid some careless people flash wrong model , I usually provided that edition with my modified BIOS. And here is the official 0.74.
To my understanding , what we need to do is only add 50652 uCode using latest BIOS , that's all. ASUS just let us boot with B0 ES ? We can't mod this to other motherboard ?
I post the result here: For supporting QL33(or whatever kaby CPU) on P310 , just need 3 step: 1.Dump BIOS with SPI Programmer , and dump DMI information use AMIDEWINx64. 2.Replace BIOS Region of dump with P320 official one(download from Lenovo website.). 3.Flash hybrid file to device. And write DMI information back use AMIDEWINx64.
The BIOS Region of P310 and P320 can be in common use.
And I've done something extra, I made it support Coffee Lake before flash.
I found 07261C8F-9F27-4409-BD78-2BB0B691F331_OemAutoDetectWLAN and 3FEDD4A3-8112-4534-8DB2-E886EB35075E_ErrorMessage containing WLAN card device id , and by removing ErrorMessage module and change jz to jmp in OemAutoDetectWLAN , I was succeed. But if I remove ErrorMessage , the machine can not boot from USB anymore. I found removing ErrorMessage module will cause this problem. [[File:OemAutoDetectWLAN.png|none|auto]] If I do not remove ErrorMessage , it will show "Error 1802: Unauthorized network card is plugged in - Power off and remove the network card." And it will stuck here , can not boot into system. I can find these strings in IDA , but I don't know how to find which function referenced to them. [[File:ErrorMessage.png|none|auto]]
Zitat von davidm71 im Beitrag #1019Just wanted to report that using DSanke’s 2003 Apex X mod that the voltage regulation is spot on what it should be on the 9700K which use to be on my old Z270-WS that had all the voltage issues not being accurate. Even the bios properly identified the cpu. Something to be said about using an actual Coffeelake bios vs modding a Kaby Lake bios for Coffeelake. Anyhow we need a separate thread or rather @dsanke please start your own separate thread so we can discuss in our own topic flow.
Thanks
if port BIOS donor and receptor have the same pwm controller , then the voltage adjustment usually work. like m10a/m9a m10h/m9h , and many msi/asrock z370/z270.
Did you use Flash Image Tool to replace ME? If not so, that's the problem. When you use UEFITool or Hex Editor to replace ME Region, you can not transfer settings stored in ME Region. And it will cause various issues like long time post or other.
Try set AC Load Line and DC Load Line to 1.6 for your 9900K ,and both SA IO 1.2v to see if XMP works.
Zitat von Lost_N_BIOS im Beitrag #2@dsanke , to confirm, please check MEInfoWin.exe -verbose Please also show me image of output of >> MeInfoWin.exe -fwsts
The Dell Alienware X51 R3 which have MSI manufactured Z170 motherboard , and I am modifying it for kaby/coffee lake support. But after I flash BIOS , it doesn't boot anymore. I found Boot Guard was enabled.
Is there is any way to make Intel Boot Guard disabled?
Zitat von plutomaniac im Beitrag #2I don't understand what you're saying. If you are talking about me_cleaner, I don't provide support for it. Instead, you can open an issue at its developers' github page.
Use me_cleaner to cut COR SKU ME FW, whitelist MFS, and it will become 2.5MB.It can be put into ASUS/MSI's flash chip, but other need change flash chip from 64Mb/128Mb to 128Mb/256Mb for larger ME Region. Now remove FF at the end of FTPR partition. Move MFS forward to make ME FW less than 2MB so that it can fit every motherboard's Flash Chip. That's what @shixinyuan have done.
The reason for this is we found COR SKU ME with Reserved bit can run Xeon on non-C PCH.
the same problem here. i have modified it to run cfl cpu. with 1070 , i5 8400/9400f work without issues. with 1060, i5 8600t error code 43. i tried clevo and msi mxm vbios but it doesn't work too. i also tried edit subsystem id for graphic card(to clevo and asrock) but it doesn't work too.
Anyone success boot 16 threads? Without porting Z370 BIOS Region, I can only get 16 threads run on Gigabyte and ASRock motherboards. All others stuck at Logo. ASUS M8I debug light show different code with 8700K 96 B2 99 B4 99 A2 A9 with 9900K 96 B2 99 and stuck here. I tried remove 0639408B-19A6-4B5D-BAFB-12A2F5114032 Acoustic but it doesn't help. When I remove that module , it even can not boot with 8700k.
Zitat von Lost_N_BIOS im Beitrag #19Thanks @dsanke - when you mentioned CPU logic, I was thinking of something else I guess. Do you know if that does same thing as PCIE Patcher here on forum?
ASRock BIOS also have a logic regarding 906E0 as 506E0. And always return "1" for 906E0. I modify it always return "1" regardless of CPUID.
Win-Raid Forum (Drivers - Firmware - Modding) » Search for dsanke's content 
Sun Aug 11, 2019 8:21 am