Panic Attack - computer restarted because of problem - Watchdog

Panic Attack - computer restarted because of problem - Watchdog


I have been getting INSANE amount of unexpected shutdown. I have tried reinstall of MacOS multiple times using different method; in-place erase and reinstall, reinstall from recovery, reinstall using bootable USB but experiencing same issue. MAC OS MONTEREY 12.4 


panic(cpu 2 caller 0xffffff8015767938): watchdog timeout: no checkins from watchdogd in 98 seconds (6 total checkins since monitoring last enabled)


Panicked task 0xffffff8b92d63670: 198 threads: pid 0: kernel_task


Backtrace (CPU 2), panicked thread: 0xffffff8b92e56540, Frame : Return Address


0xffffffb0ae86bb90 : 0xffffff8012281c8d 


0xffffffb0ae86bbe0 : 0xffffff80123e1596 


0xffffffb0ae86bc20 : 0xffffff80123d0963 


0xffffffb0ae86bc70 : 0xffffff8012221a70 


0xffffffb0ae86bc90 : 0xffffff801228205d 


0xffffffb0ae86bdb0 : 0xffffff8012281816 


0xffffffb0ae86be10 : 0xffffff8012b15223 


0xffffffb0ae86bf00 : 0xffffff8015767938 


0xffffffb0ae86bf20 : 0xffffff8015767273 


0xffffffb0ae86bf50 : 0xffffff8013a6e265 


0xffffffb0ae86bfa0 : 0xffffff801222119e 


      Kernel Extensions in backtrace:


         com.apple.driver.watchdog(1.0)[D6F8B92D-3418-34BA-B42B-F553E0C44C29]@0xffffff8015765000->0xffffff8015767fff


         com.apple.driver.AppleSMC(3.1.9)[2B59F3D8-402A-351E-AF4E-6F42A7923DBB]@0xffffff8013a5f000->0xffffff8013a77fff


            dependency: com.apple.driver.watchdog(1)[D6F8B92D-3418-34BA-B42B-F553E0C44C29]@0xffffff8015765000->0xffffff8015767fff


            dependency: com.apple.iokit.IOACPIFamily(1.4)[3224D91D-C81D-33E2-A8B3-1A168235F4E7]@0xffffff801497b000->0xffffff801497cfff


            dependency: com.apple.iokit.IOPCIFamily(2.9)[654ABF9D-EB24-3B64-AB1C-EC2AC8357192]@0xffffff8014e24000->0xffffff8014e4ffff




MacBook Pro 13″, macOS 12.4

Posted on Jun 22, 2022 8:15 PM

Reply
Question marked as Top-ranking reply

Posted on Jul 5, 2022 7:05 PM

The last started extension in that report mentions "msdos" which usually indicates a USB stick or an SD card was connected, but could be almost any external drive as well since some of them may actually have a hidden FAT partition on them. Even some other devices you would never suspect could possibly have a FAT partition which macOS may access when the device is connected. Have you possibly opened & mounted (or attempted to mount) some archive bundle or .iso file which may have a FAT file system with it? Something triggered that "msdos" extension to load.


I do see a lot of the "ProxiedDevice Bridge/stacks...xxxxxx.ips" crashes in your EtreCheck report. I have seen a lot of other similar type of crash entries in some of the EtreCheck reports for users running Monterey. Maybe this is the real source of the problem, but I'm not sure they are the same error. Monterey seems to have a lot of issues with each new update (some get fixed, new issues are created).


Try to pay attention to the apps you are running at the time, how you are using those apps and the laptop, as well as noting any connected devices. Maybe you can notice a pattern for the crashes. Being able to reproduce the problem on demand or much more often is the best way to find the source of the problem (and also to verify any potential solutions).


Maybe try running Disk Utility First Aid on the hidden Container. Within Disk Utility you may need to click "View" and select "Show All Devices" so that the physical SSD and hidden Container appears on the left pane of Disk Utility. Run First Aid on the physical SSD in order to check the partition table. Even if First Aid says everything is "Ok", click "Show Details" and scroll back through the report to see if any unfixed errors are listed. If there are any unfixed errors listed, then you will need to run First Aid from Internet Recovery Mode (Command + Option + R), otherwise you will need to erase the whole physical SSD before restoring from a backup or clone to fix the file system issue.


Disconnect all external devices just in case one of them is causing a problem.


Did you actually perform a clean install of macOS by first erasing the whole physical SSD? And did you test the clean install before installing any third party apps and before restoring/migrating from a backup? This is the only way to separate out hardware & software issues since you may have brought back the problem from your backups. Another more drastic option is to "Restore" the T2 firmware which resets the T2 security chip, updates the system firmware, and pushes a new copy of macOS onto the SSD much like when you use a computer to restore an iPhone or iPad.

Revive or restore an Intel-based Mac using Apple Configurator - Apple Support


If you have the issues after "Restoring" the T2 firmware, but before installing third party apps and before restoring/migrating from a backup, then you have enough proof to have Apple support focus on your issue since both the hardware & software at that moment all Apple and should just work.


