Provide screenshots for the SMART Attributes of each SSD if you are able. ... View more

Is the MX300 firmware up to date with version M0CR060?   Please post a screenshot of the SMART Attributes using Crucial Storage Executive.   Did you make any other hardware or software changes just before or after your SSD upgrade?  Did you try with BIOS default settings (no overclocking) with the SATA controller set to AHCI mode.  Does Event Viewer show anything in the logs that might help?   Try performing a clean install of Win10 to see if the problem is just software or a clone issue.  If a fresh install of Windows works, then either something went wrong with the clone or there is some other software issue.  You can download the most recent version of Win10 direct from Microsoft.   You could also create a bootable USB Acronis disk and boot from it to clone your old drive again.  This might eliminate some possible cloning issues.   If that does not work, there are some other free or low cost cloning utilities available you could try. ... View more

Yes, you should set the SATA mode to AHCI mode before installing Windows. ... View more

  Since the SMART Attributes look Ok in your screenshot, then I think this Self-Test failure is due to something left over with the old firmware.   If you've left the drive on but inactive for a long enough time, then I think you will need to do the Secure Erase to reset the drive.   If you still have the failing self-tests after the Secure Erase, then I think you will need to RMA the drive.   I'm betting the Secure Erase will solve the problem.   If you want to try avoiding a re-install, you could try changing the BIOS SATA controller to AHCI mode and boot to a Knoppix USB drive and try running another Self-Test using GSmartControl (already installed) just in case this setting is somehow interfering with the test (doubtful).   ... View more

@franzkrauzer  I know the early Ryzen motherboards (all brands) had memory issues which I believe most of the issues were resolved with later firmware updates, but I think there may still be some stability/compatibility issues even with the B450 series.   I saw some posts where people ran the RAM at a lower speed (2400) and another where someone actually lowered the voltage for the RAM to make it work.  I wouldn't advise to raise the voltage without knowing what you are doing since that could damage the RAM and void the warranty.   Since the BSOD references a Memory Management issue, it would seem to be memory related or perhaps power related since that will affect it as well.  While testing the system, you should remove any unneccessary items from the motherboard.    Do you have another power supply you could test?  And try connecting to another electrical outlet especially one not shared with an appliance or laser printer, etc. which might cause a blip in the power to your system.   Also if the BX300 is your boot drive, check the SMART Attributes on the BX300 for reallocated blocks and other errors which might not trigger a health failure yet.   Run a chkdsk on the boot drive (no need for the bad block scan if using an SSD) and run a "sfc /scannow" check of the Windows system files just to be safe.   Doubtful this is the cause, but it is good to double check just to be safe.   You might want to try running Prime95 in Torture Test mode as it can test & stress your CPU and memory (and power supply/motherboard) which might help to reproduce the failure more quickly while you are testing various fixes.  There is an option which focuses mostly on the CPU, one to focus more on memory and a third which is a mix.   Please update us if you find a solution as I am planning to build a couple of Ryzen systems soon. ... View more

As I mentioned in your other post, the file system may be playing a part.   Now you are comparing with another OS, app and filesystem  each of which will affect the readings and performance.   I've personally seen odd behavior when testing on OSX so I wouldn't be too concerned about the readings especially using the brand new APFS filesystem which still holds hidden mysteries.  While the APFS readings are not what I would expect to see, we don't fully understand how APFS behaves since it is so new or how it works on non-Apple SSDs (it shouldn't matter, but Apple usually only tests things on their own hardware since that is all they officially support).   I believe your SSD is fine.   If you have doubts or are concerned about APFS compatibility with the Crucial SSD, then re-install OSX and force it to use HFS+ instead by modifying the installer.   ... View more

