Kernel Panic - Restart Required

[neilmcg]

I'm wondering if anyone can confirm my suspicions here.
I have a MBP, it had a flickering screen (graphics card), so I got it fixed under warranty, then about a month after the fix, the MBP refused to wake - I took it back again and it was fixed.
Now the MBP is experiencing repeated kernel panics - especially after the any system update - there were a few recently.
The only solution seems to be switching the machine off and letting it cool.

It recognises that there is a problem after a successful boot - I have attached the Report. There seem to be references to graphics again - has anyone else seen anything like this?

Interval Since Last Panic Report: 703343 sec
Panics Since Last Report: 1
Anonymous UUID: BA80B9B9-D8BA-467A-8422-ACA4FBC0DD28

Sun Mar 14 09:11:45 2010
panic(cpu 1 caller 0x001AB0FE): Kernel trap at 0x00cccc1e, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x000000bc, CR3: 0x019f9000, CR4: 0x00000660
EAX: 0x6347d630, EBX: 0x07c3d004, ECX: 0x07be0000, EDX: 0x00000000
CR2: 0x000000bc, EBP: 0x6347d668, ESI: 0x00000000, EDI: 0xffffffff
EFL: 0x00010246, EIP: 0x00cccc1e, CS: 0x00000008, DS: 0x07be0010
Error code: 0x00000000

Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x6347d408 : 0x12b4c6 (0x45f91c 0x6347d43c 0x13355c 0x0) 
0x6347d458 : 0x1ab0fe (0x469a98 0xcccc1e 0xe 0x469248) 
0x6347d538 : 0x1a1713 (0x6347d550 0x9 0x6347d668 0xcccc1e) 
0x6347d548 : 0xcccc1e (0xe 0x48 0x63470010 0xd00010) 
0x6347d668 : 0xcd4baa (0xc1d00005 0x2000000 0x2000003 0x40) 
0x6347d6c8 : 0xcc728f (0x6347d858 0x6 0x0 0x0) 
0x6347d828 : 0xcb8402 (0x0 0x600d600d 0x7027 0x6347d858) 
0x6347d8e8 : 0xea601b (0xc1d00005 0x2000000 0x2000003 0x40) 
0x6347d918 : 0xeb17ac (0x42f4c000 0x2000000 0x88100090 0x3e) 
0x6347f8a8 : 0xe8d189 (0x42f4c000 0x2000000 0x15 0x42f4c01c) 
0x6347f9a8 : 0xcb3b29 (0x42f4c000 0x0 0x6347fab2 0x80) 
0x6347fa08 : 0xca869d (0x7706400 0x0 0x6347fab2 0x80) 
0x6347fb38 : 0xca9f44 (0x7706400 0xcad62c 0x6347fbec 0x4) 
0x6347fc08 : 0x7ccc18 (0x7706400 0x1 0x0 0x13) 
0x6347fc68 : 0x7c5be6 (0x7706400 0x5 0x5 0x7706400) 
0x6347fc98 : 0x415e83 (0x7706400 0x6f57234 0x6f57234 0x0) 
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.4.8)@0xcb0000->0xf0efff
dependency: com.apple.iokit.IONDRVSupport(1.7.3)@0xca2000
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x629000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x7bd000
com.apple.iokit.IONDRVSupport(1.7.3)@0xca2000->0xcaffff
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x629000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x7bd000
com.apple.iokit.IOGraphicsFamily(1.7.3)@0x7bd000->0x7d9fff
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x629000

BSD process name corresponding to current thread: WindowServer

Mac OS version:
9L31a

Kernel version:
Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386
System model name: MacBookPro5,1 (Mac-F42D86C8)

