User profile for user: leisa198
leisa198 Author
User level: Level 1
4 points

How do you troubleshoot the panic system crash?

Log file attached

"files_to_attach":["\/Library\/Logs\/DiagnosticReports\/ProxiedDevice-Bridge\/panic-full-2025-03-02-122435.0003.ips"],"component_id":"923030","log_path":"\/Library\/Logs\/DiagnosticReports\/ProxiedDevice-Bridge\/panic-full-2025-03-02-122435.0003.ips","panic_string":"panic(cpu 2 caller 0xffffff801966389b): userspace watchdog timeout: no successful checkins from remoted (2 induced crashes) in 4531 seconds\nremoted returned not alive with context : is_alive_func returned unhealthy : heartbeat failed (code: 0x5\nservice: logd, total successful checkins in 36319 seconds: 1038, last successful checkin: 0 seconds ago\nservice: WindowServer, total successful checkins in 36284 seconds: 1034, last successful checkin: 0 seconds ago\nservice: remoted (2 induced crashes), total successful checkins in 36319 seconds: 990, last successful checkin: 4531 seconds ago\nservice: opendirectoryd, total successful checkins in 36319 seconds: 1038, last successful checkin: 0 seconds ago\nservice: configd, total successful checkins in 36319 seconds: 1038, last successful checkin: 0 seconds ago\n\nPanicked task 0xffffff90b25bb2e8: 3 threads: pid 128: watchdogd\nBacktrace (CPU 2), panicked thread: 0xffffff958025f0e0, Frame : Return Address\n0xfffffff42131f500 : 0xffffff80167e8351 \n0xfffffff42131f550 : 0xffffff801695622c \n0xfffffff42131f590 : 0xffffff8016945af3 \n0xfffffff42131f660 : 0xffffff801677d971 \n0xfffffff42131f680 : 0xffffff80167e8647 \n0xfffffff42131f780 : 0xffffff80167e7ce2 \n0xfffffff42131f7f0 : 0xffffff8016fd21a7 \n0xfffffff42131f8e0 : 0xffffff801966389b \n0xfffffff42131f8f0 : 0xffffff8019663356 \n0xfffffff42131f910 : 0xffffff8019662421 \n0xfffffff42131fa40 : 0xffffff8016f39716 \n0xfffffff42131fa70 : 0xffffff8016f39a8d \n0xfffffff42131fbe0 : 0xffffff80168fd01f \n0xfffffff42131fd00 : 0xffffff80167c54d0 \n0xfffffff42131fda0 : 0xffffff80167d8a45 \n0xfffffff42131fdf0 : 0xffffff80167d9134 \n0xfffffff42131fee0 : 0xffffff801692a3aa \n0xfffffff42131ffa0 : 0xffffff801677ddd6 \n Kernel Extensions in backtrace:\n com.apple.driver.watchdog(1.0)[5610F54C-E9E6-31D7-9E4E-B3663B860017]@0xffffff8019661000->0xffffff8019663fff\n\nProcess name corresponding to current thread (0xffffff958025f0e0): watchdogd\n\nMac OS version:\n24D70\n\nKernel version:\nDarwin Kernel Version 24.3.0: Thu Jan 2 20:22:00 PST 2025; root:xnu-11215.81.4~3\/RELEASE_X86_64\nKernel UUID: 0FA106B0-CE42-3EF5-98D6-610845FB1DE7\nroots installed: 0\nKernelCache slide: 0x0000000016400000\nKernelCache base: 0xffffff8016600000\nKernel slide: 0x00000000164e4000\nKernel text base: 0xffffff80166e4000\n__HIB text base: 0xffffff8016500000\nSystem model name: MacBookPro16,1 (Mac-E1008331FDC96864)\nSystem shutdown begun: NO\nHibernation exit count: 0\n\nSystem uptime in nanoseconds: 36319751648919\nLast Sleep: absolute base_tsc base_nano\n Uptime : 0x0000210859e544f7\n Sleep : 0x0000210442949591 0x0000afe8e90598b4 0x000020f81bda3ea4\n Wake : 0x0000210477aa1c48 0x0000b05fef859040 0x00002104569a825c\nCompressor Info: 3% of compressed pages limit (OK) and 8% of segments limit (OK) with 1 swapfiles and OK swap space\nZone info:\n Zone map: 0xffffff80b20bf000 - 0xffffffa0b20bf000\n . PGZ : 0xffffff80b20bf000 - 0xffffff80b40c0000\n . VM : 0xffffff80b40c0000 - 0xffffff85808bf000\n . RO : 0xffffff85808bf000 - 0xffffff871a0bf000\n . GEN0 : 0xffffff871a0bf000 - 0xffffff8be68bf000\n . GEN1 : 0xffffff8be68bf000 - 0xffffff90b30bf000\n . GEN2 : 0xffffff90b30bf000 - 0xffffff957f8bf000\n . GEN3 : 0xffffff957f8bf000 - 0xffffff9a4c0bf000\n . DATA : 0xffffff9a4c0bf000 - 0xffffffa0b20bf000\n Metadata: 0xffffff80639b8000 - 0xffffff80839b8000\n Bitmaps : 0xffffff80839b8000 - 0xffffff80869b8000\n Extra : 0 - 0\n\nlast started kext at 16880369802: >AudioAUUC\t1.70 (addr 0xffffff7fab80f000, size 12288)\nloaded kexts:\n>AudioAUUC\t1.70\n>!AHIDALSService\t1\n>!ATopCaseHIDEventDriver\t8420.1\n>AGPM\t137\n>!APlatformEnabler\t2.7.0d0\n>X86PlatformShim\t1.0.0\n@UVCService\t1\n@filesystems.autofs\t3.0\n>!AUpstreamUserClient\t3.6.12\n@kext.AMDRadeonX6000\t6.0.1\n@kext.AMDRadeonServiceManager\t6.0.1\n>!AGFXHDA\t400.1\n>!A!IKBLGraphics\t23.0.0\n>!AGraphicsDevicePolicy\t8.1.10\n>!ABridgeAudio!C\t530.2\n@AGDCPluginDisplayMetrics\t8.1.10\n>!AMuxControl2\t8.1.10\n>pmtelemetry\t1\n@filesystems.nfs\t1\n|IOUserEthernet\t1.0.1\n>usb.!UUserHCI\t1\n>!ARXE\t1.0\n>!AHV\t1\n>AGDCBacklightControl\t8.1.10\n>!A!IPCHPMC\t2.0.1\n>!A!ICFLGraphicsFramebuffer\t23.0.0\n>!AFIVRDriver\t4.1.0\n>!A!ISlowAdaptiveClocking\t4.0.0\n>!ABacklight\t180.11\n>!AThunderboltNHISpeedTest\t0.0.1\n>!AThunderboltIP\t4.0.3\n>BridgeAudioCommunication\t530.2\n>!AAVEBridge\t6.1\n>ACPI_SMC_PlatformPlugin\t1.0.0\n>!AMCCSControl\t1.17\n>usb.!UHostBillboardDevice\t1.0\n>BCMWLANFirmware4388.Hashstore\t1\n>BCMWLANFirmware4387.Hashstore\t1\n>BCMWLANFirmware4378.Hashstore\t1\n>BCMWLANFirmware4377.Hashstore\t1\n>BCMWLANFirmware4364.Hashstore\t1\n>!AFileSystemDriver\t3.0.1\n@filesystems.tmpfs\t1\n@filesystems.lifs\t1\n@filesystems.hfs.kext\t677.81.4\n@BootCache\t40\n@!AFSCompression.!AFSCompressionTypeZlib\t1.0.0\n@!AFSCompression.!AFSCompressionTypeDataless\t1.0.0d1\n@filesystems.apfs\t2317.81.2\n>!ABCMWLANBusInterfacePCIeMac\t1\n@private.KextAudit\t1.0\n>!ASmartBatteryManager\t161.0.0\n>!AACPIButtons\t6.1\n>!ASMBIOS\t2.1\n>!AACPIEC\t6.1\n>!AAPIC\t1.7\n@!ASystemPolicy\t2.0.0\n@nke.applicationfirewall\t406\n|IOKitRegistryCompatibility\t1\n|EndpointSecurity\t1\n@Dont_Steal_Mac_OS_X\t7.0.0\n>!ADiskImages2\t379.60.1\n@kec.!AEncryptedArchive\t1\n>!AHIDKeyboard\t8010.1\n>!AHS!BDriver\t8420.1\n>IO!BHIDDriver\t9.0.0\n>!AActuatorDriver\t8420.1\n>!AMultitouchDriver\t8420.1\n>!AInputDeviceSupport\t8000.26\n@kext.AMDRadeonX6100HWLibs\t1.0\n@kext.AMDRadeonX6000HWServices\t6.0.1\n>!ASMBusPCI\t1.0.14d1\n>!UAudio\t720.24\n>!AAudioClockLibs\t420.3\n>!A!ILpssUARTv1\t3.0.60\n>!A!ILpssUARTCommon\t3.0.60\n>!AOnboardSerial\t1.0\n>!AHDA!C\t600.2\n|IOHDA!F\t600.2\n|IOAudio!F\t600.2\n@vecLib.kext\t1.2.0\n>!AGraphicsControl\t8.1.10\n@kext.triggers\t1.0\n>IOHIDPowerSource\t1\n>!ACallbackPowerSource\t1\n|IOAVB!F\t1320.3\n>!AUIO\t1\n|IORDMA!F\t1.0\n>!ARSMChannel\t1\n|IORSM!F\t1\n>!AIPAppender\t1.0\n@kext.AMDRadeonX6000Framebuffer\t6.0.1\n@kext.AMDSupport\t6.0.1\n|IOAccelerator!F2\t485\n@plugin.IOgPTPPlugin\t1330.2\n@!AGPUWrangler\t8.1.10\n@!AGraphicsDeviceControl\t8.1.10\n|IOSlowAdaptiveClocking!F\t1.0.0\n>driverkit.serial\t6.0.0\n>!ABacklightExpert\t180.11\n|IONDRVSupport\t598\n>!AThunderboltEDMSink\t5.0.3\n>!AThunderboltDPOutAdapter\t8.5.1\n>IOPlatformPluginLegacy\t1.0.0\n>X86PlatformPlugin\t1.0.0\n>IOPlatformPlugin!F\t6.0.0d8\n|IOGraphics!F\t598\n>!ASMBus!C\t1.0.18d1\n>usb.IOUSBHostHIDDevice\t1.2\n>usb.cdc.ecm\t5.0.0\n>usb.cdc.ncm\t5.0.0\n>usb.cdc\t5.0.0\n>usb.networking\t5.0.0\n>usb.!UHostCompositeDevice\t1.2\n>!AThunderboltPCIDownAdapter\t4.1.1\n>!AThunderboltDPInAdapter\t8.5.1\n>!AThunderboltDPAdapter!F\t8.5.1\n>!AHPM\t3.4.4\n>!A!ILpssI2C!C\t3.0.60\n>!A!ILpssI2C\t3.0.60\n>!A!ILpssDmac\t3.0.60\n>!ABSDKextStarter\t3\n|IOSurface\t372.3.5\n@filesystems.hfs.encodings.kext\t1\n>!ASyntheticGame!C\t12.3.1\n>!AXsanScheme\t3\n>!AThunderboltNHI\t7.2.81\n|IOThunderbolt!F\t9.3.3\n>!ABCMWLANCoreMac\t1.0.0\n|IO80211!F\t1200.13.1\n>IOImageLoader\t1.0.0\n>!AOLYHALMac\t1\n|IOSerial!F\t11\n>corecapture\t1.0.4\n>usb.!UVHCIBCE\t1.2\n>usb.!UVHCICommonBCE\t1.0\n>usb.!UVHCI\t1.2\n>usb.!UVHCICommon\t1.0\n>!AEffaceableNOR\t1.0\n|IONVMe!F\t2.1.0\n|IOBufferCopy!C\t1.1.0\n|IOBufferCopyEngine!F\t1\n>usb.!UHostPacketFilter\t1.0\n|IOUSB!F\t900.4.2\n>usb.!UXHCIPCI\t1.2\n>usb.!UXHCI\t1.2\n>!AEFINVRAM\t2.1\n>!AEFIRuntime\t2.1\n>!ASMCRTC\t1.0\n|IOSMBus!F\t1.1\n|IOHID!F\t2.0.0\n|IOTimeSync!F\t1330.2\n|IOSkywalk!F\t1.0\n>mDNSOffloadUserClient\t1.0.1b8\n|IONetworking!F\t3.4\n>DiskImages\t493.0.0\n|IO!B!F\t9.0.0\n|IOReport!F\t47\n$quarantine\t4\n$sandbox\t300.0\n@kext.!AMatch\t1.0.0d1\n>!ASSE\t1.0\n>!ALockdownMode\t1\n>!AKeyStore\t2\n>!UTDM\t556\n|IOUSBMass!SDriver\t250.60.2\n|IOUSBHost!F\t1.2\n>!UHostMergeProperties\t1.2\n>usb.!UCommon\t1.0\n>!ABusPower!C\t1.0\n|IOSCSIBlockCommandsDevice\t500\n|IOSCSIArchitectureModel!F\t500\n>!AFDEKeyStore\t28.30\n>!AEffaceable!S\t1.0\n|IO!S!F\t2.1\n>!ACyrus\t1\n>!AMobileFileIntegrity\t1.0.5\n$!AImage4\t7.0.0\n@kext.CoreTrust\t1\n>!ACredentialManager\t1.0\n|CoreAnalytics!F\t1\n>!ASEPManager\t1.0.1\n>IOSlaveProcessor\t1\n>!AACPIPlatform\t6.1\n>!ASMC\t3.1.9\n|IOPCI!F\t2.9\n|IOACPI!F\t1.4\n>watchdog\t1\n@kec.pthread\t1\n@kec.XrtHostedXnu\t1\n@kec.Libm\t1\n@kec.Compression\t1.0\n@kec.corecrypto\t14.0\n"}


