macbook pro Impossible Kernel Panic, cant boot, cant reinstall, cant safe mode, cant recovery mode

Question

Level 1

8 points

macbook pro Impossible Kernel Panic, cant boot, cant reinstall, cant safe mode, cant recovery mode

What does this panic log mean?

I cant boot, cant install new copy of mac OS, cant enter safe mode, cant enter recovery mode, apple hardware test revealed no problems, i "reflowed" my gpu, i even place my macbook in the freaking freezer and no results.

I am ay my witts end, what does this log mean, anyone?

Anonymous UUID: F8460BEA-647C-9ED5-3242-FB522D787F24

Sun Dec 31 17:38:15 2000

*** Panic Report ***

panic(cpu 1 caller 0x001A8C8A): Kernel trap at 0x3527715b, type 14=page fault, registers:

CR0: 0x8001003b, CR2: 0x000000bc, CR3: 0x00c8a000, CR4: 0x00000660

EAX: 0x34279630, EBX: 0x03c8c404, ECX: 0x03d6f800, EDX: 0x00000000

CR2: 0x000000bc, EBP: 0x34279668, ESI: 0x00000000, EDI: 0xffffffff

EFL: 0x00010246, EIP: 0x3527715b, CS: 0x00000008, DS: 0x03d60010

Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x34279408 : 0x12b0f7 (0x458124 0x3427943c 0x133230 0x0)

0x34279458 : 0x1a8c8a (0x461650 0x3527715b 0xe 0x460e00)

0x34279538 : 0x19ece5 (0x34279550 0x9 0x34279668 0x3527715b)

0x34279548 : 0x3527715b (0xe 0x48 0x34270010 0x352b0010)

0x34279668 : 0x3527ef44 (0xc1d00005 0x1000000 0x1000003 0x40)

0x342796c8 : 0x35273ecf (0x34279858 0x6 0x0 0x0)

0x34279828 : 0x35267012 (0x0 0x600d600d 0x7027 0x34279858)

0x342798e8 : 0x3543a54b (0xc1d00005 0x1000000 0x1000003 0x40)

0x34279918 : 0x3544398f (0x23a05000 0x1000000 0x88100090 0x3e)

0x3427b8a8 : 0x35427c6e (0x23a05000 0x1000000 0x15 0x23a0501c)

0x3427b9a8 : 0x35261572 (0x23a05000 0x0 0x3427bab2 0x80)

0x3427ba08 : 0x2e3065a5 (0x3b62c00 0x0 0x3427bab2 0x80)

0x3427bb38 : 0x2e307d74 (0x3b62c00 0x2e30b358 0x3427bbec 0x4)

0x3427bc08 : 0x2e2f3133 (0x3b62c00 0x1 0x0 0x13)

0x3427bc68 : 0x2e2ec93a (0x3b62c00 0x2507 0x3427bd2c 0x438f448)

0x3427bc98 : 0x40ebc5 (0x3b62c00 0x438f448 0x438f448 0x0)

Backtrace continues...

Kernel loadable modules in backtrace (with dependencies):

com.apple.NVDAResman(5.2.6)@0x35260000->0x3549ffff

dependency: com.apple.iokit.IONDRVSupport(1.5.2)@0x2e300000

dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x2e364000

dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0x2e2e4000

com.apple.iokit.IONDRVSupport(1.5.2)@0x2e300000->0x2e30dfff

dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0x2e2e4000

dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x2e364000

com.apple.iokit.IOGraphicsFamily(1.5.2)@0x2e2e4000->0x2e2fffff

dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x2e364000

BSD process name corresponding to current thread: WindowServer

Mac OS version:

9C2031

Kernel version:

Darwin Kernel Version 9.2.1: Tue Feb 5 23:08:45 PST 2008; root:xnu-1228.4.20~1/RELEASE_I386

System model name: MacBookPro4,1 (Mac-F42C89C8)

Posted on Jul 11, 2019 9:39 PM

Reply

Answer 1

Jul 12, 2019 2:49 PM in response to Grant Bennet-Alder

1) Panic reason: [Addresses removed for simplicity]

panic: Kernel trap , type 14=page fault

a page fault is a reference to an address in memory that the task does not own. It is most often cased by memory problems. a flipped bit changes a valid address to an invalid reference, and that generates a page fault.

2) kernel extensions at the "scene of the crime":

Kernel Extensions in backtrace: [addresses they occupy edited out to make it easier to read]

com.apple.iokit.IOGraphicsFamily(2.4.1)

dependency: com.apple.iokit.IOPCIFamily(2.9)

