@Evoliddaw
You are right. They were all wrong in the hashlist file. It seems i didn’t clicked the right Bios file on my PC when i calculated it. I now corrected them. Sorry for the confusion.
I wanted to thank you again for keeping this bios updated with whatever updates may remain or be released for the NVME. Check your paypal.
Hello , I have Crosshair V formula Z and AMD FX 9590 processor ,32 gig Ram . I have tried all the mod available in first post , the problem is my m.2 normally detecting and can see in my computer but unable
to install windows in it !!!
Window setup starts installing once the setups gets ready and restarts the screen directly goes to bios setting not to further installation process. Anyone can help me to install windows 10 in m.2 ??
please.
I know there is some silly step i’m missing but this is first time trying to mod bios!!
Bios updated to v12
Changelog:
[Updated] - EFI LAN Intel PRO/1000 UNDI v9.0.03 -----> v9.1.12
>ASUS-Crosshair-V-Formula-Z-2201 MOD v12 (2020-02-16)<
Thank you for your time and effort.
hi, what happens if you try to boot after the installation? does it always throw you to bios menu? if that’s the case, check the boot device priority, and the certificates and secure boot stuff. If it’s not the case, try to describe the process, detailed as much as you can and what do you see.
I have a microcode updated X570 Creation BIOS. I updated the microcode in it to cpu00870F10_ver08701021_2020-01-25_E0F8186D.bin and it shows that it is updated in HWInfo.
How do I update the AGESA 1.0.0.5 from the beta X570 ACE BIOS into the X570 Creation BIOS?
The ACE and Creation BIOS’s are too big to attach, from my OneDrive.
https://drive.google.com/file/d/1WHHgBGk…iew?usp=sharing
https://drive.google.com/file/d/1RkEoXGV…iew?usp=sharing
@KedarWolf
My recommendation is to not change the AGESA version. Update everything else but not that.
There is no totally safe way to do this. Some Bios has 1 module that must be changed and some Bios has 2 modules. If it is a 2 modules Bios and you change just 1 than your Bios can brick. If the problem would be only that then i would just say do it but be carefull, but… Unfortunately, it is not just that. Those 1 or 2 modules are somewhat integrated or at least made specifically for some rather specific motherboeards and changing modules don’t cover all what is needed to change contrary to the popular belief on the internet. Just changing module(s) never do the job completely. And that is the real problem: It is that everyone wants to update the AGESA and after reports on the internet that it worked and that they were successfull… And they were, technically, not lying because they truly believed they managed to do it. After all, the Bios seems to work… But is practice, the truth is that litlle hidden bugs were created that they didn’t see and did not find right away. Amongst the many bugs possible, it can be the amount of memory that is wrongly reported in the Bios, the CPU overclock is not working, the Cool & Quiet function is not working, good old random BSOD or, to name a last one (and it is my favorite because it is the hardest to spot) the amount of memory in the video card is wrongly reported in the video card software (Catalyst, Adrenalyne, etc).
If you want to try updating the AGESA anyway then i really understand you. I did the same myself and i had to do it to learn by myself that it never worked perfectly. With all that said, if you still want to work on that, i will answer your question:
- You have to find which module(s), 1 or 2 of them, that is related to the AGESA. Usually a research in the modules in the Bios for “AGESA x.x.x.x” or just “AGESA” should enable you to find to right module(s). You may have one module that is obvious by being named AGESA something but the second one is usually a pain to find and requires searching each module to find it (assuming there is even a second one in your Bios).
greetings…
my problem is that it stays on the splash screen. f2 and delete crash on screen. Is there a solution?
@huseyin
First try the “Clear CMOS” function. If it doesn’t work, then i suggest you use the Flashback function. This should repair it. Be sure to use the Bios v12 in post #324. The downloads in the first post are not updated anymore by the owner of this thread.
Hope this help.
I am confused as to post #327 showing Agesa 1.5.0.7. The version in mine is 1.5.0.2 with Bios updated to v12. Is there something that I am missing or does this not pertain to us? Thank you
@MailmanMike
Short answer: It doesn’t really pertain to anyone already realising how this thread works. So no, you are not missing anything.
Long answer: The reference to AGESA 1.5.0.7 in post #327 was related to the first post of this thread that is not updated anymore. This thread came to life and those old downloads links were made at a time when all the possible bugs introduced by any change in the AGESA version were unknown and unnoticed (even by me at that time). Later in that history, the owner of this thread lost the time to keep maintaining it and asked me to take over it. I accepted because i was already modifying and own the Crosshair Formula (non-Z) Bios thread since even before this one existed and both are basically the same Bios (very few differrences in the Bios of the Z and non-Z and the hardware to manage in it).
At that time, at least 6 things happened:
- The owner told me that his lack of time could be temporary so i accepted to take care of it untill he return BUT the ownership of this thread was not passed to me so i have no access at all to the first post and, because of that, the first post was not updated since that time. To be honest, because it was a long time ago, i now doubt the owner will ever return…
- By that time, the AGESA problems was known to me because of all my experimentations with the non-Z version (you can find and read my thread on the non-Z version for more details). So the first thing i did was to do a fresh start and completely remodify the original Bios from scratch to account for that fact. This was the birth of the v1 version. So everything in the first post is older than v1.
- Obviously, this also means i introduced version numbers to simplify things for everyone.
- With no access to the first post, i was forced to post all updates as a normal post (like post #324) which makes it more confusing for anyone new to this thread that are, understandably, starting it by reading everything in the first post.
- Because i have to make a new post for each updates, because i can’t just change the first post and wanted to keep my posts as short (but still clear) as possible, i put all the original changes i made listed in my v1 post and all posts with a subsequent version only contain the changes since the last version before it. Why? Because it was by far simpler for me and also because the total of all changes is in the “changelog.txt” file in the download anyway for anyone who wants to see all the changes at once.
- Because of the last thing, i put the version changes in blue color in my update posts so they are more easy to find.
Hope this post will help clarify and simplify things for anyone new to this thread who reads it.
@Phoenix48
Hello, I’m new to the Forum I was looking in to running a pair of SATA SSD in Raid 0 and came upon this gold thread. I wanted to ask my current sistem runs on a OCZ 256GB SSD and a WD 500GB HDD velociraptor (it’s screaming for an upgrade) can I flash the BIOS with my current setup prior to upgrade or do I have to Fresh install after the Bios?
@RagnaCaT
No, you don’t have to do a fresh install because of the new Bios. You can flash it immediately without any problems. But because you will change from the original Bios, the only precaution to avoid unnecessary problems is to just make sure to clear all the old Bios setings by: Loading the default and safe settings at the first boot, then restart, then enter and save your own personnal Bios settings, then restart again. This ensure any old remnants ghost settings of the original old Bios are truly gone.
Also, and ONLY if your Windows is currently installed in Legacy mode, if you want your Windows to be installed in UEFI mode then you may wish to do a fresh install after the Bios upgrade, and be sure your disks are in GPT before installing, otherwise it will still run in Legacy mode.
Gentlemen and… Ladies possibly?
I strongly recommend you all support Phoenix48 via his PayPal link.
This gentleman is a true enthusiast and has a passion for his work. I asked him if he could do to the A88X-Pro what he did with the refinement and continued support for the CrossHair V Formula-Z. I swear in less than an hour he had it done. I only wanted NVME boot capability (as he did for us all on the Crosshair), but he went above and beyond and ALSO updated the AMD RAIDXpert2 (EFI), AMD RAIDXpert2 (OROM), AMD GOP Driver (EFI), VBIOS Trinity (OROM)v1.58.0.0.0, Realtek UNDI Driver (EFI), and the Realtek Boot Agent GE (OROM).
I also recommend donating to StickMode for the original post and effort on the CrossHair.
Give these gents some coffee money to feed their awesome brains!
The v12 link is broken on post #324. Please repair or re-direct me to another download site.
Thanks for all your hard work!
Sorry, operator error.
Bios updated to v13
Changelog:
[Updated] - EFI LAN Intel PRO/1000 UNDI v9.1.12 -----> v9.2.06
>ASUS-Crosshair-V-Formula-Z-2201 MOD v13 (2020-05-23)<
Thank you for the update, I’ve sent something your way via PayPal. Is it possible to explain how this update improves the system? I am only trying to learn so I can better understand the bios
@MailmanMike
Unfortunately, there is no way to know what is the changelog for a specific module version update. Most companies don’t make the changelog available to the public.
The closest i can give you as a useful answer is that, sometimes, there are some informations in the changelog version of the whole package that Intel provide. Take note that those packages provides all the different Intel LAN modules that are fairly recent at the time the new package version comes out and include the tool BootUtil to use it. So sometimes you can see some infos or hints of the changes between 2 packages versions. If you are interrested in exploring that, you can download the latest package here.