camer0 :
techgeek :
If you look under your SATA controller in Device Manager, what does it have for a driver? Is is iaStorA.sys or something like that?
Though you have a different SSD than I do, some of your numbers look a little low, particularly your write values. Almost like Trim isn't working. I assume you had another OS (or even an old Windows 10 Preview) before you installed the present OS, did you do a secure erase of your SSD prior to installing the OS?
Where exactly do I find the SATA controller in Device Manager? I am having difficulties locating it.
No I just let the Windows 10 "format" the drive to install it
An SSD operates differently than a HDD with regards to writing data. When you format a drive, the data isn't erased, the format deletes and remakes the file location table. So technically all the data is still there, but there is no way for the OS to find it because the map to locate each file is gone. Then as data is written to the drive it overwrites the old data. For HDD's this isn't an issue. For SSD's though, it can cause write performance problems. When data is written to a NAND cell, the firmware checks to see if there is data stored in that cell. If it has data, the drive first has to erase what is stored in the cell and then write to it. It's actually a little more complicated than this, but these are broad strokes. If you want a more detailed explanation have a look at this article:
Trim and Garbage Collection explained
This becomes more complicated when all the data is orphaned by the OS (in the case of it being wiped and re-installed), but the process is the same.
So if you don't secure erase the drive, and then re-install the OS, you could actually be causing performance problems. There is another component in the firmware of your drive that almost guarantees this behavior. It's called wear leveling. Since NAND has a finite number or write cycles, you firmware will not likely write to a location that has data in it (although it's no longer valid) in an attempt to share the write cycles around.
Now if used long enough, the TRIM function and garbage collection should clean this up. However I'm not sure the TRIM function will work on orphaned data (data leftover from a previous OS install) since the OS isn't aware of the data that was on the drive prior to you installing it. So garbage collection maybe the only automatic fix. Again though this may take a long time depending on how aggressive the garbage collection subroutine is in the firmware of the drive.
There is a quick fix though. You can run Defraggler's SSD Optimizer. I'm not a 100% sure that it will work on Windows 10, though I would think as long as your SSD was formatted NTFS, that it should work.
However I'm not sure that this will necessarily fix your original problem.
As for the driver, yes you find this in Device Manager under Driver Details.