Question Motherboard not recognizing any drives

[noahmitcjell]

Hi guys, I have recently purchased a Crosshair Vi and and r5 3600, I updated the bios so it was compatible with the 3000 series, but my problem is that whenever I get into BIOS I can't seem to get my drives to recognize. I've tried different cables, different slots in the motherboard, different power supply and everything. I tried flashing the bios to an older edition that has ryzen 3000 support and still no luck. Any thoughts?

 

[fzabkar]

Did you change the PSU and, if so, did you swap cables between your old and new PSUs?

 

[noahmitcjell]

Did you change the PSU and, if so, did you swap cables between your old and new PSUs?

Yes, still no luck.

 

[popatim]

What he means is, initially, did you use the old PSU cables connected to the new PSU when you turned the system on?

 

[noahmitcjell]

I am using a different PSU with it's own cables, I have however tried to use a different PSU with it's own cables and it did not work either.

 

[QwerkyPengwen]

Try a CMOS reset.

 

[fzabkar]

Just to make absolutely sure we are on the same page …

Warning: do not interchange modular PSU cables:
http://www.hddoracle.com/viewtopic.php?f=56&t=2545

 

[gn842a]

I'm glad to see other people putting out the word on psu cables not being interchangeable.

I'm not fully understanding what's happening here. The OS install on the original drive should be done with no other drives connected, it helps avoid a lot of confusion. Once everything is up and running the other drives can be connected and tested.

Only one drive hooked up and either a memory stick or optical drive set up in the boot order in the #1 position. You take it out of #1 position once you have a working C: drive.

So the when you boot the system should load to the optical drive or the memory stick which will have an install program.

If on the other hand what is being said is that you had a working OS in Win 10 and sticking it on to this system is not working well, then it may be that the "new windows" philosophy of allowing you to port from one system to another isn't working so well. Anyhow I find this part of the presentation confusing.

Greg N

 

[tony_parker]

Well, there could be various reasons for an internal drive to become unresponsive or undetected. It can be a hardware issue or some technical issue in the software. Below are the few possible reasons for any drive being unresponsive:

1. Lot of bad sectors
2. Infected File (Virus or Malware)
3. Driver issue
4. Mechanical failure

You can try the below options to resolve the issue:

1. Run CHKDSK
2. Use an Antivirus & Anti-Malware tool
3. Re-install the drivers

Hope it will work out.