@hilikus wrote:   A couple of comments, 1) the firmware when the drive died was M0CR050. I updated it today to see if that would fix the problem, but no    I've personally found the earlier firmware had issues which kept the SSD from properly reallocating bad blocks.   The issues persisted after the firmware update until I performed a Secure Erase, but if I had the time, I might have been able to let the internal maintenance routines correct the issue.     2) drive usage says 0GB, I hope that's because the partitions are not NTFS partitions and not because my data is gone. Is my assumption correct?    I don't know about this since I don't use Windows and CSE, but I would think your assumption is correct.   3) The AHCI warning, I tried to set the BIOS SATA setting to AHCI but then I wasn't able to boot windows, maybe the SSD supports AHCI but my other disks don't? could this have caused the problem?   You cannot change BIOS controller settings or Windows won't boot due to not having the necessary drivers installed.  I've seen posts with hacks to do this, but I don't know if I would trust it not to have side effects.  I don't think it would affect Ubuntu.   If you have the choice, I would definitely enable AHCI mode.       4) the overall status says "good health" but the SMART tests show otherwise. Why is it saying the health is ok? SSDs are built with extra reserved blocks to replace failing blocks, so it is normal expected behavior for an SSD to have some bad blocks over the course of its life.  As long as the bad blocks don't accumulate too quickly or affect the OS it should be Ok.   While your SSD did experience some Uncorrectable Errors which corrupted an Ubuntu system file, I would repair/reinstall Ubuntu and see how the drive works for a while since it has a 3 year warranty.  All of the bad blocks have already been reallocated.  After updating our MX300's I haven't noticed any issues for a year now after updating to the M0CR060 firmware.    If you are repairing Ubuntu, leave the SSD sitting powered on, but idle over night (disconnect the data cable or let it sit at the BIOS boot menu) so the internal maintenance routines can have time to run and fix things internally.  If you get the GRUB menu, then try booting an earlier kernel if available.  If you don't get the GRUB menu, then boot the Ubuntu installer as it has an option to fix simple boot issues such as reinstalling the MBR & GRUB.  Outside of this, I'm not sure it will be easy to discover the failure, but it would involve looking at the boot log and trying to determine which package needs reinstalled or which preference file needs repaired.  You could reinstall and keep your Home folder if it is on its own partition.   If you are re-installing, then do a Secure Erase on the SSD as that will reset it to factory defaults and correct any faults left over from the old firmware.  A Secure Erase requires the SSD to be connected to an internal SATA controller configured for AHCI mode or an external e-SATA port.   If CSE on your Windows drive won't do it because of the IDE mode, then you can temporarily set the BIOS to AHCI mode and Secure Erase using Knoppix.   Create a Knoppix USB disk using a portable version of Etcher. Read this guide and note all the warnings.  Then you should be able to Secure Erase the MX300 using the following commands substituting "sdX" with your SSD's identifier.   Sometimes I have problems sleeping/waking Knoppix to unfreeze the SSD so you may need to hot (re)plug the data cable on the SSD. Use GSmartControl to get the MX300 Linux identifier "sdX", or use one of the following commands: sudo lsblk -f sudo fdisk -l Use this command to check on the SSD security status: sudo hdparm -I /dev/sdX If it shows "frozen", then you need to sleep/wake Knoppix or hot re-plug the data cable on the MX300.   When it shows "not       frozen", then you can proceed to the next step. Use these commands to Secure Erase the SSD: sudo hdparm --user-master u --security-set-pass Eins /dev/sdX sudo hdparm --user-master u --security-erase Eins /dev/sdX   Monitor the SMART Attributes for a while to see if you get any more bad blocks especially ones which cause the Uncorrectable Error count to increase as those can affect the filesystem.   To better understand how SSDs fail, you should check out the very informatitive article series which stress tested SSDs 24/7 for a couple of years and documents their behavior and eventual failure.   ... View more

No, I would not expect it (actually I would expect it to be slower on writes), but it is a new filesystem and I haven't had much hands on experience with it yet to know how it behaves. ... View more

OEM user guides and specifications such as supplied by Dell will only tell you about what the OEM supplies for the system.  They don't always tell you what it is capable of supporting with aftermarket parts.   If it can support the 500GB NVMe drive, then I see no reason it won't also support the 1TB as long as the physical dimensions of the SSD fit the system.   If you are purchasing the SSD direct from Crucial and the Crucial guide says it is compatible, then you can always return it for a refund if it turns out it is not compatible. ... View more

The only two things I can think of is:   1)  The MX300's internal write cache is giving it the boost on writes   2)  Spotlight is indexing during the 2nd read phase.   Maybe if you are using APFS it has something odd going on here. ... View more

