X370 ITX/ac 4.70 UEFI (AGESA 1.0.0.4) released: |
Post Reply |
Author | |
cristy6100
Groupie Joined: 15 Mar 2018 Location: Romania Status: Offline Points: 269 |
Post Options
Thanks(0)
Posted: 04 Aug 2018 at 4:27am |
Ok, so finally ASRock decided to release the UEFI with AGESA 1.0.0.4, bugs fixed:
1. Stuttering/throttling of CPU/GPU 2. They also added GPU overclock options with normal frequency and voltage fields in OC Tweaker, I tested and it works wonders. *They also fixed the rear USB 3.0 ports connected to the CPU/APU not working (they broke them when using the 1.0.0.2 beta UEFI) Not fixed: Chassis Fan 1/W_PUMP RPM drops between 700-1000 RPM when setting control mode to "DC Mode" from "PWM Mode" M.2 drives still appear as removable drives in Windows (safe remove icon) Setting the SATA controller to disabled will not actually disable the SATA controller, HDD will still be detected in Windows Possible bugs that have not been fixed: SATA ports have priority over M.2 slot (try to install Windows 10 when you have a PCIe M.2 drive and SATA drives also, and your M.2 drive will be listed last when selecting the Disk on which to install Windows), it will also be listed last in all utilities that use the numbering the UEFI assigns to disks. M.2 should always be treated by the UEFI to be Drive 0 (when only one M.2 slot, if two slots then Drive 0 and 1 and so on for how many M.2 slots are present) But how can you fix these when you cant even fix the damn M.2 drives to not appear as removable drives within Windows and having a dammed safe remove icon for it, that ironically tells my It cant eject the drive. 10 out of 10 for ASRock for managing the impossible More to come Cheers Edited by cristy6100 - 04 Aug 2018 at 4:54am |
|
Main Rig: AMD Ryzen 2400G | ASRock Fatality X370 ITX/ac UEFI 4.90 | Corsair LPX DDR4 2400@3200 1.35V | Corsair RM650i PSU | CM ML120L AiO Cooler
|
|
wino
Newbie Joined: 30 Sep 2017 Status: Offline Points: 175 |
Post Options
Thanks(0)
|
I have Samsung 960 EVO 250 GB M.2 drive from the beginning (almost a year). I had 2.1, 3.0, 3.1, 3.4, 3.6 and from today 4.7 UEFI and never had this issue. So it's not an ASRock (or this board) problem, but yours. And don't tell me that I have different MB...
|
|
| AB350 Gaming-ITX/ac 10.08 BIOS | Ryzen 5 5600 | G.Skill Flare X 2x8GB @ 3400 14-14-14-28 | Zotac GTX 1050 Ti | Kingston KC3000 1 TB M.2 | SilentiumPC Supremo M2 Gold 550W V2 |
|
|
cristy6100
Groupie Joined: 15 Mar 2018 Location: Romania Status: Offline Points: 269 |
Post Options
Thanks(0)
|
I see you are using a Samsung drive, for me the problem starting after upgrading to 4.50 series UEFI, both my new ADATA SX8200 and my old Lite-On MU-X show this behaviour, the 4.50 update fixed some Samsung nvme drives not being detected in UEFI, after that update this started happening.
Samsung drives use their own driver that removes this issue, but drives that use the default Windows nvme driver will exhibit this issue, but again this started happening after the 4.50 UEFI update
Edited by cristy6100 - 04 Aug 2018 at 2:55pm |
|
Main Rig: AMD Ryzen 2400G | ASRock Fatality X370 ITX/ac UEFI 4.90 | Corsair LPX DDR4 2400@3200 1.35V | Corsair RM650i PSU | CM ML120L AiO Cooler
|
|
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |