Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Hey bzgnyc2, here is the activity from three hours after booting, without loading anything except iStat, TG Pro, Carbon Copy Cloner, Some Logitech app for my webcam, BetterDisplay, and Adobe Creative Cloud. Oh! And ClipMenu—an app that is really old but really, really useful.
View attachment 2487386

That's interesting especially 3 hours after booting. mediaanalysisd and mds_stores are still working up a storm. With VTDecoderXPCService throwing in for good measure. If I had to guess, Spotlight (mds) is scanning every photo/video it can find, using VTDecoderXPCService to decode videos, and mediaanalysisd to identify faces, objects, etc to create text searchable indexes for them.

Questions that come to mind:
-Do you have lots of photos/videos on your system? I haven't had this issue but either way I wouldn't think all this would run for so long unless you had more than a few.
-How long have they been there? Unless the videos recently created, I would think these already would have been indexed since your initial system installation/last major update unless your indexes got cleaned out (did you do the Safe Boot right before this? or is this just one of Spotlight's random index rebuilds)
-Do you need Spotlight and/or indexing of your photos/videos? If this indexing persists and/or causes other problems, you could disable altogether as fisherrman suggested or perhaps just your photos/videos depending on your needs

Although I find the Spotlight of recent versions of macOS less useful/reliable than earlier (as in I end up just doing a brute force search for files when it can't find something I know is there), I haven't yet given into disabling it completely. I have disabled it for select drives and work areas for files where I know it won't be useful but I leave it in general I guess I still have hope...

Another Macrumors member shared this link in another thread and was surprised to see Apple is still working on the basics:

The bug about unmounting is one that I've experienced back to at least Mojave so now curious to test the latest Sequoia. Maybe they did more than just load it up but with AI junk...

EDIT: And the only fault I'm seeing on console is

sharedcache fault 16:04:10.218235-0500 com.apple.WebKit.WebContent checkinWithServer Failed bootstrap_lookup2 for name of coreservicesd, kern_return_t=#1100/0x44c Permission denied name=com.apple.CoreServices.coreservicesd

Okay, I'm also seeing an error with imagent and siriinferenced. Maybe I should nuke Siri?

Are the "siriinferenced" errors and "imagent" in the same message or seem related or are they two independent recurring error messages?

"imagent" is related to instant messaging / Messages. Are you using that on your Mac? And if so, is there likely lots of videos/images coming through your text / iMessages?

siriinferenced may be related to the above indexing of videos and perhaps making Spotlight indexes accessible from Siri but hard to say based on Apple's documentation these days...

My general tendency is to disable things I don't want (e.g. Siri, all services under Sharing, Location Services, etc) but of course varies by needs/preferences.

However, it doesn't look like your logd/runningboardd were unusually active in the above. Before they seemed constantly active and I would have been concerned about repeating errors/warnings to the log. One or two here or there unless related to a specific issue you are having is normal. Unfortunately, the signal / noise ratio in the logs / Apple's Console isn't optimal but that's an issue beyond the scope of this thread...in the meantime, what I would say is if/when logd/runningboardd start showing constant CPU usage (in top or Activity Monitor), return to the Console to see if there is anything you can pick out to see what's driving that.

Last, I would say monitor the above mds/mediaanalysisd/etc and see if they ever comes to rest. If so, I bet you would actually see pretty reasonably %idle after that (not counting any Safari, etc you start when you actually want to get work done). The rest of the processes look pretty light. A few higher than I would expect (e.g. PerfPowerServices and searchpartyd) and a few I don't even know (e.g. PID=375 and PID=264) but not terrible. Maybe you would be at 98% idle at that point and if so I would be curious your CPU temperature under those circumstances.
 
Hey bzgnyc2, I think I finally fixed it! Friday evening, I repasted the CPU using Arctic MX-6. Now, here is the CPU Top after about two hours at idle:
1740952832420.png

Temps are so much better. I'm at 71 degrees celsius .. now 64 . . . I don't think my first repaste was that good, because the Airflow Ambient Intake temperature was the same as the Airflow Exhaust. Now, exhaust is higher. Also, now the fan can knock CPU PECI from 88 to 64 in a second.

YAY!!
 
Last edited:
  • Like
Reactions: bzgnyc2
Hey bzgnyc2, I think I finally fixed it! Friday evening, I repasted the CPU using Arctic MX-6. Now, here is the CPU Top after about two hours at idle:
View attachment 2487672
Temps are so much better. I'm at 71 degrees celsius .. now 64 . . . I don't think my first repaste was that good, because the Airflow Ambient Intake temperature was the same as the Airflow Exhaust. Now, exhaust is higher. Also, now the fan can knock CPU PECI from 88 to 64 in a second.

YAY!!

Great glad to hear things are better. Definitely sounds like you needed to redo the thermal paste.

I would still keep an eye on those various background processes and such. It looks after 2 hours they are still consuming almost one core of your i5. Not sure why airportd or locationd wouldn't be almost 0% more than 2 hours after boot when the system is otherwise idle. In any case, presumably mediaanalysisd and everything related will eventually finish which is most of it. At that point you might find your system is down to the 50s at idle while also having more spare power for your actual needs.
 
Dude. I've got MS Word open, Mail, several PDFs, and my CPU is at 8% as a I type this.

EDIT: And CPU PECI is at 37 degrees celsius.
 
  • Like
Reactions: bzgnyc2
Aaaaand this is what Top looks like now:
1740966051514.png

I think the answer to my question that started this thread is a resounding "yes."
 
  • Like
Reactions: bzgnyc2
I never figured out the BB code, but my system is running sooooo much better now. And, it finally looks like programs are able to use the 64 gigs of memory I added.

It's crazy that thermal problems would result in so many software problems, isn't it? How does one explain that?
 
This all seems like an insane amount of work and tinkering to get to the end point of having a functioning Mac. I've had probably 20 Macs over the years and I've not once needed to apply "thermal paste" to make them work right.

I get it, it can be fun to work out a problem like this, but if it was me and I was spending this much time, I'd just buy a used M1 Mini or better and call it a day. ¯\_(ツ)_/¯
 
Last edited:
  • Like
Reactions: MacCheetah3
I do love to tinker! If I had the money, I maybe would have purchased a new Mac . . . but there is something that endears me to the machines when I've saved them from being trashed or recycled.

It's SOOOO nice not to hear the fan spin up every few seconds! My CPU usage is at 8-16% now, and CPU PECI is at 42 degrees!
 
  • Like
Reactions: bzgnyc2 and tjktony
Interesting thread, I'm going to soon check out and probably replace the old thermal grease on my 2011 Mac Mini. Over the last few years with light workloads its become increasingly likely to heat up when the room temperature rises above above normal levels such as in summer.

There is the "Endurance" app on the App Store that can be used to put a controlled load on the CPU. You can fire up 1 or several CPU cores, for my Mini I can select 1, 2, or 4 cores to get CPU levels of about 25%, 50%, or 100%. I have an app that shows CPU temperature and fan speed, I'd like to find out if the new thermal grease makes a difference.
 
I'll check that out! Or maybe I shouldn't . . . less I decide that I need to redo the thermal paste a third time!

Just kidding. Do do before-and-after comparisons frank4 and please report back!
 
Hello!

I just repasted at the end of January. I used Thermal Grizzly's Hydronaut. It prevent my CPU from throttling when browsing the web. Now, WindowServer is slowing my system down to the point where I need to restart every few hours.

I'm looking at using ARCTIC MX-6. Is this just stupid after a month?

Maybe I should get a new CPU cooler?
It's 2025... maybe websities are more heavier than in 2018?
 
Forgive me, but maybe you're heavier than in 2018?
Nope... I went WFPB ~1,200kcal OMAD, 2,000+kcal 3-4hr daily active calories and sleep before 10pm and wake up after 6am night for the past year and I've been dropping 10kg monthly.

So no... I am lighter than 2018 me.... I'm trying to be leaner than 2001 me.

Targeting BMI 20.0 @ <10% BF
 
  • Like
Reactions: Engender
Uhhh . . . I don't know how to say this and I don't want to start a new thread about it, but one of my tbolt controllers died. I noticed that my Mini had reset into recovery mode. The controller running the external nvme had died. Confirmed it with hardwear test.

Hmmm.

Okay, it looks like maybe 1/4 ports. Into one of the two ports I can plug USB . . . maybe only USB 2.0 speed devices in at least one of the effected tbolt ports. Is that possible? It will recognize devices connected to a 3.0 hub, but only with 2.0 seeeds.
 
Last edited:
Uhhh . . . I don't know how to say this and I don't want to start a new thread about it, but one of my tbolt controllers died. I noticed that my Mini had reset into recovery mode. The controller running the external nvme had died. Confirmed it with hardwear test.

Hmmm.

Okay, it looks like maybe 1/4 ports. Into one of the two ports I can plug USB . . . maybe only USB 2.0 speed devices in at least one of the effected tbolt ports. Is that possible? It will recognize devices connected to a 3.0 hub, but only with 2.0 seeeds.

Since you've been taking the machine apart and putting it back together a few times, is it possible one of the USB-C ports is being shorted and/or not grounded -- throwing its Tbolt controller into confusion?

Each pair of USB-C ports on the Mac Mini 2018 is handled by an Intel JHL7540 controller, and it is my understanding that it handles both the Thunderbolt and USB2-3.x protocols (as well as DisplayPort) so its unclear to me how just the Thunderbolt and USB3.x protocol connectivity would be broken. When it connects to a device at USB 2.0, is communication with the device otherwise normal? Or is it only supporting downstream charging?

I am guessing there are various resisters, capacitors, diodes, etc sitting between the port and the controller and maybe one of those blew in a way that doesn't impact USB 2.0 but that's just wild speculation on my part. Afraid we're getting into the electrical engineering of it all and sure others could better advise on that.

If you're not ready to leave Intel behind (I'm not), something like this may be the cheapest "repair":
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
When it connects to a device at USB 2.0, is communication with the device otherwise normal? Or is it only supporting downstream charging?
I've got a USB 2.0 dock connected to one of the blown Tbolt ports now, and it's transferring purchases from my iPad. So, USB 2.0 data but now Displayport (which I tried with a monitor).
 
@Engender "...one of my tbolt controllers died. I noticed that my Mini had reset into recovery mode. The controller running the external nvme had died. Confirmed it with hardware test."

Historically, the first step in trouble-shooting funky port behaviour on a Mac was to reset the SMC (several times, maybe). And the PRAM.
This sorted out firmware glitches on pre-T2 Macs, and may well still be effective in the last Intel Macs?
 
Last edited:
Historically, the first step in trouble-shooting funky port behaviour on a Mac wass to reset the SMC (several times, maybe). And the PRAM.
This sorted out firmware glitches on pre-T2 Macs, and may well still be effective in the last Intel Macs?
I did reset PRAM. Let me reset the SMC . . . although I'm going to have to refresh myself on how to do that.
 
If you're not ready to leave Intel behind (I'm not), something like this may be the cheapest "repair":
I'm starting to think this is the solution, because I could get Apple Care on the unopened 2018 Mac Mini, right? That way, if I started having problems like this I could probably get it replaced . . . and maybe I'd get an M4 in place of the 2018 if the Tbolt connectors start failing.

EDIT: Except the ****ing second Tbolt bus is back after resetting the SMC, at least according to system information. Dude.
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
And my Mac Mini just passed an Apple Hardware Test. Kind of frustrating, to be honest. Anyone have any advice or thoughts?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.