Irregular freezes MacBook Pro

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.

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.

Start by uninstalling "Techtool Pro" and "disk doctor". Rule 1 of Macs is don't install junk.

Is there anyway to analyse such reports to find a possible cause for these freezes?

You can post it here. Crash reports don't often reveal an obvious cause, but sometimes they do. Use the "Additional text" icon:

<< I will contact an Apple repairservice about this. >>

Wait. To avoid massive frustration, Read this first:

General debugging tips:

Make certain you have applied all available software updates, because no one wants 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".

Use Apple Diagnostics to test your Mac - Apple Support

Use Apple Diagnostics to test your Mac - Apple Support

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.

Telephone Support:

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, Do NOT allow them to tell your it’s fine or there is nothing more they can do for you!

You should insist on having your problem escalated to a specialist. Specialists are more likely to actually read your panic other reports. If still no resolution, ask them to start a formal, tracked Bug Report on your behalf. If they think this might be a Hardware problem they can DIRECT an Apple service provider to swap things (likely mainboard) for a new one.

Apple support does appreciate what we do as Volunteers here on the forums. They can and should read what has already been posted. Be sure to tell them where they can read it. But they do NOT take our conclusions at face value -- they have their own more rigorous procedures they follow.

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.

Genius Bar:

if you take it to an Apple service provider first, they CAN run their diagnostics, which are a bit more comprehensive than 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 KP report. The one you posted suggests a hardware fault endemic to the T2 chip that only Apple can fix.

Official Apple Support

Try disabling any background processes from the Microsoft Corporation, under "General" -> "Log In & Extensions". That's what fixed the panic freezes and crashes for me, immediately. My computer would crash up to 12 times a day, no kidding. I posted my answer today.

<< "macOSPanicString" : "panic(cpu 8 caller 0xffffff80062b089b): userspace watchdog timeout: no successful checkins from logd >>

Logd is the always-running daemon that maintains order and launches anything else that needs to get launched. It has stopped responding, but has not died.

I think this confirms what John Galt has asserted, that there is a T2 chip communication problem. There are no simple user fixes for that.

King Sardius wrote:

Try disabling any background processes from the Microsoft Corporation, under "General" -> "Log In & Extensions". That's what fixed the panic freezes and crashes for me, immediately. My computer would crash up to 12 times a day, no kidding. I posted my answer today.

This one?

MacBook Pro 13" i7 Crashed Constantly; I FOUND THE ANSWER - Apple Community

While I sincerely appreciate posting your solution, and I agree that Microsoft products tend to be inefficient and their UI often runs counter to Apple's developer guidelines, I think there may be more to your story.

I'm happy it worked for you, but the solution is probably not as simple as you describe. I suspect you ameliorated a symptom but the underlying cause remains undiagnosed.

Besides, the OP's Mac is suffering from a hardware problem that Microsoft cannot possibly have caused no matter how hard it tries. It may not even have any MSFT products installed. We don't know, but it's irrelevant.

I suggest you return to that Discussion and provide the additional information its other participants asked for.