Mac pro keeps crashing, please help with analysing crash report

Hello, my mac keeps crashing. It was just serviced by Apple.


This is the crash report:

Anonymous UUID: EA861633-6B74-539D-5EE5-4F87D1B47BBE


Wed Jun 19 20:37:36 2019


*** Panic Report ***

panic(cpu 10 caller 0xffffff800b58780f): Kernel trap at 0xffffff800b56d87d, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x0000000020445000, CR4: 0x00000000001626e0

RAX: 0x0000000000000001, RBX: 0x0000000000000000, RCX: 0x0000000000000060, RDX: 0x0000001f90b19000

RSP: 0xffffffce35d53840, RBP: 0xffffffce35d538d0, RSI: 0xffffff80d72c24a0, RDI: 0x0000000001f7fda5

R8: 0x0000000000000001, R9: 0x0000000000000040, R10: 0x0000000001f7fda5, R11: 0x0000000000000001

R12: 0xffffff80d72c24a0, R13: 0xffffff810e2d4530, R14: 0xffffffffffffffbf, R15: 0x0000000000000000

RFL: 0x0000000000010206, RIP: 0xffffff800b56d87d, CS: 0x0000000000000008, SS: 0x0000000000000000

Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0xa, PL: 1, VF: 5


Backtrace (CPU 10), Frame : Return Address

0xffffffce35d53310 : 0xffffff800b46bf96

0xffffffce35d53360 : 0xffffff800b595354

0xffffffce35d533a0 : 0xffffff800b5875e4

0xffffffce35d53410 : 0xffffff800b41dfb0

0xffffffce35d53430 : 0xffffff800b46ba0c

0xffffffce35d53560 : 0xffffff800b46b7cc

0xffffffce35d535c0 : 0xffffff800b58780f

0xffffffce35d53730 : 0xffffff800b41dfb0

0xffffffce35d53750 : 0xffffff800b56d87d

0xffffffce35d538d0 : 0xffffff800b51f2cc

0xffffffce35d53bf0 : 0xffffff800b959ca3

0xffffffce35d53c30 : 0xffffff800b68a3a6

0xffffffce35d53cc0 : 0xffffff800b681685

0xffffffce35d53d30 : 0xffffff7f8c57c0c4

0xffffffce35d53d90 : 0xffffff7f8df3faee

0xffffffce35d53de0 : 0xffffff7f8df48960

0xffffffce35d53e20 : 0xffffff7f8df16c20

0xffffffce35d53e50 : 0xffffff7f8f12cecc

0xffffffce35d53e80 : 0xffffff7f8f12c58b

0xffffffce35d53ec0 : 0xffffff7f8f12c159

0xffffffce35d53f10 : 0xffffff7f8f12db2b

0xffffffce35d53f30 : 0xffffff800ba97ed2

0xffffffce35d53f70 : 0xffffff800ba974fc

0xffffffce35d53fa0 : 0xffffff800b41d557






Mac Pro

Posted on Jun 19, 2019 8:48 PM

Reply
Question marked as Top-ranking reply

Posted on Jun 20, 2019 7:38 AM

Your panic-reason is page fault, a reference to an Address that does not belong to the task trying to reference it.


The extensions at the 'scene of the crime' are AHCI SSD disk I/O drivers and related software.


You are running a third-party disk extension, a LaCie driver of some sort. That is a really bad idea.


