Overclock.net banner
1 - 11 of 11 Posts

Noariss921

· Registered
Joined
·
7 Posts
Discussion starter · #1 ·
2-3 days I can’t go to the website to download UEFI, update, because I’m sitting on 6042, it’s BETA, and I have a problem: the computer itself can freeze, and then UEFI does not see my SSD (this is after the UEFI update), it was not before was (at least I don't remember). Now I can't go to the site -_- so I'm looking for a newer version from someone, because I doubt there will be an update for my motherboard, because there is no off page, maybe because of this photo (below), maybe not .

P. S. If anyone knows the above SSD issue please let me know, it might not be a UEFI issue but a board or SSD issue. My SSD: ADATA XPG Gammix S11 Pro 512GB.

Rectangle Font Brand Logo Parallel
 
Well, there's some good news at least. The bios files for download remain accessible via direct link. My notes bellow are for what I remember regarding the X470-F, but same should be valid on the Prime as both MBs share bios number versions with near simultaneous releases:
Please try the following:
https://dlcdnets.asus.com/pub/ASUS/mb/BIOS/PRIME-X470-PRO-ASUS-5861.ZIP (1.2.0.3 Patch C final, last without EDC bug as we haven't got 1.2.0.A yet)
https://dlcdnets.asus.com/pub/ASUS/mb/BIOS/PRIME-X470-PRO-ASUS-6023.ZIP (1.2.0.6b beta, likely first with proper X3D support/boost, but only mentioned on 6024)
https://dlcdnets.asus.com/pub/ASUS/mb/BIOS/PRIME-X470-PRO-ASUS-6024.ZIP (1.2.0.6b final)
https://dlcdnets.asus.com/pub/ASUS/mb/BIOS/PRIME-X470-PRO-ASUS-6042.zip (1.2.0.7 beta/final , 6042 was later moved from beta to final without file change. First with fTPM stutter fix)
https://dlcdnets.asus.com/pub/ASUS/mb/BIOS/PRIME-X470-PRO-ASUS-6061.zip (1.2.0.8 beta, security fixes)
https://dlcdnets.asus.com/pub/ASUS/mb/BIOS/PRIME-X470-PRO-ASUS-6063.zip (1.2.0.8 final, latest that was availabe on the support site)
 
Discussion starter · #5 ·
Well, there's some good news at least. The bios files for download remain accessible via direct link. My notes bellow are for what I remember regarding the X470-F, but same should be valid on the Prime as both MBs share bios number versions with near simultaneous releases:
Please try the following:
https://dlcdnets.asus.com/pub/ASUS/mb/BIOS/PRIME-X470-PRO-ASUS-5861.ZIP (1.2.0.3 Patch C final, last without EDC bug as we haven't got 1.2.0.A yet)
https://dlcdnets.asus.com/pub/ASUS/mb/BIOS/PRIME-X470-PRO-ASUS-6023.ZIP (1.2.0.6b beta, likely first with proper X3D support/boost, but only mentioned on 6024)
https://dlcdnets.asus.com/pub/ASUS/mb/BIOS/PRIME-X470-PRO-ASUS-6024.ZIP (1.2.0.6b final)
https://dlcdnets.asus.com/pub/ASUS/mb/BIOS/PRIME-X470-PRO-ASUS-6042.zip (1.2.0.7 beta/final , 6042 was later moved from beta to final without file change. First with fTPM stutter fix)
https://dlcdnets.asus.com/pub/ASUS/mb/BIOS/PRIME-X470-PRO-ASUS-6061.zip (1.2.0.8 beta, security fixes)
https://dlcdnets.asus.com/pub/ASUS/mb/BIOS/PRIME-X470-PRO-ASUS-6063.zip (1.2.0.8 final, latest that was availabe on the support site)
You don't know what the problem might be:
I click to reboot the PC>reboot goes on>the screen goes blank>and the diode in the monitor flashes for 15-20 seconds, and after that it reboots... I don’t remember this on the old BIOS, maybe I forgot something... I know the problem on AMD, with a long starting or booting, but this surprises me...
 
Oh, finally. Yesterday when I posted the site was still down, so I had to look for the direct links on archive.org and rename from known later -F bios links.

My X470-F always had a false start from a cold state (fans spin up/down, psu clicks as on a reset, fans spin up/down again and it finally posts), either with bios 5861 (on 5800X/2600X w/ 4x8GB), 6042 (5800X3d w/ 4x8GB) or as far back as 4024 (2600X w/ 2x8GB, no NVME yet), iirc also every time after saving+exiting bios to apply new settings (can't confirm for you now, not near that system). AFAIK it was normal and widely reported on these Asus boards (and the CHVII), depending on user non-Auto settings on bios that can only be finally applied after it has started once (likely memory+voltage related).

OTH, it does a regular single boot showing POST on screen without any retry when rebooted from windows (w10 fast startup is disabled). Maybe yours is having some issue with current memory settings+training, or you have disabled the Fast Start on bios settings so it has to repeat the process all the time.

For the previous NVME thing, you might check if there's any firmware update for it. Your OS could be freezing if it's on the NVME and it drops (maybe event viewer will have frequent stornvme errors). I'd nearly exclude some instability on the IOD leading to PCI-E losses (even if caused by different auto vsoc/vddg among bios versions, which can depend on ram speed), if the NVME remains dead after the reboot and only wakes up after a complete power cycle -- sorta points to itself.
Monitor its temps to see if freezes happen after it starts to throttle, re-seat it and look for any dust, or check if on the lower secondary M2 slot (slower connection to chipset instead of cpu) the issues persist. Ideal situation would be cloning and trying on another nvme, but you wouldn't be asking if the option was readily available. Just to troubleshoot, temporarily back down ram speed to what amd specs as max for your cpu (not 3600 if it's the case), just to be sure IOD is under spec and needs no further voltage adjustments.
 
Discussion starter · #7 ·
Oh, finally. Yesterday when I posted the site was still down, so I had to look for the direct links on archive.org and rename from known later -F bios links.

My X470-F always had a false start from a cold state (fans spin up/down, psu clicks as on a reset, fans spin up/down again and it finally posts), either with bios 5861 (on 5800X/2600X w/ 4x8GB), 6042 (5800X3d w/ 4x8GB) or as far back as 4024 (2600X w/ 2x8GB, no NVME yet), iirc also every time after saving+exiting bios to apply new settings (can't confirm for you now, not near that system). AFAIK it was normal and widely reported on these Asus boards (and the CHVII), depending on user non-Auto settings on bios that can only be finally applied after it has started once (likely memory+voltage related).

OTH, it does a regular single boot showing POST on screen without any retry when rebooted from windows (w10 fast startup is disabled). Maybe yours is having some issue with current memory settings+training, or you have disabled the Fast Start on bios settings so it has to repeat the process all the time.

For the previous NVME thing, you might check if there's any firmware update for it. Your OS could be freezing if it's on the NVME and it drops (maybe event viewer will have frequent stornvme errors). I'd nearly exclude some instability on the IOD leading to PCI-E losses (even if caused by different auto vsoc/vddg among bios versions, which can depend on ram speed), if the NVME remains dead after the reboot and only wakes up after a complete power cycle -- sorta points to itself.
Monitor its temps to see if freezes happen after it starts to throttle, re-seat it and look for any dust, or check if on the lower secondary M2 slot (slower connection to chipset instead of cpu) the issues persist. Ideal situation would be cloning and trying on another nvme, but you wouldn't be asking if the option was readily available. Just to troubleshoot, temporarily back down ram speed to what amd specs as max for your cpu (not 3600 if it's the case), just to be sure IOD is under spec and needs no further voltage adjustments.
Thanks for the tips.

1) The problem is not in memory or voltage, because all settings give the same effect.
Also, resetting UEFI settings doesn't solve the 15-20 second problem, and there are three options:
1.1 Board.
1.2 SSD.
1.3 Windows (more on this below).
2) There is one more problem:
PC freezes, blue screen (errors are different, as far as I remember there are three of them, and Dump is not saved...).
The PC reboots automatically and I get this error:

