Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

tetet

macrumors newbie
Sep 13, 2017
23
5
So my results of 890MB/s write 1090MB/s read are quite coherent with your 1000MB/s write. You have read speed lower that write speed on the 15" ? I'll try to test on my 15" and tell you..

Sorry for the mistake. I got about 800MB/s write and 1500MB/s read on adata XPG7000. I can privide you a screen shot if you are interested.

And kernel panics occured 100% of times (with the backup failing always after 30-50 GB data copied) while doing the same full backup (400GB) from a Samsung 960 evo/pro to an external fast (300MB/s) samsung T2 usb 3.0 ssd.

I will try the same method, and update you with the results.
 

damex

macrumors newbie
Nov 12, 2017
14
6
hi,
i sadly started encountering a panics (which lead to immediate reboots) over heavy disk i/o with 1T 960 pro on mbp13 early 2015. reproducible. using sintech adapter.
not reproducible with linux or windows.

i removed it from 2014 mac mini. if i set it up as main drive - same panics. no panics if i use linux or windows. if i set it up as a secondary drive for my 2014 mac mini - it works perfectly fine on osx and no issues so far. linear speed is lower because interface has just two pci-e lines/lanes...

sadly had to revert back to original apple ssd on macbook pro;(
 

wawon

macrumors member
Oct 2, 2017
61
16
Japan
I ordered SSD adapter for sintech again, and the order arrived today. To my surprise, PCB was not green but black and its size was small. So I carefully see it suspecting that old products have been sent, it seems that Kapton tape is affixed and there is no difference from the green adapter in terms of circuit. It seems that a new version of the adapter was offered.
P1040012.JPG
 
  • Like
Reactions: Audit13

MacIsHard

macrumors newbie
Oct 24, 2017
11
3
Has anyone found a workaround for the crashes and battery issues when using the Evo 960?
Am already using Kapton and hibernation mode 0 with the larger shin-tech adaptor.
 

ravic

macrumors member
Jul 2, 2007
84
10
I just ordered a Sintech adapter from their webSite
Also ordered a Samsung PM961 512gb ssd

I am looking to install it in a MacBook Pro 13” early 2015

I will post here what my results are. Looks like some folks are successful here with this combination

I just got the SSD, so i installed with the cheap ChenYang adapter from Amazon while i wait for the sintech. It works well so far. I had to shutdown and reboot twice for the laptop to detect the SSD to install High Sierra. But once detected it installed well and working well.

Edit: spoke too soon. I do see the sleep issues as others have reported. Waiting for my sintech adapter to arrive from china. Hopefully next week. Then i will post an update if that the big variable with all of these kernel panics /sleep issues.
 
Last edited:

fgoma

macrumors newbie
Jan 23, 2018
1
0
Time to a little update.

Compatibility with AHCI PCIe drives : (ex. lite-on LGT-512B1P)
- work in every 2013-2014-2015-2017 macs, but sleep may be a concern (past 2014)
It is to be noted that Transcend announced some PCIe SSDs (probably AHCI) for every PCIe macs, the transcent Jetdrive 820 (but only 2 lanes and price not yet available) :
https://www.transcend-info.com/apple/jetdrive_pcie

Compatibility with Apple NVMe drive : (like those found in 2017 iMacs)
- Mac Pro late 2013 : doesn't work [edit 2017-09] : works after bootrom update
- MacBook Pro retina 13"-15" late-2013 : doesn't work [edit 2017-09] : works after bootrom update
- MacBook Air early 2014 : doesn't work [edit 2017-09] : works after bootrom update
- MacBook Pro retina 13"-15" mid-2014 : doesn't work [edit 2017-09] : works after bootrom update
- Macmini Late 2014 : works
- MacBook Air early 2015 : works
- MacBook Pro 13"-15" early 2015 : works
- MacBook Air early 2017 : works

Compatibilty with non-Apple NVMe drive, (Samsung ), to this date the tests I have done yet are :
- Mac Pro late 2013 : doesn't work [edit 2017-09] : works after bootrom update
- MacBook Pro retina 13"-15" late-2013 : doesn't work [edit 2017-09] : works after bootrom update
- MacBook Air early 2014 : doesn't work [edit 2017-09] : works after bootrom update
- MacBook Pro retina 13"-15" mid-2014 : doesn't work [edit 2017-09] : works after bootrom update
- Macmini Late 2014 : works
- MacBook Air early 2015 : works
- MacBook Pro 13"-15" early 2015 : doesn't work [edit 2017-09] : works after bootrom update and with Kapton tape on adapter
- MacBook Air early 2017 : works

* : The problem with the MacBook Pro 13" and 15" early 2015 seems not to be insurmountable.
Sometimes, the NVMe drive work, but mostly they fail to be recognized.

To me, it's a timing or signal quality issue due to adapters (Sintech or other) between Apple 12+16 and M.2).

Those adapters are not designed to handle PCIe 3.0 speeds I guess.
They add a connector and complexity to the signal path, so they lower the RF integrity and compatibility with the higher speed of the PCIe 3.0 signals (8Ghz vs 5Ghz for PCIe 2.0).

The MBA (even 2017) and MacMini 2014 being stuck to PCIe 2.0 due to their Broadwell 5xxx CPU, they don't have this problem...

I'm still investigating on how to either downforce PCIe to 2.0, either insure better signal quality to make the SSD work with 2015 MBPr 13" and 15".

Hi @gilles_polysoft I have been trying to upgrade a Macmini Late 2014 but my SSD still unrecognized, and have followed the thread booted from externar disk with macos High Sierra, maybe I'm missing something. Can you confirm if this parts could work in Macmini?
 

Attachments

  • IMG_6850.jpg
    IMG_6850.jpg
    845.9 KB · Views: 710
  • IMG_6854.jpg
    IMG_6854.jpg
    590.7 KB · Views: 572
  • IMG_6855.jpg
    IMG_6855.jpg
    575.9 KB · Views: 520
  • IMG_6856.jpg
    IMG_6856.jpg
    532.8 KB · Views: 599
  • IMG_6857.jpg
    IMG_6857.jpg
    1.2 MB · Views: 576
  • IMG_6858.jpg
    IMG_6858.jpg
    918.1 KB · Views: 530
Last edited:

ravic

macrumors member
Jul 2, 2007
84
10
monofase, i ordered a sintech adapter too. But seems like they are shipping a newer black version. Hopefully it is as stable as yours. Mine is stable but has sleep issues with the chenyang adapter. I have a PM961 which is very similar to 960 Evo
 

Attachments

  • DiskSpeedTest2.png
    DiskSpeedTest2.png
    583.9 KB · Views: 458

Earl Urley

macrumors 6502a
Nov 10, 2014
793
438
Some 960's shipping with newer firmware may be the cause of some of the issues; if your firmware is a certain older level it should be fine, as I have had no issues with the revision I have.

If your 960 EVO has a firmware revision of 3B6QCXP7, you might run into problems. Newer stock may be shipping with this version.

My 500 GB 960 EVO has the previous version, 2B7QCXE7 and I haven't encountered any problems.

Windows users report a lot of problems with 3B6QCXP7 here and here, among other places.

DriveDx or smartctl from Homebrew can tell you what firmware is on your 960 EVO.

BTW, 10.13.3 seems to be working okay with my 960 EVO, don't think there were any changes to the BootROM or the NVME plugin though.
 
Last edited:

gymboy

macrumors member
Jan 1, 2018
35
7
London, UK
A little update here:

Macbook Pro 13" 2015 daily use NO ISSUES! With @gilles_polysoft 's green sintech adapter, kapton tape and 960 Evo! Works like a beast!

Same for my side as well! Thanks to @gilles_polysoft for the large green snitch adapter and the 960 Evo is working fab on my 2015 MBA, no issues so far, will monitor and give an update as well!

monofase, i ordered a sintech adapter too. But seems like they are shipping a newer black version. Hopefully it is as stable as yours. Mine is stable but has sleep issues with the chenyang adapter. I have a PM961 which is very similar to 960 Evo

For the black ones you will still have problems with sleep I think, I am not too sure, but my 960 Evo with the Black Sintech Adapter had problems with waking up from sleep. I think it's probably an issue with the Black Adapters, not too sure though.
 

chrissnn

macrumors newbie
Jan 23, 2018
9
0
Hi to all,

I just tried to make a little table of all the SSD I've tested so far. Hope it helps a little.

View attachment 746441

PS : I'm waiting for a Toshiba XG5 and will add it to the results in a few days.
If you have other data or results, please tell me so that I can add them or confirm or infirm the datas I have.

[EDIT]: I just add the same table sorted by price instead of by name

View attachment 746448
I've read most of the forum posts. Thanks for all the work done!! Are there any updates regarding this overview? I saw the Samsung evo also giving stable results?
 
Last edited:

ravic

macrumors member
Jul 2, 2007
84
10
Some 960's shipping with newer firmware may be the cause of some of the issues; if your firmware is a certain older level it should be fine, as I have had no issues with the revision I have.

If your 960 EVO has a firmware revision of 3B6QCXP7, you might run into problems. Newer stock may be shipping with this version.

My 512 GB 960 EVO has the previous version, 2B7QCXE7 and I haven't encountered any problems.

Windows users report a lot of problems with 3B6QCXP7 here and here, among other places.

DriveDx or smartctl from Homebrew can tell you what firmware is on your 960 EVO.

BTW, 10.13.3 seems to be working okay with my 960 EVO, don't think there were any changes to the BootROM or the NVME plugin though.

Firmware version on my Samsung PM961 512GB is 6L7QCXY7
I have issues with sleep with the cable (ChenYang) adapter. Researching to see what version this is.
 

ravic

macrumors member
Jul 2, 2007
84
10
Добрый день,
Если ваш комп не видит диск проверьте, что контакты 18(3.3V) & 20(Зарезервирован) на переходнике соединены как на изображениях (ножки 9-10 если считать со стороны). Спайка решила мою проблему на MacBook Pro a1502 2013 late. Диск - Samsung 960 Pro 512 гб. После спайки диск был обнаружен. Кстати в диспетчер дисков глючит и с первого раза не видит диск.

Счастливо

Добавлено позже:
Работать можно, но если хочется что-бы после перезагрузки с диском не было видно папку с вопросом нужно заниматься еще одним паянием. Если решусь на это, то напишу в постах дальше.

Hi guys,
If you have a problem with the adapter check pins 18(3.3V) & 20(Reserved) as on image(9-10 by side). Have be connected.
MacBook Pro a1502 2013 late. SSD is Samsung 960 Pro 512 gb. The soldering solved problem for me.

Regards.

I wonder if soldering mentioned here is the fix for the issue with cablecc adapter?
 

Marno

macrumors newbie
Oct 13, 2017
10
0
Hello everyone,
I received a KC1000 906GB (for 4K format) and a BLACK sintech NGFF adaptor and I also ordered some kapton Tape.
I will update my EFI in order to stay with my current Sierra install (don't plan to update to high sierra for a while).
Then I will keep you posted if I happen to run into problems.
Regards.
 

flemmingdjensen

macrumors member
Nov 30, 2017
37
16
Denmark
Hi, here is a little update from my experiences ;)

I have now been using the KC1000 960GB in my MBP15 Mid 2014 for several weeks.

I do get Kernel Panics occasionally - say maybe every second or third day. So Im still hanging in there trusting the JFS to do its work :)

