Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

tsialex

Contributor
Jun 13, 2016
13,454
13,601
My MBP 2021 14" M1 Pro is with the Monterey 12.5.1, with the latest update, and I have never encountered with a crash since I updated it a few weeks ago. I tried almost all scenarios: e.g. with and without HDMI, with and without charger cable plugged, with and without any USB C accessory plugged. In each scenario, everything went well and I had no issue so far.

I'm missing your point here, could you care to explain what you M1 MBP have to do with the late-2013 Mac Pro firmware issues?
 

GoztepeEge

macrumors 6502
Nov 21, 2015
267
185
Munich, Germany
I'm missing your point here, could you care to explain what you M1 MBP have to do with the late-2013 Mac Pro firmware issues?
I was not aware that the topic was exclusive for the Late 2013 ones.

This crash in sleep problem is a common thing among all other models including mine and yours. Hence I wanted to leave a comment so that you know.
 
  • Like
Reactions: vddobrev

steve123

macrumors 65816
Aug 26, 2007
1,155
719
I went back to Big Sur and crashed with the MCA error. I also noticed something peculiar. Before the crashing started again, I noticed that the prevent sleep setting was active. I did not change the setting and when i deactivated the setting, the crashes began. Now I would like to know if this is something Apple may have done this with the most recent firmware update? Please check your prevent sleep setting and confirm if it is unchecked.
 

arw

macrumors 65816
Aug 31, 2010
1,236
979
I went back to Big Sur and crashed with the MCA error. I also noticed something peculiar. Before the crashing started again, I noticed that the prevent sleep setting was active. I did not change the setting and when i deactivated the setting, the crashes began. Now I would like to know if this is something Apple may have done this with the most recent firmware update? Please check your prevent sleep setting and confirm if it is unchecked.
Nothing changed here. Big Sur 11.6.8 with 430.140.2.0.0 (installed 7 weeks ago right after release).
D300 & D500 machines running and sleeping perfectly fine.
 
Last edited:

symaze

macrumors newbie
May 18, 2022
5
1
Did you replaced the BR2032 RTC battery? 470.0.0.0.0 is rock solid with sleep, can't say the same with 12.6.1 RC2.
Yep, battery replaced when I did the upgrade to the 10 core CPU a few months back. The system works 100% besides the crashing at sleep. It isn't too big of a deal since I just shut it off when I'm done with it and keep sleep disabled, but I'd still love for this to be fixed someday. It could certainly just be an issue with my machine too since it seems pretty rare otherwise with other people, but who knows.
 

krakman

macrumors 6502
Dec 3, 2009
450
511
Yep, battery replaced when I did the upgrade to the 10 core CPU a few months back. The system works 100% besides the crashing at sleep. It isn't too big of a deal since I just shut it off when I'm done with it and keep sleep disabled, but I'd still love for this to be fixed someday. It could certainly just be an issue with my machine too since it seems pretty rare otherwise with other people, but who knows.
Have you tried formatting your SSD and re installing Monterey? I experienced plenty of wake from sleep problems. But one day I replaced the stock Apple SSD with an NVME drive which obviously required a format and fresh install of Monterey. Since then the trash can has been rock solid.

I then bought a PCIE card to fit the 256gb Apple ssd (which had the previous installation of Monterey on it) into my old 5.1 and I experienced wake from sleep issues! So then I formatted it and reinstalled Monterey and it works fine now.
 

tsialex

Contributor
Jun 13, 2016
13,454
13,601
Dang I thought I had this issue licked, nope still happening with a d300 with 470 fw. I’m wondering if it’s a hardware problem 🙁
If you already updated to 470.0.0.0.0 and the RTC battery voltage is good, it's much more probable that your Mac Pro have a hardware defect, no software or firmware issues reported with late-2013 Mac Pro currently.

Another thing, check your PCIe switch diode temp, if it's over 80ºC, you have a problem. Some people installed a heatsink to the PCIe switch to keep the temperatures down to around 70ºC.
 
Last edited:

MrMacintoshBlog

macrumors 6502
Sep 21, 2009
458
311
Chicago, IL
If you already updated to 470.0.0.0.0 and the RTC battery voltage is good, it's much more probable that your Mac Pro have a hardware defect, no software or firmware issues reported with late-2013 Mac Pro currently.