Double check your BIOS settings just in case something changed accidentally.  Perhaps even toggle the settings just to make sure they are not corrupt.  There are a couple of different settings which affect your M.2 slot and your other SATA controllers & even the PCIe slots.  Your M.2 slot shares resources with a couple of your standard SATA ports which must be empty.   Did you change any of your hardware at the time?  Is your motherboard firmware up to date?   Without another system or USB adapter to test the M.2 drive, it is hard to say if it is really bad or not since there is only one M.2 slot on your motherboard.  Maybe purchase an M.2 USB adapter such as this or this and see if you can see the drive. ... View more

I'm not sure what happened.  Perhaps your anti-virus or security software interfered or kept it from writing to the MX500.  Did it complete without an error?   I would create a bootable Acronis USB drive and boot from that to clone your system.   You should be able to create the bootable  USB drive from within the Acronis software on your original drive.   If the MX500 doesn't have a recognizable Windows filesystem, then it won't show up in Windows Explorer or under "This PC", etc.   ... View more

Is the Windows installer one you downloaded direct from Microsoft?  If not, then try using one downloaded direct from Microsoft.     Have you tried resetting the BIOS/UEFI to defaults or even removing the CMOS battery if it is accessible (maybe something is corrupt and holding its settings)?   If you install Ubuntu on the SSD, then in theory you should be able to boot it whether it is connected internally or externally (disable the HD password if used externally as I'm not sure you can unlock easily).  Might be worth a try to eliminate the SATA controller.  I don't use Ubuntu, but I believe it is compatible with Secure Boot. ... View more

When you reinstalled the software, did you first uninstall it and reboot?   What version of Windows are you using?   Have you checked to make sure your anti-virus or malware software isn't blocking it for some reason?   Have you checked Event Viewer to see if it is reporting any errors for this app which might aid in troubleshooting? ... View more

It sounds like you've tried everything possible.   Try the power cycle trick with your new adapter just to be sure, but if you don't see the MX500 as a physical drive in the BIOS of a standard PC, then it sounds like it just died.   If you boot from your original hard drive and connect the MX500 externally, do you see any LED activity on your dock/adapter?  Check Apple System Profiler under USB to see if the drive is physically seen by the system.  You could also check the system log to see if any errors are reported when connecting it using USB.   Many times with cases like this you may see errors reported as the computer is trying to communicate with the SSD's controller.   I've seen a fair amount of internal SSD controllers get stuck and unable to communicate with the host system (mostly non-Crucial SSDs).   If you were using FileVault on the SSD, then you should be Ok since your data is encrypted.   Otherwise you have to put your trust in  Crucial and/or the eBay vendor if you want to replace the drive under warranty.   If you decide the risk is too great, then you can physically destroy the SSD or you could keep the drive stored in a safe location and try accessing it again a year or two from now.   I've had a couple of SSDs come back to life after sitting on the shelf for a year or two.    ... View more

If you have the 13" model, then replace the hard drive cable.   This cable was known to have a high rate a failure on the 13" model.   If this is the 15" model, then you could disconnect the power supply & battery and try reseating the hard drive cable on the Logic Board in case it came loose during the upgrade.   If you want to confirm the internal hard drive cable is the issue (for either model), you can remove the SSD and connect it externally using a USB to SATA Adapter.   What version of OSX are you running?  If it is OSX 10.13+, is the drive formatted using APFS or HFS+?   Did you perform a clean install or did you clone the system?  If you cloned it, what utility did you use? ... View more

Please provide a screenshot of the SMART Attributes for the MX200.  In the mean time you could try leaving the SSD powered on, but idle to let the SSD's internal maintenance routines work their magic over night.  You can do this by unplugging the data cable (after unmounting the drive) or leaving the system sit at the BIOS screen or BIOS boot menu.    How much free space do you have on the MX200?  If the drive is almost filled, it can cause slowdowns since it requires more idle time for maintenance routines to work.  Also disable any settings that would put the SSD to sleep since it can take time for the SSD to wake up. ... View more

@nadhim wrote: I thought my 8GB is good enough for now but after making about 20videos my imac slowed down and I cant see smoothly the videos on FCPX while editing... Is it because of my memory which is 8GB? If your iMac is using a hard drive you should check to see if it might be starting to fail.  If things were fine and just suddenly got worse, I would suspect the hard drive.   You can use SmartReporter or DriveDx to check your drive.  You should manually check the RAW values of the following SMART attributes and if they are non-zero, the drive is failing:  Reallocated Sectors, Reallocated Event Count, Reported Uncorrectable Errors, and Current Pending Sectors.    Also check the Value/Worst value of the Load Cycle Count if the drive has this attribute.  If it shows as "001" then the drive is possibly failing and is definitely on life support and this was caused by having OSX "putting the drive to sleep when possible" setting in Energy Saver.   Check to make sure you are not running out of free space on your drive.   I'm actually surprised you can even edit videos using just 8GB of RAM. ... View more

I'm not a Windows user, but from my understanding you should be Ok without reinstalling if everything is working as you want it. ... View more

Probably the best thing to try first is downloading the Win10 installer direct from Microsoft.  Boot from the Win10 installer and select "Repair my computer", then select "Advanced" --> "Troubleshooting" -->  "Startup Repair".   The problem is most likely that the BIOS/UEFI needs to be pointed to the boot files on the MX500 and the Startup Repair should perform this operation for you.   If this doesn't work, please let us know and we'll see about other options. ... View more

When you tried setting the BIOS hard drive password, would it let you set it?  If not, then Win10 may have enabled hardware encryption and you will need to do a PSID revert on the MX500 which changes the MX500's internal encryption keys which should make the SSD appear blank.  I would also do a Secure Erase as well (after the PSID revert) to reset it to factory defaults just to make sure the drive is in a good clean state, but this should not be necessary.    Then you should be able to set a BIOS hard drive password.     If Samsung believes the MX500 SED features are interfering, then I would go into the laptop's BIOS/UEFI settings and disable Secure Boot and the TPM & reinstall Windows.   As a more extreme test, you could also disable UEFI mode and enable pure legacy mode if this is an option (may be under CSM settings) and reinstall Windows again by booting the installer using the traditional MBR boot option if available.  In theory this should minimize any Samsung laptop features from interfering.  Hopefully just disabling Secure Boot or the TPM would be enough if you don't want to use a hard drive password.   Another option would be to install Ubuntu Linux to the MX500.  If it can boot and reboot to the MX500 then you know the MX500 is compatible with the hardware (even with the above settings enabled: UEFI only mode, Secure Boot & TPM).   If this works, then you have a Windows issue.   As @targetbsp mentions, I don't see how the MX500's internal encryption would have any affect on the laptop since it should be invisible to it.   The laptop should only see a regular SSD until software enables the extra security features.   The BX series does not support hardware encryption, but unfortunately it does not have a 1TB option since the BX series is considered a budget or economy line.   ... View more

Firmware version MU03 was released in May 2018 for the MX100 series.  The note on it was to resolve a security vulnerability, but you never know if just the act of flashing it could resolve the issue.  Worth a try at this point. ... View more

As long as you are not writing continuously to the MX300 you should be Ok.  If you write continuously to it non-stop for more than 40 seconds, the internal cache fills up and performance can drop significantly (at least on the older firmware, I never checked with the new firmware).  Reading from the drive is fine.   Just make sure the firmware is up to date as I did have issues reallocating bad blocks on firmware older than M0CR060.   Since updating to this firmware I have   not experienced   any reallocation issues with our MX300s.   If you have the choice between the MX300 and the MX500 then I would definitely prefer the MX500 as it is much improved.    With the previously noted exception, the slight performance difference will probably be undetectable in normal use.   SSDs suddenly dying can happen to any brand although it does appear to happen less often with Crucial from my personal experience.  Make sure you have good working backups for any important data when using any SSD.    FYI, unless it is regional the MX300 I believe has a 3 year warranty and the MX500 series has a 5 year warranty from Crucial. ... View more

I have not used too many of the MX500s myself yet, but so far they've been good for an SSD utilizing TLC NAND.  I haven't seen many complaints on these forums either.   I'm really happy the prices have started dropping recently. ... View more