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!

@pershoot

The only reason i changed to NvmExpressDxe_4 is to restore the full functionality of the module like it was in v3 module but keep the improvements of the vSmall module. The _small version was already an equivalent of NvmExpressDxe_4 but some fonctionality were removed to make it small. Those are restored in the ordinary v4 version of the module. Differrences are things that usually no one ever use. Like be able to unload a driver in EFI Shell and some debugging support. Things like that. For more details, see this post about the changes between the _small module versus the old v3 module. As for the speed between both (Small and v4), it is supposed to be the same code that manage it. For more on that part, see this thread.

Nothing else in the bios was touched in the last update and nothing in this bios was ever changed related to the memory. If you get more problems with that, i suggest to test your memory just to be sure they don't have any problems. Windows 10 got some memory test when you can access the boot menu but they are rather generic. Memtest86 or Memtest86+ are even better programs to test memory and test them more deeply.

I installed V14 yesterday, all seems operational .. if anything v14 seems smoother than v12 ...
Booting is fast and the bios seems to do everything to evaluation specs :

Power and powerpack function = operational & all setting available.
CPU functions all work (cpu is quiet on cool and quiet)
all the tabs on the hardware page seem to function, The fan controls work (on monitor page)
Overclock functions (DP)

V14
evaluated by DT

@DukeThrust

Concerning your comment about the spectre/meltdown patch, it all depends on the CPU you have and which microcode your PC is using and also which variant of the vulnerability you look at. The Bios has all the latest microcodes installed and you can easily verify that by using the latest version and database of MC Extractor. But that being said, up to date, of the 11 microcodes that are in this Bios, only 2 of them have received some mitigation patch from AMD. Those 2 are the microcodes 600F12 and 600F20.

Those 2 received the mitigation patch for CVE-2017-5715 [branch target injection], this one is totally fixed with that patch.

They did NOT receive any mitigation patch for CVE-2017-5754 [rogue data cache load] (AKA Meltdown) for the simple reason that all AMD processors are naturally immune to this one and don't require any correction at all.

They did NOT receive any mitigation patch for CVE-2018-3639 [speculative store bypass] because this one was discovered later than the others and i expect that a new patch from AMD will come out for that later in the future.


You can test yourself all your vulnerability by installing the latest version of the "Speculationcontrol" module in PowerShell. You can google it if you don't already have it.

As an example, my CPU is a FX-8150 and is using the 600F12 microcode and this is the report i get with the v14 Bios:

Phoenix48
I just update my motherboard with the modded version (stable orochi 15.0.0.0) and the pc is more stable and the temeprature lows 10 degrees.
How is the situation with the modded bios with orochi 15.0.0.7??

@Fexthor24

Still trying to make it work with the v1.5.0.2 because it is easier (kind of...) before trying to work again with v1.5.0.7.

That being said:

Here is an other try:

BIOS with AGESA v1.5.0.2 updated to v7 Beta

Changelog:

[Changed] - In short: Everything updated the same as the stable v14

[Changed] - AmdAgesaDxeDriver changed to v1.5.0.2 but nothing else related to the AGESA. (AmdProcessorInitPeim is original in this version)

Be warned that any program analyzing the Bios that report the AGESA version by pulling the number from the AmdProcessorInitPeim module will still report v1.5.0.0. Those pulling the version number from AmdAgesaDxeDriver will report v1.5.0.2.

The goal of this version is getting reports to know if all the same problems as in v6.1x are still there or not (see Beta in first post), and to know if new ones appears.