I still need to open my computer and put tape on top of the adapter where it might get close to the metal on the MAC connector.

When I get the KP it always happens at the exact same location:

=============================
*** Panic Report ***

panic(cpu 0 caller 0xffffff7f8de5ea3c): nvme: "Fatal error occurred. CSTS=0xffffffff

. FW Revision=E7FT04.6\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-356.30.6/IONVMeController.cpp:5275
=============================

I then just for fun tried googling "IONVMeController.cpp 5275" and found that there are even MBP 2017 experiencing the exact same error....

https://www.google.dk/search?q=IONVMeController.cpp+5275&oq=IONVMeController.cpp+5275

So maybe we will get an updated NVMe driver in the near future -- still hoping and then I will install my EVO 960

BR Flemming
 

gilles_polysoft

macrumors regular
Jul 7, 2017
244
671
Tours (France)
hi,
i sadly started encountering a panics (which lead to immediate reboots) over heavy disk i/o with 1T 960 pro on mbp13 early 2015. reproducible. using sintech adapter.
not reproducible with linux or windows.
[...]
sadly had to revert back to original apple ssd on macbook pro;(

Thanks damex for your report... I too have the issues with heavy disk i/o, only with samsung drives...

Hi @gilles_polysoft I have been trying to upgrade a Macmini Late 2014 but my SSD still unrecognized, and have followed the thread booted from externar disk with macos High Sierra, maybe I'm missing something. Can you confirm if this parts could work in Macmini?

Hi fgoma, please can you tell me which BootRom has your Mac Mini ? it should be MM71.0224.B00 so that any NVMe SSD can work..
[doublepost=1516832211][/doublepost]Hi to all,

I did took some time to make some comparisons between the large "v2" sintech adapter and the new "v3" black adapter.

The two things tested were :
- reboot : cold start followed by 10 reboots. The test succed if no problem occurs, and fails if connection with SSD is lost at any reboot (blinking folder)
- huge i/o transfers : a full clone from the internal NVMe boot drive to an external fast USB 3.0 Samsung T2 SSD is done with Carbon Copy Cloner 5. The test fails is a kernel panic occurs and succed if the full clone succed (with an average speed of 2-300 MB/s and 400 GB of data copied)

Here are the results, all on the same rMBP 13" late 2013 and under macOS 10.3.3 :
- black v3 sintech with adata KC7000 : reboot test succes huge i/o transfers success
- green large v2 sintech with adata KC7000 : reboot test succes huge i/o transfers not done, need to confirm.
- black v3 sintech with 960 Evo : reboot test fails, huge i/o transfers fails
- green v2 sintech with 960 Evo : reboot test succes, huge i/o transfers fails

All test done with proper kapton tape insulation at the back of the adapter (so that we got stable connexion with 4 lanes).
standby mode 0, so no problem on sleep.

So there is definitely a problem with the new black adapter and Samsung drives...

I did check electrical differences between the two adapters, with a multimeter.
This is a huge work, not yet finished, I have still to verify the full connexions table of the black adapter.

But, so far, here are my observations on the green large v.2 Sintech adapter :
- pin 49 (SSD_DEVSLP) on the Apple 12+16 connector is not connected
- pin 47 (SSD_PWR_FET_EN) on the Apple 12+16 connector is connected to M.2 pin 38 (DEVSLP)
- pin 24 (SSD_CLKREQ) on the Apple 12+16 connector is connected to M.2 pin 52 (CLRREQ)
- pin 8 (SSD_RESET) on the Apple 12+16 connector is connected to M.2 pin 50 (PERST)
The two last lines seem logical, but I don't understand why pin 49 of the Apple 12+16 connector is not connected to M.2 pin 38 (DEVSLP both !)

Here are my observations on the black v.3 Sintech adapter :
- pin 49 (SSD_DEVSLP) on the Apple 12+16 connector is left unconnected with an empty solder pad for connecting it via a cms resistor (not present) to +3,3V
- pin 52 (CLRREQ) of the M.2 SSD is left unconnected with 2 empty solder pads : one to connect it to 3,3V and another one to connect it to GND
- pin 50 (PERST) of the M.2 SSD is connected to level high (+3,3V)

Obviously those differences may explain the differences between the green and black adapters regarding reboots with Samsung drives...

The green V.2 adapter seems to have the most logical interconnexions. At least this green adapter works with every other SSDs than Samsungs and I use it for 6 months now in 3 rMBP (and kingston and thosiba drives) without any issues...


I wonder if I couldn't try to modify a green adapter with connecting both pins DEVSLP between Apple 12+16 and M.2 connectors ? I may give a try next saturday...

And I don't understand why on earth does Sintech made so many modifications on its v.3 adapter, especially modifications that seem illogical...

Here are the pinouts collected so far :

1 - Apple 12+16 PCIe SSD "gumstick3" connector.png

2 - M.2 PCIe SSD pinouts, m-key.png

3 - Sintech "v.2" large green adapter connexions, from Apple side .png

4 - Sintech "v.2" large green adapter connexions, from M.2 .png

[doublepost=1516833002][/doublepost]
I ordered SSD adapter for sintech again, and the order arrived today. To my surprise, PCB was not green but black and its size was small. So I carefully see it suspecting that old products have been sent, it seems that Kapton tape is affixed and there is no difference from the green adapter in terms of circuit. It seems that a new version of the adapter was offered.
Hi wawon,
thanks for your update ! I checked and it seems that circuit is a lot different...
At least sintech has made an effort with the kapton tape, it's fun to see it !
 
Last edited:

gilles_polysoft

macrumors regular
Jul 7, 2017
244
671
Tours (France)
Hi, here is a little update from my experiences ;)

