MacBook Pro stuck at login bar before reboot after 14.7.2 update

dust does not cause the reported slowness and does not cause crashing.

But on closer examination, even though your etrecheck report in Safe mode is inadequate for most purposes, there is this:

    disk3 - SanDisk G-DRIVE SSD 55B7 2.00 TB (Solid State - TRIM: No)

you need to have TRIM enabled for third party drives. The way to do this is to run this Terminal command:

sudo trimforce enable

enter your admin password, wcich will not be echoed, and it will read you the Riot Act about Apple is not responsible for data loss, yada, yada.

Say yes and it will change the setting and do an Auto-restart to engage.

--------

your backups on disk show as last completed on 1-13, and 21 local snapshot have been collected, clogging up the boot drive:

Backup:

Destinations:

T*********e [Local] (Last used)

Total size: 1.50 TB

Total number of backups: 94

Oldest backup: 2024-03-08 15:24:59

Last backup: 2025-01-13 04:59:30

21 local snapshots

Oldest local snapshot: 2025-01-12 09:50:13

Last local snapshot: 2025-01-13 09:37:26

tasks running (and have been crashing) include spotlight, used to collect metadata for backups, and mdworker responsible for backups.

connect your drive and let time machine run so it can remove the snapshots on your drive.

then please post a new Etrecheck report.

MauWoW wrote:

Last week I did an update to 14.7.2. Been hesitant to do updates since the update to 14.6 crashed the system. I reinstalled to 14.7, I believe. Curiously I did the update and the system was powered off this morning. When I logged in the login bar gets to about 1/4 solid before the ramped fan kicks on and the boot screen said there was an issue. I have not installed anything new. After the update the system fan was constantly running which I wasn't before. This is know because the fan can be heard on meetings and the boss is a huge stickler for non meeting sounds.

I have had the system checked out with not physical problems. I have ran EtreCheck this morning. Is there anything I should remove, temp files before rebooting out of safe mode?

<EtreCheck 2025-01-13.log>

< MacBook Pro (16-inch, 2019) >

< Kernel Panic (24 times) >

sounds like hardware...

Kernel Panics are predominately caused by hardware faults or faulty third-party kernel extensions.

Learn what to do if your computer restarts or shuts down unexpectedly, or you get a message that your computer restarted or shut down because of a problem.

If your Mac restarted because of a problem - Apple Support

In or out of warranty you can get a free over the counter 'Apple Service Diagnostics' test /assessment

Make an appointment for a "hardware issue"

Genius Bar Reservation and Apple Support Options - Apple

Outside the USA

Contact Apple for support and service - Apple Support

There MIGHT be some insights in an individual kernel 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 as much as you can here, by using the “additional text” Icon in the reply footer (looks like a paper with writing). (Once the report devolves into incessant software-names or incessant Base-64 dumps with lots of AAAAAA lines, you are done.)

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.

Classic Debugging steps:

Make certain you have applied all available software updates, because no one is willing to debug a problem that might have been seen and solved already.

Then you need to go through the 'regular" steps to eliminate added software as the cause of the problem:

• Run In Safe Mode, where no third-party add-ons are loaded

• create a new "clean" User account, and run with that to eliminate contamination in your regular User account

• run the diagnostic to check for GROSS issues. "no fault found" is not the same as "all is well".

If you are seeing kernel panics, post a panic report. Some panic-reasons suggest a Hardware issue. There is a procedure that can allow you to find those reports to post one. Ask for assistance if you need it.

if you take it to an Apple service provider first, they CAN run their diagnostics, which are a bit more comprehensive that the User diagnostics. In the very small amount of time they are run, “No faults detected” still does not mean “All is Well” but at least there are no detected GROSS problems. Unless they can find a fault, they will return your computer unchanged.

Genius Bar technicians are NOT trained to read panic reports and computer logs. When you present your computer at the Genius Bar with the expectation of a quote to repair it, you must generally meet these criteria:

• your Mac won't do anything

• your Mac fails diagnostics

• your Mac has a problem you can repeatably demonstrate on demand

one other oddball case:

• Apple online support has DIRECTED a Service Provider to replace specific components inside your Mac, such as the mainboard or display. Bring proof, such as case number.

The telephone support people are more likely to work with you. They will insist that you go through the motions to eliminate software issues. But when they get to the end of their list, you should insist on having your problem escalated to a specialist. Specialists are more likely to actually read your panic reports, and to agree this is a problem and DIRECT an Apple service provider to swap things (likely mainboard) for a new one.

You MUST have a Trusted backup before submitting your Mac for service. if the mainboard is swapped out, the boot drive will be swapped out as well, and you will not get your files back.

MauWoW wrote:

I have had the system checked out with not physical problems.

system checked out how?

the user Diagnostic...not as definitive as Apple's own AST2 (Apple Service Toolkit) back bench diagnostic

I would certain be testing without the plethora of accessories connected...

<< but Apple is saying the hardware is reading good. >>

you seem to have a WILDY optimistic view of 'diagnostics did not find anything' message.

That should read:

(In the minuscule amount of time allotted, using the very limited tests we have, during the exact time we were running them ...)

...No faults were DETECTED.

(...that does NOT mean none are present.)

all you can say in response to a passed diagnostic is that no GROSS faults were found.

This is NOT the same as "All is well".

"panicString" : "panic(cpu 0 caller 0xfffffff01bf09fe0): macOS panic detected\nDebugger message: panic

that one has no deep insights that I can decode.