@Lost_N_BIOS - When the XMP profile is turned on, the CPU does not receive enough voltage
At full load, Vcore was under 1V and I got a blue screen. I mean from 0.6xx to 1V max.
I solved this problem by manually setting VCCIO = 1.175V and CPU System Agent Voltage = 1.1625V. After that Vcore changes depending on the CPU load.
Now core voltage is in the range of 0.6xx to 1.104V.
For now and with these settings, everything works normally and I didn't have any problems. (XMP = 3200MHz)

If Vcore adjusted manually, this voltage would be constant and would not change according to CPU load.
The problem is that I don't understand what all these voltages mean and what they are for.
I only understand CPU Core/Cache Ratio and DRAM Voltage

So, what is CPU VCCIO Voltage,
CPU System Agent Voltage
PLL Termination Voltage
PCH Core Voltage
And what value should be for them?

IO: As the name impies data exchange, so the PCI-E and the closely related DMI lanes
SA: predecessor of the SS, a German... the system agent mostly consist of the RAM controller
PCH: Plattfrom Controller Hub. Formerly known as "chipsets" when they were still sets of multiple chips. Should not be influenced by CFL mods as the Z?70 stays just the same.
PLL: Phased Locked Loop. A technology to generate clocks and/or transform voltages efficiently. So basically there are dozens of circuits using pll and I would like to deliver physical compliments to every UEFI designer who names any option after the technology and not after the purpose it serves. Likewise, there are termination voltages on almost any bus, though the most common one to be changeable would be Vterm of the RAM. This one should not be influenced be CFL mod either, but using old base UEFIs often results in faulty auto RAM settings.

@PCGH_Torsten im not sure if you were talking to me about my issue. But regardless, in my case nvmie doesnt get recognised in bios nor when booting via sata (with windows 10 on a 2.5" drive) or usb with windows 10 installer.
I've tried alredy disabling sata controller or CSM and evry possible combination...

In the picture, M.2 SATA is enabled which will prevent NVME drives from beeing detected. But that should be taken care of by disabling SATA controller alltogether, so a PCI-E problem seems likely. However I do not know to further trouble shoot these.

Same as me. Since i modifies a lot inside of the bios(es) i think there is some kind of conflict or something...
I'm waiting for @Lost_N_BIOS response, if somebody can finure this out it's him. Or else i'll have to return this nvme drive and go with a standard sata m.2...
Finghers crossed q.q

Strange thing is: The M.2 is connected to the PCH, not to the CPU. So its accesspath should not even be modded.

Hi, theres the original stock unmodded bios for my motherboard.
Can you check if there some things in the wrong pathway or something?
It's possible because my motherboard has one mini pcie connector for wifi/bluetooth and one m.2 pcie x4.
But the G20CI (h270) has 2 pcie x4 and one mini pcie.
Those two pcie x4 slots are used for intel optane and or nvme drives.
Maybe there are some conflicts or something.
Here is the link: https://drive.google.com/file/d/1Pfwe9km...ew?usp=drivesdk
Thank you very much!!! :)

@PCGH_Torsten if you need more info, you can pm me.

Hi guys, I need help with modding bios and pinmod map for Gigabyte B250M-D2V (rev. 1.0) to run I5 9400F (SRF6M).
Thank you very much.

First step: Buy a CH341 bios programming tool xD

@ALviK98: Sorry, I know a couple of things about mainboard hardware, but I cannot "read" UEFIs. Technically, H270 simply has four PCI-E ports more which obviously allow to offer a second ×4 link. But those HSIOs were just added at the end of the row. The most likely ports to be used for the [primary] M.2 are lane #15 to #18 as these have native access to SATA controller #0 and #1, allowing support of both NVME and SATA modules without added external circuit. But all this is true for both H170 and H270. So even if the system adresses the PCH differently, it should still handle those ports the same way as before. Do you know if CI offers SATA on both its ×4 capable slots? In that case Asus might have changed a lot more than would be strictly necessary/expected, as H270 does not offer that capability on a second ×4 block. Also on that note: Have you checked any other function relying on PCH PCI-E? If the switch is completely fucked up because it e.g. waits for some non existent HSIOs #26 to #29 to answer, not only M.2 but also USB 3.1. LAN and WLAN could/should fail.

All usb ports are working fine. One more issue is wifi/bluetooth. It isn't working too. But I've found how to fix it through @reactive post about it. He made the same mod as i. But he lost all his fixed and fully patched bios files.
About the pcie/sata support. I think yes, they support sata too since i can see in my modded bios under sata controller (AHCI/ intelt premium controller) an "m.2" slot (empty). So i guess a sata m.2 drive is supported.

That is the primary/only slot in H170. If I understand you correctly, H270 version from which you use BIOS code, has two M.2. The question is, whether this second one does support SATA as well? This would not be a native function of H170/H270 but a clear indication, that Asus has done more than just adding an additional port and routing the additional lanes of H270 to it. (Which is what I would expect as almost all 1xx->2xx upgrades used this copy&paste style which should not cause problems if both additional port and additional lanes are simply not there because the UEFI is used in an H170 system. If however Asus changed a more, there could be quite a number of incompatibilities. In the simplest case your mixed UEFI might look for a bootable drive in the slot that your system simply does not have and disregard the slot and drive you do have.)

Okey, i dig a little bit on the internet, and seems like the G20CI supports both nvme and sata on the m.2 ports. But some claim that nvme drives larger than 256gb wont work.
Also, i had to use CI bios region because it seems like asus implemented some kind of lock or something to deny any microcode upgrade. So, even through modding G20CB bios and manually inserting even kabylake microcodes, kabylake cpus just won't work...
It may be possible to find and undo the bios lock on the G20CB bios but i couldn't manage to do anything about that. Only through G20CI bios region it works with kabylake and coffee lake cpus... Damn Asus engineers...

What about changing sku of my modded bios from H170 to H270? Would that change anything on the settings? If so, how do i actually do it xD