Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Does this crash report not give any clues as to what is causing this type of crash? 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
lr: 0xfffffff0101e46bc fp: 0xffffffe015a53560
lr: 0xfffffff0102ff770 fp: 0xffffffe015a53610
lr: 0xfffffff0107b15d8 fp: 0xffffffe015a53620
lr: 0xfffffff0101e4024 fp: 0xffffffe015a53990
lr: 0xfffffff0101e437c fp: 0xffffffe015a539e0
lr: 0xfffffff010f32974 fp: 0xffffffe015a53a00
lr: 0xfffffff010958cec fp: 0xffffffe015a53a30
lr: 0xfffffff01094a11c fp: 0xffffffe015a53aa0
lr: 0xfffffff01094c044 fp: 0xffffffe015a53b50
lr: 0xfffffff010949854 fp: 0xffffffe015a53be0
lr: 0xfffffff010910cb8 fp: 0xffffffe015a53c10
lr: 0xfffffff01071eb14 fp: 0xffffffe015a53c50
lr: 0xfffffff01071e398 fp: 0xffffffe015a53c90
lr: 0xfffffff0107bc514 fp: 0x0000000000000000
 
Nothing useful here that I can see. Can you share the full log? Try looking in /Library/Logs/PanicReporter or /Library/Logs/DiagnosticReports.
 
I just see this in the DiagnosticReports/ProxiedDevice-Bridge>Retired (followed by gibberish):