System uptime in nanoseconds: 30894725819
unloaded kexts:
(none)
loaded kexts:
com.Cycling74.driver.Soundflower	1.5.1
com.echofx.videoglide.kext.noseize.classic	1.0.0
com.echofx.usbvision.kext.noseize.classic	1.0.0
com.echofx.videoglide.kext.audio	1.0.0
com.echofx.usbvision.kext	1.0.0
com.echofx.videoglide.kext	1.0.0
com.roxio.BluRaySupport	1.1.6
at.obdev.nke.LittleSnitch	2.2.05
com.apple.driver.AppleHWSensor	1.9d0 - last loaded 30892926586
com.apple.filesystems.autofs	2.0.2
com.apple.driver.AppleHDAPlatformDriver	1.7.1a2
com.apple.iokit.IOBluetoothSerialManager	2.1.9f10
com.apple.driver.AppleMikeyHIDDriver	1.0.6
com.apple.driver.AppleUpstreamUserClient	2.7.5
com.apple.driver.AppleHDAHardwareConfigDriver	1.7.1a2
com.apple.driver.AppleHDA	1.7.1a2
com.apple.driver.AppleMikeyDriver	1.7.1a2
com.apple.driver.AGPM	100.8.7
com.apple.driver.AppleHDAController	1.7.1a2
com.apple.driver.SMCMotionSensor	2.1.1d2
com.apple.driver.AppleLPC	1.3.1
com.apple.Dont_Steal_Mac_OS_X	6.0.3
com.apple.iokit.IOFireWireIP	1.7.7
com.apple.kext.AppleSMCLMU	1.4.5d1
com.apple.driver.AppleIRController	113
com.apple.driver.AppleGraphicsControl	2.8.15
com.apple.driver.ACPI_SMC_PlatformPlugin	3.4.0a17
com.apple.driver.NVSMU	1.1.7
com.apple.driver.AppleSMBusPCI	1.0.1d1
com.apple.driver.AppleBacklight	1.6.0
com.apple.GeForce	5.4.8
com.apple.driver.AppleTyMCEDriver	1.0.0d28
com.apple.nvidia.nv50hal	5.4.8
com.apple.driver.AudioIPCDriver	1.0.6
com.apple.driver.AppleUSBTCButtons	1.7.4f1
com.apple.driver.AppleUSBMultitouch	189.35
com.apple.driver.AppleUSBTCKeyEventDriver	1.7.4f1
com.apple.driver.AppleUSBTCKeyboard	1.7.4f1
com.apple.driver.BroadcomUSBBluetoothHCIController	2.1.9f10
com.apple.driver.AppleUSBMergeNub	3.5.2
com.apple.iokit.SCSITaskUserClient	2.1.1
com.apple.driver.XsanFilter	2.7.91
com.apple.driver.AirPortBrcm43xx	366.91.21
com.apple.driver.AppleFWOHCI	3.9.7
com.apple.iokit.IOAHCISerialATAPI	1.1.2
com.apple.iokit.IOAHCIBlockStorage	1.2.3
com.apple.driver.AppleUSBHub	3.4.9
com.apple.iokit.IOUSBUserClient	3.5.2
com.apple.driver.AppleUSBEHCI	3.4.6
com.apple.driver.AppleAHCIPort	1.7.0
com.apple.nvenet	1.0.54
com.apple.driver.AppleFileSystemDriver	1.1.0
com.apple.driver.AppleUSBOHCI	3.4.6
com.apple.driver.AppleEFINVRAM	1.2.0
com.apple.driver.AppleSmartBatteryManager	158.10.5
com.apple.driver.AppleRTC	1.2.3
com.apple.driver.AppleHPET	1.4
com.apple.driver.AppleACPIPCI	1.2.5
com.apple.driver.AppleACPIButtons	1.2.5
com.apple.driver.AppleSMBIOS	1.4
com.apple.driver.AppleACPIEC	1.2.5
com.apple.driver.AppleAPIC	1.4
com.apple.security.seatbelt	107.12
com.apple.nke.applicationfirewall	1.6.77
com.apple.security.TMSafetyNet	3
com.apple.driver.AppleIntelCPUPowerManagement	76.2.0
com.apple.driver.DiskImages	199
com.apple.BootCache	30.4
com.apple.iokit.IOSerialFamily	9.4
com.apple.driver.DspFuncLib	1.7.1a2
com.apple.driver.AppleSMBusController	1.0.1d1
com.apple.iokit.IOHDAFamily	1.7.1a2
com.apple.driver.IOPlatformPluginFamily	3.4.0a17
com.apple.driver.AppleSMC	2.3.1d1
com.apple.NVDAResman	5.4.8
com.apple.iokit.IONDRVSupport	1.7.3
com.apple.iokit.IOGraphicsFamily	1.7.3
com.apple.iokit.IOUSBHIDDriver	3.4.6
com.apple.iokit.IOAudioFamily	1.6.9fc5
com.apple.kext.OSvKernDSPLib	1.1
com.apple.driver.AppleUSBBluetoothHCIController	2.1.9f10
com.apple.iokit.IOBluetoothFamily	2.1.9f10
com.apple.driver.AppleUSBComposite	3.2.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice	2.1.1
com.apple.iokit.IOSCSIBlockCommandsDevice	2.1.1
com.apple.iokit.IOBDStorageFamily	1.5
com.apple.iokit.IODVDStorageFamily	1.5
com.apple.iokit.IOCDStorageFamily	1.5
com.apple.iokit.IO80211Family	216.1
com.apple.iokit.IOFireWireFamily	3.4.9
com.apple.iokit.IOSCSIArchitectureModelFamily	2.1.1
com.apple.iokit.IOAHCIFamily	1.5.0
com.apple.iokit.IONetworkingFamily	1.6.1
com.apple.iokit.IOUSBFamily	3.5.2
com.apple.driver.AppleEFIRuntime	1.2.0
com.apple.iokit.IOSMBusFamily	1.1
com.apple.iokit.IOStorageFamily	1.5.6
com.apple.iokit.IOHIDFamily	1.5.5
com.apple.driver.AppleACPIPlatform	1.2.5
com.apple.iokit.IOPCIFamily	2.6
com.apple.iokit.IOACPIFamily	1.2.0

 

[MWPULSE]

What MacBook pro do you have there have been known issues with the gfx cards in the 2007/2008 models with the 8600. Which both apple n nvidia acknowledged.

For future reference. Alot of people ask questions about kernel panics n thus I think there is a sticky post in the forums somewhere. Or there is almost certainly a mac guide. Mroogle first eh?

Hope this helps

PTP

 

[neilmcg]

Yes, there are issues with the MBP late 2008 - and I did mention that the machine has been in twice for repair.

As you say sagely, often people ask about Kernel Panics and Google is a great search tool.

Having googled for a partial part of the kernel panic report, it actually lead me to macrumors , where in another post https://forums.macrumors.com/threads/701408/ - user wrldwzrd89 was able to analyse the report - I am hoping someone will also be able give me a similar quick answer.

Although just having joined this forum, I have been around Mac since about 1989 and have owned, administered and home serviced quite a few for myself, friends and family.
I have run through all the usual routines for isolating and trying to eliminating possible causes of the kernel panic.
http://www.thexlab.com/faqs/kernelpanics.html is a good reference. I guess you mean, http://guides.macrumors.com/Kernel_panic - although having googled, I've not found the sticky covering "kernel panics" - that you mentioned.

If I just put the MBP for service, I lose it for a week - if someone helps, with a pointer on the kernel panic report - then at least if it goes for service I know it's worth it.
I have not found any good references for this on google - so I'm hoping someone here either has experience of this or can decipher the report.

Just for others reference and potential google searchers;

The kernel panics were hardware based, not kext or other - in fact the graphics card again (third time.)

I took it into the Repair Centre and they immediately ordered a replacement part and it will be returned on Friday - under parts warranty.

...Mroogle first eh?

I find

site:forums.macrumors.com "kernel panic"

on google.com works just as well. ;-)

 

[m85476585]

Mroogle is a custom Google search for site:forums.macrumors.com, so it is exactly the same as typing site:forums.macrumors.com in google

 

[neilmcg]

Thanks for the reply - the google/mroogle issue seems to be generating the the replies, but no kernel related help.
I understand that posting gets peoples status upped, hence the following reply;

...For future reference. Alot of people ask questions about kernel panics n thus I think there is a sticky post in the forums somewhere. Or there is almost certainly a mac guide. Mroogle first eh?
Hope this helps

But I think the reply was pretty stock and I'm sure lots of people know about google and even custom searches.
I have used Macs for (almost) longer than he is old.
Given his lack of followup, it seems like a pat reply which results in his posting stats getting upped - nothing more.
I asked a question, with a proper description and a report. For courtesy I have also left a follow-up so anyone else experiencing this may benefit.
Thank you.

 

[m85476585]

I'm not sure what yo are asking. MWPULSE's reply mentioned Nvidia issues, and your second post seems to confirm that Apple is fixing it as a hardware issue. If you look at the KP log, you will see that it is a Nvidia problem.

Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.4.8)@0xcb0000->0xf0efff
dependency: com.apple.iokit.IONDRVSupport(1.7.3)@0xca2000
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x629000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x7bd000
com.apple.iokit.IONDRVSupport(1.7.3)@0xca2000->0xcaffff
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x629000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x7bd000
com.apple.iokit.IOGraphicsFamily(1.7.3)@0x7bd000->0x7d9fff
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x629000

The first line is the driver that caused the problem, and the rest of them are the drivers that the NVDAResman driver depends on. Based on the name, it's clearly a Nvidia issue. Since the Nvidia driver doesn't normally crash for no reason, that means the hardware was probably doing something it didn't expect.

It's not difficult to analyze a KP report (at least in the depth the average user can do). Just look at what the problem was traced to, and based on the name of the driver (if it is a driver), something related to that is likely causing the problem. All the hex codes (0x...) can't really be deciphered except by Apple, and the list of loaded Kexts at the bottom is just a list of everything on your system at the time. As far as I know, the section I quoted above is the only one with information useful to anyone but Apple.

It's likely that no one has posted a helpful response because either they don't know how to diagnose the problem, or because they assume (as I did) that your problem was resolved based on your second reply.

As far as I know, most users on here really are tying to help. There's not much reason to increase post count beyond 500 (at which point you can have an avatar).
https://macrumors.zendesk.com/hc/en-us#How_do_user_titles_work.3F
More posts does increase your "title", but does anyone really look at that except at a general indicator of someone's credibility? Some people post more than others, but as long as their posts are at least somewhat useful, I'd say they make a positive contribution to the forum. We get tired of answering the same questions over again, which is why a lot of times if someone asks a question, the first reply will be someone telling them to search first because it's likely already been asked or answered. There's also the MBP guide that attempts to address the most common questions, but it's not very complete yet.
http://guides.macrumors.com/MacBook_Pro_FAQ
I was able to write most of it by just looking at the most common threads in one week, taking my reply to one of them, editing it, and making it more general. I haven't had much time to work on the FAQ recently, but my goal is to be able to answer all the most commonly asked questions.

Of course I'm not saying that your problem is a common one, it's not.

 

[Eddyisgreat]

Sounds like a job for the Apple hardware test.