Samsung 840 Pro 256GB Freezing!

Garmin · 22 Jul 2013 at 10:44

I have 2 Samsung 840 Pro 256GB's in my system which have the latest firmware applied to them. I have a feeling that they are causing my system to crash, pressing ctrl +alt+del, ctrl+shift+esc, are non responsive and I have to hit reset to reboot the PC. There is no warning or pop up window before hand to indicate any errors.

This happens using win7x64 fully patched on an Asus P6X58D-E, I have a Crucial C300 128GB in the system which has not made the system freeze.

Has anybody else here experienced any issues with these drives causing the system to freeze? before I go down the route of reinstalling everything again just to eliminate the drives as the problem.

Dervious · 22 Jul 2013 at 10:49

Which of your SSDs is Windows installed on ?

Have you got the 840's in Raid mode ?

If you have Windows on one of the 840s and the Crucial, are you testing them in the same Sata port ?

Are you overclocking your CPU ?

Garmin · 22 Jul 2013 at 11:12

Just to give an update my drives would not be set up as a standard PC.
I have Win7x64 on one of the 840 Pro SSD's
I have Win8.1 on the second 840 pro
I have Win7x64 on the crucial c300 128GB
I have virtual machines and MDT 2012 installed on the c300, win8.1 is just for evaluating, and my main use drive is the one that is causing the issues.

My i7 950 is presently at 3.36Ghz, I did have the system raided when I first purchased the Samsungs, but I decided after a while to take them off of raid 0 as the main difference to me was only in benchmarks.

Dervious · 22 Jul 2013 at 11:30

You`ve probably already tried the obvious......

Remove all SSDs from the system and test each one individually.

If both of the Samsungs cause a "freeze", but the Crucial does not, it would suggest either a fault with both of the Samsungs (unlikely, but anything can happen !) or a compatibility issue.

It might pay to connect a Samsung to a non-Intel Sata port if you have any on your motherboard, that might help to identify if there is some sort of compatibility issue, or a problem with your Intel ports/drivers.