{"caused_by":"macos","macos_version":"Mac OS X 10.15.6 (19G2021)","os_version":"Bridge OS 4.6 (17P6610)","macos_system_state":"running","incident_id":"A2DBF474-AACD-4459-8040-4147696C46B1","timestamp":"2020-09-20 06:47:56.00 +0000","bug_type":"210"}
{
"build" : "Bridge OS 4.6 (17P6610)",
"product" : "iBridge2,6",
"kernel" : "Darwin Kernel Version 19.6.0: Thu Jun 18 20:30:46 PDT 2020; root:xnu-6153.145.1~1\/RELEASE_ARM64_T8010",
"incident" : "A2DBF474-AACD-4459-8040-4147696C46B1",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2020-09-20 06:47:55.56 +0000",
"panicString" : "panic(cpu 0 caller 0xfffffff0231f0cec): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 17P6610\nmacOS version: 19G2021\nKernel version: Darwin Kernel Version 19.6.0: Thu Jun 18 20:30:46 PDT 2020; root:xnu-6153.145.1~1\/RELEASE_ARM64_T8010\nKernel UUID: 828E8E47-4C82-3639-83B9-4F7DB86934F6\niBoot version: iBoot-5540.140.12\nsecure boot?: YES\nx86 EFI Boot State: 0x16\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0xec\nx86 Previous Power Transitions: 0x70707060400\nPCIeUp link state: 0x89271611\nPaniclog version: 13\nKernel slide: 0x000000001b224000\nKernel text base: 0xfffffff022228000\nmach_absolute_time: 0x7257dfd8c\nEpoch Time: sec usec\n Boot : 0x5f66f614 0x00038048\n Sleep : 0x00000000 0x00000000\n Wake : 0x00000000 0x00000000\n Calendar: 0x5f66fb0d 0x000a397e\n\nPanicked task 0xffffffe000723600: 2281 pages, 157 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe000a074d0, backtrace: 0xffffffe015aa34b0, tid: 319\n\t\t lr: 0xfffffff022a7c860 fp: 0xffffffe015aa34f0\n\t\t lr: 0xfffffff022a7c6bc fp: 0xffffffe015aa3560\n\t\t lr: 0xfffffff022b97770 fp: 0xffffffe015aa3610\n\t\t lr: 0xfffffff0230495d8 fp: 0xffffffe015aa3620\n\t\t lr: 0xfffffff022a7c024 fp: 0xffffffe015aa3990\n\t\t lr: 0xfffffff022a7c37c fp: 0xffffffe015aa39e0\n\t\t lr: 0xfffffff0237ca974 fp: 0xffffffe015aa3a00\n\t\t lr: 0xfffffff0231f0cec fp: 0xffffffe015aa3a30\n\t\t lr: 0xfffffff0231e211c fp: 0xffffffe015aa3aa0\n\t\t lr: 0xfffffff0231e4044 fp: 0xffffffe015aa3b50\n\t\t lr: 0xfffffff0231e1854 fp: 0xffffffe015aa3be0\n\t\t lr: 0xfffffff0231a8cb8 fp: 0xffffffe015aa3c10\n\t\t lr: 0xfffffff022fb6b14 fp: 0xffffffe015aa3c50\n\t\t lr: 0xfffffff022fb6398 fp: 0xffffffe015aa3c90\n\t\t lr: 0xfffffff023054514 fp: 0x0000000000000000\n\n",
"panicFlags" : "0x102",
"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 80576 **\n",
"macOSPanicFlags" : "0x0",
"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",
 
I just see this in the DiagnosticReports/ProxiedDevice-Bridge>Retired (followed by gibberish):
==============
"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",

???

Discussion of issue in the Apple Forum
The bug with the hanging macOS is reported in the Apple forum in the thread “BAD MAGIC! (flag set in iBoot panic header)” — Catalina freezing all the time! The thread starter writes the following in early November 2019:

 
Doesn't shed much light. IIRC, you reinstalled macOS as per support's request, yes? Just asking based on the thread OkiRun shared, but really grasping at straws here.
 
Doesn't shed much light. IIRC, you reinstalled macOS as per support's request, yes? Just asking based on the thread OkiRun shared, but really grasping at straws here.
I have reinstalled a new system twice - second time on a new volume Apple Support had me create.

Last word I got was they agreed to replace the machine and took my Credit Card to put a $10,000 hold on it (since I have been trying to get this resolved since day-one). That was 3 weeks ago tomorrow and they are no longer answering my emails. I waited 2 weeks before emailing them for a status update and asked again a couple days ago - no reply.

So I guess that is the end of any support in my case.
 
Last word I got was they agreed to replace the machine and took my Credit Card to put a $10,000 hold on it (since I have been trying to get this resolved since day-one). That was 3 weeks ago tomorrow and they are no longer answering my emails. I waited 2 weeks before emailing them for a status update and asked again a couple days ago - no reply.

So I guess that is the end of any support in my case.

WTF. 3 weeks and still no machine?? I've ordered a few now (all replacements of the one that preceded it) and takes 7-8 days from the time the order is submitted until delivered to my doorstep (in Seattle, WA area).

My takeaway from all this is ALWAYS purchase direct from Apple, verify all good within the 2-week window, and if ANY issues, return it for a replacement until the issue is resolved -- or just return and move on if product fails to meet expectations.

@choreo, the good news here is that when you finally get your replacement system, you should be able to follow this pattern as if originally purchased form Apple, except for perhaps the full refund and move on part since originally purchased from B&H.
 
Last edited:
@choreo, the good news here is that when you finally get your replacement system, you should be able to follow this pattern as if originally purchased form Apple, except for perhaps the full refund and move on part since originally purchased from B&H.

True, but this purchase from B&H was handled differently than any other Apple computer/device I have purchased from B&H in the past. It looks like the order was just forwarded to Apple in Austin, TX which handled all the shipping and communication directly with me. B&H just took the money? It does not even show up in my list of probably 100 B&H orders online and I never heard another word for B&H after I hit the Submit button?
 
Well, I updated to Big Sur Beta 8 yesterday and had my fist Panic this morning: Beta 6 had no panics at all.

Panic(CPU 4, time 6540292313202): NMIPI for unresponsive processor: TLB flush timeout, TLB state:0x0
RAX: 0xffffffd23abe7000, RBX: 0xffffffd23abe7000, RCX: 0x0000000000010046, RDX: 0x0000000000000001
RSP: 0xffffffa2266abb40, RBP: 0xffffffa2266abbb0, RSI: 0x0000000000000001, RDI: 0xffffff876fc61930
R8: 0x0000000000000001, R9: 0x0000000000000046, R10: 0x0000000000000000, R11: 0x000000000fada000
R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0xffffffffffffffff, R15: 0xffffff9408f48900
RFL: 0x0000000000000246, RIP: 0xffffff7faa256290, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 4), Frame : Return Address
0xffffffa1acb64f80 : 0xffffff8017bed6eb
0xffffffa1acb64fd0 : 0xffffff8017a60bdd
0xffffffa2266abbb0 : 0xffffff7faa2613b2
0xffffffa2266abbe0 : 0xffffff7faa1fe575
0xffffffa2266abc50 : 0xffffff7faa1fe293
0xffffffa2266abd80 : 0xffffff7faa1fe937
0xffffffa2266abe00 : 0xffffff7fb749eddd
0xffffffa2266abe60 : 0xffffff7fb74acc10
0xffffffa2266abea0 : 0xffffff7fb74ac3a0
0xffffffa2266abee0 : 0xffffff8018214e10
0xffffffa2266abf30 : 0xffffff801821357e
0xffffffa2266abf70 : 0xffffff8018212b66
0xffffffa2266abfa0 : 0xffffff8017a6013e
Kernel Extensions in backtrace:
com.apple.iokit.IOAcceleratorFamily2(439.35.1)[B3730610-3599-3C8A-BBC1-A356C7D5A886]@0xffffff7fb749a000->0xffffff7fb7503fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A32AA12A-2BD1-38BF-B7FA-17D083336A70]@0xffffff8018fda000->0xffffff8018feefff
dependency: com.apple.iokit.IOGraphicsFamily(585)[BA2080E4-BA85-3D7D-BA31-4528A9C7FB7E]@0xffffff7fb75fd000->0xffffff7fb762bfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[6223446D-5319-3378-9CE2-0A8E8E74F67B]@0xffffff801a3df000->0xffffff801a406fff
dependency: com.apple.iokit.IOReportFamily(47)[CA61C5AE-5FC0-3924-86D7-694C4FEE5F02]@0xffffff801a415000->0xffffff801a417fff
dependency: com.apple.iokit.IOSurface(289.2)[E1C5DA52-605F-35E7-8986-EAD3B1EE5148]@0xffffff801a523000->0xffffff801a53efff
com.apple.kext.AMDRadeonX6000(4.0)[0603AA9F-E2CA-3032-9E8C-90EA1E5D900A]@0xffffff7faa1f3000->0xffffff7faa326fff
dependency: com.apple.iokit.IOAcceleratorFamily2(439.35.1)[B3730610-3599-3C8A-BBC1-A356C7D5A886]@0xffffff7fb749a000->0xffffff7fb7503fff
dependency: com.apple.iokit.IOGraphicsFamily(585)[BA2080E4-BA85-3D7D-BA31-4528A9C7FB7E]@0xffffff7fb75fd000->0xffffff7fb762bfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[6223446D-5319-3378-9CE2-0A8E8E74F67B]@0xffffff801a3df000->0xffffff801a406fff
dependency: com.apple.iokit.IOSurface(289.2)[E1C5DA52-605F-35E7-8986-EAD3B1EE5148]@0xffffff801a523000->0xffffff801a53efff
Kernel Extensions in backtrace:
com.apple.kext.AMDRadeonX6000(4.0)[0603AA9F-E2CA-3032-9E8C-90EA1E5D900A]@0xffffff7faa1f3000->0xffffff7faa326fff
dependency: com.apple.iokit.IOAcceleratorFamily2(439.35.1)[B3730610-3599-3C8A-BBC1-A356C7D5A886]@0xffffff7fb749a000->0xffffff7fb7503fff
dependency: com.apple.iokit.IOGraphicsFamily(585)[BA2080E4-BA85-3D7D-BA31-4528A9C7FB7E]@0xffffff7fb75fd000->0xffffff7fb762bfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[6223446D-5319-3378-9CE2-0A8E8E74F67B]@0xffffff801a3df000->0xffffff801a406fff
dependency: com.apple.iokit.IOSurface(289.2)[E1C5DA52-605F-35E7-8986-EAD3B1EE5148]@0xffffff801a523000->0xffffff801a53efff

