MacBook Pro M3 crashes daily r/t LG UltraGear monitor

Kernel Panic is not ONE problem, it is one of Thousands of problems.

It is good that you found correlation to your LG displays. but not nearly sufficient. we need at least one panic report.

Kernel Panic Reports are stored in the Folder at:

/Library/Logs/DiagnosticReports

If you copy and paste that string into:

Finder > Go menu > Go to Folder

it will take you to the Folder where those reports are stored.

Kernel panic reports are named with Date&Time and start or end in ‘panic’

If you find one, please 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.

If you post your kernel panic here in its entirety, using the additional text icon in the reply footer, we do have some Readers (typically with developer background) who can attempt to interpret those panic reports. Even if no clear symptom emerges, this can still save a step if you DO need to contact Apple support later, because Apple Support specialists can read the panic reports you posted here, if you tell them what discussion or what Avatar.

...

This line gets things going:

"panicString" : "panic(cpu 0 caller 0xfffffe00214f6de8): DCPEXT1 PANIC - IOMFB int_handler_gated: failure: axi_rd_err [0x40310600]\n - iomfb_driver(10)\nIOMFB int_handler_gated: failure: axi_rd_err

DCP is display co-processor

DCPEXT1 is likely the first display interface

IOFMB is the Mobile Frame Buffer

axi_rd_err suggests stuff could not be read

so this takes the mystery out of why this only occurs with the external display is attached -- with the external display attached, some stuff becomes unreadable for more reason.

later in the report this set of messages its very concerning:

No mapping found for coredump section: 0xffffffff0014b000 - 0xffffffff0018afff\n

No mapping found for coredump section: 0xffffffff0018b000 - 0xffffffff001cafff\n

No mapping found for coredump section: 0xffffffff001cb000 - 0xffffffff001cbfff\n

No mapping found for coredump section: 0xffffffff001cc000 - 0xffffffff001ccfff\n

FOUR sections or memory have become unreadable ??

that defies explanation, unless you have some kind or really invasive third-party software installed, the stack got corrupted, or you had a RAM failure.

have you run the diagnostic? 'no faults detected during testing' answer-code is not the same as "all is well" but the diagnostic does detect GROSS failures.

¿Running any third-party Virus checkers, optimizers, Cleaners, app-removers, or a VPN?

Consider downloading and running this little "discovery" utility, Etrecheck. It changes NOTHING. Etrecheck was developed by senior contributor here, and uses system calls to collect often-needed information.

it contains little tests for speeds of devices, CPU utilization, memory usage, energy usage and a digest of recent problems, in one easy to use package. it does not even need to be Installed. Because less can be learned when your Mac is running great, best time to run is when your problems are actually occurring, if possible.

if you follow the directions faithfully, its report (pre-laundered of all personally-identifiable information) can be "Shared" to the system ClipBoard, then Pasted into an ‘Additional Text’ window in a reply on the forums.

How to use Etrecheck Pro for free

http://etrecheck.com

...

M3 plain, running MacOS 14.5

AppleT8122DPTXPort(dptx-phy)::deactivateTimeoutOccurred(0x100000386): deactivate() incomplete 10 seconds after displayRelease()!

MacOS told the display to be quiet, and it was still talking a full ten seconds later.

>> look at den.thed posting on this thread for discussion of that issue:

Mac Studio Kernel Panics every time the d… - Apple Community

.

.

iare there nay outstanding firmware updates for your display?

you have already posted the glaringly obvious work around to eliminate crashes -- disconnect the LG display forever.

Since you have continued to discuss other alternatives here, I want to make some suggestions that may be different from the way you are used to working. These are expected to lead to a more stable and productive Mac.

By far the easiest way to cause poor performance, instability, overheating and crashing is to install ANY third-party speeder-uppers, Cleaners, Optimizers, or Virus scanners, Bit Torrent, or a VPN that you installed yourself. The main reason is that they are relentless in scanning your files, non-stop, looking for virus-like patterns in Everything, or looking for files that have changed. When completed, they do it all again.

The idea that a third party, with no special knowledge of the inner workings of MacOS, can somehow find a simple way to protect or speed up your computer — that is not already being done by MacOS itself — suggests that the MacOS developers are somehow "holding out on you". That is absurd.

You should remove any and all (other than Apple built-in) virus scanners, speeder uppers, optimizers, cleaners, App deleters or VPN packages you installed yourself, or anything of that ilk.

that includes:

malwareBytes -- readers love the idea of running their scanner, ONCE, but never alway scanning

NordVPN

Little Snitch

IPnet monitor

DuckDuckGo endpoint security. I love its search engine, but there is no need for so-called protection or VPN

CrashPlan

CCleaner

if you are running Windows in that Parallels virtual machine, install whatever Virus protection you need on the WINDOWS side, Windows "stuff" cannot infect your Mac.

