Windows failing to install on NVMEs.

[Snikpoh1390]

Hey all. I am in dire need of help. 

 

I recently had a 7800x3d, and to help a buddy out, bought a 9800x3d and gifted him the 7800x3d. Since the upgrade, I have failed utterly to get windows installed on my NVMEs. 

 

After I switched the CPU, windows kept crashing over and over. Any time I tried to install something, it would freeze. Then it got to the point where it would freeze even if I turned it on and logged in. I have reseated and pasted the new CPU like 4 times. I've made sure theres no debris or anything in the socket or on the chip. Now my NVMEs, since the failed installs, won't even show in the BIOS. I have since taken those drives put them on an external enclosure on another device and they work COMPLETELY fine. You can wipe and add or remove partitions, items can be added or removed from the drives, everything. They work fine. Toss them back into the PC? Nothing. BIOS only sees my crucial and my SSD through SATA. The 990pro and 980pro aren't even seen. I tried to install Windows on the Crucial and it gets to some arbitrary % and fails. I cannot figure wtf is going on. I have verified CSM is off and its not in RAID. I have reset the BIOS on the board and updated it slowly and tried again..and again..and again. Its like the board can't communicate with the NVMEs for longer than a few seconds before fucking off. 

 

Someone please help. Please. My Motherboard is less than a month old, my CPU is less than a week old. The NVMEs work fine on an external enclosure on another PC. Please. Someone. Anyone. Help me. I'm desperate and super frustrated. 

 

CPU: Ryzen 7 9800x3d

GPU: zotac 4080

MB: Gigabyte X870-GAMING-X-WIFI 7

Storage: SK Hyniqs 1tb SSD

Samsung 990 Pro 2tb

Samsung 980 Pro 1tb

Crucial 2tb

OS: Win11

 

[strange13930]

40 minutes ago, Snikpoh1390 said:

Hey all. I am in dire need of help. 

 

I recently had a 7800x3d, and to help a buddy out, bought a 9800x3d and gifted him the 7800x3d. Since the upgrade, I have failed utterly to get windows installed on my NVMEs. 

 

After I switched the CPU, windows kept crashing over and over. Any time I tried to install something, it would freeze. Then it got to the point where it would freeze even if I turned it on and logged in. I have reseated and pasted the new CPU like 4 times. I've made sure theres no debris or anything in the socket or on the chip. Now my NVMEs, since the failed installs, won't even show in the BIOS. I have since taken those drives put them on an external enclosure on another device and they work COMPLETELY fine. You can wipe and add or remove partitions, items can be added or removed from the drives, everything. They work fine. Toss them back into the PC? Nothing. BIOS only sees my crucial and my SSD through SATA. The 990pro and 980pro aren't even seen. I tried to install Windows on the Crucial and it gets to some arbitrary % and fails. I cannot figure wtf is going on. I have verified CSM is off and its not in RAID. I have reset the BIOS on the board and updated it slowly and tried again..and again..and again. Its like the board can't communicate with the NVMEs for longer than a few seconds before fucking off. 

 

Someone please help. Please. My Motherboard is less than a month old, my CPU is less than a week old. The NVMEs work fine on an external enclosure on another PC. Please. Someone. Anyone. Help me. I'm desperate and super frustrated. 

 

CPU: Ryzen 7 9800x3d

GPU: zotac 4080

MB: Gigabyte X870-GAMING-X-WIFI 7

Storage: SK Hyniqs 1tb SSD

Samsung 990 Pro 2tb

Samsung 980 Pro 1tb

Crucial 2tb

OS: Win11

 

have you tried updating the bios?

[Snikpoh1390]

1 hour ago, strange13930 said:

have you tried updating the bios?

Yes. Incrementally as well. I went through each one. 

[jmwhite33]

13 hours ago, Snikpoh1390 said:

Hey all. I am in dire need of help. 

The 990pro and 980pro aren't even seen. I tried to install Windows on the Crucial and it gets to some arbitrary % and fails. I cannot figure wtf is going on. I have verified CSM is off and its not in RAID. I have reset the BIOS on the board and updated it slowly and tried again..and again..and again. Its like the board can't communicate with the NVMEs for longer than a few seconds before fucking off. 

 

Someone please help. Please. My Motherboard is less than a month old, my CPU is less than a week old. The NVMEs work fine on an external enclosure on another PC. Please. Someone. Anyone. Help me. I'm desperate and super frustrated. 

 

CPU: Ryzen 7 9800x3d

GPU: zotac 4080

MB: Gigabyte X870-GAMING-X-WIFI 7

Storage: SK Hyniqs 1tb SSD

Samsung 990 Pro 2tb

Samsung 980 Pro 1tb

Crucial 2tb

OS: Win11

 

taking a look at the manual;

https://download.gigabyte.com/FileList/Manual/mb_manual_x870-gaming-x-wifi7_1002_e.pdf?v=f4b62ad48699925a4194633224d93c0b

it mentions using rubber backing on motherboard under the nVME drives to insulate it from the motherboard.

Are you using those pads? It could simply be the Samsung is a different thickness and shorting against the board.

sounds odd, I know, but the manual is rather emphatic about using the rubber pads.

[Snikpoh1390]

4 hours ago, jmwhite33 said:

taking a look at the manual;

https://download.gigabyte.com/FileList/Manual/mb_manual_x870-gaming-x-wifi7_1002_e.pdf?v=f4b62ad48699925a4194633224d93c0b

it mentions using rubber backing on motherboard under the nVME drives to insulate it from the motherboard.

Are you using those pads? It could simply be the Samsung is a different thickness and shorting against the board.

sounds odd, I know, but the manual is rather emphatic about using the rubber pads.

I actually didn't notice that. I can add those. I actually do have some little rubber nubs that came with the board. However, these NVME drives worked no problem on the 7800x3d.

[Snikpoh1390]

I have since moved windows to a 2.5in ssd rather than a NVME. The computer now boots to windows without problem, however, I still cant use anything NVME related without an immediate freeze. Also, if I play a game, as soon as the game loads past the main menu, the computer just straight up restarts. I cant find the problem in event viewer either.