Process name corresponding to current thread: kernel_task
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20A5374i

Kernel version:
Darwin Kernel Version 20.1.0: Thu Sep 17 22:14:18 PDT 2020; root:xnu-7195.40.84.171.5~4/RELEASE_X86_64
Kernel UUID: 1BEB2151-70F0-3656-AF8F-9BF853F1F2C1
KernelCache slide: 0x0000000017800000
KernelCache base: 0xffffff8017a00000
Kernel slide: 0x0000000017810000
Kernel text base: 0xffffff8017a10000
__HIB text base: 0xffffff8017900000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Hibernation exit count: 0

System uptime in nanoseconds: 6540292394454
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000005f2c7ce125a
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000016b8703476 0x0000000000000000
last started kext at 123901732861: @filesystems.smbfs 3.4.1 (addr 0xffffff7fb7fff000, size 434176)
last stopped kext at 256715009340: >!A!ILpssGspi 3.0.60 (addr 0xffffff8018f03000, size 32768)
loaded kexts:
com.hzsystems.terminus.driver 4
com.Cycling74.driver.Soundflower 1.6.7
com.intel.driver.EnergyDriver 3.7.0
@filesystems.smbfs 3.4.1
>AGPM 119
>!APlatformEnabler 2.7.0d0
>X86PlatformShim 1.0.0
@fileutil 20.036.15
>!AUpstreamUserClient 3.6.8
>!AMCCSControl 1.14
@kext.AMDFramebuffer 4.0.0
@filesystems.autofs 3.0
@kext.AMDRadeonX4000 4.0.0
@kext.AMDRadeonX6000 4.0.0
@kext.AMDRadeonServiceManager 4.0.0
>!AGraphicsDevicePolicy 6.1.23
@AGDCPluginDisplayMetrics 6.1.23
>pmtelemetry 1
>!ABridgeAudio!C 6.78
>LuaHardwareAccess 1.0.16
>BridgeAudioCommunication 6.78
>!AAVEBridge 6.1
|IOUserEthernet 1.0.1
>!A!IMCEReporter 115
>usb.!UUserHCI 1
|IO!BSerialManager 8.0.0d53
@Dont_Steal_Mac_OS_X 7.0.0
>!AHV 1
>!ADiskImages2 1
>!AGFXHDA 100.1.431
>!A!ISlowAdaptiveClocking 4.0.0
>!AThunderboltIP 4.0.3
@kext.AMD9500!C 4.0.0
>!A!IPCHPMC 2.0.1
|SCSITaskUserClient 436.40.2
>BCMWLANFirmware4378.Hashstore 1
>BCMWLANFirmware4377.Hashstore 1
>BCMWLANFirmware4364.Hashstore 1
>BCMWLANFirmware4355.Hashstore 1
@filesystems.tmpfs 1
@filesystems.hfs.kext 556.40.4
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
>!ABCMWLANBusInterfacePCIeMac 1
@filesystems.apfs 1677.40.31
@private.KextAudit 1.0
>!AAHCIPort 346
>!AACPIButtons 6.1
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 310
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
|IO!BHost!CUARTTransport 8.0.0d53
|IO!BHost!CTransport 8.0.0d53
>!ASMBus!C 1.0.18d1
@kext.triggers 1.0
@kext.AMDRadeonX4700HWLibs 1.0
|IOAccelerator!F2 439.35.1
@kext.AMDRadeonX4000HWServices 4.0.0
>!AGraphicsControl 6.1.23
@kext.AMDRadeonX6000HWLibs 1.0
>!A16X50Serial 3.2
|IOAVB!F 900.11
@plugin.IOgPTPPlugin 900.10
|IOEthernetAVB!C 1.1.0
@kext.AMDRadeonX6000Framebuffer 4.0.0
>usb.cdc.acm 5.0.0
>usb.serial 6.0.0
>!UAudio 401.1
@!AGPUWrangler 6.1.23
|IONDRVSupport 585
|IOAudio!F 300.6.1
@vecLib.kext 1.2.0
|IOSlowAdaptiveClocking!F 1.0.0
>X86PlatformPlugin 1.0.0
@kext.AMDSupport 4.0.0
@!AGraphicsDeviceControl 6.1.23
>IOPlatformPlugin!F 6.0.0d8
@kext.AMDRadeonX6000HWServices 4.0.0
|IOGraphics!F 585
|IOSCSIMultimediaCommandsDevice 436.40.2
|IOBD!S!F 1.8
|IODVD!S!F 1.8
|IOCD!S!F 1.8
>usb.!UHub 1.2
>usb.cdc.ncm 5.0.0
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>!AThunderboltPCIDownAdapter 4.1.1
>!AThunderboltDPInAdapter 8.1.3
>!AThunderboltDPAdapter!F 8.1.3
>!AHPM 3.4.4
>!A!ILpssI2C!C 3.0.60
>!A!ILpssDmac 3.0.60
>!ABSDKextStarter 3
|IOSurface 289.2
@filesystems.hfs.encodings.kext 1
>!AEthernetAquantiaAqtion 1.0.64
>!ABCMWLANCoreMac 1.0.0
|IOSerial!F 11
|IO80211!FV2 1200.12.2b1
|IOSkywalk!F 1
>mDNSOffloadUserClient 1.0.1b8
>IOImageLoader 1.0.0
>corecapture 1.0.4
>!AThunderboltNHI 7.2.8
|IOThunderbolt!F 9.3.2
|IOAHCIBlock!S 332
>usb.!UVHCIBCE 1.2
>usb.!UVHCICommonBCE 1.0
>usb.!UVHCI 1.2
>usb.!UVHCICommon 1.0
>!AEffaceableNOR 1.0
|IONVMe!F 2.1.0
|IOBufferCopy!C 1.1.0
|IOBufferCopyEngine!F 1
|IOUSB!F 900.4.2
>!A!ILpssI2C 3.0.60
|IOAHCI!F 294
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
>!ASMCRTC 1.0
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$!AImage4 3.0.0
|IOTimeSync!F 900.10
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 8.0.0d53
|IOReport!F 47
|IO!BPacketLogger 8.0.0d53
$quarantine 4
$sandbox 300.0
@Kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 511.40.3
|IOUSBMass!SDriver 184.40.4
|IOSCSIBlockCommandsDevice 436.40.2
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 436.40.2
>!AMobileFileIntegrity 1.0.5
@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.corecrypto 1.0
@kec.Libm 1
panic(cpu 2 caller 0xffffff8017bc7201): "IPI timeout, unresponsive CPU bitmap: 0x10, NMIPI acks: 0x0, now: 0x0, deadline: 6539589242075, pre-NMIPI time: 0x5f29de4cdab, current: 0x5f2bbb2337c, global: 1"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.40.84.171.5/osfmk/x86_64/pmap.c:2891
Backtrace (CPU 2), Frame : Return Address
0xffffffa21b7b3610 : 0xffffff8017abb65d
0xffffffa21b7b3660 : 0xffffff8017bfdb33
0xffffffa21b7b36a0 : 0xffffff8017bedf4a
0xffffffa21b7b36f0 : 0xffffff8017a60a2f
0xffffffa21b7b3710 : 0xffffff8017abaefd
0xffffffa21b7b3830 : 0xffffff8017abb1e8
0xffffffa21b7b38a0 : 0xffffff80182b9b8a
0xffffffa21b7b3910 : 0xffffff8017bc7201
0xffffffa21b7b39d0 : 0xffffff8017bcd08f
0xffffffa21b7b3ab0 : 0xffffff8017bcde46
0xffffffa21b7b3b10 : 0xffffff8017b5b1b5
0xffffffa21b7b3c60 : 0xffffff8017b5ab03
0xffffffa21b7b3c90 : 0xffffff8017b53ed1
0xffffffa21b7b3cc0 : 0xffffff801819f861
0xffffffa21b7b3ce0 : 0xffffff8018249614
0xffffffa21b7b3d40 : 0xffffff8017bab88a
0xffffffa21b7b3d90 : 0xffffff8017ac0c87
0xffffffa21b7b3e00 : 0xffffff8017a975b5
0xffffffa21b7b3e60 : 0xffffff8017aaeb62
0xffffffa21b7b3ef0 : 0xffffff8017bd2183
0xffffffa21b7b3fa0 : 0xffffff8017a61216

Process name corresponding to current thread: TG Pro

Lou
 
WTF. 3 weeks and still no machine?? I've ordered a few now (all replacements of the one that preceded it) and takes 7-8 days from the time the order is submitted until delivered to my doorstep (in Seattle, WA area).

Finally got through to Apple Tech Support again yesterday (transferred me to a different technician). He said I am still scheduled, but the hold up is my exact configuration has to show up in the Apple Store online showing a 7-day or less delivery time before they can process the replacement. Right now it still shows just over 7 days!

Of course my original "showed" 6-weeks delivery time, I got in in a few days.
 
my exact configuration has to show up in the Apple Store online showing a 7-day or less delivery time
That's a really odd requirement and a bit of a mixed bag response. It's good that Apple is exercising some leeway to hook you up with a replacement machine, but they're OK leaving you in a lurch for so long?? I guess they get a "C" -- assuming the replacement machine addresses the issues. Best of luck getting to the finish line ASAP.
 
  • Like
Reactions: choreo
That's a really odd requirement and a bit of a mixed bag response. It's good that Apple is exercising some leeway to hook you up with a replacement machine, but they're OK leaving you in a lurch for so long?? I guess they get a "C" -- assuming the replacement machine addresses the issues. Best of luck getting to the finish line ASAP.
This is exactly as stupid as apple needing my entire Mac Pro back to test the GPU which I'm claiming is faulty/not fit for sale. In what world should my Mac be going back. It's just absurd.
 
