Stuck on Mobo splash screen with new m.2

Hardware Hub Storage
1

Current system key specs:
CPU: Ryzen 5 1600
RAM: Team 2x8 GB DDR4 2666
GPU: ASUS RTX 3070 KO
Mobo: ASRock B450M Pro4 Rev1.01 UEFI ver P3.50
PSU: SeaSonic 750W 80+ Platinum

I’ve ensured BIOS is up to date for what will still support my CPU, removed all fans but CPU cooler fan, unplugged all perrefrials, other drives, Wi-Fi/Bluetooth card, ect. I’ve swapped each stick of RAM into different slots. I’ve unplugged the power supply and hit the switch on the power supply before removing the CMOS battery for 30 minutes before placing back into the system, and trying again. I cannot get my system to pass the ASRock splash screen on POST with the new 1TB Crucial P3 Plus m.2 that I picked up on Prime Day. I’ve already had the first one replaced after encountering this before. This is only happening when the new drive is installed.

2

It sounds like you’ve done quite a bit of troubleshooting already. Given that your system fails to pass the ASRock splash screen only when the new Crucial P3 Plus M.2 drive is installed, there are a few additional steps you can take to narrow down the issue:

  1. Check BIOS Settings:
    Ensure that the BIOS is set correctly for the new NVMe drive:

CSM (Compatibility Support Module): Try enabling or disabling CSM in the BIOS. This setting can sometimes affect how NVMe drives are detected.
NVMe Configuration: Check if there are any specific settings for NVMe drives in your BIOS.
2. BIOS Update:
Although you’ve mentioned that the BIOS is up to date, double-check if any newer beta versions are available that might improve NVMe compatibility. Sometimes, motherboard manufacturers release updates specifically to address issues with newer hardware.

  1. Drive Compatibility:
    Even though the Crucial P3 Plus should be compatible, there can sometimes be compatibility issues with specific motherboards:

Firmware Update for the SSD: Check if a firmware update is available for the Crucial P3 Plus. You might need to connect the drive to another system to update its firmware.
Consult ASRock Support/Forums: Look for any reports from other users with the same motherboard and NVMe drive. This can sometimes provide insight into whether it’s a known issue.
4. Test in Another System:
Test the Crucial P3 Plus in another system to see if it works there. This can help determine the issue with the drive or your specific setup.

  1. Alternate M.2 Slot:
    If your motherboard has more than one M.2 slot, try installing the drive in a different slot to see if that changes anything.

  2. Check for Physical Issues:
    Ensure that the M.2 slot and the drive are free of dust or debris causing poor connectivity.

  3. Boot Drive Priority:
    Ensure that the new NVMe drive is not initially set as the first boot device. Boot into the BIOS and see if the drive is recognized there. If it is, set your original boot drive as the primary boot device, save, and exit. Then, once you are in the OS, you can manage the new drive.

  4. Reset BIOS to Default Settings:
    After installing the new drive, reset the BIOS to default settings and see if it helps.

If the system still fails to pass the splash screen with the new drive installed after all these steps, it might be worth considering that there could be an inherent compatibility issue between the specific NVMe drive and your motherboard. In such cases, seeking further assistance from ASRock support might be necessary, or a different model of NVMe SSD might be considered.

1 Like
3

Is it windows? I had similar issue and then booted into safe mode one time based on someone else having the issue. Then it worked after the one boot into safe mode.

1 Like
4

This is where I would start.
Have you tried booting a linux USB to confirm the drive is empty?

Followed by:

What OS are you running?

2 Likes
5

I can’t get into the BIOS with the drive installed. The to ASRock splash screen comes up and it freezes there.
There’s only one NVMe m.2 slot on the board, and was planning on upgrading the Toshiba KXG50ZNV256 I’ve been using and had harvested out of an old laptop that died. Secondary drives have been:
1x 1TB Samsung 850 Evo m.2
1x 1TB WD Black HDD
1x 2TB HGST HDD
All are disconnected when I try booting with new drive installed.
I’ve disabled compatibility mode (as it was enabled) and set the only boot drive in the boot order to a Win10 installation USB with a keyboard as the only other things plugged in.

IMG20240806144518
IMG202408061445181920×2560 252 KB

Unfortunately, the changes had no effect. Will be checking with my roommate to see if I can borrow their system to test if symptoms persist. Hopefully with them running current gen Ryzen, the drive will still be good and I’ll just need to look at other upgrades instead.

6

Without knowing what motherboard or the motherboard manual in front of me @BluJay614, there isn’t a lot I can suggest to try except if you are planning on installing Windows 11 to reset your BIOS to the factory setting, create a special Windows 11 USB boot stick and install Windows. At the end of my post, I will link two videos I used to create a particular ISO file for my Windows 11 virtual machine. @BluJay614 would make a special Boot USB stick. The drive you are trying to use might have been destroyed when the laptop @BluJay614 had died.

It is more complicated to install Windows and Linux on the same drive, but it can be done if @BluJay614 wants to.

7

I actually would rather stay on Windows 10 until I’m forced to upgrade… As far as what motherboard, I specified that in the original post at the top of this thread:
ASRock B450M Pro4 ver1.0 with BIOS version 3.5 (The last version to support Summit Ridge, including posted beta BIOS versions available).
I’m planning on trying to upgrade the CPU platform anyways, so may just hang onto there drive until then and if it’s still presenting problems, RMA it.

8

@BluJay614, you did mention which motherboard you have; somehow, in rereading your first post, I missed it. You could try the same procedure I suggested in my last post using Windows 10 instead. Another procedure you could try is resetting your BIOS to the factory setting and installing Windows 10 on any drive you choose. Frankly, I would RMA the questioned drive.

1 Like
9

The only other things that relate to booting are:

  1. SMART values readout on boot (my Asus mobo does this). Try to disable

  2. Toggle fastboot in UEFI (this could be carrying a different name)

  3. Risky: hotplug the drive while in Linux. My Asus mobo advertises hotplug support for SATA in UEFI but it must be explicitly enabled. I am not sure what the deal is on consumer mobo’s, if in doubt then don’t… unless you feel adventurous.

  4. Not risky: USB enclosure for the SSD. I had an HDD once that was stuck firmware-wise and wouldn’t POST. It had to rewrite a sector – or something like that – before the bug would go away. It’s been running fine ever since. Although why would you go for this if you can choose a different SSD and avoid the motherboard issue? How likely is that for both SSDs to be dead?.. other than the slot being dead :skull_and_crossbones:

1 Like