MacBook keeps crashing when moving big files (Panic Report)

[Siggisiggi]

Hello everybody

This is my first post, and I could really use some help. I've been looking all over the forum, and found people with similar problems, but not exactly like my problem.

My Macbook Pro (13-inch, Mid 2012, 2,9 GHz Intel Core i7, 8 GB 1600 MHz DDR3, Intel HD Graphics 4000 1536 MB, and in spring I installed a Samsung EVO 850 500 GB SSD) is suffering from crashes, when I'm moving big files. It can easily transfer files for a couple of minutes, but it crashes after maybe 10 minutes of transferring.

I have a backup. I've opened up my MacBook and transferred all my files to an external harddrive with another Mac.
And I also tried installing the OS all over, wiping the SSD and repairing the disk.

Before the reinstallation my MacBook was SOOO slow, and it was really hard for me to use it.
Now I can use it for browsing and typing, but moving files are hard. And I'm afraid, that the MacBook will crash during some important work.

I hope that some of you can help


Here is the latest report:


Tue Sep 5 21:08:27 2017

*** Panic Report ***
panic(cpu 2 caller 0xffffff802f76ad26): "Process 1 exec of /sbin/launchd failed, errno 2"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3789.60.24/bsd/kern/kern_exec.c:5031
Backtrace (CPU 2), Frame : Return Address
0xffffff8138aebde0 : 0xffffff802f2ea53c
0xffffff8138aebe60 : 0xffffff802f76ad26
0xffffff8138aebee0 : 0xffffff802f738304
0xffffff8138aebf00 : 0xffffff802f786771
0xffffff8138aebf50 : 0xffffff802f2e3e29
0xffffff8138aebf80 : 0xffffff802f3ffbbe
0xffffff8138aebfa0 : 0xffffff802f29b55f

BSD process name corresponding to current thread: init

Mac OS version:
Not yet set

Kernel version:
Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64
Kernel UUID: FB2170A8-257D-3C64-B14D-BC06CC94E34C
Kernel slide: 0x000000002f000000
Kernel text base: 0xffffff802f200000
__HIB text base: 0xffffff802f100000
System model name: MacBookPro9,2 (Mac-6F01561E16C75D06)

System uptime in nanoseconds: 7193567333
last loaded kext at 3089530007: com.apple.driver.AppleXsanScheme 3 (addr 0xffffff7fb1972000, size 40960)
loaded kexts:
jp.plentycom.driver.SteerMouse 4.1.3
com.logitech.manager.kernel.driver 6.62.1
com.apple.iokit.IOBluetoothUSBDFU 5.0.4f18
com.apple.driver.AppleUSBTCKeyEventDriver 252
com.apple.driver.AppleUSBTCKeyboard 252
com.apple.driver.AppleIRController 341.2
com.apple.iokit.SCSITaskUserClient 394.50.1
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.BootCache 40
com.apple.filesystems.hfs.kext 366.50.19
com.apple.iokit.AppleBCM5701Ethernet 10.2.10
com.apple.driver.AirPort.Brcm4331 800.20.24
com.apple.driver.AppleSDXC 1.7.6
com.apple.driver.AppleAHCIPort 326.60.1
com.apple.driver.AirPort.Brcm4360 1150.10.1a2
com.apple.driver.AppleFWOHCI 5.5.5
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 5.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 5.0
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 219.0.0
com.apple.nke.applicationfirewall 172
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 219.0.0
com.apple.driver.AppleXsanScheme 3
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 5.0.4f18
com.apple.iokit.IOBluetoothHostControllerUSBTransport 5.0.4f18
com.apple.iokit.IOBluetoothHostControllerTransport 5.0.4f18
com.apple.driver.AppleUSBMultitouch 258
com.apple.driver.usb.IOUSBHostHIDDevice 1.1
com.apple.iokit.IOSCSIBlockCommandsDevice 394.50.1
com.apple.iokit.IOUSBMassStorageDriver 131.60.1
com.apple.iokit.IOSCSIArchitectureModelFamily 394.50.1
com.apple.driver.usb.cdc 5.0.0
com.apple.driver.usb.networking 5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice 1.1
com.apple.driver.usb.AppleUSBHub 1.1
com.apple.filesystems.hfs.encodings.kext 1
com.apple.driver.AppleThunderboltDPInAdapter 5.0.2
com.apple.driver.AppleThunderboltDPAdapterFamily 5.0.2
com.apple.driver.AppleThunderboltPCIDownAdapter 2.1.3
com.apple.driver.AppleThunderboltNHI 4.5.4
com.apple.iokit.IOThunderboltFamily 6.5.7
com.apple.iokit.IOEthernetAVBController 1.0.3b4
com.apple.iokit.IOAHCIFamily 288
com.apple.driver.AppleUSBMergeNub 900.4.1
com.apple.iokit.IO80211Family 1200.12.2
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.iokit.IONetworkingFamily 3.2
com.apple.driver.corecapture 1.0.4
com.apple.iokit.IOFireWireFamily 4.6.6
com.apple.driver.usb.AppleUSBEHCIPCI 1.1
com.apple.driver.usb.AppleUSBEHCI 1.1
com.apple.driver.usb.AppleUSBXHCIPCI 1.1
com.apple.driver.usb.AppleUSBXHCI 1.1
com.apple.driver.usb.AppleUSBHostPacketFilter 1.0
com.apple.driver.AppleUSBHostMergeProperties 1.1
com.apple.driver.AppleEFINVRAM 2.1
com.apple.driver.AppleEFIRuntime 2.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.KernelRelayHost 1
com.apple.driver.DiskImages 444.50.16
com.apple.iokit.IOStorageFamily 2.1
com.apple.driver.IOBluetoothHIDDriver 5.0.4f18
com.apple.iokit.IOBluetoothFamily 5.0.4f18
com.apple.iokit.IOReportFamily 31
com.apple.iokit.IOUSBHIDDriver 900.4.1
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.iokit.IOUSBFamily 900.4.1
com.apple.iokit.IOUSBHostFamily 1.1
com.apple.driver.AppleBusPowerController 1.0
com.apple.driver.AppleACPIPlatform 5.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.Libm 1
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0