MacBook Pro 16″, macOS 15.3

Posted on Mar 2, 2025 8:23 AM

Reply
7 replies
Sort By: 
User profile for user: Mac Jim ID
Mac Jim ID
User level: Level 8
36,881 points

Mar 2, 2025 8:37 AM in response to leisa198

The best way to tell what is going on with your computer is by posting the free EtreCheck report using the Additional Text option when posting. The report contains no personal information, but provides much more detail on the third party apps that may be causing a conflict along with reports of other crashes that may be useful in determining the cause. Most of the time a Panic will be due to third party add ons launching on startup causing a conflict, but it could be hardware related as well.

How to use the Add Text Feature When Post… - Apple Community


The types of apps that have been seen to cause a conflict with the OS are:

  • Cleaners
  • Optimizers
  • AntiVirus
  • VPN's
Reply
User profile for user: Grant Bennet-Alder
Grant Bennet-Alder
User level: Level 10
135,349 points

Mar 2, 2025 9:25 AM in response to leisa198

<< "panic_string":"panic(cpu 2 caller 0xffffff801966389b): userspace watchdog timeout: no successful checkins from remoted (2 induced crashes). >>


Says remoted daemon wandered off, and did not report in for a very long time. The watchdog timer set to ensure remoted is still running well and is checking in from time-to-time fired.