needing my entire Mac Pro back to test the GPU

Yea, that's pretty messed up.

It seems Apple isn't serious about having a pro line, which needs to go hand in hand with pro support. People who depend on their machines to make money cannot be out a machine for days or weeks at a time.
 
as I typed this, the system crashed. This time on launching After effects. Nothing else open. and it just stalled. No mouse activity, no ability to swap apps just totally unresponsive, Eventually panicking and restarting itself. This is the first in over 2 a week and a half.
 
as I typed this, the system crashed. This time on launching After effects. Nothing else open. and it just stalled. No mouse activity, no ability to swap apps just totally unresponsive, Eventually panicking and restarting itself. This is the first in over 2 a week and a half.
Mine made it about 6 days three weeks ago without a single crash, then it came back with a vengeance (about 5 in one day). It is totally random here.
 
This is exactly as stupid as apple needing my entire Mac Pro back to test the GPU which I'm claiming is faulty/not fit for sale. In what world should my Mac be going back. It's just absurd.

Same here. That is why I wanted to purchase a "modular" Mac. Of course, I have never had a single hardware issue with the cheaper modular Macs in the past (still running my 2012 Mac Pro with no problems), so I really was not expecting this. Since I live several hundred miles from the nearest Apple Store, I was thinking that if a component like a GPU or a Power Supply went out, they could just send me a new one. Also, my Brother has owned several iMacs and he lives in Dallas, but every time he had a problem with one and had to have Apple come out to fix them (or had to take one to an Apple Store), they usually made the problem worse (as they really are not designed to take apart). He always ended up buying a new iMac after Apple tried to fix them (usually display issues). I made this massive purchase (massive for me) based only past experience that I have never had a modular Mac hardware problem in 30 years.

