Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

BillieG

macrumors newbie
Original poster
Jun 22, 2017
4
0
New Orleans
I have a MacBookPro 3,1 (17 inch - 2.4 Ghz) model.
Processor: 2.6 Ghz Intel Core 2 Duo
Memory: 4 GB 667 MHz DDR2 SDRAM
Graphics: NVIDIA GeForce 8600M GT 128 MB
Running OS X El Capitan version 10.11.6
Due to overheating problems melting the solder points of the 256MB graphics card on the motherboard, we used an outside vendor to repair, they replaced the 256mb graphics chip with a 128mb graphics chip.
Except for the erratic kernel panics, which now happens about every month, the system works and performs good.
I did a clean reinstall of the OS, reset NVRAM(PRAM) and SMC, did disk checks, and I am trying to do an AHT which is scary as I do not know how to get the right link to download the AHT for my system. I am just clueless about what to do next, as I do not know what the panic report really says and what it all means.
Maybe one of you knows how to interpret the panic report? Or what might be wrong with my system or OS?
Thank you for the help...
Billie

Here's the latest report after late last nights crash:

Anonymous UUID: 4E336065-5DAA-CA10-4D52-6490A356C4EE

Thu Jun 22 11:50:26 2017

*** Panic Report ***
panic(cpu 0 caller 0xffffff8003998004): launchd exited (signal 9, exit status 0 CS_KILLED)

uuid info:
0x7fff6e48c000 uuid = <884763fc-cc0f-31cc-acc4-75a805ce401d>
0x109bb8000 uuid = <07cec787-54b0-3ba6-9ba7-7b4adbe20434>

Thread 4 crashed

RAX: 0x0000000000000000, RBX: 0x00007fff6e4cc5f8, RCX: 0x0000000109bb8a00, RDX: 0x0000000109c007c8
RSP: 0x000070000021ca40, RBP: 0x000070000021cac0, RSI: 0x00000000000001b1, RDI: 0x00007fff6e4cc5f8
R8: 0x00007fff88cb9119, R9: 0x0000000000000005, R10: 0x0000000000265e00, R11: 0x0000000109bf8170
R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0x0000000109bfe839
RFL: 0x0000000000010246, RIP: 0x00007fff6e4a64d0, CS: 0x000000000000002b, SS: 0x0000000000000023

Thread 0: 0xffffff800e963920
0x00007fff92846dcd
0x0000000000000000

Thread 1: 0xffffff800e689000
Could not read LR from frame at 0x0000700000116d48

Thread 2: 0xffffff800e8c9490
0x00007fff928557b5
0x0000000000000000

Thread 3: 0xffffff800eb00920
0x00007fff8fe75341
0x0000000000000000

Thread 4: 0xffffff801020f920
0x00007fff6e490063
0x00007fff88cb9262
0x0000000109bf8170
0x0000000109be5ba4
0x00007fff9284140b
0x00007fff92851675
0x00007fff92845a83
0x00007fff92846200
0x00007fff9284c707
0x00007fff92844d53
0x00007fff92844b00
0x00007fff8fe774de
0x00007fff8fe75341
0x0000000000000000

Thread 5: 0xffffff80131be240
0x00007fff94bc06c6
0x00007fff94bc05bd
0x0000000109be3349
0x00007fff92859324
0x00007fff9284140b
0x00007fff9284603b
0x00007fff9284c707
0x00007fff92844d53
0x00007fff92844b00
0x00007fff8fe774de
0x00007fff8fe75341
0x0000000000000000

Thread 6: 0xffffff8010c0d240
0x00007fff8fe75341
0x0000000000000000

Thread 7: 0xffffff8011cd7000
0x00007fff8fe75341
0x0000000000000000

Thread 8: 0xffffff8010654240
0x00007fff8fe75341
0x0000000000000000

