F5F Stay Refreshed Hardware Desktop M.2 device fails to be detected in MSI Bios 5 and freezing occurs with horizontal lines displayed.

M.2 device fails to be detected in MSI Bios 5 and freezing occurs with horizontal lines displayed.

M.2 device fails to be detected in MSI Bios 5 and freezing occurs with horizontal lines displayed.

Pages (2): 1 2 Next
U
UniqueSmurf
Junior Member
36
03-18-2024, 05:38 PM
#1
I made an error by copying my son’s SSD to his new M.2 drive. This caused a conflict in Disk Manager, so I switched the drive letters once Windows recognized the M.2. After that, we experienced frequent crashes (screenshots included) and the system stopped working properly. The issues appeared on two fresh Windows installs using the old SSD. Sometimes the M.2 showed up in Disk Management or Device Drivers, but other times it didn’t. Now I just want to install Windows on this new M.2 (WD Black SN770) without using the SSD, but I’m stuck at the BIOS setup stage. I’ve unplugged all drives and tried both CSM and UEFI, yet the MSI BIOS still fails to detect the M.2. I need it to be visible for a proper Windows install. I cleared the CMOS and updated the BIOS to a build date of November 3, 2024. What’s going wrong? I’m trying to get this resolved quickly, but it feels like a major setback. Sincerely, a dad who messed up his son’s PC upgrade and now can’t fix it.
U
UniqueSmurf
03-18-2024, 05:38 PM #1

I made an error by copying my son’s SSD to his new M.2 drive. This caused a conflict in Disk Manager, so I switched the drive letters once Windows recognized the M.2. After that, we experienced frequent crashes (screenshots included) and the system stopped working properly. The issues appeared on two fresh Windows installs using the old SSD. Sometimes the M.2 showed up in Disk Management or Device Drivers, but other times it didn’t. Now I just want to install Windows on this new M.2 (WD Black SN770) without using the SSD, but I’m stuck at the BIOS setup stage. I’ve unplugged all drives and tried both CSM and UEFI, yet the MSI BIOS still fails to detect the M.2. I need it to be visible for a proper Windows install. I cleared the CMOS and updated the BIOS to a build date of November 3, 2024. What’s going wrong? I’m trying to get this resolved quickly, but it feels like a major setback. Sincerely, a dad who messed up his son’s PC upgrade and now can’t fix it.

Y
YouGetPwned
Junior Member
13
03-18-2024, 11:12 PM
#2
Ensure the drive is correctly installed with no debris or obstructions. Verify a different M.2 port if available. Disable CSM as it’s unnecessary. Consider installing on another computer if possible, confirming proper formatting. Also, check for available firmware updates on the SSD.
Y
YouGetPwned
03-18-2024, 11:12 PM #2

Ensure the drive is correctly installed with no debris or obstructions. Verify a different M.2 port if available. Disable CSM as it’s unnecessary. Consider installing on another computer if possible, confirming proper formatting. Also, check for available firmware updates on the SSD.

J
JustSoKawaii
Member
65
03-19-2024, 03:08 AM
#3
I installed it in the bottom M.2 port and started up using the previous SSD. It worked with the old SSD, allowing me to format the new one (NFTS seems correct). After removing the SSD, I tried booting only the M.2 slot in the top port—no BIOS or post appeared. CMOS was cleared as well.
J
JustSoKawaii
03-19-2024, 03:08 AM #3

I installed it in the bottom M.2 port and started up using the previous SSD. It worked with the old SSD, allowing me to format the new one (NFTS seems correct). After removing the SSD, I tried booting only the M.2 slot in the top port—no BIOS or post appeared. CMOS was cleared as well.

K
Kyoks
Junior Member
3
03-19-2024, 04:35 AM
#4
Windows needs NTFS to work, so yes. If it can recognize the drive, it should be able to install. Make sure it's also formatted for GPT. Press shift+f10 in the installer to open Command Prompt, then type "diskpart" and "list disk" — this will confirm if it's using GPT. No extra steps needed if it already is.
K
Kyoks
03-19-2024, 04:35 AM #4

Windows needs NTFS to work, so yes. If it can recognize the drive, it should be able to install. Make sure it's also formatted for GPT. Press shift+f10 in the installer to open Command Prompt, then type "diskpart" and "list disk" — this will confirm if it's using GPT. No extra steps needed if it already is.

P
Pawtex
Member
114
03-19-2024, 09:18 AM
#5
After several restarts and what looked like an unusual cycle, the system finally started up in Windows without needing a restart. It used the old SSD with the OS installed and the new M.2 slot at the top. The M.2 isn’t showing up in Device Manager or Disk Management, and Diskpart also didn’t list it. It seems the problem only appears when the M.2 is inserted into that specific top slot on the motherboard. There’s a flat rubber pad under the M.2, possibly affecting contact. It might be related to conflicts between PCIe lanes and SATA ports, as the SSD seems to cause issues whenever it’s placed in the top slot.
P
Pawtex
03-19-2024, 09:18 AM #5

