Windows 10 is crashing after new installation on Samsung 980 SSD M.2 NVMe

[Bulbasaur]

Hello everyone, Windows 10 is crashing after new installation on Samsung 980 SSD M.2 NVMe. The system crashes and goes into recovery after a few restarts. I switched to a new Samsung SSD 870 with SATA Data Cable and that doesn't help either. What could be causing this?

[DGroves]

random crashing across different boot storage drives usually indicates a hardware based problem with the ram/cpu being the most common issues is the system being overclocked? if so reset to defaults same for the cpu

also is the cpu and case fans working correctly? excessive heat can also cause random crashing

a failing power supply

i would also download the HP cloud recovery software image for your model workstation and reinstall the os using that image

https://support.hp.com/us-en/document/ish_4511095-4511141-16

[Bulbasaur]

 system not overclocked,I have rest the cpu batry and the biaos. cpu fans are working properly. I don't think it's related to the operating system. I think it's related to power supply or motherboard, but the support in my country refuses to help, claiming that component was replaced (the ssd) they don't provide support even though the computer is under warranty.

Is there a way to check what's not working properly? In HP PC Hardware Diagnostics all components appear to be functioning correctly. Thank you in advance. 

[SDH]

You spoke of upgrading to a Samsung 980 Pro M.2 SSD... do you still have your original boot drive and if so can you plug it back in and function off of that? That would help narrow down the problem if the workstation still works well from that drive.

Second, the Samsung Magician 8.2, recently released, is a free utility that can recognize the firmware present on Samsung consumer drives (Pro and Evo) and can firmware update your M.2 drive easily. If you get things running stable I'd run that to make sure you have latest firmware.

Third, where were you running that 980 Pro M.2 drive from? There are two "on-motherboard" M.2 sockets for that workstation (assuming it is the Xeon version) One is primary and the other is secondary. Those are labeled 0 and 1 respectively. The M.2 stick could also have been in a Z Turbo Drive PCIe card. Ideally, you'd want it in the motherboard's primary M.2 socket.

If all was stable and good before the upgrade it also could be a BIOS problem. Consider going into BIOS and setting that to Factory Defaults, and save on the way out of BIOS.

Good luck... that is an excellent workstation and a very good M.2 SSD.

[Bulbasaur]

1. yes its Xeon version

2. There no crashes of the operating system on the original disks (HDD) But work slow.
3. I installed Samsung Magician 8.2 was already updated, and it still didn't solve the problem.
4. I installed from the primary and it still crashes. Will Z Turbo Drive PCIe card will solve my problem?
5. I reset the BIOS, including removing the battery. Could there be something in the BIOS settings that I'm not doing correctly that's causing this? UEFI mod? 

[SDH]

1. Good... that has two on-motherboard M.2 sockets. The Core version only has one. However I'd stick to using a 2.5" form factor SSD for now because that is most basic. You can upgrade to M.2 later after you get this figured out. No need for a HP ZTD PCIe card instead... that will only make your situation more complex.

2. You did not answer my question. Do you still have that original hard disk drive and can you run from it? Did that come from HP with your workstation?

3. Nothing more to do on that front. That means when you get things running you'll have a nice fast M.2 drive to use later.

4. You installed from the primary M.2 socket onto the 980 Pro... what did you use to install from?

5. The factory default BIOS settings are generally the most compatible. No, UEFI is mature in these workstations and that should be fine for you.

DGroves gave you good advice above. Did you look into that? You need to provide your workstation's serial number in the process to download (and use) the Restore kit that HP has for you. That satisfies the need to prove your workstation is licensed to use their custom Windows kit. There is a kit for W10 and for W11 for your Z4 G4 (both are Win Pro -64 versions)... some workstations only have a kit for W10 Pro -64. If you are licensed for W10 you're licensed for W11 assuming it is a Win-licensed workstation and not a Linux version. Those kits are custom installers most compatible with your workstation and OS with settings hand selected by HP. Generic W10/W11 installers are not fine tuned that way. I'd download the W11 version from where DGroves recommended, install that, and then use Windows Update to upgrade from the older W11 version you got from HP. When you use Windows Update do not take any optional preview updates. Wait for those to become official in a month or so.

A good computer shop with HP workstation experience may be the way for you to go.

[Bulbasaur]

thank you!

2. Yes, I still have the Pro M.2 NVMe and Samsung SSD 870I purchased them new for installation.

I don't want to install because it causes the OS to crash.

4. Boot USB  white License key

i wil tray DGrove advice and if the installation doesn't work, I'll go to computer shop as you suggested.

Thank you.

[Bulbasaur · Accepted solution]

last one: I am trying to create a recovery USB using HP Cloud recovery tool. After typing the product ID, I get a message that Product ID is invalid. My system runs Windows 10 pro version

[SDH]

If I recall correctly, HP changed the alphanumeric to enter from product ID to your actual serial number. That is on a label on your workstation's case. 

See in my post above #5:

"You need to provide your workstation's serial number in the process to download (and use) the Restore kit that HP has for you. "

Try that and let us know. My recall is from when I did that for my Xeon Z4 G4...

[Bulbasaur]

I managed to find the download file through someone in the forum who requested it. I installed it on the Samsung 980 SSD M.2 NVMe, and so far, more than ten hours have passed without a crash. I'll try again next time.Thanks for your help.