RandomInsano
New member
Used machine, no history. Has a large dent from a hard drop on the front-right side. Currently hitting random kernel panics whether the machine is hot or cold. No visible water damage on the back of the motherboard.
Because coreaudiod seems to be on the CPU most often during death, I wonder if the sound hardware is to blame. Test details below.
MacBook Pro (17-inch, Mid 2010)
2.53 GHz Intel Core i5
BTO/CTO
I'm expecting this is the particular motherboard given the date and processor specs, but I can get more details if needed.
http://www.powerbookmedic.com/MacBoo...2-p-24188.html
Processes on the current thread during crash:
Coreaudiod (more than twice)
kernel_task (more than twice)
com.apple.geod (once)
Steps to troubleshoot:
1. Swapped RAM and SSD, reinstalled macOS 10.13.6
2. Ran hard OpenGL and CPU processes
2. Ran Ubuntu Linux 2019.04, similar random apps crashing
3. Ran YouTube videos
4. Disabled on-board graphics, discreet graphics
I've managed to have the machine be fairly stable overnight playing audio *while muted* (left Google Play running for over eight hours without a crash), and I've pushed the discreet graphics hard with some WebGL aquarium demo and confirmed the GPU is being taxed by that with a tool called OpenGL Extensions Viewer:
https://webglsamples.org/aquarium/aquarium.html
https://apps.apple.com/us/app/opengl...er/id444052073
I've also run some 15-20 minute compiles and Cinebench R20 to make sure the CPU isn't the problem, and it seems to be unaffected.
To make sure the audio circuit wasn't the problem, I did try running YouTube videos through Bluetooth audio and crashing still occurs. It does.
I've tried disabling the internal graphics from the power pane in macOS and it still crashed. I've disabled discreet graphics with the NVRAM trick and it still crashes.
All of the above was done while plugged into power and fully charged. When battery dropped to ~%80 crashes happened in quick succession every three minutes or so (too short to be able to save the crash report text) until I plugged into power. I'll try and replicate again.
I'd appreciate some ideas on what to try and narrow down where on the PCB I should start checking for voltage/cracked traces.
Because coreaudiod seems to be on the CPU most often during death, I wonder if the sound hardware is to blame. Test details below.
MacBook Pro (17-inch, Mid 2010)
2.53 GHz Intel Core i5
BTO/CTO
I'm expecting this is the particular motherboard given the date and processor specs, but I can get more details if needed.
http://www.powerbookmedic.com/MacBoo...2-p-24188.html
Processes on the current thread during crash:
Coreaudiod (more than twice)
kernel_task (more than twice)
com.apple.geod (once)
Steps to troubleshoot:
1. Swapped RAM and SSD, reinstalled macOS 10.13.6
2. Ran hard OpenGL and CPU processes
2. Ran Ubuntu Linux 2019.04, similar random apps crashing
3. Ran YouTube videos
4. Disabled on-board graphics, discreet graphics
I've managed to have the machine be fairly stable overnight playing audio *while muted* (left Google Play running for over eight hours without a crash), and I've pushed the discreet graphics hard with some WebGL aquarium demo and confirmed the GPU is being taxed by that with a tool called OpenGL Extensions Viewer:
https://webglsamples.org/aquarium/aquarium.html
https://apps.apple.com/us/app/opengl...er/id444052073
I've also run some 15-20 minute compiles and Cinebench R20 to make sure the CPU isn't the problem, and it seems to be unaffected.
To make sure the audio circuit wasn't the problem, I did try running YouTube videos through Bluetooth audio and crashing still occurs. It does.
I've tried disabling the internal graphics from the power pane in macOS and it still crashed. I've disabled discreet graphics with the NVRAM trick and it still crashes.
All of the above was done while plugged into power and fully charged. When battery dropped to ~%80 crashes happened in quick succession every three minutes or so (too short to be able to save the crash report text) until I plugged into power. I'll try and replicate again.
I'd appreciate some ideas on what to try and narrow down where on the PCB I should start checking for voltage/cracked traces.
Last edited: