Newly bought Crucial MX300 SSD made Windows 10 desktop unstable

Peter_221

Prominent
Feb 27, 2017
7
0
520
Hello gals & guys,

I went through a ton of similar but not identical issues posted on various hardware forums. Tried some of the proposed solutions with no luck. Decided to post my specific problem. Will be thankful for any suggestions (I have to make my living using this machine an was hoping for the SSD kick, which I got but... :).

My system:
GA-P55A-UD4 (rev. 1.0, BIOS ver. F15),
i7-860 (Zalman-coolled, no overclocking),
GoodRAM 4x4GB (DDR3 1600 MHz, CL9, underclocked at 667 MHz in dual channel, 1.5 V),
MSI GTX660 TwinFrozr III OC (stock-clocked),
2x WD Black 500GB (SATA2) in RAID0 (stripe) - both powered from a single PSU line,
1x Crucial MX300 525GB (SATA3) - powered from a separate PSU line,
LG BlueRay/DVD combo (SATA2) - powered from a separate PSU line,
PSU Chieftec CFT-650-14C (nearly 8 yrs in service),
Windows 10.0 Pro 64 bit, build 14393, up to date, all power saving turned off

The problems described below can occur also in a basically idle system with temperatures across the CPU, mobo, HDDs, SSD, GPU in the range 25-35 deg C.

This system originally had just the RAID0 storage with the OS and everything else on it. I bought the SSD, cloned the RAID0 using Acronis True Image (in 'clone disks & partitions' mode) onto the SSD, and attempted to run the OS from the SSD.

The mobo has two SATA controllers: the Intel SATA2 in the chipset and a Marvell 9128 SATA3. I get the following symptoms:
1. SSD on Intel channel 0, RAID0 on Intel channels 2 and 3, boot from RAID0 -> no problems whatsoever,
2. SSD on Intel channel 0, RAID0 on Intel channels 2 and 3, boot from SSD -> OS running stably except for random instant shutdowns (power-offs, like from a power outage); their frequency prevents reliable use of the system,
3. SSD on Marvell in AHCI (media not accessible in IDE mode), RAID0 on Intel channels 2 and 3, boot from SSD -> OS unstable, applications' crashes, system freezes, use of the system impossible.
4. SSD in AHCI mode on either Intel or Marvell, RAID0 dismantled into two non-RAID drives on Intel -> same problems as in cases 2 and 3, respectively.

The SATA3 of Marvell isn't worth it since the PCI-E 1x it is hooked on allows 2.5 Gbps (read from Marvell BIOS) making it slower than the Intel SATA2 (confirmed with CrystalDiskMark).

So far, I cleared the CMOS, loaded optimized BIOS defaults, rebuilt the power management tables in Windows 10 by running 'winsat formal', to no avail. Intuition told me a clean OS install wouldn't help, so I didn't bother, yet.

A possible hint: monitoring the system voltages using CPUID HWMonitor I noticed occasional significant drops of ALL the voltages when the system was idling. Particularly, the +5 V dances in idle state. It becomes a sharp 5.107 V only when the CPU is loaded. Is this a normal behavior or could it point to a worn out PSU?

UPDATE:
Case 1 above is no longer valid. I have just noticed crashes and computer turn-offs even with the SSD no longer in the computer and running the old RAID0. CyberLink AudioDirector triggers the bad event each time I try to load a file into a project, which is associated with intensive HDD work.
 
Solution
The problem is now solved. There were actually two separate problems.

Firstly, the PSU, which was 7+ years in service, decided to go bad when the SSD was hooked up. This is understandable because SSDs draw 3 times as much current as the HDDs. After replacing the PSU, the system started working reliably with the RAID0. However, Windows 10 continued to crash without apparent causes when booted from the SSD. (Meanwhile I stress-tested the CPU and the RAM to discover they were rock-stable.)

Somewhere in this forum I read about the importance of loading the right SATA driver in Windows 10. I discovered that I had some historical Intel Matrix Storage installed, although the device manager stated a Microsoft SATA driver was in use. I cleaned...

Peter_221

Prominent
Feb 27, 2017
7
0
520
The problem is now solved. There were actually two separate problems.

Firstly, the PSU, which was 7+ years in service, decided to go bad when the SSD was hooked up. This is understandable because SSDs draw 3 times as much current as the HDDs. After replacing the PSU, the system started working reliably with the RAID0. However, Windows 10 continued to crash without apparent causes when booted from the SSD. (Meanwhile I stress-tested the CPU and the RAM to discover they were rock-stable.)

Somewhere in this forum I read about the importance of loading the right SATA driver in Windows 10. I discovered that I had some historical Intel Matrix Storage installed, although the device manager stated a Microsoft SATA driver was in use. I cleaned all that up and installed the latest Intel Rapid Storage Technology drivers (recommended for all Intel systems running all Windows versions up to Windows 10) and voila!
 
Solution