1/29/2024 0 Comments Msi z87 uefitool nvme![]() Since the hex code is not identical with the BIOS, which you had modified, it may be a good idea to flash the attached BIOS via USB Flashback and to report, whether your problem has been solved or not. My question: Which BIOS tool did you use?Īttached is the BIOS, where I have just inserted the NvmExpressDxe_4.ffs module “as is” (like you did) into the original ASUS BIOS 2302 by using the AMI Aptio IV UEFI MMTool. Meanwhile I have done some tests while trying to add the NvmExpressDxe_4.ffs module to the original BIOS 2302 for your ASUS Sabertooth Z87 mainboard and got slightly different results by using different BIOS modding tools. Once the current problems have been solved, you can try to update any of the already existing BIOS modules. Since a negative impact of any other BIOS modification on your system can not be excluded, I suggest to concentrate your efforts on being able to boot and to reboot properly and permanently. I agree with regarding the possibilty of an interference between the added NVMe module and any other natively present BIOS module. + You may need to also install NVME driver from here too, unsure? Fernando will have to advise you on that Recommended AHCI/RAID and NVMe Drivers Use v13.2.x.xxxx drivers - Recommended AHCI/RAID and NVMe Drivers * Edit - Here, I used stock BIOS and made you test BIOS with updated RST legacy orom = v13. Are you using the latest BIOS Version, I didn’t check? If not, maybe update to latest version could help too. No, you placed the NVME module in the correct location in the BIOS, that’s all done correctly so it’s not that. Did you try both ways of secure boot enabled/disabled + CSM enabled/disabled, to see if maybe only one of the BIOS RST modules causes this issue (orom Legacy one, or EFI) for your reference Fernando)Īlso, I can make you a BIOS for testing with updated RST orom and EFI modules if you want to see if that helps. What driver are you using, and what is the actual device model? Maybe can suggest best drivers for you? (Current stock BIOS modules both =12. Well I think the oroms could be updated and maybe that could help, but I doubt they are causing this issue, unless there is some known conflict with the current version and your NVME device and you just aren’t aware of the issue/conflict.ĭid you already test a few driver versions in windows? Specific: NVMe Drivers
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |