glad you were able to resolve. Can you provide the drive part number? @dark_skeleton
There aren’t any cases matching your exact behaviour when looking online, but NVME detection issues are certainly not exclusive to ASUS on x670. 1516 introduced AMD’s PI 220.127.116.11b, so it’s possible we can attribute it to something that changed here if enough users see the same behaviour. Clearly if the new drive works we can rule out a board defect.
Let me preface this post with the fact that there are zero issues with that NVMe being detected on BIOS 1416 as well as every older BIOS version that I have tested since March or so. Issues started with 1516 and continue in 1602. Rolling back to 1416 fixes the issue for me but I am unable to use the most recent BIOS.
The issue is that as soon as 1516 or 1602 is flashed, the NVMe in slot M.2_4 (connected to chipset) is no longer being detected in BIOS.
Relevant build details:
Things I tried that didn't help:
Things I did not try because they would require me disassembling the PC:
Is anyone able to test/verify this and/or contact the right internal team at Asus?
Thanks in advance
Looks like you've tried quite a lot to troubleshoot this already. Have you tried updating the firmware for the Kingston? Definitely worth a shot. Let me know and if not I'll see if I can get this issue replicated.
Thanks, was worth a shot. If you see any other cases of this online please link in the thread. It would be useful if you could try putting the drive in another M.2 slot just to confirm.
Ehh I know... I would have done that already but a) my PC is mounted so it's a pain to unplug and take it out to open it and b) The M.2_4 slot is under the GPU... and to take the GPU out I need to remove the side-panel... You get the idea. It's not a 10 minute task.
I honestly am unable to understand why this happens so consistently when updating the firmware but the reports I got so far from others on reddit seemed rather inconsistent for now.
I can relate. I have a hardline build and need to repaste my 13900KS but finding the time isn't easy. Not trying to send you up the garden path as it were, just helps to get as much info as possible - and the more cases the quicker we can get any potential issues looked into.
I have the same problem on 1516 except that sometimes just be restarting a few times it will "rediscover" the drive and work fine for reboots from then on. But if I power down instead of rebooting the drive will usually be lost again. I believe it is M.2_4 for me as well. Problem started with 1516 as stated above.
Edit: this time I fixed it by shutting down. On restart the drive came back.
Relevant build details:
Issue persists in BIOS version 1709
I also tried flashing via FlashBack feature this time, same result.
EDIT: also the version 1709 appears bugged, EZ Flash claims older BIOS versions (i.e. 1416 on which the NVMe slot works absolutely fine) are not valid, regardless of the rollback BIOS setting being enabled. The only way to roll back from version 1709 is by using the BIOS FlashBack feature again.
@Drwags thanks for sharing your experience, I'm quite surprised so few people are reporting this tbh. Sadly I am unable to get 1516 and newer to detect the drive in M.2_4 slot even after multiple restarts / reboots / power cycles etc.