Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
Apple Computing Products:
macOS - Notebook Hardware
Strange hardware behavior
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="bcoffeyphoto" data-source="post: 1876298" data-attributes="member: 407137"><p>I'm running into this as well, had a 2019 iMac, worked with Apple, the OWC RAM manufacturer, was running Mojave at the time. RMA replacement on 128GB of RAM, that didn't fix it. Sent the 2019 into an Apple 3rd Party Repair Center (Apple was closed in CA due to COVID) they couldn't figure it out. Spent months on various support calls and emails from Apple, they finally RMA'd the 2019 iMac and shipped out a new 2020 iMac and the problem persists. Tested the RAM (which was replaced) kernel panicked, tried different sticks, kernel panics, finally got it working somehow through the tests...seemed better. Started a transfer of 5.6TB worth of data between two Thunderbolt RAID arrays, kernel panicked. I have another RMA out to replace the RAM for the second time, arriving Wednesday 2/17, after that if that doesn't fix it, I'll call OWC and see what else is going on. My issue is different than yours because it is a true panic, but there's definitely some similarities, primarily your log message that brought me here. First it was FinderSyncAPIExtension, so I killed all of those (Dropbox/Google/Adobe Finder Integrations) then it was</p><p></p><p>CVMCompiler[1635]: getattrlist failed for /System/Library/Extensions/AMDShared.bundle/Contents/Resources/cl_kernel.amd.dbl.fmath.pch: #2: No such file or directory</p><p></p><p>com.apple.xpc.launchd[1] (com.apple.mdworker.shared.10000000-0100-0000-0000-000000000000[1610]): Service exited due to SIGKILL | sent by mds[102] times 3 w/various numbers</p><p></p><p>Then com.apple.xpc.launchd[1] (com.apple.applefsplaceholder): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.</p><p></p><p>In that order, Panic, Reboot. </p><p></p><p>You're not alone man, I've been chasing this for 3 months, first on a 2019 iMac with Mojave, now on a brand new 2020 iMac with Big Sur. I'm losing my mind over here.</p></blockquote><p></p>
[QUOTE="bcoffeyphoto, post: 1876298, member: 407137"] I'm running into this as well, had a 2019 iMac, worked with Apple, the OWC RAM manufacturer, was running Mojave at the time. RMA replacement on 128GB of RAM, that didn't fix it. Sent the 2019 into an Apple 3rd Party Repair Center (Apple was closed in CA due to COVID) they couldn't figure it out. Spent months on various support calls and emails from Apple, they finally RMA'd the 2019 iMac and shipped out a new 2020 iMac and the problem persists. Tested the RAM (which was replaced) kernel panicked, tried different sticks, kernel panics, finally got it working somehow through the tests...seemed better. Started a transfer of 5.6TB worth of data between two Thunderbolt RAID arrays, kernel panicked. I have another RMA out to replace the RAM for the second time, arriving Wednesday 2/17, after that if that doesn't fix it, I'll call OWC and see what else is going on. My issue is different than yours because it is a true panic, but there's definitely some similarities, primarily your log message that brought me here. First it was FinderSyncAPIExtension, so I killed all of those (Dropbox/Google/Adobe Finder Integrations) then it was CVMCompiler[1635]: getattrlist failed for /System/Library/Extensions/AMDShared.bundle/Contents/Resources/cl_kernel.amd.dbl.fmath.pch: #2: No such file or directory com.apple.xpc.launchd[1] (com.apple.mdworker.shared.10000000-0100-0000-0000-000000000000[1610]): Service exited due to SIGKILL | sent by mds[102] times 3 w/various numbers Then com.apple.xpc.launchd[1] (com.apple.applefsplaceholder): Service only ran for 0 seconds. Pushing respawn out by 10 seconds. In that order, Panic, Reboot. You're not alone man, I've been chasing this for 3 months, first on a 2019 iMac with Mojave, now on a brand new 2020 iMac with Big Sur. I'm losing my mind over here. [/QUOTE]
Verification
Name this item 🌈
Post reply
Forums
Apple Computing Products:
macOS - Notebook Hardware
Strange hardware behavior
Top