Another thing, check your PCIe switch diode temp, if it's over 80ºC, you have a problem. Some people installed a heatsink to the PCIe switch to keep the temperatures down to around 70ºC.
Thanks for that info! holy cow I had no clue that it takes 40 min to replace the battery 😳 Any way to check it without taking it apart?

Checked PCIe switch diode temp and it is 70C
 

tsialex

Contributor
Jun 13, 2016
13,454
13,601
Thanks for that info! holy cow I had no clue that it takes 40 min to replace the battery 😳 Any way to check it without taking it apart?

Checked PCIe switch diode temp and it is 70C
There are test points for the RTC battery on the I/O board:

Screen Shot 2022-10-29 at 22.51.45.png


Use the screw as the GND. You can download the service manual here:

 
  • Like
Reactions: MrMacintoshBlog

MrMacintoshBlog

macrumors 6502
Sep 21, 2009
458
311
Chicago, IL
There are test points for the RTC battery on the I/O board:

View attachment 2104813

Use the screw as the GND. You can download the service manual here:

You are the best! Thank you tsialex 👍

Tested 3.1v
 

mikas

macrumors 6502a
Sep 14, 2017
898
648
Finland
Unfortunately You are not alone MrMacintoshBlog.

Finally me too updated to 470.0.0.0.0 this week, and just had a crash waking from sleep.
This one is a 6-core D300 too. PCIe Switch diode at 60+. Battery newish BR2032, tested 3V+ at change, and CPU/GPU thermal pastes done by me earlier this year, in January if I recall it right.

Do we have a right to suspect the firmware again? I have yet to stress test my D500 with 470.0.0.0.0. I still have a D500 with earlier firmware too, but wouldn't have time to test them accordingly towards each other, not just now.

Bummer, to say it mildly!
 

mikas

macrumors 6502a
Sep 14, 2017
898
648
Finland
And just had a warm crash, within a few minutes from the last one.
panic(cpu 3 caller 0xffffff800f49db56): [Bank ledger]: element modified after free (off:8, val:0x0000000000000040, sz:120, ptr:0xffffff86dba4eca8, prot:zero)
8: 0x0000000000000040
16: 0x0000000000008000
Backtrace (CPU 3), Frame : Return Address
0xffffffa0f839aea0 : 0xffffff800ec8921d
0xffffffa0f839aef0 : 0xffffff800edd1bb3
0xffffffa0f839af30 : 0xffffff800edc21aa
0xffffffa0f839af80 : 0xffffff800ec2da2f
0xffffffa0f839afa0 : 0xffffff800ec88a3d
0xffffffa0f839b0c0 : 0xffffff800ec88d33
0xffffffa0f839b130 : 0xffffff800f49bb2a
0xffffffa0f839b1a0 : 0xffffff800f49db56
0xffffffa0f839b620 : 0xffffff800ece7d16
0xffffffa0f839b690 : 0xffffff800ec9a12a
0xffffffa0f839b6d0 : 0xffffff800ecffe43
0xffffffa0f839b730 : 0xffffff800ecff87d
0xffffffa0f839b770 : 0xffffff800ec77e92
0xffffffa0f839b840 : 0xffffff800ec770e3
0xffffffa0f839b8a0 : 0xffffff800ec76e5b
0xffffffa0f839b8f0 : 0xffffff800ec79213
0xffffffa0f839ba10 : 0xffffff800ec7b9fd
0xffffffa0f839ba90 : 0xffffff800ec70bfb
0xffffffa0f839baf0 : 0xffffff800f1fc881
0xffffffa0f839bc80 : 0xffffff800f1fda2c
0xffffffa0f839bd90 : 0xffffff800f1fdbe8
0xffffffa0f839bdc0 : 0xffffff8011fe7192
0xffffffa0f839be60 : 0xffffff800f1cb6ba
0xffffffa0f839beb0 : 0xffffff800f1cbf53
0xffffffa0f839bf30 : 0xffffff800f1cb284
0xffffffa0f839bf70 : 0xffffff800f1cb1e6
0xffffffa0f839bfa0 : 0xffffff800ec2d13e
Kernel Extensions in backtrace:
com.apple.kec.pthread(1.0)[88B21ABA-D3E7-3F77-B8F2-D4AE8ADF2165]@0xffffff8011fe5000->0xffffff8011fedfff

