W5700X Crashes

Those first three are kernel panics, and should have produced a report that ends in .panic.

Do you have more of that third report?

can you run EtreCheck, change preferences to "allow Full disk Access" and then say GO? This will append a digest of crashes and panics to the end of the report.

Using EtreCheck to Troubleshoot Potential… - Apple Community

.

I still have more to remove, but after removing a few of the files on the list, restarting and following sleep, upon waking I was welcomed by the login screen (either crashed during sleep or upon waking - fail common).

I am attaching that system report. I notice the last line mentions "BSD process name corresponding to current thread: Adobe CEF Helper". Not sure if that is the cause of the crash, but if it is not sure what to do about it since Adobe CC is the main use for buying this machine.

Same story here.

Took delivery first week in July 2020 - 12-Core/1TBSSD/W5700X/32GB Ram w/AppleCare - Catalina 10.15.7.

I experienced my first freeze/auto-restart on Day-1 when I was setting up the machine with a single 26" NEC 2K monitor attached. Once I got everything configured, I disconnected my set-up monitor and cable and moved the machine to my main workstation area (to replace my 2012 Mac Pro running 3 NEC 27" monitors). I started getting crashes mostly when launching Adobe Illustrator CC, InDesignCC and Acrobat Pro CC sporadically. Usually they would only crash on "launch" and relaunching them would usually solve the issue - rarely had a problem while actually doing work inside an app. Most of the crashes would occur either during sleep or perhaps waking from sleep. I always forwarded crash reports to Apple and Adobe when prompted. During the first few days, I contacted AppleCare to report the issues and went through tons of instructions doing gall the usually troubleshooting steps including clean reinstall of system and Adobe CC clean reinstall. Same problems persisted. During this whole period I was reading more and more posts on the MacRumors forum from new Mac Pro owners that were seeing the same behavior with their Mac Pros running the same w5700x card. Several of those people finally gave up and purchased the far more expensive Vega Pro II card which according to all their reports ended ALL their problems. I did not have another $3,000 to fix my problem!

Eventually my case got escalated to Ari in Tech Support (who was extremely knowledgeable and helpful). Again we tried everything - clean installs, removing .kext files, etc. and nothing helped. He was working in concert with Apple Engineering as I was told to help diagnose the issues. After exhausting every avenue, Apple Engineering decidedI had a bad logic board? They insisted that the GPU was not the source of the problems. So they finally approved replacing my entire machine with the exact same configuration. There were stock delays for weeks, but the new replacement machine arrived the first part of November 2020. I hooked everything up, reinstalled software, etc. and the same problems began again and have persisted ever since.

I have recorded 34 crashes/restarts since I got the new machine. Most have occurred during sleep (or waking from sleep). I am assuming that most of those crashes occur on "wake" as my Carbon Copy Cloner auto-backups always completes during the sleep cycles at different times.

Experiences:

• Adobe AI - usually on launch right after palettes appear if it is going to freeze/crash/restart.
• Adobe InDesign - usually on launch right after palettes appear if it is going to freeze/crash/restart.
• Adobe Acrobat Pro DC - usually on launch right after interface appears if it is going to freeze/crash/restart.
• Dreamweaver - Unable to Cut and Paste text in Code View twice - restarting app fixed it?
• Quicktime - usually freeze/crash/restart right after launch when double-clicking a tutorial .mov thumbnail.
• Quickbooks - one crash
• Safari - two crashes
• Just selecting a file on the Desktop once caused freeze/crash/restart
• At least (3) times, waking from sleep first thing in the morning, greeted by login screen asking for password with a dialog that the computer shut down improperly.
• Only seen a Kernel Panic dialog once.
• Never seen a problem with Quicken, Mail, or Messages (which I am in extensively)
• Mac Pro power light always stays on - even after all crashes/logouts - only powered off once the first day I got it.
• When freezes occur, Force Quit cannot be accessed - machine just restarts.

Similar to the thread-started in this post, sometimes I will go for days with no problem, then it will do it once a day or sometimes 3-4 times a day. I just made it 10 days without a problem and then yesterday it crashed in InDesign after working in the app for about 45 minutes - computer speakers started making a rhythmic stain sound fro about 5 cycles, then crash (a common audible precursor, but not always).

I have had Top-Of-The line Macs going back 30 years and never seen anything like this! Never had a single freeze on my 2012 Mac Pro over 8 years of hard use.

Looks like the only fix is to spend $3,000 for the upgraded card (which I cannot swing right now).

If your Macs are crashing post the panic reports.

Panic Reports are stored at:

/Library/Logs/DiagnosticReports

If you copy and paste that string into:

Finder > Go menu > Go to Folder

it will take you to where those reports are stored.

They are named with Date&Time and end in .panic

You can post the entire report here, by using the “additional text” Icon in the reply footer (looks like a paper with writing).

Please don’t post more about 20 lines of any other types of reports — they are interminable, and any information useful for this purpose is on the first screenful.

Grant Bennet-Alder...

I have no crash reports in that location that end in .panic

Some of the reports I see when a crash occurs (which I forward to Apple and Adobe when prompted), are only a few lines while others are probably over 100 lines.

Here are (4) beginning segments of reports I have received (2 from my first Mac Pro and 2 from my replacement):

First Mac Pro: Most of these random crashes that occur while the displays are in sleep have fairly short crash reports...

panic(cpu 0 caller 0xfffffff010958cec): x86 CPU CATERR detected

Debugger message: panic

Memory ID: 0xff

OS version: 17P6610

macOS version: 19G2021

Kernel version: Darwin Kernel Version 19.6.0: Thu Jun 18 20:30:46 PDT 2020; root:xnu-6153.145.1~1/RELEASE_ARM64_T8010

Kernel UUID: 828E8E47-4C82-3639-83B9-4F7DB86934F6

iBoot version: iBoot-5540.140.12

secure boot?: YES

x86 EFI Boot State: 0x16

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x1

x86 Previous Power Transitions: 0x70707060400

PCIeUp link state: 0x89271611

Paniclog version: 13

Kernel slide: 0x000000000898c000

Kernel text base: 0xfffffff00f990000

mach_absolute_time: 0x6006f50d32a

Epoch Time: sec usec

Boot : 0x5f62c404 0x0003d50b

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x5f66f608 0x000e2854

Panicked task 0xffffffe0000df600: 2352 pages, 157 threads: pid 0: kernel_task

Panicked thread: 0xffffffe000399520, backtrace: 0xffffffe015a534b0, tid: 304

lr: 0xfffffff0101e4860 fp: 0xffffffe015a534f0

Made it almost 12 hours after an update. Crashed when waking displays:

panic(cpu 0 caller 0xfffffff018f78cec): x86 CPU CATERR detected

Debugger message: panic

Memory ID: 0xff

OS version: 17P6610

macOS version: 19H2

Kernel version: Darwin Kernel Version 19.6.0: Thu Jun 18 20:30:46 PDT 2020; root:xnu-6153.145.1~1/RELEASE_ARM64_T8010

Kernel UUID: 828E8E47-4C82-3639-83B9-4F7DB86934F6

iBoot version: iBoot-5540.140.12

secure boot?: YES

x86 EFI Boot State: 0x16

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x7

x86 Previous Power Transitions: 0x70707060400

PCIeUp link state: 0x89271611

Paniclog version: 13

Kernel slide: 0x0000000010fac000

Kernel text base: 0xfffffff017fb0000

mach_absolute_time: 0x97f6845887

Epoch Time: sec usec

Boot : 0x5f6cff6c 0x0009f1e5

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x5f6d69a4 0x00025ba5

Panicked task 0xffffffe0006b1400: 2257 pages, 157 threads: pid 0: kernel_task

Panicked thread: 0xffffffe000a28000, backtrace: 0xffffffe015cc34b0, tid: 335

11 hours after receiving the replacement Mac Pro

Computer just restarted on it’s own while unattended. I heard (4) what sounded like static rhythmic audible pulses through the external speakers followed by auto-restart?

REPORT:

panic(cpu 0 caller 0xfffffff0232b4cec): x86 CPU CATERR detected

Debugger message: panic

Memory ID: 0x6

OS version: 17P6610

macOS version: 19H2

Kernel version: Darwin Kernel Version 19.6.0: Thu Jun 18 20:30:46 PDT 2020; root:xnu-6153.145.1~1/RELEASE_ARM64_T8010

Kernel UUID: 828E8E47-4C82-3639-83B9-4F7DB86934F6

iBoot version: iBoot-5540.140.12

secure boot?: YES

x86 EFI Boot State: 0x16

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x1

x86 Previous Power Transitions: 0x20002000200

PCIeUp link state: 0x89271611

Paniclog version: 13

Kernel slide: 0x000000001b2e8000

Kernel text base: 0xfffffff0222ec000

mach_absolute_time: 0x8a3581fecc

Epoch Time: sec usec

Boot : 0x5fa26160 0x000aca18

Sleep : 0x5fa2f23f 0x00064dba

Wake : 0x5fa2fd6c 0x000a0ce2

Calendar: 0x5fa318c5 0x000881dd

Panicked task 0xffffffe0007e2a00: 2317 pages, 157 threads: pid 0: kernel_task

Panicked thread: 0xffffffe0009ada68, backtrace: 0xffffffe015dd34b0, tid: 320

lr: 0xfffffff022b40860 fp: 0xffffffe015dd34f0

Application crash when quitting InDesign today (computer itself did not crash):

Process: Adobe InDesign 2021 [20227]

Path: /Applications/Adobe InDesign 2021/Adobe InDesign 2021.app/Contents/MacOS/Adobe InDesign 2021

Identifier: com.adobe.InDesign

Version: 16.1.0.20 (16100)

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Adobe InDesign 2021 [20227]

User ID: 501

Date/Time: 2021-02-21 15:15:15.581 -0600

OS Version: Mac OS X 10.15.7 (19H524)

Report Version: 12

Bridge OS Version: 5.2 (18P4346)

Anonymous UUID: 978229B3-C901-9B11-CD01-AEB6770D1985

Sleep/Wake UUID: CE5B84AC-2FD0-4527-B4CF-7473C06EACC1

