I keep seeing the post where The Stilt mentioned AGESA v1.5.0.8, sadly, cannot find that anywhere else, maybe he miss-typed (and he doesnt respond to PM’s on either site he mentioned it), otherwise its such a shame that its so difficult to update the AMD “microcode”, sadly my 8350 system I used to play with bricky type things has a few issues supposedly fixed by a newer AGESA but of course, ASRock has no plans to update any of those BIOS’s 
Thanks for all the testing Phoenix48, this may be for an ASUS board, but it pretty much applies to all that I have seen
I am sorry to be a bother, but I’ve looked through this whole thread and can’t seem to figure out where to go to download these BIOS mod(s). So dumb question: Where do you go to download them?
Also, can you please direct me the the latest stable release (that doesn’t have any more problems than the final official ASUS release from 2012 had)? Thanks a TON! I’m trying to get my system up aon running on one of these newfangled 960 EVOs. 
And a HUGE ‘THANK YOU’ to the maker of this mod, Phoenix 48. You absolutely RULE!!! You’re the only person - in this world of 73 BILLION people - who’s done it. That’s awesome!
** UPDATE **
DOH! I found them. Somehow, I didn’t find the links at first. So Version 10 it will be! Wish me luck!!!
BIOS with AGESA v1.5.0.0 updated to v11
Changelog:
[Changed] - NvmExpressDxE_3 -----> NvmExpressDxe_Small
Changes in NvmExpressDxe_Small (see this thread for more details):
- Based on UDK2017 NvmExpressDxe
- Includes bug fixes from UDK2018
- Removed functionality not present in UDK2014 (not supported by AMI Aptio 4 either)
- Removed component name protocol support (useful for debugging only)
- Removed driver unload support (not used outside of the EFI Shell)
- Bug fixes and improvements preserved
- Refactored for smaller code
Had some issues with >CrosshairV-Formula-ASUS-1703.ROM with AMD AGESA OrochiPI v1.5.0.0 mod v11 any overclock would cause a crash in the latest windows 10, fresh install. Seems to be linked to memory timings, still crashes under any heavy loads. Multiple programs running / moving a lot of files all at once.
There’s a weird stability issue with Amd Sata controller v1.3.1.276 and v1.3.1.277 will freeze the system under any crystaldisk random load.
Moved back to >CrosshairV-Formula-ASUS-1703.ROM with AMD AGESA OrochiPI v1.5.0.0 mod v10 as it seems to be the most stable, not a single DPC Watchdog Violation blue screen since moving back to this version. The sata controller is still giving issues. Currently working around this by using the Asmedia port for the boot drive and putting the AMD ports in RAID mode forcing the RAID driver to be used. This makes it the most stable for the time being, run 24 hours with no serious issues.
Thanks for the hard work, your bios mods have kept my machine and my friends machines running stable.
edit not using NVME, test system is an 860 evo sata, two plextor sata drives and a western digital sata drive
@xkronusx
Thanks for the feedback.
Unfortunately, i don’t know what to say about an overclock crash with the v11 because, as written in the changelog in post #83, only the nvme module was changed since v10 and nothing else, and this has no reasons that i can see to affect the overclock. Is your system using nvme? I will try to make some test with the overclock in the week end on my system to see if i can reproduce this and find anything.
@everyone else
Please report if you have the same problem or not with v11.
Also, to those who use their system with nvme, please report if you see an increase in boot speed/performance with the new nvme module or not.
I tried to reproduce the overclock crash but, up to date, i was not able. My system is stable with v11. Unfortunately, i don’t have a nvme disk so i can’t test that part to see if it would make a difference.
Sorry took a while to figure out what the issue was, wanted to make sure I figured it out for sure before posting again.
It’s my buddies machine and it looks like it was a bad SSD causing the crashes, we were running a more complex setup with a raid 0 of two plextor 256GB drives that had been working properly since they were installed
but it looks like one of the drives is failing, pulling it out of the raid and setting them single we found the one drive was having writing errors with anything to do in small randoms and reads, not great but it happens to
a drive that’s 5 plus years at this point.
Sorry for the confusion, I haven’t done much more testing in v11 but at the very least we figured out it was a bad drive.
Cheers.
BIOS with AGESA v1.5.0.0 updated to v12
Changelog:
[Changed] - CPU microcode cpu00600F12_ver0600063D_2013-03-06_0E64F5CB -----> cpu00600F12_ver0600063E_2018-02-07_8187EA3E
[Changed] - CPU microcode cpu00600F20_ver0600084F_2016-01-25_C8460314 -----> cpu00600F20_ver06000852_2018-02-06_893C1544
The MD5 (16) and the SHA256 (64) hashes match, but the WHIRLPOOL (64) does not. Have tried downloading multiple times with the same result: WHIRLPOOL (64) is mismatched. (This is using both the SecurityXploded tool you used and other online tools for hashing the file.)
Could you please be so kind as to re-hash the file using WHIRLPOOL and update your results, notifying if there is any change to your result or not?
Thank you!
p.s. The WHIRLPOOL hash I am getting every time is:
aa10d214fb066a0d713941b30a34c9064c248ef95ded6080d83c6044a23f12f2351356274effe0f81a45bf2302a08b4b8b0117d7d07831be167dbf788e7f535e
Here are my results:
WHIRLPOOL (64) -
aa2614a941290664ac2b08791c79ebf5d6f04bcd2e36e2d60675d795296757ad15831b5260f7e1368c0db4ddfdb9a89e793532afb662436bcea27cac51988c59 (From my original file on my PC and listed in HashList.txt)
aa2614a941290664ac2b08791c79ebf5d6f04bcd2e36e2d60675d795296757ad15831b5260f7e1368c0db4ddfdb9a89e793532afb662436bcea27cac51988c59 (Recheck of the original file on my PC with HashGenerator)
aa2614a941290664ac2b08791c79ebf5d6f04bcd2e36e2d60675d795296757ad15831b5260f7e1368c0db4ddfdb9a89e793532afb662436bcea27cac51988c59 (Check from a download of the file from the server)
aa10d214fb066a0d713941b30a34c9064c248ef95ded6080d83c6044a23f12f2351356274effe0f81a45bf2302a08b4b8b0117d7d07831be167dbf788e7f535e (Your reported result in the last post for easy comparison)
Usually i would say there was a problem in your download but you already said you downloaded it multiple times with the same results. So the way i see it, only one thing remains as a possibility: The program you use to unzip it is maybe doing something wrong and changing something in the file while unziping it. Try with 7-Zip from 7-zip.org, this is what i use and my hash results are OK.
Hey Phoenix. I recently picked up a new radeon card (RX560) and the PC has been acting quite strange with the modded bios. Lots of GPU related lag, PC will BSOD randomly, related to ‘MEMORY’, etc. On the stock bios, lag appears to be gone. Will observe for the BSOD on stock over the course of the next few days. I even went back to a very low memory clock on the modded bios. Same issue with BSOD (gpu still lags (rendering 2d (browsing, etc) throughout).
Letting you know…
@pershoot
Thanks for the report.
Are you using the bios v12 with the original AGESA? If yes, i am surprised that you get problems with your video card because none of the changes in that bios are related to the video card or the memory. All the other bios (in beta version) have some problems with that because of the AGESA change but not this one. I don’t have a RX560 card to test it but maybe other users of the v12 bios have a RX560 and can report if they experience the same thing.
Yup, using v12. im unsure if it has this behavior on previous versions.
Just got the same MEMORY MANAGEMENT bsod after restarting from a day’s worth of uptime on stock bios. Investigating… So the bios is factored out from this specific issue. GPU is running good on stock bios. Unsure what would cause the lag on the modded.
I’ll report back as it may help others if I can find the solution (or upgrade to zen2+, haha).
BIOS with AGESA v1.5.0.0 updated to v13
Changelog:
[Changed] - OROM LAN Intel Boot Agent GE v1.5.85 -----> v1.5.86
There seems to be a reboot issue with v12 Windows; and the bios spectra/meltdown patch is stated as not being in the code!
Thank you for the work…
DT
GPL - Key Storage Providers PKCS#11, and native libraries
Interfaces via YubiHSM KSP, PKCS#11, and native libraries
Crypto enabled applications can leverage the YubiHSM via Yubico’s Key Storage Provider (KSP) for Microsoft’s CNG or industry-standard PKCS#11. Native libraries are also available on Windows, Linux and macOS to enable more direct interaction with the device’s capabilities.
Technical Specifications
Operating System Support
Windows, Linux, macOS
Operating System Version Architecture
Linux CentOS 6
CentOS 7
Debian 8
Debian 9
Fedora 25
Ubuntu 1404
Ubuntu 1604 amd64
Windows Windows 10
Windows Server 2012
Windows Server 2016 amd64
macOS 10.12 Sierra
10.13 High Sierra amd64
https://www.yubico.com/support/knowledge…yubihsm2-tools/
https://www.yubico.com/wp-content/upload…1-windows64.zip
https://eprint.iacr.org/2015/1018.pdf
DT
****
Crypto order
<cipherSuites>
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384_P384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384_P256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256_P256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA384_P384
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256_P384
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256_P256
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256_P384
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA384_P384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA384
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384_P384
TLS_DHE_ECDSA_WITH_AES_256_GCM_SHA384_P384
TLS_DHE_ECDSA_WITH_AES_128_GCM_SHA256_P384
TLS_DHE_ECDSA_WITH_AES_128_GCM_SHA256_P256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384_P256
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256_P256
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_AES_256_GCM_SHA384
TLS_RSA_WITH_AES_128_GCM_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA
TLS_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
TLS_DHE_DSS_WITH_AES_256_CBC_SHA
TLS_DHE_DSS_WITH_AES_128_CBC_SHA
TLS_PSK_WITH_AES_256_GCM_SHA384
TLS_PSK_WITH_AES_128_GCM_SHA256
TLS_PSK_WITH_AES_256_CBC_SHA384
TLS_PSK_WITH_AES_128_CBC_SHA256
TLS_AES_256_GCM_SHA384
TLS_AES_128_GCM_SHA256
TLS_RSA_WITH_RC4_128_SHA
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
SSL_CK_RC4_128_WITH_MD5
SSL_CK_DES_192_EDE3_CBC_WITH_MD5
Fix Windows Meltdown - Patch bat - run admin
https://drive.google.com/open?id=1M3V9ci…e6_cZpK-33vuRbo
from http://science.n-helix.com/2018/01/micro…g-meltdown.html
http://science.n-helix.com/2017/04/boinc.html
http://science.n-helix.com/2017/04/rng-and-random-web.html
CPU Melt/Specter Microcode without Windows patch
https://github.com/platomav/CPUMicrocodes
BIOS with AGESA v1.5.0.0 updated to v14
Changelog:
[Changed] - NvmExpressDxe_Small -----> NvmExpressDxe_4
did some more testing. lowered strap and upped HTT to compensate. seems ok now with regards to memory management BSOD (but, still observing).
flashed v14 to test. same issue; seems to make my system a bit more slower for some sorted reason. any potential patches in there that could be the culprit?
thx for your work!