Process name corresponding to current thread: coresymbolicationd

Mac OS version:
20G918

Kernel version:
Darwin Kernel Version 20.6.0: Thu Sep 29 20:15:11 PDT 2022; root:xnu-7195.141.42~1/RELEASE_X86_64
Kernel UUID: DE0C803D-FA15-3D45-8FC0-5CBB60045DA2
KernelCache slide: 0x000000000ea00000
KernelCache base: 0xffffff800ec00000
Kernel slide: 0x000000000ea10000
Kernel text base: 0xffffff800ec10000
__HIB text base: 0xffffff800eb00000
System model name: MacPro6,1 (Mac-F60DEB81FF30ACF6)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 102182502197
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000017ca8d4b29
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x000005f293fea191 0x0000000000000000
last started kext at 61074892578: @plugin.IOAVBDiscoveryPlugin 940.4 (addr 0xffffff7fa9977000, size 32768)
loaded kexts:
>!APlatformEnabler 2.7.0d0
>AGPM 122.1
>X86PlatformShim 1.0.0
@fsplaceholder 1.14.0
@filesystems.autofs 3.0
@fileutil 20.036.15
>AudioAUUC 1.70
>!AUpstreamUserClient 3.6.8
>!AMCCSControl 1.14
@kext.AMDFramebuffer 4.0.6
@kext.AMDRadeonX4000 4.0.6
@kext.AMDRadeonServiceManager 4.0.6
>!AGraphicsDevicePolicy 6.3.6
@AGDCPluginDisplayMetrics 6.3.6
>pmtelemetry 1
|IOUserEthernet 1.0.1
>usb.!UUserHCI 1
|IO!BSerialManager 8.0.5d7
>!AHDAHardwareConfigDriver 283.15
>!AHDA 283.15
@Dont_Steal_Mac_OS_X 7.0.0
>!AHV 1
>!ADiskImages2 1
>!AFIVRDriver 4.1.0
>!A!ISlowAdaptiveClocking 4.0.0
>ACPI_SMC_PlatformPlugin 1.0.0
>eficheck 1
@kext.AMD7000!C 4.0.6
>!ALPC 3.1
>!AThunderboltIP 4.0.3
>!A!IMCEReporter 115
>!AMGPUPowerControl 6.3.6
|IO!BUSBDFU 8.0.5d7
>usb.realtek8153patcher 5.0.0
>!AFileSystemDriver 3.0.1
@filesystems.tmpfs 1
@filesystems.hfs.kext 556.100.12
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@filesystems.apfs 1677.141.3
>AirPort.BrcmNIC 1400.1.1
>!AAHCIPort 346.100.2
|!ABCM5701Ethernet 11.0.0
@private.KextAudit 1.0
>!AACPIButtons 6.1
>!ARTC 2.0
>!AACPIEC 6.1
>!AHPET 1.8
>!ASMBIOS 2.1
>!AAPIC 1.7
>!A!ICPUPowerManagementClient 222.0.0
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 311
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
>!A!ICPUPowerManagement 222.0.0
@plugin.IOAVBDiscoveryPlugin 940.4
@kext.triggers 1.0
>!AHIDKeyboard 224
>!ASMBus!C 1.0.18d1
@kext.AMDRadeonX4030HWLibs 1.0
|IOAccelerator!F2 442.9
@kext.AMDRadeonX4000HWServices 4.0.6
|IOAVB!F 940.4
|IOEthernetAVB!C 1.1.0
>DspFuncLib 283.15
@kext.OSvKernDSPLib 529
@!AGPUWrangler 6.3.6
|IOSlowAdaptiveClocking!F 1.0.0
>usb.cdc.acm 5.0.0
>usb.serial 6.0.0
|IOSerial!F 11
>IOPlatformPluginLegacy 1.0.0
>X86PlatformPlugin 1.0.0
@kext.AMDSupport 4.0.6
@!AGraphicsDeviceControl 6.3.6
>IOPlatformPlugin!F 6.0.0d8
>!AThunderboltEDMSink 5.0.3
>!UAudio 405.39
>!AHDA!C 283.15
|IOHDA!F 283.15
|IOAudio!F 300.6.1
@vecLib.kext 1.2.0
>!ASMBusPCI 1.0.14d1
>!AGraphicsControl 6.3.6
>!ABacklightExpert 1.1.0
|IONDRVSupport 585.2
|IOGraphics!F 585.2
@plugin.IOgPTPPlugin 985.2
|Broadcom!BHost!CUSBTransport 8.0.5d7
|IO!BHost!CUSBTransport 8.0.5d7
|IO!BHost!CTransport 8.0.5d7
>usb.cdc.ecm 5.0.0
>usb.IOUSBHostHIDDevice 1.2
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>usb.!UHub 1.2
>!AThunderboltPCIUpAdapter 4.1.1
>!AThunderboltDPOutAdapter 8.1.4
>!AHPM 3.4.4
>!A!ILpssI2C!C 3.0.60
>!A!ILpssI2C 3.0.60
>!A!ILpssDmac 3.0.60
>!AThunderboltDPInAdapter 8.1.4
>!AThunderboltDPAdapter!F 8.1.4
>!AThunderboltPCIDownAdapter 4.1.1
>!ABSDKextStarter 3
|IOSurface 290.8.1
@filesystems.hfs.encodings.kext 1
>!AXsanScheme 3
>!AThunderboltNHI 7.2.8
|IOThunderbolt!F 9.3.2
>usb.!UHostPacketFilter 1.0
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
|IONVMe!F 2.1.0
|IO80211!F 1200.12.2b1
|IOSkywalk!F 1
>corecapture 1.0.4
|IOUSB!F 900.4.2
|IOAHCI!F 294.100.1
>mDNSOffloadUserClient 1.0.1b8
>usb.!UEHCIPCI 1.2
>usb.!UEHCI 1.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$!AImage4 3.0.0
|IOTimeSync!F 985.2
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 8.0.5d7
|IOReport!F 47
|IO!BPacketLogger 8.0.5d7
$quarantine 4
$sandbox 300.0
@Kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 511.141.1
|IOUSBMass!SDriver 184.140.2
|IOSCSIBlockCommandsDevice 436.140.1
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 436.140.1
>!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 11.1
@kec.Libm 1
It's not the watchdog this time, which did appear mostly in the logs before. Do not know if that's indicative of anything though.