"Reboot and select the correct boot device or insert the bootable media into the selected boot device and press the key"

After that I quickly go into UEFI and there is no SSD in the lower right corner (but it is physically connected and in the priority list it is, in UEFI), it is also not in the list of connected drives (when you enter UEFI, right in the middle, if you don't understand, I will attach a photo later), so I think it is the SSD or the board. But first I will reinstall Windows because Windows created extra disks…

3) Might have to change the SSD, unfortunately I don't have another SSD to check. But there is another problem that I discovered. When I installed Windows 11 I chose GPT format and today I checked which format and it turns out that it is not GPT, the fact is that 100, 16, 15 Mb are automatically created in addition (for C drive only need to confirm) and the installer automatically created for me on all four of my physical disks, I don't know how, but it's funny ... maybe that's why it hangs for 15-20 seconds (scans all drives and then goes back to the main one).

4) I know about the problem (very long start on AM4), this is a problem exclusively of AMD, this is how they treat their customer shamefully. Personally, I don't plan on buying an AMD platform again.

5) I cannot update the SSD firmware because it is not on the offsite... and the program through which the SSD firmware is updated is not updated, I understand that they also decided to sneeze at their customers.

P. S. Sorry in advance for my English. This is all Google Translate :D.
 
1+4) The thing about the automatic boot retry I experience on the X470-F from cold boot or after applying bios settings, but never after a simple reboot (which again, can be particular to some boards of that era, but not for all AM4 boards, as my other msi B450 is free from it), doesn't seem related to your permanent issue. Specially if you experience a much longer silent delay without any listenable signs of the mb doing automatic resets in between.
Said this, you might check if without any drive plugged it finally POSTs much quicker. If positive, then just the nvme, and adding the others one by one (you'll want to disable the full screen logo and adjust delay if needed, so you can see drive detection). Test it also with just kb and mouse plugged to usb + monitor, to exclude any other device causing boot issues.

2) If the OS on your nvme freezes/bsods due to a sudden loss of its main drive, then there will be no disk to write the dump to. Following it, if the nvme firmware remains in a semi-crashed state and requires a full power cycle to return to normal operation, then it'll also make sense that your mb bios will still have trouble booting from it after a freeze+forced reboot, despite still being listed in some bios section-> It could also happen that the boot manager rests currently on another drive that remains detected/listed there (due to some windows installation mishap), so it'll only fail to boot after that one points to the missing NVME (that could be the case if you can't even start W11 with just the nvme plugged).

Just in case, if under windows you have any software that constantly reads temperatures 24/7 (also problematic rgb soft, like asus aura), you might check if temporarily stop using it makes any difference to prevent these freezes (in case it could be mb EC polling related, as these asus boards can crash due to it, or even the nvme not playing well with constant SMART accesses).

3) Assuming you have no drive encryption set atm, have a reliable usb w11 install media pen created with the MS mediacreationtool, and nuking your OS nvme isn't a concern: to properly fresh install your OS, fist try disconnecting all other drives, and on bios force UEFI boot and disable CSM to ensure Windows won't even try MBR. Then right after you boot from the w11 install media, use shift f10 to open the command prompt so you can run diskpart to list and select drive, clean and convert the nvme to gpt if needed, exit both and let windows install and automatically partition the only available drive (your nvme). By this point there should be no issues with boot ending somewhere else, and W11 must be able to start on that drive alone - so now, with just the nvme plugged you might check if the boot delay has improved. Just in case it was one of the other drives causing a delay at post, or a somewhat messed boot setup.
After that, it should be safe to sort the mess that was previously made on the other disk partitions without disturbing your OS.

I'm a bit out of ideas, hope someone can give you better feedback. (listing your system components will help)

P.S.: No problem understanding your posts (on the other hand, my English can be a bit weird). In any case, sometimes you might find deepl more accurate than google translate.
 
Discussion starter · #9 · (Edited)
1+4) The thing about the automatic boot retry I experience on the X470-F from cold boot or after applying bios settings, but never after a simple reboot (which again, can be particular to some boards of that era, but not for all AM4 boards, as my other msi B450 is free from it), doesn't seem related to your permanent issue. Specially if you experience a much longer silent delay without any listenable signs of the mb doing automatic resets in between.
Said this, you might check if without any drive plugged it finally POSTs much quicker. If positive, then just the nvme, and adding the others one by one (you'll want to disable the full screen logo and adjust delay if needed, so you can see drive detection). Test it also with just kb and mouse plugged to usb + monitor, to exclude any other device causing boot issues.

2) If the OS on your nvme freezes/bsods due to a sudden loss of its main drive, then there will be no disk to write the dump to. Following it, if the nvme firmware remains in a semi-crashed state and requires a full power cycle to return to normal operation, then it'll also make sense that your mb bios will still have trouble booting from it after a freeze+forced reboot, despite still being listed in some bios section-> It could also happen that the boot manager rests currently on another drive that remains detected/listed there (due to some windows installation mishap), so it'll only fail to boot after that one points to the missing NVME (that could be the case if you can't even start W11 with just the nvme plugged).

Just in case, if under windows you have any software that constantly reads temperatures 24/7 (also problematic rgb soft, like asus aura), you might check if temporarily stop using it makes any difference to prevent these freezes (in case it could be mb EC polling related, as these asus boards can crash due to it, or even the nvme not playing well with constant SMART accesses).

3) Assuming you have no drive encryption set atm, have a reliable usb w11 install media pen created with the MS mediacreationtool, and nuking your OS nvme isn't a concern: to properly fresh install your OS, fist try disconnecting all other drives, and on bios force UEFI boot and disable CSM to ensure Windows won't even try MBR. Then right after you boot from the w11 install media, use shift f10 to open the command prompt so you can run diskpart to list and select drive, clean and convert the nvme to gpt if needed, exit both and let windows install and automatically partition the only available drive (your nvme). By this point there should be no issues with boot ending somewhere else, and W11 must be able to start on that drive alone - so now, with just the nvme plugged you might check if the boot delay has improved. Just in case it was one of the other drives causing a delay at post, or a somewhat messed boot setup.
After that, it should be safe to sort the mess that was previously made on the other disk partitions without disturbing your OS.

I'm a bit out of ideas, hope someone can give you better feedback. (listing your system components will help)

P.S.: No problem understanding your posts (on the other hand, my English can be a bit weird). In any case, sometimes you might find deepl more accurate than google translate.
1) To your first point.
1.1 PC long start up is an AMD problem, just some manufacturers like MSI (from your words) don't have a problem, so they spent their resources and fixed this bug, which AMD should have done.

2) "Specially if you experience a much longer silent delay without any listenable signs of the mb doing automatic resets in between."
2.1 Not understood(.

3) "Said this, you might check if without any drive plugged it finally POSTs much quicker."
3.1 I disconnected all drives from the PC except the SSD, the result is the same (15-20 seconds).

4) "Test it also with just kb and mouse plugged to usb + monitor, to exclude any other device causing boot issues."
4.1 Thanks for the tip, I forgot about such a banal method).

5) "If the OS on your nvme freezes/bsods due to a sudden loss of its main drive, then there will be no disk to write the dump to."
5.1 As if I was writing it down... but I won't argue, thanks for the tip).

6) To your 2nd point, and in it the second line.
6.1 The problem is 15-20 seconds, only when I press to restart the PC, ie during reboot. Everything is fine when starting the PC or exiting UEFI.
6.2 I remembered something else. How long do I not turn on the computer? here it is turned off all night, and I turn it on during the day, it sometimes takes a long time to turn on (like a car, and in winter you need to heat it).

7) Your second point (paragraph).
7.1 I know about the Asus Aura problem, I don't use it because it makes no sense. I use HWinfo64, MSI Afterburner, CapFrameX.
7.2 SSD temperature is normal if you sit in the browser 39-40 degrees, in the apartment 28-29 every day.
But the most important thing is that there is no moisture (that's why even 25 degrees in the yard seems like hell). They planned to make repairs, they even started, but the second stage of the war began, the first was on February 20, 2014, with the seizure of Crimea.
And then there will be the third phase of the war. Or rather, 4 and 5 and so on before the fall of muscovia. As our General Zaluzhnyi says, 3 days of rest and back to work (this is from his last interview at this time). But these are details. With details in private correspondence, because we are on a technical forum), so I think I will not be allowed to write like that.
Somewhere like that.

