@scarvalhojr On catalina your kernel panic will be a little bit different. I've had this issue on Catalina and opened a case about it with Apple support. The issue was then fixed with Big Sur. Only to reappear in a different way (different kernel panic) with 11.3. See also this reddit post where someone found this kernel panic during beta testing: https://www.reddit.com/r/MacOSBeta/comments/mpcd54/macos_11_113_beta_7/ The Catalina kernel panic was: panic(cpu 6 caller 0xffffff801cb27998): "kfree: size 4539647261356396544 > kalloc_largest_allocated 16302080"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.141.1/osfmk/kern/kalloc.c:868 B

@klemensz yeah, the support engineer assigned to my case also claims it not on their end. But my 15" MacBook with the same macOS version works just fine. And I can even trigger the issue from Safe mode, so no local modifications possible (it's a bit harder to trigger from safe mode, it happens less frequently then when the os is actually running with software). The reason I frequently ran into this issue is that I had my audio connected via displayPort and the audio does not work after waking from sleep. I just connected the audio directly in the MacBook and now I no longer have to turn my displays off an on again to regain my audio, so no more crashes. For me it doesn't crash after waking from sleep.

@scarvalhojr I’ve tested this issue with a different model 2019 16” macbook pro. The cheaper model without the AMD Radeon Pro 5500M in it. I was not able to crash that one. Those laptops you had this issue with, did they have the extra video card option as well?

@kinovoki for me it started with 11.3 and Reddit agrees(https://www.reddit.com/r/MacOSBeta/comments/mpcd54/macos_11_113_beta_7/) someone found it with the first beta of 11.3. Somewhere in this thread people claim one of the fixes is to install 11.2.3 but since that has serious security issues I would strongly suggest not to do that. @who842 I can crash it with just an USB-C to DisplayPort cable. I’m quite sure you are experiencing a different issue

@scarvalhojr yes, only with DP it crashes. and the crash only happens after the display first has the “sleep problem”: the display is detected but does not get a signal from the laptop (you can see the display in the displays setting). after that, turning it off and on again results in the crash. but you seem to be right, all have a AMD. So I’m lost why the 2019 model at the support center didn’t crash :( Then perhaps it’s related to the upgrade 5500M, and not the base model 5300M. At least, I have the 5500M, the center had the cheapest macs so the 5300M, of the 5600M I don’t know if that one is also affected since that’s also an option according to https://support.apple.com/kb/SP809?locale=en_US

@scarvalhojr my test in the support center was with my dell monitor, I brought it with me. i saw the same “sleep” issue with that macbook, but it always crashes when that happens on my mac, even in recovery mode, but it didn’t crash their mac. I was sure I would crash their mac as well… so then I thought, what else is different. must be the videocard. with all replies in here so far I’m getting more confident that it’s related to the 5500M.

Been to the Apple Store today. Unfortunately no 5500M equipped MacBook available, even though I explicitly asked for that by phone before going there. Also tried the LG monitor they had in store. Was not able to even get the "sleep" issue with that one, not on USB-C nor on DisplayPort. So it seems to be the combination of the dell monitor and the 5500M. Apple Support should call me back tomorrow again. Not sure if the people with docks that experience this issue are also using dell monitors.

@zskii that's disappointing :( I hoped to get 0 replies about the 5300M. This because I couldn't crash a system with this video card in it. Are you sure you are getting exactly the same kernel panic? This part seems to be the same for all, including the same off: value of 1672.  [kext.kalloc.2048]: element modified after free (off:1672,

Installing 12 Beta 2 now, will install 11.5 beta 3 on different partition after that

11.5 Beta 3 is still affected: panic(cpu 0 caller 0xffffff8013e98a66): [kext.kalloc.2048]: element modified after free (off:1672, val:0xfffffffe00000000, sz:2048, ptr:0xffffff93880aa800, prot:zero) Mac OS version: 20G5042c

So far indeed unable to crash Monterey beta 2. I've been able to loose display to one of the 2 external displays, turning it off and on again doesn't restore it in macOS, so guess I'll need to reboot to get that one to work again (disconnecting dock and reconnecting was enough to restore it). While turning displays off and on, my MacBook screen behaves weird. It seems to turn off and on again multiple times. And my mouse cursor is very unresponsive while this is happening. But at least no more crashes.

With HDMI as well? What's the reproduction path then? I was not able to reproduce the issue with HDMI :( But that's because my reproduction path is: turn off display, turn it on again, see if it's not getting a signal from the Mac, if that's the case: turn it off and on again: success (a crash)! With HDMI turning a display off doesn't send a signal to macOS, so the trigger for the error is not there.

Your crash looks a little different. [kext.kalloc.2048]: element modified after free (off:1672, vs [data.kalloc.4096]: element modified after free (off:1184, So I'm not sure if you are experiencing the same issue.

Interesting, your off value is different then what most of the people in this thread seem to have. You have off 1584, while most have off: 1672. Not sure what this difference means though :(

Still crashes :(