Results 1 to 2 of 2
  1. #1

    Member Since
    May 15, 2018
    Old 17" Macbook pro keeps locking up any insight would be appreciated.crash log below

    If anyone out there could help analyze what's going on with my macbook pro 2009/2010 I would be very appreciative!
    I know it's a crazy old computer and most would say just cheuck it away....however I am a designer and they don't make these 17" laptops anymore so I really want to hang on to this one as the big sceen is awesome for design work.

    I was running 10.6.8 for the longest time. In the last few days it really started locking up with kernel panics and just unresponsive lockups.
    So I upgraded it to El Capitan 10.11.6 yesterday. Kernel panics aren't happening really anymore but still locking up a lot. Did a disk repair and message says everything is ok.
    I have new ram and new battery on the way right now . I know the battery for sure needs replacing. I thought I would replace and upgrade the ram at the same time...from 4gb to 8gb.

    I am hoping I just have bad RAM and that the battery was part of the problem. But if anyone has any ideas other than those two things after looking at the crash report below I would love to hear,
    I can answer any questions you have about my computer to the best of my ability if you have any.
    Macbook pro 17" mid 2009
    2.8 ghz intel core 2 duo
    4gb memory 1067 mhz ddr3

    I am typing on the computer right now and it hasn't locked up but I know it's coming LOL
    Thank you in advance.

    This was the latest crash log that was to be sent off to adobe:
    Anonymous UUID: 7B643E06-38C7-BC04-1FBF-93E0C88365A3

    Mon May 14 23:02:20 2018

    *** Panic Report ***
    panic(cpu 1 caller 0xffffff800d1ce6fa): Kernel trap at 0xffffff800d65e567, type 6=invalid opcode, registers:
    CR0: 0x0000000080010033, CR2: 0x00007fff5b541ef8, CR3: 0x000000012c41a000, CR4: 0x0000000000002660
    RAX: 0x0000000000000000, RBX: 0x0000000000000028, RCX: 0x0000000000000029, RDX: 0xffffff90a7b425ac
    RSP: 0xffffff90a7b42528, RBP: 0xffffff90a7b42540, RSI: 0x0000000000000044, RDI: 0xffffff8019463638
    R8: 0xffffff90a7b42d80, R9: 0x0000000000000027, R10: 0xffffff80193af200, R11: 0x0000000000000021
    R12: 0xffffff90a7b425b0, R13: 0xffffff90a7b42d7e, R14: 0xffffff8019463638, R15: 0xffffff90a7b43580
    RFL: 0x0000000000010216, RIP: 0xffffff800d65e567, CS: 0x0000000000000008, SS: 0x0000000000000010
    Fault CR2: 0x00007fff5b541ef8, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0

    Backtrace (CPU 1), Frame : Return Address
    0xffffff90a7b421b0 : 0xffffff800d0dab52
    0xffffff90a7b42230 : 0xffffff800d1ce6fa
    0xffffff90a7b42410 : 0xffffff800d1ec563
    0xffffff90a7b42430 : 0xffffff800d65e567
    0xffffff90a7b42540 : 0xffffff800d65d5eb
    0xffffff90a7b435d0 : 0xffffff800d65e2f6
    0xffffff90a7b43600 : 0xffffff7f8de5eb52
    0xffffff90a7b43650 : 0xffffff7f8de5e605
    0xffffff90a7b436b0 : 0xffffff800d71824a
    0xffffff90a7b43760 : 0xffffff800d57c7aa
    0xffffff90a7b43890 : 0xffffff800d5985f7
    0xffffff90a7b43c10 : 0xffffff800d596b51
    0xffffff90a7b43cc0 : 0xffffff800d595452
    0xffffff90a7b43f60 : 0xffffff800d628701
    0xffffff90a7b43fb0 : 0xffffff800d1ecd66
    Kernel Extensions in backtrace:[A1E91DE9-D69F-3E42-BDE8-4C4786993FE9]@0xffffff7f8de5b000->0xffffff7f8de6cfff

    BSD process name corresponding to current thread: xpcproxy

    Mac OS version:

    Kernel version:
    Darwin Kernel Version 15.6.0: Mon Aug 29 20:21:34 PDT 2016; root:xnu-3248.60.11~1/RELEASE_X86_64
    Kernel UUID: E349749B-3303-3DDF-959C-B5885A0E1F6E
    Kernel slide: 0x000000000ce00000
    Kernel text base: 0xffffff800d000000
    __HIB text base: 0xffffff800cf00000
    System model name: MacBookPro5,2 (Mac-F2268EC8)

    System uptime in nanoseconds: 23354467256
    last loaded kext at 2990031452: 245.4 (addr 0xffffff7f8f34d000, size 20480)
    loaded kexts: 245.4 4.4.6f1 3.0.1 eDataless 1.0.0d1 eZlib 1.0.0 38 245.4 245.4 327.6 3.7.7 2.8.5 5.5.4 800.20.24 2.0.22 3.1.8 1.0.1 1.0.1 161.0.0 2.0 1.8 4.0 2.1 4.0 1.7 t 218.0.0 163 3 8 218.0.0 1.0.1 250.5 1.0.1 900.4.1 3.7.7 1.8 1.8 1.8 5.0.0 5.0.0 1.0.1 3 2.6.2 3.7.7 4.6.1 1110.26 1.0.4 3.2 2.2.9 2.8.1 2.0 900.4.1 1.0.1 1.0.1 900.4.1 1.0.1 1.0.1 2.0 2.0.0 1.1 300.0 1.0.0d1 2 1.0.5 1.0 417.4 2.1 31 28.30 4.0 2.9 1.4 1 1 1.0
    Model: MacBookPro5,2, BootROM MBP52.008E.B05, 2 processors, Intel Core 2 Duo, 2.8 GHz, 4 GB, SMC 1.42f4
    Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
    Graphics: NVIDIA GeForce 9600M GT, NVIDIA GeForce 9600M GT, PCIe, 512 MB
    Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334548312D4346382020
    Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334548312D4346382020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (
    Bluetooth: Version 4.4.6f1 17910, 3 services, 18 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en1
    Serial ATA Device: Hitachi HTS545050B9SA02, 500.11 GB
    Serial ATA Device: MAT****ADVD-R UJ-868
    USB Device: USB Bus
    USB Device: BCM2046A
    USB Device: USB Bus
    USB Device: Apple Internal Keyboard / Trackpad
    USB Device: IR Receiver
    USB Device: USB 2.0 Bus
    USB Device: USB 2.0 Bus
    USB Device: Built-in iSight
    Thunderbolt Bus:

  2. #2

    chscag's Avatar
    Member Since
    Jan 23, 2008
    Keller, Texas
    2017 27" iMac, 10.5" iPad Pro, iPhone 6s+, iPhone 7+, Numerous iPods, High Sierra
    Welcome to our forums.

    Your post was moderated because of the kernel panic report and the fact that you're a new member. I approved the post so that it is now available for discussion.

    Your particular MacBook Pro is known for its GPU failures and was the subject of an Apple recall and free repair for several years. That option is long gone. The kernel panic report you posted does not show the GPU acting up but that's my strong suspicion with your model MacBook Pro.

    Also, why would you send the kernal panic report to Adobe? I can assure you they will either not respond or refer you to Apple. And since your MacBook Pro is vintage, Apple will refuse to work on it.

    Where are you located in Canada? You might be able to take your MacBook Pro to an authorized Apple repair service who might agree to work on it or provide diagnostics. You can try running your machine in Safe Mode to see if it runs without crashing.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. SSD Crash! Macbook Pro Mid 2014 15" Retina 2.2Ghz
    By Arkaedun in forum Apple Notebooks
    Replies: 9
    Last Post: 11-14-2014, 04:17 PM
  2. MacBook Pro logicboard issues? Help appreciated!
    By skaufman87 in forum Apple Notebooks
    Replies: 1
    Last Post: 04-27-2012, 09:01 PM
  3. Assassin's Creed crash macbook pro 13" 2011
    By Pris0wner in forum macOS - Apps and Games
    Replies: 2
    Last Post: 05-31-2011, 02:35 PM
  4. MacBook Pro 2010 15" CRASH
    By patbatchelder in forum Apple Notebooks
    Replies: 7
    Last Post: 05-26-2011, 01:53 PM
  5. MacBook Pro Screen Problem, Insight Needed.
    By Maweners in forum Apple Notebooks
    Replies: 0
    Last Post: 10-04-2009, 09:57 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts