Kernel Panic!!

J

jhferguson

Registered
Ok guys, I am a tech working for a mom and pop type computer shop. Unfortunately I am mostly a Windows guy and do not know a whole lot about Mac's. But I had a customer bring a Mac desktop into the shop the other day which was displaying constant kernel panics.

I have held down D on startup and ran the extended test. The information showed that all tests passed, but it only took 5 minutes or so, is that normal? I have also ran Memtest and the RAM checks out ok, plus I have checked the RAM one module at a time with the same result. A guy came in not long ago who is a Mac guy and said it was the video card but could not resolve our issue, so we took the video card out and placed it in a Windows environment and did not have any issues with it. Could it be the firmware?

Unfortunately I cannot boot to the original install disk to run any diagnostics. I put in the disk and hold down C and it spins, makes noise, and acts like it wants to boot up but I eventually get the same kernel panic that I started with. I am not familiar with the Mac OS but judging from my own research and the look of the kernel panic screen it is at least 10.3 or less.

I have the HD yanked out and am currently viewing it using Ubuntu Live so I can grab the kernel panic logs for you. Here is a copy of everything in the panic.log

I really appreciate all the help, if you need more info let me know. Thanks again guys

Mon Apr 19 02:27:01 2010
panic(cpu 2 caller 0x001A49CB): Unresolved kernel trap (CPU 2, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x000000c0, CR3: 0x01081000, CR4: 0x000006e0
EAX: 0x255bb438, EBX: 0x042b8004, ECX: 0x00000001, EDX: 0x00000000
CR2: 0x000000c0, EBP: 0x255bb468, ESI: 0x00000000, EDI: 0x00000040
EFL: 0x00010246, EIP: 0x006a4f1a, CS: 0x00000008, DS: 0x04340010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x255bb1e8 : 0x128d0d (0x3cc65c 0x255bb20c 0x131f95 0x0)
0x255bb228 : 0x1a49cb (0x3d2a94 0x2 0xe 0x3d22b8)
0x255bb338 : 0x19b3a4 (0x255bb350 0x1 0x255bb378 0x6d9587)
0x255bb468 : 0x6aa671 (0xc1d00001 0x8000000 0x8000003 0x40)
0x255bb4c8 : 0x6a0ec3 (0x255bb7e4 0x255bb788 0x0 0x3bd5d4)
0x255bb7a8 : 0x697527 (0x0 0x600d600d 0x7027 0x255bb7e4)
0x255bb858 : 0x810cf4 (0xc1d00001 0x8000000 0x8000003 0x40)
0x255bb888 : 0x80621f (0x23c9d000 0x0 0x0 0x0)
0x255bb8e8 : 0x8011e1 (0x23c9d000 0x8000000 0x15 0x23c9d01c)
0x255bb9c8 : 0x69233a (0x23c9d000 0x0 0x255bbad2 0x80)
0x255bba28 : 0x689133 (0x3ee9000 0x0 0x255bbad2 0x80)
0x255bbb58 : 0x68a813 (0x3ee9000 0x68dcac 0x255bbbfc 0x4)
0x255bbc18 : 0x675875 (0x3ee9000 0x1 0x0 0x3ee9000)
0x255bbc78 : 0x66f06b (0x3ee9000 0x5 0x5 0x3ee9000)
0x255bbc98 : 0x38c991 (0x3ee9000 0x3bfa1c0 0x3bfa1c0 0x0)
0x255bbce8 : 0x3b2df6 (0x3ee9000 0x3bfa1c0 0x3bfa1c0 0x0) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(4.5.6)@0x691000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5a9000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.8)@0x667000
dependency: com.apple.iokit.IONDRVSupport(1.4.8)@0x682000
com.apple.iokit.IONDRVSupport(1.4.8)@0x682000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5a9000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.8)@0x667000
com.apple.iokit.IOGraphicsFamily(1.4.8)@0x667000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5a9000

Kernel version:
Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386


*********

