Samsung 850Pro/Windows 10 Anniversary performance is horrible

[dmitche3]

SO I made the mistake of upgrading to the Windows 10 Anniversary edition,and eventually to the latest Samsung Magician 5.0.

I say mistake as with the Anniversary update my system is taking nearly 3 minutes to boot while it was about 20 seconds prior to the update. In attempts to solve the problem I upgraded Charleton 5.0, err Magician 5.0 which no longer allowed me to enable Rapid Mode.

The SSD is now more than twice as slow as booting from my Western Digital Black drive. Even running things are very slow to start, so it isn't limited just to booting up.

Any suggestions including blowing it up are appreciated.

I don't think that losing the RAPID mode would make that much of a difference and to cause such horrible boot times.

My performance benchmark numbers are nearly 1/2 of what they were for random read/write, now at:

Sequential: MB/s
546 reads
499 write

random: IOPS
34,994 reads
31.965 write

I've searched Tom's and the web but nothing appears relevant as the drive had been working fine until the Windows 10 update. All of my drivers and such had been up-to-date prior to the upgrade and none have changed since, other than what Microshit may have altered without my knowing. 🙁


BTW, yes ACHI is still active as well as trim enabled.

hardware:
Asrock Fatal1ty 970
AMD 8370 8 core
16 GB Performance memory, (forgot the brand but not cheap stuff)
Geforce GTX 970 4Gb Asus

Samsung 850Pro SSD 256GB
WD 1TB black ( data storage and backup boot partition in the event of failures)
Seagate 2TB (data storage)

 

[SchizTech]

What OS did you have prior to upgrade? In the device manager, what do you see under "storage controllers" and "IDE ATA/ATAPI controllers?"

 

[dmitche3]

What OS did you have prior to upgrade? In the device manager, what do you see under "storage controllers" and "IDE ATA/ATAPI controllers?"

Windows 10. Under the controllers are:
ASROCK 3.0TB Unlocker
ASROCK RAM DRive
Microsoft Storage Space Container

IDE:
ATA Channel 0
ATA Channel 1
Standard Dual Channel PCI IDE Controller
Standard SATA ACHI Controller.

In the meantime I have reverted back to the prior build ( Windows 10 without anniversary and my performance has improved significantly, probably about 80% - 90% of what it was. But at this point it could be just a placebo effect. I don't think so.

I've also gone back to Magician 4.4 which allowed me to provision the drive which 5.0 took away. I did that before reverting to basic Windows 10. Random IOPS is now at 52k and random writes at 32k. So, quite a bit of improvement in the random reads, according to the tool. 🙁 I don't put much trust into it thought.

So, it looks like I'm in trouble as someday Microshaft will force the update on my and at that point I'm better running on my HDD, which I'm doing at this point. I'm going to install the update on the HDD and see if I get the same performance issues.

I'm afraid to bite the bullet and go to Linux as I've never had good luck with gaming. I like to use my computer these days and not have to play with it but Microsoft is really making that impossible. 🙁



UPDATE: WHOOOPS> I gave those results while running on my HDD. I'll reboot and post the results in a few minutes.

 

[dmitche3]

Well, I'm 99% satisfied with my conclusion of what the problem is but I don't like it.

The problem was the anniversary update but not the update itself. After rebooting back to my SSD drive it began complaining of a corrupted recycle bin on my HDD, which it shouldn't be using. As it turned out the anniversary update ended up co-mingling my two copies of the OS, one on the SSD and the one on the HDD.

I'm surprised that this happened but it isn't the first time I've experienced problems of this nature. Windows has always had a problem if it isn't installed in C:\windows. Okay, I haven't tried installing it to another location for the past 3 years but either windows or software will end up screwing you big time if you do.

But this is a slightly new twist, that the update found the wrong version and messed things up is very bad. Since it knows where I booted from and where my OS is I don't know how Microsoft could screw this up. Doing a BCDEDIT showed everything proper.

So, I disconnected my F: drive, put the Windows 10 DVD into the drive and did a repair and everything is running great. I then put the F: drive back online and freaked out as it was being accessed at boot, but only to see that it was indexing files. 🙁

I reran my Magician 4.4 and my results are much better. The IOPS are 55k, and 35k for random reads and writes. The system is just as snappy as it was before the Microsoft Anniversary update.

So Now that my HDD OS is buggered up I'll clone it from my SSD and then disconnect the drive and leave it off line until after doing the update.

But first time to get some sleep as I've been working on this for the past 22 hours straight and it's 5AM.

Thanks Microshaft for such excellent QA testing.

 

[dmitche3]

Follow up. I'm still a bit shocked at the Windows anniversary update co-mingling my two separate versions of Windows 10. What is the most surprising is that the event log showed no signs of problems other than the runtimebroker was having permission problems. But as I don't give a dam about windows stores I was in no hurry to fix it.

I've now updated by my HDD and SDD with the anniversary version having taken the HDD offline while doing the SSD and the SSD while doing the HDD update and things appear to be fine.

I'm back to Magician 4.4 for the Samsung 850Pro as the latest version didn't allow for overprovisioning nor RAPID mode using an AMD chipset. Having this drive 3 years I've had no problems with it other than it died with a power outage and I had to send it back to Samsung's 3rd party to be repaired. I saw no performance 'slow down' with RAPID on as Samsung claimed was the reason that they disallowed it with AMD chipsets. The only bad thing is that Samsung Magician does NOT, I REPEAT that MAGICIAN does NOT give firmware updates to my drive. Version 4.4 said that there were no firmware updates for my drive but version 5.0 indicated that there was an update. Hopefully Samdung (their more appropriate name) hasn't pulled a fast one and is hiding a defect that will now become an issue now that the firmware is newer and Magician is not. 🙁

 

[dmitche3]

Well, I was wrong. But not by much. There is a serious bug in windows 10 and here it is. After doing what I said above I connected my HDD which contains a separate Windows 10 installation. And guess what? Windows 10 on my SSD drive started running the programs under the HDD windows folder when I rebooted. Crazy but it just decided to run which every copy it finds. Forcing the HDD offline via a "chkdsk /f f:" and the OS relaunched the applications that were using the F: drive to use the SSD windows folder. Sacre Chat! This is amazingly stupid. Time to open a ticked with MS.