remoted is a daemon (always running in the background) that discovers remote devices and services.


seeing it become lost is deeply problematic, and an Etrecheck report might turn up WHY.

Reply
User profile for user: g_wolfman
g_wolfman
User level: Level 4
2,722 points

Mar 2, 2025 11:18 AM in response to Grant Bennet-Alder

ProxiedDevice-Bridge panics usually involve the logic board and/or T2 chip (or at least the comms bus it sits on). The last loaded kext was AudioAAUC.


My first guess would be that remoted locked up trying to communicate with something on one of the USB buses, which of course eventually led the watchdog process to panic after remoted was unresponsive for too long.

Reply
User profile for user: Grant Bennet-Alder
Grant Bennet-Alder
User level: Level 10
135,349 points

Mar 2, 2025 7:55 PM in response to g_wolfman

Thanks for that great insight.


I made the mistake of reading what was showing through the additional text window, and missed that the lines were actually truncated to fit. There was a width slider as well. If i had looked harder, I might have seen that important information.


I am not sure I know enough about it to make the good recommendations you did, but now I know to check that I got the full width of the information available.

Reply
User profile for user: g_wolfman
g_wolfman
User level: Level 4
2,722 points

Mar 3, 2025 4:24 PM in response to Grant Bennet-Alder

Oh, I think everything you said was true and correct.