Mac OS version: 15G1510
Kernel version: Darwin Kernel Version 15.6.0: Tue Apr 11 16:00:51 PDT 2017; root:xnu-3248.60.11.5.3~1/RELEASE_X86_64
Kernel UUID: 4BE0C0F5-2855-346B-8595-18FFCE9A51DC
System model name: MacBookPro3,1 (Mac-F42388C8)

System Profile:
Graphics: NVIDIA GeForce 8600M GT, GeForce 8600M GT, PCIe, 128 MB
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), Atheros 5416: 4.0.74.0-P2P
Bluetooth: Version 4.4.6f1 17910, 3 services, 26 devices, 1 incoming serial ports
PCI Card: pci168c,24, Other Network Controller, PCI Slot 5
Thunderbolt Bus:
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: Bluetooth HCI
USB Device: USB Bus
USB Device: USB Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: IR Receiver
USB Device: USB 2.0 Bus
USB Device: Built-in iSight
USB Device: USB 2.0 Bus
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F7F7FF70000, 0x00004B363435365536314535363637460000
Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F7F7FF70000, 0x00004B363435365536314535363637460000
Parallel ATA Device: MATSHITADVD-R UJ-85J
Serial ATA Device: SAMSUNG HM250JI, 250.06 GB
Network Service: Wi-Fi, AirPort, en1
Model: MacBookPro3,1, BootROM MBP31.0070.B07, 2 processors, Intel Core 2 Duo, 2.6 GHz, 4 GB, SMC 1.18f5
 

BillieG

macrumors newbie
Original poster
Jun 22, 2017
4
0
New Orleans

ab298

macrumors member
Jun 18, 2017
62
12
Thanks ab298,
From Every Mac:
Keywords=Mac-F42388C8
This serial number is for a 15-Inch PowerBook G4 (Gigabit Ethernet).
Mine is a 17" and is the
  • MacBookPro3,1 Mac-F4238BC8
It's not a serial number. Put only F42388C8 in the everymac search and it does return the MBP3.1

F4238BC8 is the 2.2GHz model,I believe.Yours shows as the 2.6, as recorded in the report.
 

BillieG

macrumors newbie
Original poster
Jun 22, 2017
4
0
New Orleans
It's not a serial number. Put only F42388C8 in the everymac search and it does return the MBP3.1

F4238BC8 is the 2.2GHz model,I believe.Yours shows as the 2.6, as recorded in the report.
Thank you ab298! :)
Your response made me try this command:
ioreg -l | awk -F\" '/board-id/ { print $4 }' in the terminal and it gave me the F42388C8.
I was using the wrong Hardware Test download!
Well, hopefully now it will work and I will maybe be able to see whether there is a hardware problem that causes it to crash once in a while.
Let's also hope that someone might just explain the Panic report to me... lol.
Thanks again from one MR newbie to another MR newbie ... :-D
 

ab298

macrumors member
Jun 18, 2017
62
12
I've seen suggestions that similar reports were due to a failing HD in conjunction with Time Machine backups; and others that did seem to be memory related.

Removing/cleaning/replacing both memory modules won't hurt. http://www.kelleycomputing.net/rember/
is more convenient & likely more thorough than AHT, albeit you would need to override the unidentified developer warning.
 

BillieG

macrumors newbie
Original poster
Jun 22, 2017
4
0
New Orleans
I've seen suggestions that similar reports were due to a failing HD in conjunction with Time Machine backups; and others that did seem to be memory related.

Removing/cleaning/replacing both memory modules won't hurt. http://www.kelleycomputing.net/rember/
is more convenient & likely more thorough than AHT, albeit you would need to override the unidentified developer warning.
Thanks for that link ... I see that it can help me further troubleshoot ...
I was able to run the Apple Hardware Test, ran the AHT both the short and extended versions, each one pass, and no troubles were found.
Will try the other one now ... but at kelley computing I also read something about the ''Easy Sleep or Smart Sleep'' corrupt file... so I might try that one too ... and then I keep thinking about the graphic memory downgrade to 128MB.
Anyway, thank you so much for the help ...
Love & Peace
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.