Not sure, I didn't check but installed latest firmware from https://ssd.skhynix.com/download/what is the P31 firmware version?
Not sure, I didn't check but installed latest firmware from https://ssd.skhynix.com/download/what is the P31 firmware version?
Sintech adapter won't help to stop the crash in a case where the ssd itself is problematic.Just picked up a 2015 Early MacBook Pro 13", it's a really nice machine! Turns out it has a NFHK N-941A SSD adapter and a WD PC SN720 NVME M.2 SSD. Runs great till machine goes to sleep then it crashes and reboots with error, invalid third party NVME Adapter.
I just ordered on Amazon a Sintech NGFF M.2 SSD Adapter as recommended on this thread. Will this fix my issue? Or is this just the WRONG SSD drive? Am I better selling and sourcing an Apple branded SSD on e-bay or anyone have a different recommendation? I can't ready through 431 Pages to know if this SSD will work with the Sintech!
This is the error I get:
panic(cpu 3 caller 0xffffff80087856a2): nvme: "3rd party NVMe controller. Fatal error. Delete IO submission queue. fBuiltIn=1 MODEL=WDC PC SN720 SDAQNTW-512G-1001 FW=10190101 CSTS=0x0 US[1]=0x0 US[0]=0x6c VID=0x15b7 DID=0x5002 CRITICAL_WARNING=0x0.\n" @IONVMeController.cpp:6090
Panicked task 0xffffffa57408f670: 177 threads: pid 0: kernel_task
Backtrace (CPU 3), panicked thread: 0xffffffa0a6f62000, Frame : Return Address
0xffffffffddb03a80 : 0xffffff8005e7fd6d
0xffffffffddb03ad0 : 0xffffff8005fe1086
0xffffffffddb03b10 : 0xffffff8005fd03f3
0xffffffffddb03b60 : 0xffffff8005e1fa70
0xffffffffddb03b80 : 0xffffff8005e8013d
0xffffffffddb03ca0 : 0xffffff8005e7f8f6
0xffffffffddb03d00 : 0xffffff8006714e03
0xffffffffddb03df0 : 0xffffff80087856a2
0xffffffffddb03e00 : 0xffffff80087687cb
0xffffffffddb03e30 : 0xffffff8008768661
0xffffffffddb03e70 : 0xffffff8005ed2655
0xffffffffddb03ee0 : 0xffffff8005ed3722
0xffffffffddb03fa0 : 0xffffff8005e1f19e
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[5001E486-38BD-3F9B-978E-A380678E3A90]@0xffffff8008760000->0xffffff800878cfff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[2E89B457-9830-3554-A342-E5A4659F9D28]@0xffffff80075b1000->0xffffff80075d2fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[22B97C0A-53BF-3843-B4B5-4DE866C375B0]@0xffffff8008a35000->0xffffff8008a61fff
dependency: com.apple.iokit.IOReportFamily(47)[66824C9A-7BC1-3F5D-A056-D789C8A86B8C]@0xffffff8008a73000->0xffffff8008a75fff
dependency: com.apple.iokit.IOStorageFamily(2.1)[24743B95-072D-31C4-A59D-7FF38502C0C4]@0xffffff8008b78000->0xffffff8008b8efff
Process name corresponding to current thread (0xffffffa0a6f62000): kernel_task
Mac OS version:
21G83
Kernel version:
Darwin Kernel Version 21.6.0: Wed Aug 10 14:25:27 PDT 2022; root:xnu-8020.141.5~2/RELEASE_X86_64
Kernel UUID: D0DC2052-71F4-3DCB-B189-BEE5A59B3B42
KernelCache slide: 0x0000000005c00000
KernelCache base: 0xffffff8005e00000
Kernel slide: 0x0000000005c10000
Kernel text base: 0xffffff8005e10000
__HIB text base: 0xffffff8005d00000
System model name: MacBookPro12,1 (Mac-E43C1C25D4880AD6)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0
System uptime in nanoseconds: 2394935784948
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000022d9d4bfa38
Sleep : 0x0000022d8833f7b6 0x00000002085589fb 0x0000000000000000
Wake : 0x0000022d9709c5b6 0x000007a3a1aaa44c 0x0000022d9571302b
Compressor Info: 2% of compressed pages limit (OK) and 1% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff90a6d95000 - 0xffffffb0a6d95000
. PGZ : 0xffffff90a6d95000 - 0xffffff90a7d96000
. VM : 0xffffff90a7d96000 - 0xffffff95747fc000
. RO : 0xffffff95747fc000 - 0xffffff970e0c8000
. GEN0 : 0xffffff970e0c8000 - 0xffffff9bdab2e000
. GEN1 : 0xffffff9bdab2e000 - 0xffffffa0a7594000
. GEN2 : 0xffffffa0a7594000 - 0xffffffa573ffa000
. GEN3 : 0xffffffa573ffa000 - 0xffffffaa40a61000
. DATA : 0xffffffaa40a61000 - 0xffffffb0a6d95000
Metadata: 0xffffff9053c03000 - 0xffffff9073c03000
Bitmaps : 0xffffff9073c03000 - 0xffffff9076c03000
last started kext at 32571348241: >driverkit.serial 6.0.0 (addr 0xffffff7f9f0b5000, size 28672)
last stopped kext at 712431298403: >IOPlatformPluginLegacy 1.0.0 (addr 0xffffff7f9efb1000, size 36864)
loaded kexts:
>!AUpstreamUserClient 3.6.9
>AudioAUUC 1.70
>X86PlatformShim 1.0.0
>AGPM 129
>!APlatformEnabler 2.7.0d0
@filesystems.autofs 3.0
>!AHDA 340.2
>!AGraphicsDevicePolicy 6.5.7
>!A!IBDWGraphics 18.0.8
>!ASMCLMU 212
>eficheck 1
>!ALPC 3.1
>!ACameraInterface 7.9.1
@AGDCPluginDisplayMetrics 6.5.7
>pmtelemetry 1
|IOUserEthernet 1.0.1
>usb.!UUserHCI 1
>!AHV 1
>!ADiskImages2 126.141.2
>!ABacklight 180.8
>!AMCCSControl 1.16
>!A!ISlowAdaptiveClocking 4.0.0
>!A!IBDWGraphicsFramebuffer 18.0.8
>!AThunderboltIP 4.0.3
|SCSITaskUserClient 456.140.3
>!UCardReader 533.120.2
>!AFileSystemDriver 3.0.1
@filesystems.tmpfs 1
@filesystems.lifs 1
@filesystems.hfs.kext 583.100.10
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@filesystems.apfs 1934.141.2
>!ATopCaseHIDEventDriver 5450.8
>AirPort.BrcmNIC 1400.1.1
@private.KextAudit 1.0
>!ARTC 2.0.1
>!ASmartBatteryManager 161.0.0
>!AACPIButtons 6.1
>!AHPET 1.8
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 402
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
@Dont_Steal_Mac_OS_X 7.0.0
@kec.!AEncryptedArchive 1
>driverkit.serial 6.0.0
|IOSerial!F 11
@kext.triggers 1.0
>DspFuncLib 340.2
@kext.OSvKernDSPLib 529
>!AAudioClockLibs 140.1
>!AHDA!C 340.2
|IOHDA!F 340.2
|IOAudio!F 340.2
@vecLib.kext 1.2.0
>!AGraphicsControl 6.5.7
|IO!BSerialManager 9.0.0
|IO!BPacketLogger 9.0.0
|IO!BHost!CUSBTransport 9.0.0
|IO!BHost!CUARTTransport 9.0.0
|IO!BHost!CTransport 9.0.0
>IO!BHost!CPCIeTransport 9.0.0
|IOAVB!F 1040.6
@plugin.IOgPTPPlugin 1040.3
|IOEthernetAVB!C 1.1.0
|CSR!BHost!CUSBTransport 9.0.0
|Broadcom!BHost!CUSBTransport 9.0.0
|Broadcom!B20703USBTransport 9.0.0
>!AIPAppender 1.0
>!ABacklightExpert 1.1.0
|IONDRVSupport 597
>!ASMBus!C 1.0.18d1
@!AGPUWrangler 6.5.7
|IOSlowAdaptiveClocking!F 1.0.0
|IOAccelerator!F2 462.8
@!AGraphicsDeviceControl 6.5.7
|IOGraphics!F 597
>!AThunderboltDPOutAdapter 8.5.1
>X86PlatformPlugin 1.0.0
>IOPlatformPlugin!F 6.0.0d8
>usb.IOUSBHostHIDDevice 1.2
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>!AThunderboltDPInAdapter 8.5.1
>!AThunderboltDPAdapter!F 8.5.1
>!AThunderboltPCIDownAdapter 4.1.1
>!ABSDKextStarter 3
|IOSurface 302.14
@filesystems.hfs.encodings.kext 1
>!AActuatorDriver 5460.1
>!AHIDKeyboard 228.2
>!AXsanScheme 3
>!AMultitouchDriver 5460.1
>!AInputDeviceSupport 5460.1
>!AHS!BDriver 5450.8
>IO!BHIDDriver 9.0.0
>!AThunderboltNHI 7.2.81
|IOThunderbolt!F 9.3.3
>!AHSSPIHIDDriver 63
|IO80211!FLegacy 1200.12.2b1
|IOSkywalk!F 1.0
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
|IONVMe!F 2.1.0
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
>!AHSSPISupport 63
>!A!ILpssSpi!C 3.0.60
>!A!ILpssI2C 3.0.60
>!A!ILpssGspi 3.0.60
>!A!ILpssDmac 3.0.60
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
|IOTimeSync!F 1040.3
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 9.0.0
|IOReport!F 47
$quarantine 4
$sandbox 300.0
@Kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 533.120.2
|IOUSBMass!SDriver 210.120.3
|IOSCSIBlockCommandsDevice 456.140.3
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 456.140.3
>!AMobileFileIntegrity 1.0.5
$!AImage4 4.2.0
@kext.CoreTrust 1
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!ACredentialManager 1.0
>KernelRelayHost 1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
>!AACPIPlatform 6.1
>!ASMC 3.1.9
|IOPCI!F 2.9
|IOACPI!F 1.4
>watchdog 1
@kec.pthread 1
@kec.Libm 1
@kec.corecrypto 12.0
That's what I was trying to find out. What tells you the SSD is the problem vs. the Adapter?Sintech adapter won't help to stop the crash in a case where the ssd itself is problematic.
Either pick another NVME SSD. or do this from terminal :
sudo pmset -a standby 0 hibernatemode 0
you will lost more battery during sleep, but it won't crash (as often - in most cases, it wont crash at all)
The lower power consumption was probably measured while using the SSD in a Windows environment where the OS, logic board bios, and driver work together to minimize power consumption. More than likely, macOS and the MBP firmware are not using optimized power settings because the SSD is not fully supported.I've got Corsair MP510 1TB for my MBP 2015 but even that it's listed at lower power consumption than the original Apple drive my NVMe temperatures are higher by at least 10 degrees and I assumed that if power consumption is similar the temps would be similar. The original NVMe idles at around 35 degrees while the Corsair idles at around 45 degrees making the whole system a lot hotter as a result. Is this normal? I've tested both on vanilla BigSur and on one with ssdpmenabler + lilu + nvmefix. Is there a NVMe that would get me lower temps close to the original NVMe - speed is not that important as long as performance is similar to the original NVMe?
Maybe but I think that they've measured using macOS because otherwise the data is not useful. I'm talking about the data in the first post of the thread.The lower power consumption was probably measured while using the SSD in a Windows environment where the OS, logic board bios, and driver work together to minimize power consumption. More than likely, macOS and the MBP firmware are not using optimized power settings because the SSD is not fully supported.
Sorry, my apologies. I incorrectly assumed you were referring to the manufacturer's listed power specifications.Maybe but I think that they've measured using macOS because otherwise the data is not useful. I'm talking about the data in the first post of the thread.
Even if power consumption is similar, the performance is different. The nvme is faster than factory ssd.I've got Corsair MP510 1TB for my MBP 2015 but even that it's listed at lower power consumption than the original Apple drive my NVMe temperatures are higher by at least 10 degrees and I assumed that if power consumption is similar the temps would be similar. The original NVMe idles at around 35 degrees while the Corsair idles at around 45 degrees making the whole system a lot hotter as a result. Is this normal? I've tested both on vanilla BigSur and on one with ssdpmenabler + lilu + nvmefix. Is there a NVMe that would get me lower temps close to the original NVMe - speed is not that important as long as performance is similar to the original NVMe?
Sintech adapter won't help to stop the crash in a case where the ssd itself is problematic.
Either pick another NVME SSD. or do this from terminal :
sudo pmset -a standby 0 hibernatemode 0
you will lost more battery during sleep, but it won't crash (as often - in most cases, it wont crash at all)
You can trySo, I'm still waiting on my new SSD to be delivered, I set the hibernate mode to 0 and standby to 0, but it still seems to have gone to sleep and crashed. Should I just set the Display to never got to sleep, and then turn it off when I"m not using it? I really just need to have it work well until Monday when I get my new SSD. I'm selling my other 2 laptops tomorrow, someone really wants them and I could use the cash! A 2017 pro and a 2014 air.
What OS version do you use ? BigSur and Monterey is tend to be slower, especially if it's not a clean installation (updated from previous versions). Did you install it clean ?Howdy Folks,
So I upgraded my early 2015 13" MBP with a 500gb Crucial P2 and the long Sintech Adaptor. I find its very slow booting up and not as speedy as I had expected. In particular the boot up time... is there anything that can be done to increase this or do I just live with it as the machine is 7 years old and tailor my expectations...
Thanks
Howdy,What OS version do you use ? BigSur and Monterey is tend to be slower, especially if it's not a clean installation (updated from previous versions). Did you install it clean ?
Normally Monterey will boot within 5-7 seconds after the loading bar appear.
try to rebuild your kext cache first.
Open terminal and run : sudo kextcache -i /
did you use FileVault ? If yes, then probably just turn it off. Personally never fan of FileVault. Cause more headache shall you need to do any troubleshoot.
Done, let's see what happens! Not sure the excitement for the NVME SSD if it causes all these problems and 431 pages of MacRumor discussion, but I did order an enclosure for it, so I'll have a really nice USB flash drive to use once I get my Apple Branded Drive in and this one out!You can try
sudo pmset -a hibernatemode 0 standby 0 sleep 0 autopoweroff 0 powernap 0
and, yes, turning off the macbook completely is recommended for troublesome SSD.
The excitement is because apple would charge you $400-500 bucks during that time to get 1TB of drive. While you can get it less than 100 by using NVME.Done, let's see what happens! Not sure the excitement for the NVME SSD if it causes all these problems and 431 pages of MacRumor discussion, but I did order an enclosure for it, so I'll have a really nice USB flash drive to use once I get my Apple Branded Drive in and this one out!
The speed is about right for P2 on 13" 2015 machine. Nothing to worry aboutGave that a whirl. It took 36 seconds to boot into login credentials. So maybe that's normal?
I took a speed test with the Blackmagic app. See below. I don't know if the below is good or ok. Again I know I have a 7 year old machine and need to manage my expectations...
Zero in my experience, done in two macbooks pro and one macbook air.The excitement is because apple would charge you $400-500 bucks during that time to get 1TB of drive. While you can get it less than 100 by using NVME.
The key is only choosing the right SSD, and it will give you near 0 problem
but even with the caveat from wrong ssd, it still worth the 200-300 bucks saving for most of users, lol
I can vouch for 0 problem as well. After all, i won't dare to install it to hundred of my customers mac if it will give them problem, which will turn into my problem (cust complaint) later on. LolZero in my experience, done in two macbooks pro and one macbook air.
1200 Mb/s it´s an excellent speed for that model. About x2 in writing than the original Apple drive.Hello guys, just want to chime in and say thank you for everyone’s in this thread! And to post my experience:
I bought a last in stock Kingston A2000 1TB at a local store a week ago, for around USD 90.
Installed it on a used MBA early 2015 8gb with an unknown brand short adapter. And did a clean Monterey install with the SD card slot that I downloaded before the upgrade.
I have not update the ssd beforehand, just plug and install like real simple, and it’s all working!
There’s no obvious battery drain while closing the lid with no kext installed. After idling for a day and I reopened it, it only losses around 3% of battery.
R/W speed is around 1200 only, and atm it’s still indexing. But it’s alright to me anyway.
I will post again if there’s any problem.
Thank you all, goodluck!
If it's 2014Hello guys!
I have a Crucial P2 1to with Mojave for 1 year, on a Macbook 15" 2014.
It works fine, but I experienced severe temperature rises and my CPU is 10° hotter than the Apple SSD. Sometimes I have big scares, I have errors when starting the mac. But it is okay for now.
I would like to upgrade to Big Sur, I'm thinking of changing SSD.
What are the best SSDs of the moment for a macbook pro 2014?
There are so many, it's hard to choose. ! I saw that the SK hynix Gold P31 is one of the best,
it's still true ?
Thanks !