I'm not an OSX expert (and everyone on this forum knows that!!!) but because of its 'nix under the bonnet I take an interest in the OS internals. I've heard for a few years of the bug that allows the OS to run away with the CPU and overheat the system. "kernel_task" bug. So hopefully this issue that you are having is not directly related to the fact it's a 12-core box. You state that you've searched all four corners of the planet for a solution so you've probably read all about this already (but just in case):
Location: Asia Pacific, Cyberspace, in the Dark Dystopia
Thanks Given: 2,351
Thanked 3,358 Times in 1,877 Posts
Got a phone call from Apple iCare today, and the technician told me that there was a bad sensor chip on my logic board and that was the cause of the problem.
He said this MacPro was still under warranty and asked my permission to order the chip from Singapore, estimating (worse case) the chip would arrive from Singapore and he could get the work done in 7 to 10 days.
Since we were speaking in Thai, I could not really get the details on the chip or the chip number; but I'll try to go by the Apple shop and ask them in a few days.
Pretty good Apple service, I think. Dropped the round trash can Mac Pro off at 11AM and got a call back with the status at 8PM the same day.
Just upgraded my MacPro (2013) from Catalina 10.15.2 to 10.15.3.
After the routine download and restart for upgrade installation, the Mac would not boot. Totally crashed.
Now, I'm in the process of a 15 hour restore from my last time machine backup.
I'm not very happy with... (3 Replies)
Hey MacPro users.
I just bought a refurbished 13-Core MacPro with 64GB of RAM for a cybersecurity gaming project I'm working on. Could not wait for the new MacPro in 2019, so this will have to do:
2013 Apple Mac Pro 2.7GHz 12 Core/64GB/256GB Flash/Dual AMD FirePro D700 6GB 6,1
Now, I'm... (0 Replies)
I installed 10.5 (Leopard) on my G4 733 Mhz (after minor tampering with the install package, just switched a boolean FALSE to TRUE).
Everything works fine after startup, but once I sleep the computer and wake it back up, kernel_task starts using at as much CPU runtime as it can, as in past 90%.... (0 Replies)