Short version: Can an M.2 NVME (Samsung 970 EVO) cause profound CPU damage?
Long Version: The day before yesterday my Dell XPS 2-in-1 arrived. In addition I bought myself a Samsung 970 EVO 2TB to install manually (yes is allowed and also within the guarantee etc.).
Everything worked great, laptop has started up, even with the new cloned SSD. When I then wanted to boot from Windows into Safe Mode (with SHIFT + Restart) the laptop did not start up and the LED has indicated a CPU error.
Called Dell Support yesterday, today was the technician and has replaced the motherboard (+ CPU, GPU). Everything worked as expected. New hard drive installed: works too. When he then (out of fun) tried to reproduce the error and start in safe mode (SHIFT + reboot): exactly the same story - CPU error. Device is now completely replaced by Dell.
Now, my fear is that it's because of the SSD, because that was the only common denominator in both disturbances.
Should I have the SSD replaced or it is not technically possible that it's.der SSD. After all, the M.2 NVME is directly connected to the processor, which leaves me a bit thoughtful.
PS: Sorry for the catchy title, but in itself it describes the title quite well.
So the thing shows you a CPU error but the technician does not exchange the CPU but only the board?
Uh, no, do not think it's because of the SSD.
To be honest, I find it hard to imagine how the SSD should destroy the CPU.
Especially so that it only happens in safe mode and everything else starts wonderfully.
I mean, if the SSD had a short circuit and sent the PCIe power supply to the PCIe controller in the CPU, it would grill the CPU safely, but that would happen immediately and you would never even come near Windows.
On the other hand. Something seems to be obviously in the bad. Only what?
He wrote: Motherboard + CPU / GPU. So… Pretty much everything.
Since it is a laptop, the processor is firmly soldered to the motherboard. An exchange of only the CPU is not possible.
Ah, read over.
Me too, but I'm unsure about the new technology. Just talked to the Samsung support and said as well that they have never heard of it.
The only thing that would come to mind is that it is due to cloning. Image was made with "Acronis True Image" and I got the error message: https://kb.acronis.com/de/content/49346
Possibly the serious error only comes up, if is started directly into the UEFI, which however according to error message from Acronis possibly is not possible.
Sounds complicated, is probably also very far-fetched.
In any case, the technician was afraid that a global recall would have to be started haha