Some of these vendor-specific drivers "do you a favor" by leaving your drive as a Windows New Technology File System (NTFS) drive, and simulating a Mac file structure on top of that. An immediate problem with that is the drive is unreadable without full blown MacOS AND the extension running. (it won't work in Recovery or in Safe Mode.)


If you have a trusted backup of that drive, you should remove the vendor extension, re-initialize the drive, and restore from backup. If you don't already have a trusted backup, that should be your top priority.


If you need additional clarification or suggestions, do not hesitate to ask, and Readers will be glad to provide more information.






Similar questions

8 replies
Question marked as Top-ranking reply

Jun 20, 2019 7:38 AM in response to redwhale

Your panic-reason is page fault, a reference to an Address that does not belong to the task trying to reference it.


The extensions at the 'scene of the crime' are AHCI SSD disk I/O drivers and related software.


You are running a third-party disk extension, a LaCie driver of some sort. That is a really bad idea.


Some of these vendor-specific drivers "do you a favor" by leaving your drive as a Windows New Technology File System (NTFS) drive, and simulating a Mac file structure on top of that. An immediate problem with that is the drive is unreadable without full blown MacOS AND the extension running. (it won't work in Recovery or in Safe Mode.)


If you have a trusted backup of that drive, you should remove the vendor extension, re-initialize the drive, and restore from backup. If you don't already have a trusted backup, that should be your top priority.


If you need additional clarification or suggestions, do not hesitate to ask, and Readers will be glad to provide more information.






Jun 21, 2019 7:44 PM in response to redwhale

Still getting crashes after removing LAcie driver:


mp_kdp_enter(): 3967, 1, 12 TIMED-OUT WAITING FOR NMI-ACK, PROCEEDING

panic(cpu 7 caller 0xffffff8003d881ba): "Machine Check at 0xffffff7f875689d6, registers:\n" "CR0: 0x000000008001003b, CR2: 0x0000000110357000, CR3: 0x0000000018c28000, CR4: 0x00000000001626e0\n" "RAX: 0x0000000000000020, RBX: 0xffffff8106a33400, RCX: 0x0000000000000001, RDX: 0x0000000000000000\n" "RSP: 0xffffffce4b1c3d60, RBP: 0xffffffce4b1c3d90, RSI: 0x0000000000000001, RDI: 0xffffff8106fa6f00\n" "R8: 0xffffff8107104500, R9: 0x00000322d1600a8c, R10: 0x0000000000000003, R11: 0x00000000e0000000\n" "R12: 0xffffff7f8757db80, R13: 0xffffff8106e23e40, R14: 0x00000000000007b0, R15: 0x0000000000000006\n" "RFL: 0x0000000000000046, RIP: 0xffffff7f875689d6, CS: 0x0000000000000008, SS: 0x0000000000000000\n" "Error code: 0x0000000000000000\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.71.45/osfmk/i386/trap_native.c:168

Backtrace (CPU 7), Frame : Return Address

0xffffff8003b4fb30 : 0xffffff8003c6bf96

0xffffff8003b4fb80 : 0xffffff8003d95354

0xffffff8003b4fbc0 : 0xffffff8003d875e4

0xffffff8003b4fc30 : 0xffffff8003c1dfb0

0xffffff8003b4fc50 : 0xffffff8003c6ba0c

0xffffff8003b4fd80 : 0xffffff8003c6b7cc

0xffffff8003b4fde0 : 0xffffff8003d881ba

0xffffff8003b4fed0 : 0xffffff8003c1e82f

0xffffffce4b1c3d90 : 0xffffff7f87559d8f

0xffffffce4b1c3e60 : 0xffffff7f87558fe9

0xffffffce4b1c3f10 : 0xffffff8003d893ec

0xffffffce4b1c3f30 : 0xffffff8003c8a442

0xffffffce4b1c3f80 : 0xffffff8003c8aa10

0xffffffce4b1c3fa0 : 0xffffff8003c1d557

Kernel Extensions in backtrace:

com.apple.driver.AppleIntelCPUPowerManagement(220.50.1)[754BAA00-8D55-3D24-8FED-FC2502F8246B]@0xffffff7f87557000->0xffffff7f87580fff


BSD process name corresponding to current thread: kernel_task


Mac OS version:

17G7024


Kernel version:

Darwin Kernel Version 17.7.0: Wed Apr 24 21:17:24 PDT 2019; root:xnu-4570.71.45~1/RELEASE_X86_64

Kernel UUID: A2B2C3B5-C3BF-3BD6-97E2-BD8CAFF51AEB

Kernel slide: 0x0000000003a00000

Kernel text base: 0xffffff8003c00000

__HIB text base: 0xffffff8003b00000

System model name: MacPro6,1 (Mac-F60DEB81FF30ACF6)


System uptime in nanoseconds: 3449084178683

last loaded kext at 3299804103609: com.logitech.driver.LogiGamingMouseFilter 1 (addr 0xffffff7f8832d000, size 40960)

last unloaded kext at 311934515654: com.apple.filesystems.msdosfs 1.10 (addr 0xffffff7f882a3000, size 61440)

loaded kexts:

com.logitech.driver.LogiGamingMouseFilter 1

com.logitech.driver.LogiWheelDriver 1

com.devguru.driver.SamsungMTP 1.4.27

net.telestream.driver.TelestreamAudio 1.1.1

com.waves.driver.soundgrid 9.7.99

com.squirrels.airparrot.framebuffer 5

com.squirrels.driver.AirParrotSpeakers 1.8

com.logmein.driver.LogMeInSoundDriver 411.3.31

com.uaudio.driver.UAFWAudio 4.3.1 47542

com.hzsystems.terminus.driver 4

com.digidesign.iokit.DigiDal 8.0.3f1

com.Sonarworks.driver.Sonarworks 1.8.11

com.paceap.kext.pacesupport.snowleopard 5.7.2

com.paragon-software.filesystems.ntfs 293.0.15

com.driver.LogJoystick 2.0

com.uaudio.driver.UAD2System 9.9.0

at.obdev.nke.LittleSnitch 5284

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Mac pro keeps crashing, please help with analysing crash report

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.