Time Awake Since Boot: 96000 seconds

Time Since Wake: 640 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Main Thread Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: EXC_I386_GPFLT

Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11

Termination Reason: Namespace SIGNAL, Code 0xb

Terminating Process: exc handler [20227]

Thread 0 Crashed:: Main Thread Dispatch queue: com.apple.main-thread

Here is all I have of the 3rd report...

REPORT:

panic(cpu 0 caller 0xfffffff0232b4cec): x86 CPU CATERR detected

Debugger message: panic

Memory ID: 0x6

OS version: 17P6610

macOS version: 19H2

Kernel version: Darwin Kernel Version 19.6.0: Thu Jun 18 20:30:46 PDT 2020; root:xnu-6153.145.1~1/RELEASE_ARM64_T8010

Kernel UUID: 828E8E47-4C82-3639-83B9-4F7DB86934F6

iBoot version: iBoot-5540.140.12

secure boot?: YES

x86 EFI Boot State: 0x16

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x1

x86 Previous Power Transitions: 0x20002000200

PCIeUp link state: 0x89271611

Paniclog version: 13

Kernel slide: 0x000000001b2e8000

Kernel text base: 0xfffffff0222ec000

mach_absolute_time: 0x8a3581fecc

Epoch Time: sec usec

Boot : 0x5fa26160 0x000aca18

Sleep : 0x5fa2f23f 0x00064dba

Wake : 0x5fa2fd6c 0x000a0ce2

Calendar: 0x5fa318c5 0x000881dd

Panicked task 0xffffffe0007e2a00: 2317 pages, 157 threads: pid 0: kernel_task

Panicked thread: 0xffffffe0009ada68, backtrace: 0xffffffe015dd34b0, tid: 320

lr: 0xfffffff022b40860 fp: 0xffffffe015dd34f0

lr: 0xfffffff022b406bc fp: 0xffffffe015dd3560

lr: 0xfffffff022c5b770 fp: 0xffffffe015dd3610

lr: 0xfffffff02310d5d8 fp: 0xffffffe015dd3620

lr: 0xfffffff022b40024 fp: 0xffffffe015dd3990

lr: 0xfffffff022b4037c fp: 0xffffffe015dd39e0

lr: 0xfffffff02388e974 fp: 0xffffffe015dd3a00

lr: 0xfffffff0232b4cec fp: 0xffffffe015dd3a30

lr: 0xfffffff0232a611c fp: 0xffffffe015dd3aa0

lr: 0xfffffff0232a8044 fp: 0xffffffe015dd3b50

lr: 0xfffffff0232a5854 fp: 0xffffffe015dd3be0

lr: 0xfffffff02326ccb8 fp: 0xffffffe015dd3c10

lr: 0xfffffff02307ab14 fp: 0xffffffe015dd3c50

lr: 0xfffffff02307a398 fp: 0xffffffe015dd3c90

lr: 0xfffffff023118514 fp: 0x0000000000000000

OK. I know why your Mac is unstable.

You simply have too much junk added, where 'junk' in this context is stuff that may be perfectly good, but you don't happen to need right now, like stuff in your attic. You need to strongly simplify what you have added if you want to get back to stability.

You could start by removing cindori, cleanmyMac, cocktail, flash player, and maintain. you seem to be running every file-sharing utility there is, and each of them punishes performance by reading your files non-stop. you need adequate backups, and then you would not need to have disk warrior Derived and techTool running.

The crashes shown are all Application problems. Are you certain you have the correct up-to-date versions of all those items listed as issues under Diagnostic information?

I started removing some of the things you mentioned since I saw the report and will keep seeing what I can delete. I did not know programs like Cocktail (maintain), etc. ran anything when not launched. Removed Flash Player just now.

Thanks for the feedback!

There are three quick take-aways from any panic report.

1) The panic-reason,

NMIPI is a multi-processor cooperation problem. One of the processors, possibly including the graphics processor in that set, dibbled interrupts to quickly take care of something, then wandered off before finishing.

2) the extensions present at the "scene of the crime", and

PCIe drivers. graphics drivers also, but real graphics issues tend to show only grpahics

3) the BSD process in which the problem occurred.

from your report:

BSD process name corresponding to current thread: IMDPersistenceAg

Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

that runs Messages and FaceTime.

-------

If you are seeing issue with adobe packages, adobe knows about some issues, especially under Big Sur, and you may need to re-Install their latest package.

There is an additional issue with adobe reader that may requires that adobe reader be re-installed after everything else is in place.

https://helpx.adobe.com/download-install/kb/macos-big-sur.html

.

Thanks. I may look into reinstalling Adobe Suite (yet again).

I am still running on Catalina. I have been running Big Sur on my laptop (since it is not critical for my business) and I am not ready to fight the Big Sur issues on top of everything else on the Mac Pro just yet.

I went ahead and purchased the Pro version of EtreCheck and have been doing some more house cleaning.

That is an application crash, not a panic. Its organization does not follow the organization I posted above, because it is not a kernel panic report.

It was called deliberately by adobe after effects when it got into a bind and could not proceed for some reason.