Question MSI MAG B650 tomahawk won't boot into my m.2 or a usb

[cloudy_soup]

So I built this rig back in July of last year and its been going strong up until the past week. It has. a 7800x3d, 32gb 6000 mhz cl 32 ddr5 ram, a 4070, and a 2 tb m.2 and the mobo in the title. I've narrowed down the issue to the bios just not booting into any storage device, i've tried 2 different m.2 slots, and it wont boot into a usb either. Here's the issue so far:

The issue that I'm having is that the pc won't go past the bios. This started happening a week ago, the pc was stuck on the MSI logo and the loading wheel kept spinning, so I just reset the cmos by jumping it and that did the trick. Fast forward 2 days from then, the same thing happened, however resetting the cmos did not help. I tried a bunch of different things, updating bios, reseating ram, trying 1 stick vs both sticks in different slots, and when I tried to repair windows using a usb with windows media installation it wouldn't boot into that either. Nothing seemed to work until I got to a screen that said 'attempting to repair windows' and after leaving it at that screen for a while it finally booted. Then each time that I changed something in the bios, I would have the same issue. While I was in windows I tried to repair corrupted files, and interestingly it said that there were some corrupted files in my windows that it has since fixed.

The issue has arrised again this morning and I have been trouble shooting for hours now. I tried doing what I did before where I restarted pc 3 times and got to screen where it says 'attempting to repair windows' and then the screen will just go black and my devices on the pc will start flashing on and off and my pc will stay running but the device won't boot into anything. I've tried toggling between the uefi/legacy boot option in the bios and that hasn't a difference. Has anyone had this issue and know of how to fix it. I think i've narrowed the problem down to the bios not booting into any storage device but im not sure.

Any help would be greatly appreciated, I spent a lot on this mobo, but i'm starting to think I would be better off looking for another mobo, unless theres an easy fix someone knows of. Thanks in advance!

 

[Lutfij]

Welcome to the forums, newcomer!

What BIOS version are you on for your motherboard? Make and models of your M.2 drives and which slots they're populating? Speaking of drives and motherboard's, your motherboard should have Q_LED's onboard to tell you if you're having any POST sequencing issues. If none of them are static, then the issue is your OS installation. Since repairing won't do, you should reinstall the OS with all drives disconnected except for the one you wish to install the OS onto, installing the OS in offline mode. Install all drivers in an elevated command while in offline mode, before hooking up to the www to run an OS update. FYI, you should recreate your bootable USB installer to rule out a corrupt installer.

32gb 6000 mhz cl 32 ddr5 ram
Got a link to the ram used?

 

[JayGau]

So right now you no longer have access to a PC? Because I would personally try to create a bootable USB drive with an iso like System Rescue or Hiren and see if it boots with that. If it does, then your computer is probably fine and it's Windows that is messed up.

Usually, an "attempting to repair Windows" loop means that the board detected a Windows installation but cannot load the boot partition. It happens to me regularly when I put a Windows image on a different type of drive (like SATA to NVMe) and try to boot from it. It also happens when you try to boot with the BIOS set to AHCI with a Windows that was installed in a RAID configuration (or vice-versa). When any of these happen, the solution is to boot in safe mode and Windows automatically fixes the boot partition. But your case looks different. You said that at some point the repair worked and it booted, but now it just goes to a black screen? It would be very interesting to see if it boots with one of the systems I mentioned above.

Also, in general, when Windows fails to boot 3 times (like 3 failed "attempting to repair Windows" cycles in a row) it automatically loads the Windows Recovery Environment. Are you able to reach this or does also fail to load that?