After several restarts and what looked like an unusual cycle, the system finally started up in Windows without needing a restart. It used the old SSD with the OS installed and the new M.2 slot at the top. The M.2 isn’t showing up in Device Manager or Disk Management, and Diskpart also didn’t list it. It seems the problem only appears when the M.2 is inserted into that specific top slot on the motherboard. There’s a flat rubber pad under the M.2, possibly affecting contact. It might be related to conflicts between PCIe lanes and SATA ports, as the SSD seems to cause issues whenever it’s placed in the top slot.

I
ilycookie
Member
53
03-19-2024, 11:10 AM
#6
It seems like the issue might be related to the mainboard or CPU itself. Have you inspected the socket for any bent pins? Also, did you adjust the mounting plate on the CPU cooler? The only problem that should prevent your system from working is if an NVMe drive is placed in the M.2 slot 2_2 as a PCIe port E3. Your manual doesn't mention anything about NVMe in M.2 2_1.
I
ilycookie
03-19-2024, 11:10 AM #6

It seems like the issue might be related to the mainboard or CPU itself. Have you inspected the socket for any bent pins? Also, did you adjust the mounting plate on the CPU cooler? The only problem that should prevent your system from working is if an NVMe drive is placed in the M.2 slot 2_2 as a PCIe port E3. Your manual doesn't mention anything about NVMe in M.2 2_1.

A
AlexRoosio
Member
204
03-19-2024, 02:07 PM
#7
Here’s a revised version of your notes:

An update is needed… When the M.2 was placed in Slot #1 (above the GPU) without the SSD connected, BIOS loading often failed and the CPU debug light stayed on. This suggests a possible issue with the CPU pin or the top slot itself. It might also explain the occasional crashes. The same M.2 was detected by both BIOS and Windows in the Device Manager when inserted into the bottom slot. After installing Windows in Slot 2, everything worked smoothly except for BIOS access without any drives. When the SSD was connected, Windows prompted to choose a volume, allowing installation, but crashes still occurred afterward. I didn’t experience freezing or crashes when using just the M.2. Tonight I plan another Windows install, hoping to get the usual partitions so BIOS recognizes them and loads properly. I followed the prompts during setup and formatted the drive as a single partition, but it didn’t create the expected partitions. Any thoughts or suggestions for this session?
A
AlexRoosio
03-19-2024, 02:07 PM #7

Here’s a revised version of your notes:

An update is needed… When the M.2 was placed in Slot #1 (above the GPU) without the SSD connected, BIOS loading often failed and the CPU debug light stayed on. This suggests a possible issue with the CPU pin or the top slot itself. It might also explain the occasional crashes. The same M.2 was detected by both BIOS and Windows in the Device Manager when inserted into the bottom slot. After installing Windows in Slot 2, everything worked smoothly except for BIOS access without any drives. When the SSD was connected, Windows prompted to choose a volume, allowing installation, but crashes still occurred afterward. I didn’t experience freezing or crashes when using just the M.2. Tonight I plan another Windows install, hoping to get the usual partitions so BIOS recognizes them and loads properly. I followed the prompts during setup and formatted the drive as a single partition, but it didn’t create the expected partitions. Any thoughts or suggestions for this session?

C
camchrism
Member
212
03-19-2024, 04:43 PM
#8
did you perhaps reuse the bootloader on the sat ssd?... when trying to remove it, it doesn’t load. just remove everything except the disk, then reset bios to defaults and see if installation works.
C
camchrism
03-19-2024, 04:43 PM #8

did you perhaps reuse the bootloader on the sat ssd?... when trying to remove it, it doesn’t load. just remove everything except the disk, then reset bios to defaults and see if installation works.

J
JoloYolo
Member
205
03-27-2024, 09:33 AM
#9
Maybe. To confirm, you’d need to understand what a bootloader is. Since you’re not familiar with it, think of it like this: you should have the bootloader ready on a USB drive and use it to flash it. Regarding the disk—just make sure nothing else is connected before installing anything. The M.2 card was already formatted when you put Windows on it.
J
JoloYolo
03-27-2024, 09:33 AM #9

Maybe. To confirm, you’d need to understand what a bootloader is. Since you’re not familiar with it, think of it like this: you should have the bootloader ready on a USB drive and use it to flash it. Regarding the disk—just make sure nothing else is connected before installing anything. The M.2 card was already formatted when you put Windows on it.

D
Dustyn1001
Member
194
04-06-2024, 05:54 PM
#10
if the SSD was connected during installation and Windows had already been installed there, it's common for the system to reuse the existing EFI or bootloader image. this is why it's advised to leave only the target disk available for installation. In BIOS, set default settings to factory. Begin the installation using the USB drive. Ensure the disk has no unused space before starting. If any partitions exist, delete them. Proceed with the install.
D
Dustyn1001
04-06-2024, 05:54 PM #10

if the SSD was connected during installation and Windows had already been installed there, it's common for the system to reuse the existing EFI or bootloader image. this is why it's advised to leave only the target disk available for installation. In BIOS, set default settings to factory. Begin the installation using the USB drive. Ensure the disk has no unused space before starting. If any partitions exist, delete them. Proceed with the install.

Pages (2): 1 2 Next