8) I install via USB Flash (on Rufus) because I like cleanliness. Before that, I wrote Windows through CMD, but exFAT does not understand more than 4 GB (one file).
I install via USB Flash (via Rufus) because I like cleanliness. Once I discovered for myself that through CMD in Windows, you can prepare a flash drive, and then install Windows itself, but exFAT does not understand more than 4 GB (one file). My drives are loaded with data so I don't really want to experiment because it takes a long time to transfer data. And there would be two SSDs, there would be 0 questions, I would experiment).

9) Now I plan to install Windows 10, see how the computer reboots, and then Windows 11. By the way, I forgot to say that I chose the "no TPM/no Secure Boot" option through Rufus (and chose NTFS, or rather the program chose it, because there is no other formatting, maybe this is the problem), because I don't have a physical device (TPM), I wasn't going to buy it, now I don't know :D. So maybe Windows or maybe I clicked something in UEFI for TPM and maybe that's why the reboot is taking so long. Suddenly what. Rufus v3.17.1846, in my case it's Portable, why I didn't try to install).

P. S. I just type the text, copy it (so as not to forget what I wrote), and then translate it, see if translated it correctly - correctly (as far as I'm concerned :D). At the same time, I am improving the grammar of my native language (in this way :D), one might say, "automatically".
 
2) I meant that if in your situation there wasn't a sign of consecutive failed memory training boot retries (fans won't constantly spin up and down per retry, and the psu relay won't click too) during those 15-20s, then it's surely something else other than the usual AM4 training delays or longer post. Still, the monitor blinking is suspicions.
Btw, after a regular reboot (which happens immediately after windows shuts down on my AM4s), on task manager>startup tab I usually have 9.3s bios time on the msi b450, can't remember exactly about the asus X470, but should also still be under 10s (on that one I have also disabled hd audio, not only the serial port).

5) Please don't fret on my obvious note, I was pointing it first as a detail+cause for the nvme to stay crashed after the reboot is forced by the bsod, unless a complete power cycle is done.

7.1) hwinfo should be safe for that mb, as it ignores the problematic Asus EC (the one that also shows vrm temp) by default from like 5 years ago, else silly stuff can happen such as fan pwm going bonkers after some time, or even black screens (as the Aura bloatware caused). But again, you might also try disabling its SMART monitoring to see how it goes, just in case the nvme has buggy fw that could freeze after hours of that polling when hwinfo is always running.

8) exFAT supports files larger than 4GB, it's FAT32 that doesn't but it'll be required for something like directly copying w11 dvd iso contents into a usb pen and then being able to uefi (+secure) boot from it. Problem is the serviceable install.wim file will be too large, so it must be split or compressed* into .esd to fit the FAT32 4GB limit (the ms mediacreator tool will download a slimmer esd package for a pen drive, or even to convert into iso, instead of a larger wim serviceable iso). Rufus goes around that with a boot loader+partitions (which is cleanest, is up for discussion), so ntfs can be used in these cases where only fat32 would work. YUMI is also a competent tool to format a usb drive to multi boot a collection of untouched iso files from a ntfs or exFat partition.

9) Donno, if your boot delay issues occur during post after the reboot is issued, but before you get any mb post/logo image on screen, it doesn't seem to be windows related, but doesn't hurt to try... :)

9.1) Afaik that shouldn't be problematic, as long as the patching is done correctly (that option seems to be missing on current Rufus version after selecting a w11 iso). I used the "Win 11 Boot And Upgrade FiX KiT" from the MDL forum (not sure if against forum rules to link) to patch a W11 iso to prepare it for a TPM'less VM, also bypassing sub 64GB drive limit; *there's another tool there by the same creator for the above. MDL regulars are usually very up to date on the best/safer practices for messing with windows stuff.
 
Discussion starter · #11 · (Edited)
2) I meant that if in your situation there wasn't a sign of consecutive failed memory training boot retries (fans won't constantly spin up and down per retry, and the psu relay won't click too) during those 15-20s, then it's surely something else other than the usual AM4 training delays or longer post. Still, the monitor blinking is suspicions.
Btw, after a regular reboot (which happens immediately after windows shuts down on my AM4s), on task manager>startup tab I usually have 9.3s bios time on the msi b450, can't remember exactly about the asus X470, but should also still be under 10s (on that one I have also disabled hd audio, not only the serial port).