com.apple.nvidia.classic.NVDAResmanTesla(10.0)

dependency: com.apple.iokit.IOPCIFamily(2.9)

dependency: com.apple.iokit.IONDRVSupport(2.4.1)

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)

com.apple.GeForceTesla(10.0)

dependency: com.apple.iokit.IOPCIFamily(2.9)

dependency: com.apple.iokit.IONDRVSupport(2.4.1)

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)

dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.0)

Now it is much easier to see that the path to the place where the kernel panic occurred was through the graphics Drivers (kernel extensions)

3) The BSD process where the problem occurred:

BSD process name corresponding to current thread: WindowServer

This does not run out memory problems. But both of your kernel panics occurred in graphics areas, and you said you had already "baked" your mainboard for GPU problems.

Reply

Answer 2

Jul 12, 2019 5:36 AM in response to seb197

It is important to understand that Apple hardware test says "No fault Found" and NOT "all is well" when it can't find anything in the minuscule amount of time it runs for.

You have Graphics extensions present at the "scene of the crime" in both cases.

It may be time to get a better old Mac than this 2008 model.

Reply

Answer 3

kaz-k

Level 9

51,102 points

Jul 11, 2019 10:07 PM in response to seb197

Page Fault tends to be RAM related issue, reseat RAM module and reboot could solve the issue.

It doesn't help, you would need to replace RAM module.

Reply

Answer 4

Jul 12, 2019 3:07 PM in response to Grant Bennet-Alder

sorry, that should read:

This does not Rule Out memory problems. But both of your kernel panics occurred in graphics areas, and you said you had already "baked" your mainboard for GPU problems.

Reply

Answer 5

Jul 13, 2019 12:48 PM in response to seb197

You should also read this thread for additional insights from Allan Jones:

Panic Report, any help with this ? - Apple Community

.

Reply

Answer 6

seb197 Author

Level 1

8 points

Jul 12, 2019 5:26 AM in response to kaz-k

In trying everything to figure out this kernel panic i also reseated the Ram, it didnt work.

I also replaced the pre-existing ram with others that i had laying around (i think i tried 3 different sticks, but their compatibility with macs is uncertain) which didnt work either. So replacing the RAM module is the only thing i havent tried.

Did i mention that Apple Hardware Test had no problems with RAM ?

I have one more kernel panic log to share:

Anonymous UUID: F8460BEA-647C-9ED5-3242-FB522D787F24

Sun Dec 31 17:40:47 2000

*** Panic Report ***

panic(cpu 1 caller 0xffffff8005817cc2): Kernel trap at 0xffffff7f88269483, type 14=page fault, registers:

CR0: 0x0000000080010033, CR2: 0x0000000000000010, CR3: 0x00000000639fc000, CR4: 0x0000000000002660

RAX: 0x3a83957bd9b10001, RBX: 0xffffff803c187000, RCX: 0xffffff80608d5000, RDX: 0xffffff8066003908

RSP: 0xffffff8066003ac0, RBP: 0xffffff8066003ac0, RSI: 0x0000000000000000, RDI: 0x0000000000000000

R8: 0x00000000000042ac, R9: 0xffffff800c0bfc60, R10: 0xffffff800db65040, R11: 0x000000000000003c

R12: 0x0000000000000000, R13: 0xffffff800e8a0800, R14: 0xffffff803c187000, R15: 0xffffff803c187000

RFL: 0x0000000000010293, RIP: 0xffffff7f88269483, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0x0000000000000010, Error code: 0x0000000000000000, Fault CPU: 0x1

Backtrace (CPU 1), Frame : Return Address

0xffffff8066003770 : 0xffffff800572bda1

0xffffff80660037f0 : 0xffffff8005817cc2

0xffffff80660039b0 : 0xffffff8005834b73

0xffffff80660039d0 : 0xffffff7f88269483

0xffffff8066003ac0 : 0xffffff7f8825292a

0xffffff8066003b10 : 0xffffff7f88252878

0xffffff8066003b30 : 0xffffff7f8822e056

0xffffff8066003b70 : 0xffffff7f867eb3dd

0xffffff8066003bc0 : 0xffffff7f867eb2f0

0xffffff8066003be0 : 0xffffff7f867ef808

0xffffff8066003c70 : 0xffffff7f867e7512

0xffffff8066003cb0 : 0xffffff7f87d1afe8

0xffffff8066003d00 : 0xffffff8005cb6a71

0xffffff8066003d50 : 0xffffff8005cfe175