Sometimes these intermittent issues can be so hard to narrow down. Trust me they drive service technicians crazy too.


Similar questions

7 replies
Question marked as Top-ranking reply

Jul 5, 2022 7:05 PM in response to nileshboss

The last started extension in that report mentions "msdos" which usually indicates a USB stick or an SD card was connected, but could be almost any external drive as well since some of them may actually have a hidden FAT partition on them. Even some other devices you would never suspect could possibly have a FAT partition which macOS may access when the device is connected. Have you possibly opened & mounted (or attempted to mount) some archive bundle or .iso file which may have a FAT file system with it? Something triggered that "msdos" extension to load.


I do see a lot of the "ProxiedDevice Bridge/stacks...xxxxxx.ips" crashes in your EtreCheck report. I have seen a lot of other similar type of crash entries in some of the EtreCheck reports for users running Monterey. Maybe this is the real source of the problem, but I'm not sure they are the same error. Monterey seems to have a lot of issues with each new update (some get fixed, new issues are created).


Try to pay attention to the apps you are running at the time, how you are using those apps and the laptop, as well as noting any connected devices. Maybe you can notice a pattern for the crashes. Being able to reproduce the problem on demand or much more often is the best way to find the source of the problem (and also to verify any potential solutions).


Maybe try running Disk Utility First Aid on the hidden Container. Within Disk Utility you may need to click "View" and select "Show All Devices" so that the physical SSD and hidden Container appears on the left pane of Disk Utility. Run First Aid on the physical SSD in order to check the partition table. Even if First Aid says everything is "Ok", click "Show Details" and scroll back through the report to see if any unfixed errors are listed. If there are any unfixed errors listed, then you will need to run First Aid from Internet Recovery Mode (Command + Option + R), otherwise you will need to erase the whole physical SSD before restoring from a backup or clone to fix the file system issue.


Disconnect all external devices just in case one of them is causing a problem.


Did you actually perform a clean install of macOS by first erasing the whole physical SSD? And did you test the clean install before installing any third party apps and before restoring/migrating from a backup? This is the only way to separate out hardware & software issues since you may have brought back the problem from your backups. Another more drastic option is to "Restore" the T2 firmware which resets the T2 security chip, updates the system firmware, and pushes a new copy of macOS onto the SSD much like when you use a computer to restore an iPhone or iPad.

Revive or restore an Intel-based Mac using Apple Configurator - Apple Support


If you have the issues after "Restoring" the T2 firmware, but before installing third party apps and before restoring/migrating from a backup, then you have enough proof to have Apple support focus on your issue since both the hardware & software at that moment all Apple and should just work.


Sometimes these intermittent issues can be so hard to narrow down. Trust me they drive service technicians crazy too.


Jul 17, 2022 10:26 AM in response to nileshboss

It is starting to sound like a hardware issue. However, after performing the "Restore" of the system firmware, did you have to manually enter Internet Recovery Mode to reinstall the OS? From the few times I had to perform a "Restore" I have never noticed the Mac entering Internet Recovery Mode. The "Restore" process just always seemed to have pushed the OS onto the Mac. I do admit that I never paid complete attention to the whole process, but it sure seemed to be quicker than reinstalling from Internet Recovery Mode. After the "Restore" process using Apple Configurator 2 the Mac always had a clean install of macOS. I would try to use Apple Configurator 2 again to "Restore" the system firmware and see if you have a clean install of macOS. Otherwise, I think you have a hardware issue and will need to have Apple or an Apple Authorized Service Provider examine the laptop.

Jun 24, 2022 4:25 PM in response to nileshboss

The Kernel Panic shows the last loaded driver extension was for "msdos". Did you happen to have a USB stick or SD card plugged in which uses a FAT file system? Most likely the USB stick/SD Card is bad.


Do you have any other Kernel Panics reports which you can post here so we can see if there is any pattern? The Kernel Panic logs are located in "/Library/Logs/DiagnosticReports" with file names beginning with "kernel" and ending in ".panic". Use the Finder to access this folder and any Kernel Panic logs since the Console app may not show all the log files available.

Jun 24, 2022 8:20 AM in response to nileshboss

Hey nileshboss,


Welcome to Apple Support Communities. It sounds like you need help with unexpected shutdowns on your Mac. We're happy to help.


Have you had a chance to look over this article yet?


If your Mac restarted because of a problem - Apple Support


If so, and it didn't help, reach out to Apple Support here: Contact Apple for support and service - Apple Support


Cheers!

Jul 17, 2022 6:57 AM in response to HWTech

Hi, thanks for detailed instructions/guidance. Since my mac kept getting panic attacks, I decided to Revive and Restore using Apple Configurator and now when I try to reinstall Mac OS using Recovery OS I am receiving an error stating that the operation could not be completed at the very end of installation process, so I am not sure if this is an hardware issue or not?


I also tried reinstalling Oringal Mac OS, Mojave, the computer came with but at the very end of install process it states that the computer is offline where as it is still connected to WiFi.


absolutely not sure what to do with this now.


Thanks so much for your help!

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Panic Attack - computer restarted because of problem - Watchdog

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