Similar Panic Reports:

Sun Aug 27 17:06:08 2017

*** Panic Report ***
panic(cpu 2 caller 0xffffff800ad9bafc): "wire_count == 0, m = 0xffffff8013f0bc20, obj = 0xffffff802d9b5200\n"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3789.70.16/osfmk/vm/vm_pageout.c:7516
Backtrace (CPU 2), Frame : Return Address
0xffffff8113c939c0 : 0xffffff800ace953c
0xffffff8113c93a40 : 0xffffff800ad9bafc
0xffffff8113c93d80 : 0xffffff800b2cc8c9
0xffffff8113c93de0 : 0xffffff7f8c29b291
0xffffff8113c93e00 : 0xffffff7f8c29b306
0xffffff8113c93e20 : 0xffffff800b2bd76a
0xffffff8113c93e90 : 0xffffff800b2c13d0
0xffffff8113c93f00 : 0xffffff800ad2219a
0xffffff8113c93fb0 : 0xffffff800ac978f7
Kernel Extensions in backtrace:
com.apple.driver.DiskImages(444.50.16)[7A04C2E6-40FF-36A9-84D4-FDF685F3B0A9]@0xffffff7f8c299000->0xffffff7f8c2b1fff
dependency: com.apple.iokit.IOStorageFamily(2.1)[F908D7F5-4F54-3B89-8657-57F06350F4DB]@0xffffff7f8b450000

BSD process name corresponding to current thread: kernel_task


AND

Thu Aug 24 22:11:19 2017

*** Panic Report ***
panic(cpu 2 caller 0xffffff800b36ad26): "Process 1 exec of /sbin/launchd failed, errno 2"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3789.60.24/bsd/kern/kern_exec.c:5031
Backtrace (CPU 2), Frame : Return Address
0xffffff80ebff3de0 : 0xffffff800aeea53c
0xffffff80ebff3e60 : 0xffffff800b36ad26
0xffffff80ebff3ee0 : 0xffffff800b338304
0xffffff80ebff3f00 : 0xffffff800b386771
0xffffff80ebff3f50 : 0xffffff800aee3e29
0xffffff80ebff3f80 : 0xffffff800afffbbe
0xffffff80ebff3fa0 : 0xffffff800ae9b55f

BSD process name corresponding to current thread: init

Mac OS version:
Not yet set

 

[Raz0rEdge]

Looks like your SSD is failing. Grab a copy of Blackmagic Disk Speed Test and run it, it might end up crashing on that as well since it will try testing various sized reads/writes and tries to benchmark the SSD. Not sure where you got the SSD from and the warranty of Samsung, but I remember reading some issues with the EVO drives, so you might want to get it replaced on RMA or something..

When I did the HDD -> SSD upgrade on my iMac, I did a lot of research and while the Samsungs were all over the place, a lot of people were complaining about reliability and thus I ended up with a Sandisk drive which has been working great for the past couple of years..

 

[chscag]

Welcome to our forums.

The panic reports are not conclusive in that they really do not point to anything in particular. It could be a problem with the SSD and corruption as you're trying to move large files. What you can try is boot to safe mode (hold down shift key as soon as you hear the Bong!). See if you can transfer large files while in safe mode. Let us know.

 

[pm-r]

Here is the latest report:

I was going to ask as for some odd reason that report says:
Mac OS version:
Not yet set

So what OS X version is that Mac running??

Also, what partition/format is the SSD using??





- Patrick
======

 

[harryb2448]

The first two kexts listed (Kernel extensions) are steermouse and logitech, so perhaps try it without using an external keyboard and mouse, or perhaps this is an overhang from previous software installed?

 

[pm-r]

Or how about booting up using Safe Boot Mode as chscag has already suggested, which should/will disable all the third party stuff from running, and see if things work better???