Every non-Apple "cloud" sync service you run all the time means you punishing performance. This is because these apps were PORTED rather than re-wriiten for the Mac. They COULD be taking advantage of the Mac File system event store, and be done checking in under a minute. Instead, they run for hours scanning all your files, and by the time they are done, it's time to do it all again.

you appear to be running :

oneDrive

Dropbox

? abobe Connect syncer ? I never seen that one

Google Keystone agent says you are still handing your private information to google to sell

I duuno what these are, but I run a very complex network and have never needed them. I bet you don't either

IPNotify

Internet Status helper

-------

NB> to remove an App installed by drag and drop to the /Applications folder, drag and drop to the Trash. After a Restart, the Trash can be emptied.

ALL OTHERS require the app-maker's Un-Installer, typically available on their web site. In some cases, Un-Install is a special case of Install, so the Installer must be downloaded again to obtain the Un_installer.

DO NOT USE A GENERIC UN-INSTALLER, EVER

I am not sure my issue is the same as yours, but I've been having an issue with my Mac Studio 2022 M1 Ultra where the Mac will randomly crash and reboot. I have 5, LG 27UN850-W monitors connected (HDMI, and USB-C to HDMI or DisplayPort). I've tried numerous cables (from different manufacturers, including those provided by LG) and cable combinations- even connecting the LG monitors directly to my Mac using a USB-C cable. Nothing seems to work. Everything will be fine for weeks, then suddenly, I get a crash or two. Then, all back to normal. The issue started when I upgraded to Sonoma. I cannot reproduce the issue with any consistency. Sometimes the crash occurs overnight when I am not using my Mac. Sometimes the issue occurs while I am using my Mac. When my Mac crashes during use, there is no consistency as to what I am doing. It could simply crash when I click on a browser window. I can really 'slam' my Mac with "processing requests," and it behaves like a champ. Then, weeks later, when I click on a different browser tab, crash, reboot. I have sent Apple Support all of the crash reports. I have opened a ticket with Apple Support. Apple Support has been unable to find a reason behind the crashes. I have found that if I use different monitors, from BenQ, I do not encounter any crashes. Since I cannot easily reproduce the issue, it could be that the monitor swap has nothing to do with nothing. But when I found your post about crashing when an LG monitor was connected to your MacBook Pro, I thought I would reply to your post in the event that this issue with LG monitors is more widespread.

Please post the entire report, and readers can scan it looking for trouble signs. if you follow the directions, no personally-identifable information will be included in the report.

Is this what you are referring to?

If you post your kernel panic here in its entirety, using the additional

text icon in the reply footer, we do have some Readers (typically with

developer background) who can attempt to interpret those panic reports.

Even if no clear symptom emerges, this can still save a step if you DO

need to contact Apple support later, because Apple Support specialists

can read the panic reports you posted here, if you tell them what

discussion or what Avatar.

Either your system is so entangled with all the 'stuff' you added, or Your boot drive is Messed Up.

Its Write speed is less than HALF its Read speed. in these Macs, the typical speeds are comparable, with most reports showing Write specs FASTER than Read (likely due to buffering)

Performance:

  System Load: 3.66 (1 min ago) 3.98 (5 min ago) 3.92 (15 min ago)

  Nominal I/O usage: 1.77 MB/s

  File system: 8.53 seconds

  Write speed: 2494 MB/s

  Read speed: 6145 MB/s

check DriveDx for excessive unresolved bad blocks, aka "pending sectors"

You did not say that, and the previous hundred users who had the problem you describe simply did not follow the directions, and attempted to post their panic report in-line.

In that case, post the first few pages using the additional text icon in the reply footer.

When you post it here, more than one set of eyes can look it over.

Support first responders are not trained to read panic reports. Did they have specialist contact you?

Genius Bar technicians are not trained to read panic reports either.

Yes, I did read your original instructions closely. As noted in my earlier post, the full kernel panic is too big for the "Additional Text." I did call "Additional Text" - "Additional Notes" in my earlier post.

I have run hardware diagnostics -> no problems found. Apple Support had me run the more "intensive" hardware diagnostics -> no problems found. Running MalwareBytes. No optimizers. Have Ccleaner installed, but I run manually. I have a VPN installed, but it is not running/active at the time of the crashes. Again, issue seems to only occur when I have LG monitors plugged in.

Thanks. I am unable to run a utility when the issue occurs as the Mac will crash/pink screen and reboot immediately. No warning. I have no way of recreating the problem. Sometimes the problem occurs when I am not using my Mac. I could run the utility after the crash occurs, but that is about all I could do. Since there are no discernible patterns to the crash issue, I also have no way of knowing when the crash will occur. The Mac could crash later today, or 3 months from now. Again, the only "solution" seems to be using non-LG monitors.