edit. and almost a week later, no crashes in between. phew. don't know what it was exactly.
 
Last edited:

chkwong

macrumors regular
Jan 17, 2020
101
34
Did you replaced the BR2032 RTC battery? 470.0.0.0.0 is rock solid with sleep, can't say the same with 12.6.1 RC2.
I also have sleep crash for my Mac Pro 2013, is the battery one of the case of the sleep crash?
 

vddobrev

macrumors 6502a
Original poster
Oct 28, 2016
962
833
Haskovo, Bulgaria
I also have sleep crash for my Mac Pro 2013, is the battery one of the case of the sleep crash?
Possibly, but if the battery was really low, then it will not boot at all. You can easily check it if you have a meter, there is a check point close to the one of the RAM banks.
 

chkwong

macrumors regular
Jan 17, 2020
101
34
Possibly, but if the battery was really low, then it will not boot at all. You can easily check it if you have a meter, there is a check point close to the one of the RAM banks.
Thanks for info
It can boot normally. But when I put it to sleep, it could not be waked up, only black screen.
 

MrMacintoshBlog

macrumors 6502
Sep 21, 2009
458
311
Chicago, IL
Interesting that a few are starting to report sleep wake crashes again. Seems like it could be hardware, it would be hard to believe it could be software related again?
 

tsialex

Contributor
Jun 13, 2016
13,454
13,601
Interesting that a few are starting to report sleep wake crashes again. Seems like it could be hardware, it would be hard to believe it could be software related again?
When it was a firmware related issue, everyone was reporting about the crashes when waking from sleep right off the bat. Another thing, late-2013 Mac Pros are definitively not as reliable as MacPro5,1 or MacPro7,1, there is always someone reporting crashes, so you have to evaluate the reports.

Hardware failures early on with D500 models dying like flies made Apple to do a recall, later we had D300 GPU drivers always crashing with Catalina/BigSur. There is also the PCIe switch overheating for some and the RTC battery that everyone will need to replace sometime in the near future, a non trivial procedure.
 

