06-19-2018 11:59 AM - edited 06-19-2018 12:05 PM
Hi, I'm new here so apologize any mistakes etc.
I just need help since I recently installed a new Crucial BX300 120GB SSD in my Ryzen system,
everything worked fine on a fresh Windows install except several weeks ago Windows and every window within it has been freezing.
The current window stays operational to a certain degree, whether it be a game or a program, however nothing else loads or is interactable properly, after a couple seconds - up to even 2 minutes, everything unfreezes and my commands are "sent".
If I have task manage open and catch it whilst it's freezing, the SSD jumps to 100% usage with no programs using it, I assure anyone here that I have absolutely no bloatware nor is this an issue I created - same thing happened on an old, trusty, install of Windows alongside the most brand-spanking update with a new ISO from Microsoft.
I will add some images of the two, only, but consistent events in event viewer that I recieve during the freeze.
I also want to add that I have not made any changes; the issue started occuring randomly and I updated, reset and tuned my BIOS - all steps of which still created the issue.
I've reinstalled Windows multiple times and yet the error and freeze still occurs, even on a completely fresh and updated install straight from Microsoft's ISO tool
I've heard that there may be an issue with these SSDs and the AHCI mode on the SATA controller, specifically something to do with power savings. I've tried turning off all power saving options to no avail, and my system does not have IDE mode.
This issue also seems to never, or very rarely arise, when exclusively just playing a game - especially one on a second HDD.
I would really appreciate "standard" fixes, if there are any, that I haven't tried and may be quite simple - but I wouldn't mind tinkering with stuff to get it to work as long as it's not non-optimal.
I aslso did sfc /scannow and DISM online image cleanup, no errors appeared but still keep freezing.
And if this is a manufacturing/design flaw, what should I do? I got this SSD maybe 3-4 months ago from Amazon.
The exact specifications of the system
MSI B350 Tomahawk, 'initial' BIOS: |7A34v1F|, current BIOS: |7A34v1H| (Happens on both)
Ryzen 3 1200 (Stock)
PSU/RAM/GPU are unrelated and I don't want to bloat this post as they work.
06-19-2018 12:48 PM
Check the SMART diagnostic data in Crucial Storage Executive or Crystal Disk Info. I/O errors aren't usually a good sign!
06-19-2018 01:03 PM
Since I use HWiNFO64 quite often, and it never showed warnings/errors, I never thought to check CrystalDiskInfo, thanks.
Here's the screenshot of the SSD in Crystal Disk Info and it looks 'clean' to me, but I don't know.
06-19-2018 02:36 PM
Thank you for contacting us. When it comes to an I/O errors there are a couple of things you can try to fix the issue. I would swap out the current SATA cable that is connected to the if you can. Then check to see if there is an updated SATA driver from the system manufacture. Then force Active Garbage collection on the drive. (link below will explain how to do this) Try performing a fresh install of the OS to the drive.
If none of these resolve the issue then you can contact us to proceed with a replacement.
06-19-2018 02:59 PM
Thanks for the fast reply,
I don't think I will be able to run the Active Garbage Collection by leaving it on for so long, I will try and go through with it though.
I'll do the other steps, run TRIM and 'Secure Erase +' from my motherboard to wipe the drive and give it another clean Windows install, hopefully it works but there's always the possibility it doesn't.
Anyhow, thanks again for the fast replies and nice suport.
06-30-2018 12:32 PM
Hi, I've received the RMA-d SSD yesterday, but the issue still persists.
Does anyone have any ideas as I've recently tested an M.2 SSD and it worked flawlessly, and I've used a different SSD a couple of months back in this system without issues over the span of 2-3 days.
What I'm asking is is there possibly some design with the SSD that may just be messing up with my setup, or a possible flaw that has come up from my MoBo very recently that only affects SSDs in SATA.
I would like to get to the bottom of this, and am unlikely going to bother with any more RMAs as it's a hassle and I'll soon have a use of the drive as a scratch disk for a certain suite of video production software cough cough that's memory/storage hungry, but for the meantime it's an annoyance that I wouldn't expect to have come across twice (Though, to be fair, I've had to replace 2 ram kits, a dual-case fan kit and GPU fans, so it might just be my luck)
Anyhow, thanks for the help.
07-05-2018 01:31 AM
07-05-2018 06:51 AM
The PC is a custom build, so it's not directly from one manufacturer per se, though I had and have the AMD Ryzen Chipset Driver that is on the MSI Tomahawk "Chipset Driver" tab, however I got it straight from AMD as it is easier to download and it auto updates anyway. (So it would end up on the same version)
07-06-2018 02:13 AM
Your screenshots from the first post show some information related to storahci that is generic Windows 10 AHCI driver, that is why I thought the issue may be driver related.
Please post SMART data of the drive again, your CDI screenshot is still under moderation. You can post the information as a text - with CrystalDiskInfo use 'Edit > Copy' option, just please remove drive's serial number.
Also to make sure about your SATA driver could you please check its details? You can check it with Device manager -> IDE ATA/ATAPI Controllers (or Storage Controllers) -> right click on the selected controller -> Properties -> Driver tab
07-06-2018 07:36 AM
I'll put the SMART data of the SSD below and on pastebin.com/AZSAFiUn, (This is alrady a replacement one, so I would hope it's not related to the SSD but I don't know)
These are the two SATA AHCI Controllers that show up, both seem to be the exact same, the details of each one are underneath their respective window.
I also don't know why they are dated as Microsoft as I've installed all the drivers etc. unless they are supposed to be.
Here's the SMART data