I have now been using the KC1000 960GB in my MBP15 Mid 2014 for several weeks.

I do get Kernel Panics occasionally - say maybe every second or third day. So Im still hanging in there trusting the JFS to do its work :)

I still need to open my computer and put tape on top of the adapter where it might get close to the metal on the MAC connector.
Hi Flemming,

thanks for your update, and yes, please do me a favor :) open your Computer and put some insulation tape at the back of the connector.. As you can see even Sintech puts some kapton tape on the adapters they ship now :
https://forums.macrumors.com/thread...ssd-to-m-2-nvme.2034976/page-31#post-25731096

It will ensure proper insulation, and also avoid unwanted capacitances which strongly deteriorate the signal quality (which may cause kernel panics...)

I have 3 examples of rMBP using kc1000 drives properly installed with good adapters and kapton tape insulation, and they run without having had any single kernel panic for months... (they are all in Sierra with 4k blocs)

regards
 
  • Like
Reactions: flemmingdjensen

Audit13

macrumors 604
Apr 19, 2017
6,906
1,845
Toronto, Ontario, Canada
The SM series is much faster than PM so a SM951 is a better deal than a PM961. Not sure what they did elsewise between the series but I was impressed with the SM951 and very dissapointed with PM961. Have yet to test if the SM samsung crash on heavy file transfers.
[doublepost=1515837551][/doublepost]
Have installed several 600p 512GB. Only way to fix the deep sleep issue I found out is to disable hibernate and write lock sleep image file. Then very stable and no special power issues. No problems with large file transfers.
I finally got a pci-e adapter so I could flash the firmware on my Intel 600p 256 GB from PSF100C to PSF121C with my Windows desktop.

No change in write or read speeds after a clean install of High Sierra. The battery still drains more quickly than the oem Apple SSD but no other issues to report.
 

ravic

macrumors member
Jul 2, 2007
84
10
Hi again,

Yes I need to put the kapton tape on the adapter as instructed.

My ultimate goal is to get my EVO 960 SSD to work in the MBP.

Has anybody tried patching the NVMe driver?

It might be the only way to get those drives with a lot of KPs to work?

https://github.com/RehabMan/patch-nvme

/// Flemming

Thanks. Interesting patch. I need to research it to see if it can help with Samsung ssd.
[doublepost=1516877474][/doublepost]
Thanks damex for your report... I too have the issues with heavy disk i/o, only with samsung drives...



Hi fgoma, please can you tell me which BootRom has your Mac Mini ? it should be MM71.0224.B00 so that any NVMe SSD can work..
[doublepost=1516832211][/doublepost]Hi to all,

I did took some time to make some comparisons between the large "v2" sintech adapter and the new "v3" black adapter.

The two things tested were :
- reboot : cold start followed by 10 reboots. The test succed if no problem occurs, and fails if connection with SSD is lost at any reboot (blinking folder)
- huge i/o transfers : a full clone from the internal NVMe boot drive to an external fast USB 3.0 Samsung T2 SSD is done with Carbon Copy Cloner 5. The test fails is a kernel panic occurs and succed if the full clone succed (with an average speed of 2-300 MB/s and 400 GB of data copied)

