Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Mid 2010 Macbook Pro Kernal Panic

Hello,


My MacBook Pro (15-inch, Mid 2010) with 4GB RAM running on Yosemite has been restarting because of kernal panics for the past two years.


Initially the Panics began while using Photoshop CS6 and Final Cut 7, then previewing files caused the same issue and now panic loops are a regular occurance. The problem became much more pronounced 2 months ago when I used photoshop extensively, for some time I had been using my computer mainly for watching Netflix.


Below is the Panic Report. Is this a software or a hardware issue? I am aware that my computer is very old and much of the software out of date (I would subscribe to CC but it's out of my price range!). If I need to get a new computer so be it but if there is a way of resolving the I am very keen to hear it - I am very fond of my workhorse.


Anonymous UUID: E8427D17-E149-0991-9DD6-A7C58F39B644


Mon Dec 12 13:35:04 2022


*** Panic Report ***

Machine-check capabilities: 0x0000000000000c09

family: 6 model: 37 stepping: 5 microcode: 3

signature: 0x20655

Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz

9 error-reporting banks

panic(cpu 0 caller 0xffffff801aa1796a): "Machine Check at 0x00007fff901df433, registers:\n" "CR0: 0x0000000080010033, CR2: 0x00007f9a6af2d000, CR3: 0x000000001580c013, CR4: 0x00000000000226e0\n" "RAX: 0xffff8065950d4f70, RBX: 0x000000000000002a, RCX: 0x00000000000002a0, RDX: 0x00007fff5850ed38\n" "RSP: 0x00007fff5850ecd0, RBP: 0x00007fff5850ed20, RSI: 0x674c6b46840bf3cd, RDI: 0x0000000000000001\n" "R8: 0x000000000000003f, R9: 0x00007f9a6af2b090, R10: 0x00007f9a6c011ca0, R11: 0x00007f9a6af00000\n" "R12: 0x00007f9a6c011a00, R13: 0x00007fff7ce51e80, R14: 0x00007fff7ce52710, R15: 0x0000000000000040\n" "RFL: 0x0000000000000206, RIP: 0x00007fff901df433, CS: 0x000000000000002b, SS: 0x0000000000000023\n" "Error code: 0x0000000000000000\n"@/SourceCache/xnu/xnu-2782.70.3/osfmk/i386/trap_native.c:168

Backtrace (CPU 0), Frame : Return Address

0xffffff80b168bdd0 : 0xffffff801a92ae01

0xffffff80b168be50 : 0xffffff801aa1796a

0xffffff80b168bfb0 : 0xffffff801aa346df


BSD process name corresponding to current thread: apsd


Mac OS version:

14F2511


Kernel version:

Darwin Kernel Version 14.5.0: Sun Jun 4 21:40:08 PDT 2017; root:xnu-2782.70.3~1/RELEASE_X86_64

Kernel UUID: 9CB959EF-B0D4-3046-98E1-53536EA95A4F

Kernel slide: 0x000000001a600000

Kernel text base: 0xffffff801a800000

__HIB text base: 0xffffff801a700000

System model name: MacBookPro6,2 (Mac-F22586C8)


System uptime in nanoseconds: 12984190122

last loaded kext at 8551378987: com.apple.driver.AudioAUUC 1.70 (addr 0xffffff7f9ceab000, size 32768)

loaded kexts:

com.nvidia.CUDA 1.1.0

com.apple.driver.AudioAUUC 1.70

com.apple.filesystems.a



MacBook Pro

Posted on Dec 12, 2022 6:32 AM

Reply

Similar questions

8 replies

Dec 12, 2022 7:07 AM in response to joseppied

Hi,

Third party 's kernel extension could caused kernel panic. You installed "com.nvidia.CUDA 1.1.0" which could caused kernel panic, so try to delete it and see if you still get kernel panic.

If still get kernel panic, it could be possible that the hardware is something wrong. Try to check your MacBook Pro with Apple diagnostics or Apple Hardware Test if it reports hardware related error.

Use Apple Diagnostics to test your Mac - Apple Support


Dec 12, 2022 7:17 AM in response to joseppied

Machine check is very often a serious Hardware error.


Yours was detected in 9 different banks of memory or cache. That sort of result is what you get when a Mac with error-correcting code RAM detects an error, and most of the processors see it. But your model does not have error correction on the main memory.


It is possible that what is being reported is a parity error in cache memory. You MAY have a bad processor or cache.

Dec 12, 2022 8:15 AM in response to joseppied

Just as previously recommended, run the User diagnostic.


Unfortunately, the result may be 'no fault found' which is NOT the same as "all is well".


For the 2010 model and previous, the Apple Hardware Test diagnostic you can count on is on release Disc 2. The copy on the boot drive may have been erased a long time ago, in which case Command-D at startup will do nothing.

Mid 2010 Macbook Pro Kernal Panic

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.