Fri Jun 11 14:43:07 2010
panic(cpu 3 caller 0x001A407F): Unresolved kernel trap (CPU 3, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x000000c0, CR3: 0x01238000, CR4: 0x000006e0
EAX: 0x2529b438, EBX: 0x03af7c04, ECX: 0x00000001, EDX: 0x00000000
CR2: 0x000000c0, EBP: 0x2529b468, ESI: 0x00000000, EDI: 0x00000040
EFL: 0x00010246, EIP: 0x3d512b52, CS: 0x00000008, DS: 0x04080010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2529b1e8 : 0x128cdb (0x3c9a14 0x2529b20c 0x131cdf 0x0)
0x2529b228 : 0x1a407f (0x3cf788 0x3 0xe 0x3cefb8)
0x2529b338 : 0x19ae94 (0x2529b350 0x1 0x2529b378 0x3d54716f)
0x2529b468 : 0x3d5182a9 (0xc1d00001 0x8000000 0x8000003 0x40)
0x2529b4c8 : 0x3d50eae1 (0x2529b7e4 0x2529b788 0x0 0x3ba94a)
0x2529b7a8 : 0x3d50541f (0x0 0x600d600d 0x7027 0x2529b7e4)
0x2529b858 : 0x3d67deaa (0xc1d00001 0x8000000 0x8000003 0x40)
0x2529b888 : 0x3d67387f (0x23976000 0x0 0x0 0x0)
0x2529b8e8 : 0x3d66e902 (0x23976000 0x8000000 0x15 0x2397601c)
0x2529b9c8 : 0x3d500332 (0x23976000 0x0 0x2529bad2 0x80)
0x2529ba28 : 0x3d30d19b (0x3a41000 0x0 0x2529bad2 0x80)
0x2529bb58 : 0x3d30e859 (0x3a41000 0x3d311cf0 0x2529bbfc 0x4)
0x2529bc18 : 0x355fd155 (0x3a41000 0x1 0x0 0x2529bdd4)
0x2529bc78 : 0x355f7065 (0x3a41000 0x0 0x0 0x3a41000)
0x2529bc98 : 0x38a1a9 (0x3a41000 0x38907d0 0x38907d0 0x0)
0x2529bce8 : 0x3b032a (0x3a41000 0x38907d0 0x38907d0 0x0) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(4.3.8)@0x3d4ff000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x35404000
dependency: com.apple.iokit.IONDRVSupport(1.4.4)@0x3d306000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.4)@0x355ef000
com.apple.iokit.IONDRVSupport(1.4.4)@0x3d306000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x35404000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.4)@0x355ef000
com.apple.iokit.IOGraphicsFamily(1.4.4)@0x355ef000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x35404000

Kernel version:
Darwin Kernel Version 8.7.3: Wed Aug 16 18:54:06 PDT 2006; root:xnu-792.11.5.obj~1/RELEASE_I386


*********

Fri Jun 11 14:59:16 2010
panic(cpu 0 caller 0x001A407F): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x000000c0, CR3: 0x01236000, CR4: 0x000006e0
EAX: 0x250b3438, EBX: 0x03a0a804, ECX: 0x00000001, EDX: 0x00000000
CR2: 0x000000c0, EBP: 0x250b3468, ESI: 0x00000000, EDI: 0x00000040
EFL: 0x00010246, EIP: 0x3d797b52, CS: 0x00000008, DS: 0x04080010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x250b31e8 : 0x128cdb (0x3c9a14 0x250b320c 0x131cdf 0x0)
0x250b3228 : 0x1a407f (0x3cf788 0x0 0xe 0x3cefb8)
0x250b3338 : 0x19ae94 (0x250b3350 0x1 0x250b3378 0x3d7cc16f)
0x250b3468 : 0x3d79d2a9 (0xc1d00001 0xe000000 0xe000003 0x40)
0x250b34c8 : 0x3d793ae1 (0x250b37e4 0x250b3788 0x0 0x3ba94a)
0x250b37a8 : 0x3d78a41f (0x0 0x600d600d 0x7027 0x250b37e4)
0x250b3858 : 0x3d902eaa (0xc1d00001 0xe000000 0xe000003 0x40)
0x250b3888 : 0x3d8f887f (0x23972000 0x0 0x0 0x0)
0x250b38e8 : 0x3d8f3902 (0x23972000 0xe000000 0x15 0x2397201c)
0x250b39c8 : 0x3d785332 (0x23972000 0x0 0x250b3ad2 0x80)
0x250b3a28 : 0x3d59219b (0x3b78400 0x0 0x250b3ad2 0x80)
0x250b3b58 : 0x3d593859 (0x3b78400 0x3d596cf0 0x250b3bfc 0x4)
0x250b3c18 : 0x355fb155 (0x3b78400 0x1 0x0 0x3b78400)
0x250b3c78 : 0x355f5065 (0x3b78400 0x5 0x5 0x3b78400)
0x250b3c98 : 0x38a1a9 (0x3b78400 0x388eae0 0x388eae0 0x0)
0x250b3ce8 : 0x3b032a (0x3b78400 0x388eae0 0x388eae0 0x0) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(4.3.8)@0x3d784000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x35402000
dependency: com.apple.iokit.IONDRVSupport(1.4.4)@0x3d58b000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.4)@0x355ed000
com.apple.iokit.IONDRVSupport(1.4.4)@0x3d58b000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x35402000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.4)@0x355ed000
com.apple.iokit.IOGraphicsFamily(1.4.4)@0x355ed000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x35402000

Kernel version:
Darwin Kernel Version 8.7.3: Wed Aug 16 18:54:06 PDT 2006; root:xnu-792.11.5.obj~1/RELEASE_I386


*********
 
The default test runs in a few minutes. That's not good enough as most problems, especially with RAM are not detected until much later.

Run the test in extended mode, looped. ctrl-L to get loop on, run extended for a few hours minimum (more in depth howto for that in howto&faq part of the board).

The panics above have a reference to the graphics (kernel).
Which per se could be software or hardware. So further digging needed...

Which exact Mac model is it? Mac Mini, iMac, Mac Pro..? Exact model number or fist 5 digits of the serial number (with the model of Mac) would also help.
The kernel version seems to resolve to 10.4.10 (or .11?). Unless the customer has bought a newer OS (10.5 or 10.6) we'll have to stick to 10.4.x for now.

Is there any more information on when the panics occurred? Were they doing something particular? Gaming, browsing, idle, sleep, wake from sleep, when it's been running for hours ..?
If booting to an install disc (of the same Mac OR of a later version of Mac OS X retail disc) did it also panic there or was it just hanging while waiting? (Were those discs you tried it with 10.5 or 10.6 retail discs, black in color?)
Did you try safe mode? holding down shift from startup until you see login screen (will take longer to boot).
 
Not sure of the exact model but the Serial number is G86441HKUPZ. I am guessing it is a Mac Pro, pretty good sized tower, dull silver in color. As far as I know the guy was using it like he always had (browsing the web, gaming, email) and it just started this kernel panic.

When booting from Disk 1 of 2 that came with the tower it acts like it wants to boot and even, most of the time, spins the disk but after about 5 minutes it will go to the Kernel panic screen asking me to turn off the computer. Unfortunately it does not say what version the disks are but they are a light gray in color. I did try safe mode and single user mode and the end result is very similar to when I attempt to boot to the disk, it acts like it wants to go but after 5 minutes or so I get the kernel panic screen again.

I have also cleared the PRAM and the NVRAM (I think that is what they were called) and that did not help either. I will unplug the drive and place it back in the desktop and run the looped test that you spoke of. I assume: hold down D to get to the test and ctrl+L while clicking on test?

Thanks for the fast response, all your patience, and your time
 
Code: 
com.apple.NVDAResman(4.5.6)@0x691000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5a9000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.8)@0x667000
dependency: com.apple.iokit.IONDRVSupport(1.4.8)@0x682000
com.apple.iokit.IONDRVSupport(1.4.8)@0x682000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5a9000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.8)@0x667000
com.apple.iokit.IOGraphicsFamily(1.4.8)@0x667000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5a9000
Quite likely the graphics card.

When you tested it in a Windows environment (which I assume means placing the card into a computer with Windows loaded), did you "stress" the computer to the point where it would tax the graphics card a bit?

The graphics card may not fail until it reaches a certain temperature, and running a graphics-intensive program in a loop may help the card to reach that temperature. Perhaps the Mac is more sensitive to the card than the Windows box is, which may explain why it failed in the Mac but worked reliably in a Windows computer.

If you can get your hands on another graphics card (which must be Mac-specific -- you can't use any old off-the-shelf, Windows graphics card in a Mac) and test with that, it would certainly narrow down the possibilities.

The crash log does have all fingers pointing toward a failure of the graphics card, though. Is the heatsink properly fitted, fans turn effortlessly, etc?
 
Check for blown/bulging caps on the video card. One of the video cards for that model of Mac Pro is the NVIDIA GeForce 7300 GT, which are famous for blown caps. Last time I worked on one of those with that card, Apple covered the cost of the repair because its a known issue.
 
ElDiablo - We did stress the card, but not for an extended period of time. Maybe 35 - 45 minutes. That includes gaming, browsing the web, and using some of the graphics tests found in the NVDIA software. Unfortunately we have not been able to get our hands on a different Mac specific card for testing, thats why we reversed the process and put the Mac card into the Windows machine. The heat sink feels firm, and it does not have a fan on it. One of my co-workers looked up a replacement and said it would be around $400+ which seems ridiculous for a 7300GT.

Djackmac - It is a 7300 GT. I have not checked for blown or swolen caps, but I will be sure and do that this morning when I go in. I hope it is something that simple.

Thanks for everyones input, patience, and time
 
Extended, looped, test came back with no issues, and we let it run overnight 226 passes.

The video card looks good. The heat sink is firm and there are no caps even slightly swollen
 
Ok guys check it out. With the video card in the machine and the ethernet chord plugged in. According to the DHCP table it was not pulling an IP address. Took out the card, left the network cable plugged in, booted it up, checked the DHCP table and was able to match the MAC address to an IP that was pingable and also ran tracert just to see. Both came back with positive results.

So it does look like the video card, which we tested further and have determined that there is a short in the card but are not able to pin point it so far. Although it still runs in a Windows machine, very strange. Anyway, we ordered a 7300GT from ebay and its on the way from New York. I will keep posting as updates come along. Thank you all for your time and patience, this is a good community of friendly helpful folks. Thanks again
 
I'd have the customer take that machine to an Apple authorized repair center. Even if it doesn't have bulging/blown caps, they still may be able to get one free from Apple. I haven't had a bad card like that yet without bulging/blown caps that I've tried to push through to Apple, but you never know? Better yet have the customer contact Apple telling them he had a bad video card diaged and have them tell Apple it is that card, and Apple might issue them a CS code to get it fixed.
 
Actually I called Apple attempting to troubleshoot it like it was my Mac and I was a home user and they told me that it wasn't under warranty any longer and I would have to pay $49 to speak with an expert. So I passed. But good advice none the less.
 
You must log in or register to reply here.
Back
Top