I made some logical inferences based on my reading of the same info (plus the last loaded kext, which is often the one that panics)...but hey, I could be totally wrong. And even if I'm right, "one of the USB buses" could be the internal bus - which is just a nuanced way of saying "logic board failure".


I'm hoping that it turns out to be a USB connected external audio device...but no way to know unless the OP comes back.

Reply
User profile for user: HWTech
HWTech
User level: Level 9
63,176 points

Mar 4, 2025 7:39 PM in response to leisa198

It appears this is a MacBook Pro 16" (2019) laptop from the "MacBookPro16,1" designation within the Kernel Panic log. There is a very good chance the Logic Board in your laptop is bad since this particular model has an extremely high rate of Logic Board failures....more than any other Mac. There have even been reports from users that their official Apple Logic Board replacements have suffered failures as well....sometimes as soon as they start to use the laptop at home after the repair.


Many times people may have hundreds of these ProxiedDevice-Bridge panics (associated with the T2 chip as @g_wolfman mentioned) along with other non-T2 Kernel Panics.


Personally I don't recommend spending any money on repairs to any 2016-2020 Intel Macs for multiple reasons, but especially not on this particular model. The money spent on repairs is much better put towards a new laptop.


I hope you have good backups of your data.

Reply

How do you troubleshoot the panic system crash?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up