One again thanks for the wisdom. I am monitoring and expect Assimilator! to enlighten us all on the results. Meanwhile I have the modified bios you worked for me loaded on my chip ready to go; if needed.
Just to refresh, my biggest issue was not being able to get the latest and most apropos C600 series Intel Management Engine Interface, which is very fine right now thanks to you.
Grüß Gott
@ClarenceE - what all mods did I do for you before, do you remember? If you want, once Assimilator1 confirms it’s all OK, you can send me a copy of your BIOS and I can apply this mod to your already modified BIOS
Well, this is odd, flashed the bios & it booted fine, & once I got rid of the logo I could see it said 4801-NVME 
(& I saw an extra drive appear in the boot menu, PATA SM, which IIRC is the bios seeing the NVMe drive but mislabelling it?).
But that bios introduced an odd problem that I couldn’t see any connection to! Lol.
Anyway, I noticed the default ‘auto’ cpu vcore was below default at 0.93v ish, no probs I thought as I’d planned to manually set it to 1.14v, & the VCSSA to 1.11v anyway. On rebooting & going back into the bios I saw it set the vcore to 1.5 (shite!!) & VCSSA was still just below 1, rebooting & trying other values had no effect, switching to offset mode & putting in values had no effect, setting back to auto put them back to down to ~1v (phew). Then I realised I’d forgotten to load optimised defaults, Doh! So I did that, but then the vcore & VCSSA was stuck at just under 1v anyway, no matter what I put in.
So even though I couldn’t see how the 2 features were connected, I flashed the bios to the one I’d modded (adding NVMe support), & the cpu vcore & VCSSA voltages behaved as they should (& the PATA SM was visible in the boot menu, but of course no NVME is shown on the post screen 
).
So sadly, it seems, that somehow the POST message screen edit has had some very bizarre side effects knocking out manual voltage control for (at least) vcore & VCSSA.
Any chance you’ll be able to fix that?
@Assimilator1 - Yes, I disabled Fast Boot, and disabled boot logo, then increased post delay time to infinite (until user pushes ESC), so I could take you those images.
PATA SM or PATA something is what NVME mod BIOS always says I though, until you set things up properly, then sometimes it might change to windows boot loader or something like that. Sounds like you don’t have all settings exactly as you did before possibly?
But yes, the rest does sound odd! Not sure how anything I did would cause that, but we can narrow it down and confirm if you want, I edited two modules for this, so I could send you mod BIOS with only one each and you could see which causes that.
Then I could take the module we know causes that, and try inserting with different tools/methods, in case certain tool is causing that on the rebuild?
If you want to get started and do that test, here is two BIOS to check, #1 - POST only has the POST module edited #2 - DMI - only has the other edit, which shows up in CPU-z, windows etc.
http://s000.tinyupload.com/index.php?fil…820862262912781
If it is due to the POST edit, I can try inserting that with a few other methods and see if that matters or not.
I’m confident the edit itself is fine and not part of this issue, I think that may be more due to how it’s reinserted and rebuilt, possibly messing with some other module.
If we can’t make it work, then we can just not include that edit, and have it to where you only see in CPU-z and other in windows type info apps.
I just hit the pause button to take a photo of the POST screen ;)… I think that still works, lol, or I just timed my photo right.
Re PATA SM, yea I haven’t installed anything on that NVMe drive yet. Currently still running Win7 from the SATA SSD.
Yea I’d like to get to the bottom of it too, although I’m somewhat concerned about putting 1.5v through my Ivybridge CPU again! But I guess if I just zip into the bios quickly to manually set a voltage then it shouldn’t harm it too much.
I will try those 2 bioses once I have finished stability testing this 4.2 GHz setting. And thanks again for the ongoing work :).
Pause may work still, I didn’t think of that 
Yes, I’m sorry 1.5v may happen in these tests, but I think it’s only way we can find out. Was it maybe a glitch, or did you see it twice and know it was actual/always?
I saw it many times from multiple reboots, vcore displayed in the ‘simple’ view on entering the bios, & confirmed in the advanced section (& monitoring). Didn’t check with my DMM though, wouldn’t have a clue where to stick it for that ;).
That would convince me too, at least we know for sure it wasn’t a one time glitch, but yes without checking via DMM you’d never know for sure, but it’s probably correct 
So, keep it short and get in there and set quick
Will do, been side-tracked by other stuff atm ;), but I will come back to it soon.
Hello …
I really need help and hope you can help me.
Also have an Asus P9X79PRO and the latest modification loaded here, even the old before.
Problem with both is, if I over BUpdater or also over BIOS EZ2 tries to load the mod, comes Security verification failed.
Haber already searched a lot of forum for it but all attempts ran into the void except for one where I hope he had another mod for another board. But at the beginning the problem as I have.
There was probably the problem that the checksum "CHECKSUM = 8" was wrong. How do I get the mod on my BIOS?
Have a addlink S70 1TB SSD NVMe PCIe M.2 2280 (auk1TBS70M2P) on a PCIe 16x adapter card.
Thanks a lot and hope you can help me.
I have solved … a other USB Stick and Flash by standby to push and hold the Update Button
Thanks
@Tigger-Puschelpaw - BUpdater (never useful, nor should be used, for anything BIOS related, useless creation by Asus)
EZ Flash - can never be used for mod BIOS, except on limited older boards.
USB Flashback only, bupdater or EZFlash is not used for mod BIOS.
You must use USB Flashback to flash in mod BIOS. BIOS Must be properly named for USB Flashback, and put onto the root of a small 128MB-2GB USB Stick
Here is stock NVME Mod BIOS for P9X79 PRO (Post #115) - [OFFER] P9X79 PRO BIOS Modded for NVMe SSD (8)
This is odd, I’ve recently got well over a dozen notifications to this thread! Yet there are only 2 replies since my last visit, weird…
Anyway, it’s reminded me to finally test out those new bioses! I’ll do that this afternoon seeing as the weather is rubbish today! 
If I can remember how to do it! lol
Please post your results for us. It is odd about what the recent posts have morphed into being, but I thing the site managers are doing things to put non-pertinent posts to another thread. Just monitoring here. Good information is always important.
Ok, so I’ve tried the #1 bios Lost n bios linked for me on June 20th.
That shows the NVMe on post & manually setting the vcore & vcssa worked fine :). Didn’t try default settings.
So it seems it’s the DMI settings that affected vcore? I haven’t tried the #2 bios seeing as the #1 one worked, but if you need me to try that one too (Lost n bios), then I will.
ClarenceE
Oh, were a bunch of posts moved to another thread? What were they about?
Apparently they were moved. The fellow had a different machine, but I didn’t pay much attention since the issue seemed to not be at all related to P9X79 PRO.
Hello, a happy new year 2,020.
I want to thank @Lost_N_BIOS and @Fernando for the knowledge and help.
I read the whole topic, and decided to do the test with the bios that @Lost_N_BIOS has uploaded in # 204.
It was hard for me to flash bios, apparently the usb memory was very large. Using a 4gb usb memory the result was satisfactory.
As soon as I saw that my bios had “4801-NVME” I did not hesitate and bought a Sabrent Rocket 512gb nvme ssd and a QNINE NVME Adapter with Heat Sink.
I had another problem with the USB when trying to install Windows, but once the UEFI Mod was configured, I could start from the USB memory.
I had another problem with the installation of Windows, apart from removing all hard drives, I had to remove all PCI cards too, the Xfi Fatality pro and a Wifi PCI card. Once windows was installed, I replaced the PCIe cards.
Once Windows was installed, I had the inconvenience that the SSD speeds were not complete, instead of the 3,500mb read / 2,000mb write, I threw 1,700 / 1,700. I started to read and do tests, in the end I moved the ssd nvme to another PCIe and it worked.
Now I have 3,477 mb / 2,525mb.
I have another problem with the 4KiB Q32T1 results, which are less than half, but enough for this week.
SeqQ32T1: 3477mb/s - 2525mb/s
4KiBQ8T8: 1345mb/s - 1374mb/s
4KiBQ32T1: 213mb/s - 150mb/s
4KiBQ1T1: 39mb/s - 146mb/s
Again, my thanks, Bios, for the help, knowledge and skills you have, are a blessing to people like us who don’t have enough $$ to change a whole platform. Many thanks.
My sistem: Xeon E5-1680 v2 @4.4ghz + NH D15S, Asus p9x79pro, 32gb (4x8gb) ddr3 2400 cas 11, Gigabyte RTX 2070, Sabrent Rocket 512gb + QNINE NVME Adapter with Heat Sink, 2TB Caviar Black, Xfi Titanium Fatality pro, Asus PCE-N15, Seasonic Platinum 760w, Antec 900 V1.
P.D. Sorry for my bad english, but I am very grateful and I wanted you to know.
@kdjo - Great to see your success! Yes, those 4K’s all look bad. Is your partition aligned? if you are not sure, download AS SSD benchmark and select the partition and show me image (or just confirm it says in Green - OK in top left box)
Download is at very bottom, little box/package - https://www.alex-is.de/PHP/fusion/downlo…p?download_id=9
¡Thanks for your help! “Is your partition aligned” I don’t know what this is
This is the results:
Sabrent
RKT343.1
stornvme - OK (green)
661504K - OK (green)
476.94gb
Seq: 2881 mb/s - 2374.63 mb/s
4k: 34.5 mb/s - 68 mb/s
4K-64Thrd: 1777 mb/s - 2159 mb/s
Acc. Time: 0.122 ms - 0.053ms
Score: 2100 - 2465
These results are different from Crystal Disk Mark 
Your welcome! Yes, those look OK, but still 4K is not good, but yes they will always be different since they are different tests. Your partition is aligned (due to green - OK)
Try CDM with Zero-Fill, maybe your particular NVME is not good at testing with compressed data (default is compressed). Go to menu at top, settings, test data and then choose All 0x00 (0-Fill)
Does Saberent have a disk application on their website? Check if you have not already, if they have one, download it, and see if it has a clean function (TRIM), not WIPE 
You may also need to look at other users on P9X79 boards results too, if they are similar it may be due to this chipset