I am still not convinced it is a "hardware" issue, but we will see. Of course, buying a Pro Vega is an option, but that does not mean there is a problem with the w5700x hardware necessarily.
 
Same here. That is why I wanted to purchase a "modular" Mac. Of course, I have never had a single hardware issue with the cheaper modular Macs in the past (still running my 2012 Mac Pro with no problems), so I really was not expecting this. Since I live several hundred miles from the nearest Apple Store, I was thinking that if a component like a GPU or a Power Supply went out, they could just send me a new one. Also, my Brother has owned several iMacs and he lives in Dallas, but every time he had a problem with one and had to have Apple come out to fix them (or had to take one to an Apple Store), they usually made the problem worse (as they really are not designed to take apart). He always ended up buying a new iMac after Apple tried to fix them (usually display issues). I made this massive purchase (massive for me) based only past experience that I have never had a modular Mac hardware problem in 30 years.

I am still not convinced it is a "hardware" issue, but we will see. Of course, buying a Pro Vega is an option, but that does not mean there is a problem with the w5700x hardware necessarily.
Apple are actively investigating the issue I was told. The problem being how quick they can do anything about it. “Actively looking at the problems”
 
  • Like
Reactions: choreo
Made it almost 12 hours after the 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
lr: 0xfffffff018804860 fp: 0xffffffe015cc34f0
lr: 0xfffffff0188046bc fp: 0xffffffe015cc3560
lr: 0xfffffff01891f770 fp: 0xffffffe015cc3610
lr: 0xfffffff018dd15d8 fp: 0xffffffe015cc3620
lr: 0xfffffff018804024 fp: 0xffffffe015cc3990
lr: 0xfffffff01880437c fp: 0xffffffe015cc39e0
lr: 0xfffffff019552974 fp: 0xffffffe015cc3a00
lr: 0xfffffff018f78cec fp: 0xffffffe015cc3a30
lr: 0xfffffff018f6a11c fp: 0xffffffe015cc3aa0
lr: 0xfffffff018f6c044 fp: 0xffffffe015cc3b50
lr: 0xfffffff018f69854 fp: 0xffffffe015cc3be0
lr: 0xfffffff018f30cb8 fp: 0xffffffe015cc3c10
lr: 0xfffffff018d3eb14 fp: 0xffffffe015cc3c50
lr: 0xfffffff018d3e398 fp: 0xffffffe015cc3c90
lr: 0xfffffff018ddc514 fp: 0x0000000000000000
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.