Ah, I wonder if there is a way to test the apple I/O card then...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 13.4 (Final) - Bug fixes, changes, and more
- Thread starter WilliApple
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Ah, I wonder if there is a way to test the apple I/O card then...
I would think that just running a diagnostic would report anything wrong with any attached hardware. I think it can even tell you if an attached keyboard is malfunctioning.
Last edited:
@prefuse7, Maybe you'll find this useful:
Dealing with a kernel panic
From the article:
Have you tried booting into Safe Mode to see if the kernel panics stop? Or do a fresh install on a separate drive and boot from that? And if possible, temporarily remove the two GPUs and just test the system with the Intel iGPU. You need to rule out a potential hardware or peripheral cause for the kernel panics.
If you can do that, then at least you've narrowed it down to the OS or some conflict with 3rd party software or drivers.
Dealing with a kernel panic
From the article:
Have you tried booting into Safe Mode to see if the kernel panics stop? Or do a fresh install on a separate drive and boot from that? And if possible, temporarily remove the two GPUs and just test the system with the Intel iGPU. You need to rule out a potential hardware or peripheral cause for the kernel panics.
If you can do that, then at least you've narrowed it down to the OS or some conflict with 3rd party software or drivers.
Last edited:
I literately came here to post the same article lol
eclecticlight.co
Dealing with a kernel panic
How to capture the panic log, immediate actions likely to help make a diagnosis, and how to read the panic log.
eclecticlight.co
I would also be curious of any results you'd get from running a diagnostic
support.apple.com
I have a 2020 M1 MBP that I mostly used in clamshell mode for roughly 1½ years and was getting Kernel Panics, and it ended up being a faulty dock. Running diagnostics, though, pointed to a faulty keyboard (from what they told me at the Genius Bar), but then after more investigating, it was just a bad dock..
¯\_(ツ)_/¯
Use Apple Diagnostics to test your Mac - Apple Support
Apple Diagnostics, formerly known as Apple Hardware Test, can check your Mac for hardware issues.
I have a 2020 M1 MBP that I mostly used in clamshell mode for roughly 1½ years and was getting Kernel Panics, and it ended up being a faulty dock. Running diagnostics, though, pointed to a faulty keyboard (from what they told me at the Genius Bar), but then after more investigating, it was just a bad dock..
¯\_(ツ)_/¯
Looking at the log you posted, com.apple.driver.watchdog is what's causing the Kernel Panic. That's generally in place to be a "Watch Dog" for apps/hardware that should/shouldn't be doing what they're supposed to be doing.. Vague, huh?!? Well, this ultimately means that either an app is or isn't doing what it should/shouldn't be doing, OR a piece of attached hardware hasn't "Checked In" for X amount of time.
Here's another good post of comments related to this:
talk.tidbits.com
Here's another good post of comments related to this:
What is a watchdog timeout and what causes it?
I can’t help with your specific situation, but I can provide a bit of background information, in case it helps. See also Watchdog timer - Wikipedia A “watchdog timer” is a mechanism used to detect when a process or thread has hanged. Either because of a deadlock or an infinite loop or some...
Dunno but that might be something the Apple Store could do.
BTW, have you ever stress tested both your GPUs in Windows? If you have Windows bootcamp installed, I suggest booting into Windows and stress testing both your GPUs using a program like Furmark or Unigine Superposition to push your cards to the limit. Start with Furmark and crank up the settings.
When I was having weird issues with my hackintosh, Furmark revealed that I had a defective RX 580 even though the system was stable under normal usage. It's only when certain things pushed the GPU, that the system crashed.
At the very least, this might rule out a defective GPU.
Also happens every now and then on my M2 MacBook Pro and Magic Keyboard on my M2 Mac Mini. Stops for a bit, come back later and it works again.
@gank41 @Idgit
Thanks for all of the suggestions -- since this is a Mac Pro, there is no built-in Intel GPU, so I have to use either my RX-6800XT or the MPX module in order to have video output. I have tried Safe mode and using first aid within Disk Util in recovery mode.
I have also stress tested my GPU in Windows 11 using Furmark, Cinebench, and the Unigine test. All reveal no problems with my RX-6800XT, however, interestingly enough, I was finally able to get the AHT to work, and it revealed the following:
"PPF004: There may be an issue with the fan."
Funny part is, I then booted back into macOS and installed Mac Fans Control and tested all fans and the exhaust and all of them ran to max speed fine without causing the machine to KP or do anything weird (was also monitoring activity monitor to see if WindowServer would start overusing RAM and getting ready to crash, or if watchdogd would act weird, but nothing happened) then I watched a 2 hour movie with no issues.
Needless to say, I am still going to take it into apple to see what they have to say, so thanks for all your help.
I'll report back after I take her in to apple.
In case you're curious, here is my Furmark score, and below is the Unigine:
Cheers.
Thanks for all of the suggestions -- since this is a Mac Pro, there is no built-in Intel GPU, so I have to use either my RX-6800XT or the MPX module in order to have video output. I have tried Safe mode and using first aid within Disk Util in recovery mode.
I have also stress tested my GPU in Windows 11 using Furmark, Cinebench, and the Unigine test. All reveal no problems with my RX-6800XT, however, interestingly enough, I was finally able to get the AHT to work, and it revealed the following:
"PPF004: There may be an issue with the fan."
Funny part is, I then booted back into macOS and installed Mac Fans Control and tested all fans and the exhaust and all of them ran to max speed fine without causing the machine to KP or do anything weird (was also monitoring activity monitor to see if WindowServer would start overusing RAM and getting ready to crash, or if watchdogd would act weird, but nothing happened) then I watched a 2 hour movie with no issues.
Needless to say, I am still going to take it into apple to see what they have to say, so thanks for all your help.
I'll report back after I take her in to apple.
In case you're curious, here is my Furmark score, and below is the Unigine:
Cheers.
Last edited:
I’m glad you’re at least making some headway here! Imagine all the problems people could have if we had a truly modular Mac Pro. In your case, something as simple as a hinky fan could be the culprit, but imagine having all sorts of 3rd party parts. I would think a fan could be covered under AppleCare or a warranty, too
I am really hoping it is either the fan or the apple i/o card. I will gladly pay to replace either.
This is also a good example of why apple absolutely can not stop making modular Mac Pros! (I am not a big fan of the AS ARM transition because if this was an AS machine, I would literally be forced to throw it away and have to buy anew, since EVERYTHING is soldered to the board).
Ventura 13.4 External Display Sleep Loop Bug
macOS Ventura 13.4 display sleep issueI don't know what kind of clown show Federighi is running, but it needs to stop. Stop the yearly macOS releases. Go back to 18-24 month release cycles with better software quality assurance, and fix the frickin' bugs that have been around for years.
Last edited:
Has anyone noticed improvement in battery life with this update? I have had consistently pretty bad battery life since updating to Ventura. My battery isn't that old, only a couple hundred cycles on it. I'm getting 3-4 hours max usage. I previously was getting double that. This has been the case in 13.2 and 13.3. Hopefully its better in 13.4?
With ventura 13.4 final i have a Keyboard USB bug. never experienced it prior to 13.4. after a while the keyboard no longer inputs, like it has been dropped from USB connection. disconnect and reconnecting it brings it back to life. As i dual boot with monterey also it does not disconnect in that OS only in ventura. almost like USB sleep function. real strange and very annoying.
How can we be sure this is "fixed"? AFAIK, there is no way to reproduce this problem, it just happens.
Since 13.1 or 13.2 update for my 2022 model Macbook pro 13", when I put this mac to sleep, it frozes, crashes, and restarts. Also, when it goes to sleep after a few hours of ideling period, the similar craches happen.
The crash reports are very similar in nature, as I see the keywords, Windowserver, WATCHDOG, Code 1 monitoring timed out for service, and etc.
The beginning part of the most recent crash report:
Process: WindowServer [-1]
Path: ???
Identifier: WindowServer
Version: ???
Code Type: 00000000 (Native)
Parent Process: ??? [Unknown]
User ID:
Date/Time: 2023-06-03 07:42:40.8100 +0900
OS Version: macOS 13.4 (22F66)
Report Version: 12
Anonymous UUID: 8F96E25C-3F2C-1E9F-0DB7-5F5B32B6BF10
System Integrity Protection:
Notes:
resampled 6 of 2298 threads with truncated backtraces from 0 pids:
This is a watchdog-triggered termination event, and not expected to be well-represented in the legacy crash format
Crashed Thread: Unknown
Exception Type:
Termination Reason: Namespace WATCHDOG, Code 1 monitoring timed out for service
(1 monitored services unresponsive): checkin with service: WindowServer returned not alive with context:
unresponsive work processor(s): WindowServer main thread
40 seconds since last successful checkin, 24 total successful checkins since 310 seconds ago (0 induced crashes), has not exited since first loaded
Error Formulating Crash Report:
resampled 6 of 2298 threads with truncated backtraces from 0 pids:
This is a watchdog-triggered termination event, and not expected to be well-represented in the legacy crash format
Backtrace not available
No thread state (register information) available
Binary Images:
Binary images description not available
-----------
Full Report
-----------
{"bundleID":"WindowServer","roots_installed":0,"timestamp":"2023-06-03 07:42:40.00 +0900","os_version":"macOS 13.4 (22F66)","incident_id":"83077726-93A5-4E87-9035-A95215AB7C89","share_with_app_devs":0,"bug_type":"409","app_name":"WindowServer","name":"WindowServer"}
{
"deployVersion" : 210,
"variant" : "stackshot",
"incident" : "83077726-93A5-4E87-9035-A95215AB7C89",
"crashReporterKey" : "8F96E25C-3F2C-1E9F-0DB7-5F5B32B6BF10",
"modelCode" : "MacBookPro17,1",
"cpuType" : "00000000",
"osVersion" : {
"train" : "macOS 13.4",
"build" : "22F66",
"releaseType" : "User"
},
"variantVersion" : 2,
"captureTime" : "2023-06-03 07:42:40.8100 +0900",
"pid" : -1,
"bug_type" : "409",
"procName" : "WindowServer",
"bundleInfo" : {"CFBundleIdentifier":"WindowServer"},
"termination" : {"flags":0,"indicator":"monitoring timed out for service","code":1,"namespace":"WATCHDOG","details":["(1 monitored services unresponsive): checkin with service: WindowServer returned not alive with context:","unresponsive work processor(s): WindowServer main thread","40 seconds since last successful checkin, 24 total successful checkins since 310 seconds ago (0 induced crashes), has not exited since first loaded"]},
"stackshot" : {
"processByPid" : {
"0" :
The crash reports are very similar in nature, as I see the keywords, Windowserver, WATCHDOG, Code 1 monitoring timed out for service, and etc.
The beginning part of the most recent crash report:
Process: WindowServer [-1]
Path: ???
Identifier: WindowServer
Version: ???
Code Type: 00000000 (Native)
Parent Process: ??? [Unknown]
User ID:
Date/Time: 2023-06-03 07:42:40.8100 +0900
OS Version: macOS 13.4 (22F66)
Report Version: 12
Anonymous UUID: 8F96E25C-3F2C-1E9F-0DB7-5F5B32B6BF10
System Integrity Protection:
Notes:
resampled 6 of 2298 threads with truncated backtraces from 0 pids:
This is a watchdog-triggered termination event, and not expected to be well-represented in the legacy crash format
Crashed Thread: Unknown
Exception Type:
Termination Reason: Namespace WATCHDOG, Code 1 monitoring timed out for service
(1 monitored services unresponsive): checkin with service: WindowServer returned not alive with context:
unresponsive work processor(s): WindowServer main thread
40 seconds since last successful checkin, 24 total successful checkins since 310 seconds ago (0 induced crashes), has not exited since first loaded
Error Formulating Crash Report:
resampled 6 of 2298 threads with truncated backtraces from 0 pids:
This is a watchdog-triggered termination event, and not expected to be well-represented in the legacy crash format
Backtrace not available
No thread state (register information) available
Binary Images:
Binary images description not available
-----------
Full Report
-----------
{"bundleID":"WindowServer","roots_installed":0,"timestamp":"2023-06-03 07:42:40.00 +0900","os_version":"macOS 13.4 (22F66)","incident_id":"83077726-93A5-4E87-9035-A95215AB7C89","share_with_app_devs":0,"bug_type":"409","app_name":"WindowServer","name":"WindowServer"}
{
"deployVersion" : 210,
"variant" : "stackshot",
"incident" : "83077726-93A5-4E87-9035-A95215AB7C89",
"crashReporterKey" : "8F96E25C-3F2C-1E9F-0DB7-5F5B32B6BF10",
"modelCode" : "MacBookPro17,1",
"cpuType" : "00000000",
"osVersion" : {
"train" : "macOS 13.4",
"build" : "22F66",
"releaseType" : "User"
},
"variantVersion" : 2,
"captureTime" : "2023-06-03 07:42:40.8100 +0900",
"pid" : -1,
"bug_type" : "409",
"procName" : "WindowServer",
"bundleInfo" : {"CFBundleIdentifier":"WindowServer"},
"termination" : {"flags":0,"indicator":"monitoring timed out for service","code":1,"namespace":"WATCHDOG","details":["(1 monitored services unresponsive): checkin with service: WindowServer returned not alive with context:","unresponsive work processor(s): WindowServer main thread","40 seconds since last successful checkin, 24 total successful checkins since 310 seconds ago (0 induced crashes), has not exited since first loaded"]},
"stackshot" : {
"processByPid" : {
"0" :
You and I are having the same issue! (scroll back a few pages to see my posts on it here)
Also it doesn't seem likely that they will fix this until macOS 14 (fingers crossed).
@gank41 @Idgit Wanna know something very weird and a bit interesting?!?
Since my last post on Monday, post #87 above.... I had booted into Windows and ran those benchmarks/GPU stress tests right...
Since doing that, I have NOT had ANY issues at all!
It's like, booting into Windows somehow fixed my 7,1 -- taking it back to being the way it was before I upped to 13.4 and started having all of the problems...
Weird, huh?
Since my last post on Monday, post #87 above.... I had booted into Windows and ran those benchmarks/GPU stress tests right...
Since doing that, I have NOT had ANY issues at all!
It's like, booting into Windows somehow fixed my 7,1 -- taking it back to being the way it was before I upped to 13.4 and started having all of the problems...
Weird, huh?
Even though I have not had any problem until 13.0 update, since 13.1 update and on, my MBP 13" M1 crashes when put into sleep. As it is a windowserver related crush, it came to my mind there could be some leaky applications which are causing this. As I know the typical set of applications I usually keep them open, I narrowed down to Firefox, as it seems to be taking more memories than other applications. I switched my browser from Firefox to Chrome and this sleep-crash problems have stopped. It seems this was caused by Firefox. It is possible Firefox was not optimized after 13.1 updates.
**update**after a few hours since then, the same problem has started again. So, it turns out this is nothing to do with Firefox. I should not have updated to 13.1 in hindsight.
**update**after a few hours since then, the same problem has started again. So, it turns out this is nothing to do with Firefox. I should not have updated to 13.1 in hindsight.
Last edited:
As I said to you above, check the previous pages to see my previous posts on this same error -- same exact issue as you, but I DO NOT have Firefox installed, so something else is causing it to happen.
Also, this started happening to me frequently under 13.4, an it happened only once on 13.1.
Then I booted into Windows to run the GPU benchmarks/stress tests, and my machine has been fine since.
Last edited:
Oddly enough! Just in the last week or so I installed Asahi Linux on my M1 MBP and have had no issues with macOS since. I think there’s a difference between restarting and shutting down and back on again? With me, I’m shutting down after using Linux and then waiting 15-20 seconds and then booting back up into macOS.
I am not responding to your problems. I am rather sharing my case to this group as a whole.