![]() When I came back and turned it on, it shut down within an hour. My computer stayed on all night, longer than ever before since the problem began, but then I turned it off before leaving. Please check my post too, maybe we got the same problem with the drivers? If so, please check your latest Crash report after the kernel panic and look and see if the "USB driver" is mentioned? You'll find it some lines down in your report. I'll give it a few days, but I hope it is fixed. It used to die just sitting idle for a few hours. I would have never thought to do that since it shut off even with a fresh install of Monterey on a new drive, plus the MOTU software.īut I've been using DP 11 and other processor-intensive tasks and have had no problems. I don't think I made it more than 5 or 6 hours without the Mac shutting down before. I'm not going to call it fixed yet, but I've had my Mac on with the UltraLite plugged in for over 8 hours now. Fortunately, AutoTune was in the As so it didn't take as long to find as it might. I found it by going through every App, Extension and License to make certain that I was running the latest and greatest. I recently had a nasty conflict with an older CodeMeter Runtime (Antares, NI and others use this). If you buy it from the App Store, update notifications are automatic. When diagnosing, Find Any File.app can locate things that elude Finder/Find. They've been informed and have done nothing. Suspect anything from Corel except Toast - there's a background process that causes lags and the only way to eliminate it is to disable SIP and purge everything with Corel in the name. The Activity Monitor, diligence and patience are normally your best friends. If the above doesn't do it, you have to find the culprit. sudo mdutil -E / (enter Admin password when prompted, then ) System/Library/Frameworks/amework/Frameworks/amework/Support/lsregister -kill -seed -lint -r -f -v -dump -domain local -domain system -domain user -domain network Ĥ. This is a bit of a Hail Mary but I would reset the Launch Services to Default to eliminate that as a cause.Ģ. I'll assume that you've tried resetting the NVRAM and SMC. You're doing everything right but something is getting in the way. Has anybody else experienced anything like this? I have a ticket in with MOTU. The UltraLite has been off the last few days and I haven't had anymore random shutdowns with code -3. I turned it back on and had 2 random shutdowns within 5 hours, just viewing Web pages. ![]() Then i realized when the power went out the UltraLite MK4 shut down and I never turned it back on. I was mostly using it for Web pages and listening to music with my Airpods. When the power came back on, my Mac worked fine. Last week we had a power outage that lasted 6 hours. I saw there was an update to macOS 11, so I went back to that version and installed the update. Again the Mac started shutting down without warning every few hours, even when just idle. ![]() A few days later I installed my favorite virtual synths, DP11 and the audio driver version 91429. I tried installing macOS 12 on an external drive. TG Pro has had no abnormal fans reading this whole time. ![]() It did! But every since then my Mac Pro has shut down randomly every few hours with code -3 "Multiple temperature sensors exceeded the defined limit." I cleaned out the computer and fans as I do every 3-6 months. Last month I saw MOTU Audio driver version 91429 was released in June, which was supposed to fix the lag problem. Beside the horrible lag problem that made it impossible to monitor live analog inputs from the MK4, it worked OK. I've had my Mac Pro 2019 and UltraLite MK4 a couple years. TL DR: Has anybody else had random Mac shutdowns (with cause -3 "Multiple temperature sensors exceeded the defined limit" since installing MOTU Pro Audio v91429 from June 21, 2022?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |