Since installing Catalina yesterday, multiple crashes from userspace watchdog timeout

I installed Catalina yesterday and my macbook pro has crashed 10 times in less than 24 hours, how do i fix this problem,PLEASE HELP!!!. the first error reports looked like this(omitted The rest of report) started like this:

panic(cpu 0 caller 0xffffff7f8b3053c6): "AppleAHCIDiskDriver::PolledIO, trying to do polled IO with polled command in flight, inPolledIOSelector = 0x00000004\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOAHCIBlockStorage/IOAHCIBlockStorage-316.100.5/AppleAHCIDiskDriver.cpp:

please help

I'm perfectly agree with BradSP. Now my IMac doesn't restart, it just freeze, the mouse is the only thing that works.

I repeatedly shut down brutally every 15 minutes, completely unusable.

That's why I wait Big Sur, in case of the problem still appear I unfortunately will go away it and return to Microsoft system.....

Apple are not here to respond -> Which is why I was trying to encourage people to use the Feedback Assistant. Hopefully the more crash reports etc the more attention Apple will give.

Update 10.15.7 is available to all -> No update I've had solves the problem ... yet.

So after upgrading to the latest latest version on OSX a couple of hours ago.... It appears that system hang without watchdog catching it is the new normal for me at least :-(

3 Lockups in the last hour each one requiring a power removal reboot.

Only working on Email / Safari so far. Nothing stressful like video work which is what normally causes me issues.

Thanks for that KT ... I wonder if I can achieve the same test with an external SSD on my Mac Pro ... ah well it's an excuse to buy more tech ....!

I wonder if the problem would reappear if you now upgrade that back to Catalina?

>> I wonder if the problem would reappear if you now upgrade that back to Catalina?

We shall all continue to "wonder" about that, because I am not touching this thing in ANY way!! haha.... :)

KT

I'm waiting till my Holidays in 6 weeks time to purge all the bad thoughts of Cataline. DUe to the disasters i stopped upgarding at 10.15.1 because i had external monitor issues. Then I watched the problems with all subsequent upgrades and decided in times of covid there is no way to trust apple. In 6 weeks i get enough spare time to try and return to mojave away from the mess. This will be my last MAC due to these problems and the fact this no longer 'just works' My MAC was up for update but I just got a great dell XPS 13 in the sales. The MAC unfortunately just can not be trusted to be a daily driver any more.

I've also been testing with a single monitor, and can confirm it seems to make no difference. (Mac Pro on Samsung 4k via DP)

Has anyone seen Watchdog killing WindowServer on MacBook or iMac with no external display connected?

Maybe specifically to you that could be the problem, but overall it seems like it's a larger issue than that. As I (along with many others) have the exact same issue as you, but my configuration is completely different.

MacPro (Late 2013) with a Xeon E5 and dual FirePro D300s

I had the first 16inch MBP and it crashed EVERY time the external display came out of sleep. They didi a logic board change on what was essentially a brand new laptop. It did NOT fix the problem. It was unusable for a year! 10.15.7 eventually made the problem go away. I live in Silicon Valley and offered to bring in a complete setup that reliably and predictably failed so they could diagnose the problem. No interest. I doubt my next computer will be a Mac. Computers just aren't an interesting business to them any more.

I have not an external display, but I continue to think the crash depend by Intel GPU driver. I have an Intel Iris 6200.

I honestly hope in Big Sur, otherwise I will scrap it away, and I will buy an windows pc.... :-(

So after 2 whole weeks of my MacPro (Late 2013) being at the Apple Repair Center I finally got it back.

"We were unable to reproduce your issue(s).

Our technicians performed comprehensive testing and could not reproduce the issue(s) you reported. Your product passed every diagnostic and extended test we performed."

So they didn't do squat.

How are they supposed to reproduce the issue if they don't actually do a regular startup of your system? Which I was told by the store that they don't. They only start up with their external tools and safe starts, etc.

Looks like I'm screwed. And, so far, I've heard that Big Sur doesn't fix the problem.

I too have this issue. Started with Catalina, maybe every 3rd or 4th time but it now crashes every time I wake from a lengthy sleep on Big Sur. During the day normal sleeps are fine, like a lunch hour or something but an overnight sleep always causes the Macbook Pro to crash every time it's woken with my external display attached to it.

This started happening to me today. It was happening while Windows 10 was running on Parallels. I would leave the computer for a while and come back and find the computer restarted. I received this error. I'm running new Mac Pro 2020 with Apple screen and have not had any problems until today.

anic(cpu 2 caller 0xffffff8009953a13): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds

service: com.apple.logd, total successful checkins since load (1570 seconds ago): 158, last successful checkin: 0 seconds ago

service: com.apple.WindowServer, total successful checkins since load (1540 seconds ago): 142, last successful checkin: 120 seconds ago

service: com.apple.remoted, total successful checkins since load (1570 seconds ago): 156, last successful checkin: 0 seconds ago

Backtrace (CPU 2), Frame : Return Address

0xffffffe5e674b670 : 0xffffff80066bc66d

0xffffffe5e674b6c0 : 0xffffff80067ff073

0xffffffe5e674b700 : 0xffffff80067ef6aa

0xffffffe5e674b750 : 0xffffff8006661a2f

0xffffffe5e674b770 : 0xffffff80066bbf0d

0xffffffe5e674b890 : 0xffffff80066bc1f8

0xffffffe5e674b900 : 0xffffff8006ebee84

0xffffffe5e674b970 : 0xffffff8009953a13

0xffffffe5e674b980 : 0xffffff80099536ba

0xffffffe5e674b9a0 : 0xffffff8006e460ee

0xffffffe5e674b9f0 : 0xffffff8009952b0a

0xffffffe5e674bb20 : 0xffffff8006e502bb

0xffffffe5e674bc80 : 0xffffff80067aaa61

0xffffffe5e674bd90 : 0xffffff80066c1d77

0xffffffe5e674be00 : 0xffffff80066985d5

0xffffffe5e674be60 : 0xffffff80066afb82

0xffffffe5e674bef0 : 0xffffff80067d3823

0xffffffe5e674bfa0 : 0xffffff8006662216

   Kernel Extensions in backtrace:

     com.apple.driver.watchdog(1.0)[7948A279-A8B8-3650-AFBF-B1E3EB68942A]@0xffffff8009952000->0xffffff8009953fff

Process name corresponding to current thread: watchdogd

Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:

20B29

Kernel version:

Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64

Kernel UUID: 84C6DC45-6B02-335F-9439-5D2A9BC385A4

KernelCache slide: 0x0000000006400000

KernelCache base: 0xffffff8006600000

Kernel slide:   0x0000000006410000

Kernel text base: 0xffffff8006610000

__HIB text base: 0xffffff8006500000

System model name: MacPro7,1 (Mac-27AD2F918AE68F61)

System shutdown begun: NO

Hibernation exit count: 0

For me, the problems didn't start UNTIL I installed the latest Catalina Security update for 10.15.7. It was sporadic at first, then it occurred daily, now it's happened 6 times in the last hour. I've been all over the internet reading support threads at Apple and discussions elsewhere....Since this is also happening on the M1 Macs and Big Sur, Apple must surely understand this is a real issue, no?

My set up is quite complex as I'm running a recording studio with all kinds of hardware and multiple monitors connected to an iMacPro 10 core 64gb /4TB machine. Because of that, I do not expect Apple Support to be any help whatsoever; There are too many other things to point to. I don't know...could be legit, but the thing is: It was stable and operating near perfectly before this latest update. Now, I'm afraid to walk away from it for more than 10 minutes....