Samsung 860 EVO won't boot in my laptop

jewie27

Distinguished
Sep 12, 2011
23
0
18,560
I just purchased and installed a new Samsung 860 EVO into my Asus X44H laptop. I used the Samsung Migration software and successfully cloned my fresh copy of Windows 10 64 bit. I was able to boot up fine and log into windows. I immediately launched the Samsung Magician software and verified the drive was recognized and functioning properly. I did a reboot through windows to make sure it would reboot with no problems. I immediately ran into an error PXE-E61: Media test failure, check cable. I had never seen this error before and know that the SSD was securely inserted into the SATA port because I was able to boot into windows right after installation the first time. I reseated the drive, got into the bios and made sure the new 860 EVO was selected as the primary boot device. I saved and exited the bios and it's failing to see the drive and let me into windows. I even updated my BIOS to version 211 which is the latest version from Asus' website. After several reboots and changing the bios to OPTIMIZED DEFAULTS, I still can't get the drive to work. I also put my original Hard Drive in that was working before purchasing the EVO SSD. That drive no longer boots either.
 
Solution
PXE error has nothing to do with SSD. You get it, when network boot has been enabled in BIOS.
You just had to disable network boot.

Now you have done BIOS reset and need to restore several BIOS settings to previous values to be able to boot.
Settings important - boot mode (UEFI or legacy/CSM) and
sata controller mode (ide, ahci, raid) and
secure boot setting probably needs to be disabled.
You'll have to experiment with those settings until you find the right ones, if you have not written them down somewhere.

stdragon

Proper
Apr 5, 2018
94
0
160
The PXE-E61 error is occuring because the primary boot device (your SSD or HDD) isn't available to the system, so it rolls on down to the 2nd option, and that's booting off the LAN via PXE Boot. Because you don't have anything on a LAN responding to a PXE call, you get that error. It's expecting, but non available. So that error is normal. What isn't normal is the drive dropping out like that.

See if you can disable PXE Boot in the BIOS just in case it's causing a conflict.

I'm thinking however that something died in the chipset that enumerates SATA devices.
 

SkyNetRising

Estimable
Jan 4, 2016
372
0
5,210
PXE error has nothing to do with SSD. You get it, when network boot has been enabled in BIOS.
You just had to disable network boot.

Now you have done BIOS reset and need to restore several BIOS settings to previous values to be able to boot.
Settings important - boot mode (UEFI or legacy/CSM) and
sata controller mode (ide, ahci, raid) and
secure boot setting probably needs to be disabled.
You'll have to experiment with those settings until you find the right ones, if you have not written them down somewhere.
 
Solution