Here are the results, all on the same rMBP 13" late 2013 and under macOS 10.3.3 :
- black v3 sintech with adata KC7000 : reboot test succes huge i/o transfers success
- green large v2 sintech with adata KC7000 : reboot test succes huge i/o transfers not done, need to confirm.
- black v3 sintech with 960 Evo : reboot test fails, huge i/o transfers fails
- green v2 sintech with 960 Evo : reboot test succes, huge i/o transfers fails

All test done with proper kapton tape insulation at the back of the adapter (so that we got stable connexion with 4 lanes).
standby mode 0, so no problem on sleep.

So there is definitely a problem with the new black adapter and Samsung drives...

I did check electrical differences between the two adapters, with a multimeter.
This is a huge work, not yet finished, I have still to verify the full connexions table of the black adapter.

But, so far, here are my observations on the green large v.2 Sintech adapter :
- pin 49 (SSD_DEVSLP) on the Apple 12+16 connector is not connected
- pin 47 (SSD_PWR_FET_EN) on the Apple 12+16 connector is connected to M.2 pin 38 (DEVSLP)
- pin 24 (SSD_CLKREQ) on the Apple 12+16 connector is connected to M.2 pin 52 (CLRREQ)
- pin 8 (SSD_RESET) on the Apple 12+16 connector is connected to M.2 pin 50 (PERST)
The two last lines seem logical, but I don't understand why pin 49 of the Apple 12+16 connector is not connected to M.2 pin 38 (DEVSLP both !)

Here are my observations on the black v.3 Sintech adapter :
- pin 49 (SSD_DEVSLP) on the Apple 12+16 connector is left unconnected with an empty solder pad for connecting it via a cms resistor (not present) to +3,3V
- pin 52 (CLRREQ) of the M.2 SSD is left unconnected with 2 empty solder pads : one to connect it to 3,3V and another one to connect it to GND
- pin 50 (PERST) of the M.2 SSD is connected to level high (+3,3V)

Obviously those differences may explain the differences between the green and black adapters regarding reboots with Samsung drives...

The green V.2 adapter seems to have the most logical interconnexions. At least this green adapter works with every other SSDs than Samsungs and I use it for 6 months now in 3 rMBP (and kingston and thosiba drives) without any issues...


I wonder if I couldn't try to modify a green adapter with connecting both pins DEVSLP between Apple 12+16 and M.2 connectors ? I may give a try next saturday...

And I don't understand why on earth does Sintech made so many modifications on its v.3 adapter, especially modifications that seem illogical...

Here are the pinouts collected so far :

View attachment 748338

View attachment 748339

View attachment 748340

View attachment 748341

[doublepost=1516833002][/doublepost]
Hi wawon,
thanks for your update ! I checked and it seems that circuit is a lot different...
At least sintech has made an effort with the kapton tape, it's fun to see it !

gilles, thanks for the really helpful post. I am assuming that I am going to get this newest v.3 adapter. So I have to see how to deal with that.
 
  • Like
Reactions: flemmingdjensen

ravic

macrumors member
Jul 2, 2007
84
10
Here is an observation. Sleep works really well in bootcamp under windows. After a full 24hrs of just closing my laptop screen and putting it away, I have 95% of my batter left the next day.

So it certainly looks like macOS driver is unable to handle it. I am going to attempt the nvme patch to see if it helps.
 

monofase

macrumors member
Sep 26, 2017
72
22
Italy
Some 960's shipping with newer firmware may be the cause of some of the issues; if your firmware is a certain older level it should be fine, as I have had no issues with the revision I have.

If your 960 EVO has a firmware revision of 3B6QCXP7, you might run into problems. Newer stock may be shipping with this version.

My 500 GB 960 EVO has the previous version, 2B7QCXE7 and I haven't encountered any problems.

Windows users report a lot of problems with 3B6QCXP7 here and here, among other places.

DriveDx or smartctl from Homebrew can tell you what firmware is on your 960 EVO.

BTW, 10.13.3 seems to be working okay with my 960 EVO, don't think there were any changes to the BootROM or the NVME plugin though.

I have 2B7QCXE7 version and no problems. I was wondering if it is possible to downgrade the SSDs to older version...
 

Attachments

  • Schermata 2018-01-26 alle 00.04.10.png
    Schermata 2018-01-26 alle 00.04.10.png
    1.2 MB · Views: 404

flemmingdjensen

macrumors member
Nov 30, 2017
37
16
Denmark
I have 2B7QCXE7 version and no problems. I was wondering if it is possible to downgrade the SSDs to older version...

I just gave my EVO 960 1TB a chance yesterday. Restored MacOs 10.13.3 from Time Machine backup and Restored Winclone Windows 10 backup. (750G / 250G)

Did the proper kaptan taping as gilles suggests (the part where the adapter mates the MBP connector)

So far only seen a KP during boot of MacOs.

I checked the firmware rev and it is : 3B7QCXE7

So it seems to be one of the "faulty" firmwares. Is the second last character the E for EVO and P for PRO?

Compared to the Kingston KC1000 I notice a slight quicker/better overall performance in my Mid 2014 MBP 15"

KC1000 has R: 1350 / W: 1100
EVO960 has R: 1500 / W: 1350

BTW: The suggestions about patching the NVMeDriver seems not possible currently with 10.13.3 since Rehabman has not patched the newest driver yet.

// Flemming
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.