0xffffff8066003dc0 : 0xffffff80057e26be

0xffffff8066003e10 : 0xffffff800573000c

0xffffff8066003e40 : 0xffffff80057149f3

0xffffff8066003e90 : 0xffffff800572531d

0xffffff8066003f10 : 0xffffff80058031ea

0xffffff8066003fb0 : 0xffffff8005835396

Kernel Extensions in backtrace:

com.apple.iokit.IOGraphicsFamily(2.4.1)[82EAD591-67E3-39CB-A232-A8095CA30E92]@0xffffff7f867dd000->0xffffff7f86817fff

dependency: com.apple.iokit.IOPCIFamily(2.9)[52E715FC-521D-3869-B2EA-5228FA4BEA34]@0xffffff7f85f24000

com.apple.nvidia.classic.NVDAResmanTesla(10.0)[796AE430-39FB-3255-8161-D52AFA28EE2B]@0xffffff7f87d17000->0xffffff7f87f7ffff

dependency: com.apple.iokit.IOPCIFamily(2.9)[52E715FC-521D-3869-B2EA-5228FA4BEA34]@0xffffff7f85f24000

dependency: com.apple.iokit.IONDRVSupport(2.4.1)[C0B8A85D-B32A-3F24-B4FC-B62B3BBF9E57]@0xffffff7f86824000

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[82EAD591-67E3-39CB-A232-A8095CA30E92]@0xffffff7f867dd000

com.apple.GeForceTesla(10.0)[5D1B0BFD-2642-35FD-AD39-C0652DA082E8]@0xffffff7f8822a000->0xffffff7f882f7fff

dependency: com.apple.iokit.IOPCIFamily(2.9)[52E715FC-521D-3869-B2EA-5228FA4BEA34]@0xffffff7f85f24000

dependency: com.apple.iokit.IONDRVSupport(2.4.1)[C0B8A85D-B32A-3F24-B4FC-B62B3BBF9E57]@0xffffff7f86824000

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[82EAD591-67E3-39CB-A232-A8095CA30E92]@0xffffff7f867dd000

dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.0)[796AE430-39FB-3255-8161-D52AFA28EE2B]@0xffffff7f87d17000

BSD process name corresponding to current thread: WindowServer

Mac OS version:

14D131

Kernel version:

Darwin Kernel Version 14.3.0: Mon Mar 23 11:59:05 PDT 2015; root:xnu-2782.20.48~5/RELEASE_X86_64

Kernel UUID: 4B3A11F4-77AA-3D27-A22D-81A1BC5B504D

Kernel slide: 0x0000000005400000

Kernel text base: 0xffffff8005600000

__HIB text base: 0xffffff8005500000

System model name: MacBookPro4,1 (Mac-F42C89C8)

Reply

Answer 7

seb197 Author

Level 1

8 points

Jul 15, 2019 7:52 AM in response to Grant Bennet-Alder

I forgot to mention, that this laptop before i wiped its hard-drive had Bootcamp installed, and even though Macintosh wouldnt boot due to Kernel Panic, Windows would load just fine.

Windows was fully functional. How do you explain faulty hardware in this case?

Reply

Answer 8

seb197 Author

Level 1

8 points

Jul 15, 2019 7:25 AM in response to Grant Bennet-Alder

Thanks

Reply

Answer 9

seb197 Author

Level 1

8 points

Jul 12, 2019 8:33 AM in response to Grant Bennet-Alder

>>You have Graphics extensions present at the "scene of the crime" in both cases.

Could you please explain this sentence? What are Graphics extensions and what are their significance in a kernel panic?

Thanks

Reply

Answer 10

Jul 12, 2019 2:36 PM in response to seb197

There are three quick take-aways from any panic report.

1) The panic-reason,

2) the kernel extensions present at the "scene of the crime" (shown in the " backtrace" which is the stored calling sequence of how you ended up where the panic occurred.)

3) the BSD process in which the problem occurred.

Take look at your other reports. What you are trying to determine is whether there is a TREND.

A Trend will sometimes point to the source of the problem. I will take apart your kernel panic in the next message.

Reply

Answer 11

Jul 15, 2019 11:12 AM in response to seb197

Windows likely does not understand or use the Dual Graphics, with its complex handing off between the two graphics processors, Integrated by default and also available Discrete.

The hobbyist hacks developed to save these Macs from the dustbin turn off the failed Discrete graphics and revert to just the Integrated graphics.

Reply

macbook pro Impossible Kernel Panic, cant boot, cant reinstall, cant safe mode, cant recovery mode

Similar questions