- Patrick
======

 

[Audit13]

Failed sata hard drive cables in the MBPs from 2009 to 2012 are not uncommon and could be causing this problem.

I had erasing/reading/partitioning/copying errors on a 2009 15", 2010 13", and 2011 13". In all three cases, many hardware checks of the RAM and boot drives indicated no problem. Replaced the existing hard drive cable with third-party cables from Amazon and all problems went away.

 

[pm-r]

Failed sata hard drive cables in the MBPs from 2009 to 2012 are not uncommon and could be causing this problem.

One has to admit that this bit of advice is pretty accurate for such Macs according to this and other hits:

The 13-inch MacBook Pro notebook from mid-2011 is an outstanding computer, but some of these laptops apparently were made with a bad batch of hard drive cables that failed after about a year. Although something of a pain to diagnose (this one threw us for a few weeks until we saw a pattern forming), this proved to be an easy and fun fix.

If a known-good hard drive was swapped in and the MacBook Pro exhibited the same issues, then the hard drive cable became a definite suspect and an order was placed for a replacement cable (available on eBay for about $25 or from iFixit, which has an online installation guide, for $50).

https://www.macworld.com/article/2030013/advice-from-an-apple-tech-three-common-mac-fixes.html

and more:
https://www.google.ca/search?client...F-8&gfe_rd=cr&dcr=0&ei=PSGwWYGuF9DM8gfau5yAAw




- Patrick
======

 

[pm-r]

Failed sata hard drive cables in the MBPs from 2009 to 2012 are not uncommon

Here's another supporting article regarding the failed/failing sata hard drive cables in some MBPros I came across that's quite interesting:
Diagnosing MacBook Pro Hard Drive Cable Failure

... because, there's no way to directly confirm the cable is the problem.

So I got to thinking. Computers with bad cables don't crash, or freeze. They just hang for a while randomly, then come back. JUST like a hard drive with lots of bad blocks

…

ANOTHER 2012 13" macbook pro, with a [bad] hard drive cable. The computer powered on just fine but wouldn't boot.

https://discussions.apple.com/thread/7794520?start=0&tstart=0

Interesting thoughts and experiences…

I don't know if the OP's problems are related to the cable problem or not however…





- Patrick
======

 

[Siggisiggi]

Thanks

Looks like your SSD is failing. Grab a copy of Blackmagic Disk Speed Test and run it, it might end up crashing on that as well since it will try testing various sized reads/writes and tries to benchmark the SSD. Not sure where you got the SSD from and the warranty of Samsung, but I remember reading some issues with the EVO drives, so you might want to get it replaced on RMA or something..

When I did the HDD -> SSD upgrade on my iMac, I did a lot of research and while the Samsungs were all over the place, a lot of people were complaining about reliability and thus I ended up with a Sandisk drive which has been working great for the past couple of years..

I'm sorry I haven't replied before now. My Macbook crashed, and I couldn't log in with my phone, before now.

Thanks for your reply! ?

I'm afraid you could be right. I will try out what the other guys mentions and get back.

 

[Siggisiggi]

Sorry for the late answer.

I find it strange that it doesn't state which OS. But it runs Sierra.
Mac OS Extended Journaled I think.

 

[Audit13]

My money is still on the hard drive cable being there source of the problem.

 

[Siggisiggi]

The first two kexts listed (Kernel extensions) are steermouse and logitech, so perhaps try it without using an external keyboard and mouse, or perhaps this is an overhang from previous software installed?

I've had a Logitech mouse installed before the reinstallation. But now I just use the equipped trackpad.
Could the software have an influence even though I deleted everything? And what do I do?

 

[Siggisiggi]

My money is still on the hard drive cable being there source of the problem.

Sorry I didn't reply you. How sure are you? Because the problems described in the last link doesn't sound like me problem.

My Mac can boot. But will freezes a lot.

 

[Siggisiggi]

Here's another supporting article regarding the failed/failing sata hard drive cables in some MBPros I came across that's quite interesting:
Diagnosing MacBook Pro Hard Drive Cable Failure


…

https://discussions.apple.com/thread/7794520?start=0&tstart=0

Interesting thoughts and experiences…

I don't know if the OP's problems are related to the cable problem or not however…





- Patrick
======

One of your links is not working. But the one that says "Computers with bad cables don't crash, or freeze. They just hang for a while randomly, then come back. JUST like a hard drive with lots of bad blocks" - doesn't sound like my problem. My Mac can boot up. But will freeze a lot and crash.

 

[chscag]

Go back and re-read post #2 and #3. Your SSD is the problem. If you do decide to swap it out, it would be a good idea to also change out the SATA cable at the same time.

 

[pm-r]

One of your links is not working.

I just tried all three that I posted in this thread and all three work just fine for me. It's seems you may have multiple problems.

I'd tend to agree with some of the other's and that your SSD and/or cable are goofy.

I'd take their advice and just replace them both. At worst, you'll end up with maybe a spare drive you could use for a backup.





- Patrick
======