MrMacintoshBlog

macrumors 6502
Sep 21, 2009
458
311
Chicago, IL
When it was a firmware related issue, everyone was reporting about the crashes when waking from sleep right off the bat. Another thing, late-2013 Mac Pros are definitively not as reliable as MacPro5,1 or MacPro7,1, there is always someone reporting crashes, so you have to evaluate the reports.

Hardware failures early on with D500 models dying like flies made Apple to do a recall, later we had D300 GPU drivers always crashing with Catalina/BigSur. There is also the PCIe switch overheating for some and the RTC battery that everyone will need to replace sometime in the near future, a non trivial procedure.
Thank you again for this info, I'm so used to the 5,1 and below being very reliable. The 6,1 is a whole new beast to me.

I'm wondering if I am narrowing in on my issue. I mentioned above that memory is not being recognized in slot 1 and 2. Now I just found out that my d300 slot 1 GPU (slot 2 is showing fine) is not show up in system report. I'm wondering if the riser card is going bad. Does reseating the board ever fix issues?
 
Last edited:

Natalia22

macrumors member
Nov 12, 2022
42
83
Good day, friends!
About three years ago this problem appeared, called up the technical support service, but they can not help.
Since then I have become a grateful reader of the forum.
I got this issue again after upgrading to 12.6.1. Crashes in Sleep were repeated 3-5 times a day.
Yesterday I reinstalled version 12.6, while the computer works for a day without failures.

Upd: a week later... the crashes in sleep are repeated.
_____

Mac Pro 2013 6.1, D700, 12-core, 64gb
 
Last edited:

tsialex

Contributor
Jun 13, 2016
13,454
13,601
Thank you again for this info, I'm so used to the 5,1 and below being very reliable. The 6,1 is a whole new beast to me.

I'm wondering if I am narrowing in on my issue. I mentioned above that memory is not being recognized in slot 1 and 2. Now I just found out that my d300 slot 1 GPU (slot 2 is showing fine) is not show up in system report. I'm wondering if the riser card is going bad. Does reseating the board ever fix issues?

You can try to clean it with some appropriated non-oily contact cleaner, like DeOxit. A lot of times is just oxidation and it's worth to try.

Btw, it's probably cheaper to get a working decommissioned late-2013 Mac Pro to use it to diagnose your defective Mac Pro parts then to buy any parts that you suspect that went defective. You probably can buy a whole working D300 model just for the price of one GPU.
 

ahonciano

macrumors newbie
Jan 27, 2015
10
5
Hello all, just chiming in on this thread as I too have a Mac Pro Late 2013 model. I upgraded the RAM and SSD to 1TB and 128GB back in February running Monterey. Everything was just fine until I was asked to update to 12.6.1 and in addition to the crash after sleep, I had this issue with my keyboard.

The UI was accessible via mouse, but wouldn't let the keyboard be used. To better understand this, I was able to type my password at login, but as soon as I reached my desktop, the keyboard inaccessible. The only work around was to log into my 2nd account, and user switch back to the primary one. I couldn't find the culprit.

I noticed the mac would reboot on its own while sleeping after about 30min, and this only happened after updating to 12.6.1. To fix all issues, I decided to erase and Internet Recover/Install Mac OS Monterey. DIdn't solve the sleep issues, but everything else worked fine.

I've downloaded 12.5.1 to see if I experience the same issue. Nothing in the crash log said a kernel error, just outputted my CPU's and devices plugged in. I even tried sleeping with EVERYTHING disconnected from USB and monitor, no luck.
 

wmosx

macrumors newbie
Dec 26, 2020
8
2
Good day, friends!
About three years ago this problem appeared, called up the technical support service, but they can not help.
Since then I have become a grateful reader of the forum.
I got this issue again after upgrading to 12.6.1. Crashes in Sleep were repeated 3-5 times a day.
Yesterday I reinstalled version 12.6, while the computer works for a day without failures.

Upd: a week later... the crashes in sleep are repeated.
_____

Mac Pro 2013 6.1, D700, 12-core, 64gb
Good Day Natalia,

Can you advise on where to obtain v 12.6 as I also am having this issue on my 12 Core D700 MacPro after updating to 12.6.1

Thank you,
Will
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.