5) Please don't fret on my obvious note, I was pointing it first as a detail+cause for the nvme to stay crashed after the reboot is forced by the bsod, unless a complete power cycle is done.

7.1) hwinfo should be safe for that mb, as it ignores the problematic Asus EC (the one that also shows vrm temp) by default from like 5 years ago, else silly stuff can happen such as fan pwm going bonkers after some time, or even black screens (as the Aura bloatware caused). But again, you might also try disabling its SMART monitoring to see how it goes, just in case the nvme has buggy fw that could freeze after hours of that polling when hwinfo is always running.

8) exFAT supports files larger than 4GB, it's FAT32 that doesn't but it'll be required for something like directly copying w11 dvd iso contents into a usb pen and then being able to uefi (+secure) boot from it. Problem is the serviceable install.wim file will be too large, so it must be split or compressed* into .esd to fit the FAT32 4GB limit (the ms mediacreator tool will download a slimmer esd package for a pen drive, or even to convert into iso, instead of a larger wim serviceable iso). Rufus goes around that with a boot loader+partitions (which is cleanest, is up for discussion), so ntfs can be used in these cases where only fat32 would work. YUMI is also a competent tool to format a usb drive to multi boot a collection of untouched iso files from a ntfs or exFat partition.

9) Donno, if your boot delay issues occur during post after the reboot is issued, but before you get any mb post/logo image on screen, it doesn't seem to be windows related, but doesn't hurt to try... :)

9.1) Afaik that shouldn't be problematic, as long as the patching is done correctly (that option seems to be missing on current Rufus version after selecting a w11 iso). I used the "Win 11 Boot And Upgrade FiX KiT" from the MDL forum (not sure if against forum rules to link) to patch a W11 iso to prepare it for a TPM'less VM, also bypassing sub 64GB drive limit; *there's another tool there by the same creator for the above. MDL regulars are usually very up to date on the best/safer practices for messing with windows stuff.
1) "Still, the blinking of the monitor is suspicious."
- The problem is 15-20 seconds, it is a Windows 11 problem, I reinstalled Win 11 - everything is fine, even better, it started to work more smoothly, I don't see a coincidence, because Windows updated itself.
Ever since Microsoft laid off thousands of employees (before the release of Windows 10, or during its creation, I don't remember for sure), everything went through one place. They checked Windows for errors.
2) "Please don't fret on my obvious note".
- And did not think). I understand that it looked like that.
3) I use HWiNFO because it is accurate.
4) "exFAT supports files larger than 4GB, it's FAT32 that doesn't but it'll be required for something like directly copying w11 dvd iso contents into a usb pen and then being able to uefi (+secure) boot from it."
- That's right, I forgot to write that it was exFAT32, you corrected me, thanks). During the installation of Windows 11, I decided not to delete the disk with a volume of ~500 MB, but moved it through "CMD" to the "C" disk, that is, where Windows is located, configured the system, and when configuring the system, installed the "Chipset" and "NVIDIA" drivers and that's all, because the rest of the drivers give an error when unpacking the 7zip driver.
This problem did not exist at first, that is, at the beginning of the sale of my X470, but somewhere in the middle of 2019, it appeared and still exists. And this problem is still present in most drivers for my Asus. Asus doesn't seem to be looking out for their customers either... they should point out that this is a bug.
Then I connected to the internet, Windows 11 updated itself, and then I remembered I forgot to do something, and as soon as I clicked "revert to old backup", Acronis restarted Windows... and I got a blue screen when I restarted :D... Turns out Windows 11 hates updating :D. But the old backup came back :D
5) "Regular MDL users tend to be very aware of best/safer practices for working with Windows."
- Microsoft will break any safe practice of using…

P. S. But I will see if it was a software bug or not. Of course if the blue screen comes back...
P. S. S. Only Chipset and NVIDIA drivers were not installed in Device Manager and Windows 10 drivers are not installed on Windows 11...
 
1 - 11 of 11 Posts