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

smallnshort247

macrumors 6502a
Original poster
Oct 23, 2010
531
8
Hey guys,

I don't understand why I keep getting Kernel Panics. I have replaced my RAM and HDD but the kernel panics started happening a few months before then. I then took my MacBook Pro to the Apple store and they kept it overnight. 3 days later I go to pick it up and they tell me they couldn't find anything wrong software or hardware wise. Their advice was to do a total clean install. So about a month later I did a total clean install, manually putting my stuff back on..not using time machine or migration assistant. I was going well until I just got ANOTHER kernel panic. I really thought doing the clean install would fix it. My mac has been running faster and less buggy after the clean install.

Whats your advice? Do you think the kernel panics will stop when I upgrade to the Mac OS X Lion? Like I said before, the kernel panics happened BEFORE I opened up my computer and upgraded the RAM and HDD, so putting the original parts back in I don't think will fix anything. Plus, after upgrading to 8GB of RAM, I don't think I can go back to 4GB...it wouldn't be the same.

Here are the specs of my MBP by the way..if it helps.

2.4Ghz Mid 2010 MacBook Pro 15 inch

Also, the kernel panics usually occur randomly at least once every 7 or so days. Every time it happens I'm usually running: safari, mail, adium, activity monitor, skype, echofon, and the drobo app.

Thanks for the help!
 
Take that back to Apple. Keep complaining until they fix or replace.

Kernel panics are caused by hardware issues, as I understand it. Keep hassling Apple while your machine is under warranty. You should not have to deal with this on your own.

P.S. if you still have the original HD and RAM, it might be to your benefit to put them back in before taking it to Apple. They gave my friend a hard time just because he didn't have the stock HD.
 
Take that back to Apple. Keep complaining until they fix or replace.

Kernel panics are caused by hardware issues, as I understand it. Keep hassling Apple while your machine is under warranty. You should not have to deal with this on your own.

P.S. if you still have the original HD and RAM, it might be to your benefit to put them back in before taking it to Apple. They gave my friend a hard time just because he didn't have the stock HD.

I still have the original HDD and RAM. The only problem is that I put my old HDD in my sisters Mac. I put my MBP on craigslist just for the heck of it and I got "real" offers as high as 1500 bucks. I bought it for 1788 so 200ish dollar difference is pretty good considering the laptop is 8 months old. It may just be easier to sell it and purchase the next generation of the MBP's possibly?
 
I still have the original HDD and RAM. The only problem is that I put my old HDD in my sisters Mac. I put my MBP on craigslist just for the heck of it and I got "real" offers as high as 1500 bucks. I bought it for 1788 so 200ish dollar difference is pretty good considering the laptop is 8 months old. It may just be easier to sell it and purchase the next generation of the MBP's possibly?

You could always do your best to get it fixed, then sell it if you still want to. Bottom line is that your machine obviously has a problem. Kernel panics should never happen on a healthy machine.

The only time I've experienced a kernel panic on one of my macs, it was a bad network card. That's just one example of possible causes. As far as I know, though, it's always a hardware issue that needs attention.

Personally, I wouldn't feel right selling a defective machine. At least not without full disclosure. There's no reason why you shouldn't be beating down the door at your local Apple store, demanding that this be fixed. If you're not getting good service at your nearest store, find the next nearest one. Sometimes the right people make all the difference.
 
You could always do your best to get it fixed, then sell it if you still want to. Bottom line is that your machine obviously has a problem. Kernel panics should never happen on a healthy machine.

The only time I've experienced a kernel panic on one of my macs, it was a bad network card. That's just one example of possible causes. As far as I know, though, it's always a hardware issue that needs attention.

Personally, I wouldn't feel right selling a defective machine. At least not without full disclosure. There's no reason why you shouldn't be beating down the door at your local Apple store, demanding that this be fixed. If you're not getting good service at your nearest store, find the next nearest one. Sometimes the right people make all the difference.

Considering its 8 months old and I didn't purchase Apple care for it yet. Do you think the chances of me being able to get a new unit is good? The condition of it is great..looks brand new. Do you recommend me calling Apple first or taking it to a different store? The place I took it usually gives great service. On my previous MacBook it had a dead pixel when I bought it and 30 days after buying it they still gave me a new unit. But yeah, so basically I should go in demanding a new unit because the computer is faulty?

They vibe they gave me was that if they couldn't find a problem with their "tests" nothing was wrong.
 
Kernel Panics

Just thought I would add my experiences with kernel panics. While I agree that hardware generally causes this issue, it is not the only reason. When I bought my latest MacBookPro, I experienced a kernel panic after using the migration assistant. It was persistent. I tried every trick in the book including, repairing permissions, reset PRAM and even reinstalling the OS. Nothing worked. I didn't want to go to the Apple Store because I despise working with the so-called Geniuses. So the only way I could eliminate the kernel panic was to boot from the install disk, completely erase the hard drive, reformat the hard drive and then reinstall everything. My machine works perfectly now and I haven't had a single kernel panic since. I know this procedure is a nightmare but it beats returning the machine and waiting for a new one.
 
How do I post the error? Is it the thing that comes up after I do the hard restart?

The error that is displayed after the hard restart is a file located under Library/Logs/CrashReporter, there will be files named after your machine. If you can attach one, or pm it, I'll have a look.

Are you running a 32but kernel, or 64? I've a 2010 MBP that kernel panics when I'm running a 64bit kernel, and I'm tethered to my iPhone via USB ( just a thought, do you experience panics when the Drobo dashboard isn't running? ). If I tether via Bluetooth or boot with a 32bit kernel, everything is fine.

Kernel panics are not always hardware related.
 
The error that is displayed after the hard restart is a file located under Library/Logs/CrashReporter, there will be files named after your machine. If you can attach one, or pm it, I'll have a look.

Are you running a 32but kernel, or 64? I've a 2010 MBP that kernel panics when I'm running a 64bit kernel, and I'm tethered to my iPhone via USB ( just a thought, do you experience panics when the Drobo dashboard isn't running? ). If I tether via Bluetooth or boot with a 32bit kernel, everything is fine.

Kernel panics are not always hardware related.

That's a cool tip I never knew about. Anywho, after doing the clean install, this was the first kernel panic that I've had, so I figure the past kernel panics were all erased in the log. The kernel panic that happened today should technically be in the folder but when restarting, the blue screen stayed up for over 2 minutes, usually it doesn't last that long. So I did another hard restart on top of the first hard restart which is why I'm guessing the kernel panic isn't logged. I don't see any crashes for today's date. All the other crashes logged aren't kernel panic related.
 
Just thought I would add my experiences with kernel panics. While I agree that hardware generally causes this issue, it is not the only reason. When I bought my latest MacBookPro, I experienced a kernel panic after using the migration assistant. It was persistent. I tried every trick in the book including, repairing permissions, reset PRAM and even reinstalling the OS. Nothing worked. I didn't want to go to the Apple Store because I despise working with the so-called Geniuses. So the only way I could eliminate the kernel panic was to boot from the install disk, completely erase the hard drive, reformat the hard drive and then reinstall everything. My machine works perfectly now and I haven't had a single kernel panic since. I know this procedure is a nightmare but it beats returning the machine and waiting for a new one.

I'm sure the Drobo has nothing to do with it. I just bought the Drobo for Christmas. These kernel panics have been happening months and months before I ever had a drobo
 
That's a cool tip I never knew about. Anywho, after doing the clean install, this was the first kernel panic that I've had, so I figure the past kernel panics were all erased in the log. The kernel panic that happened today should technically be in the folder but when restarting, the blue screen stayed up for over 2 minutes, usually it doesn't last that long. So I did another hard restart on top of the first hard restart which is why I'm guessing the kernel panic isn't logged. I don't see any crashes for today's date. All the other crashes logged aren't kernel panic related.

Hmmm, that's a shame. Did you have anything attached to your MBP? Was the Drobo app running? Something else, do you have any VM software installed? I had a BlackBook many moons ago with VMware installed, that would panic when the screen saver kicked in. Turned out the video driver did odd things with the VMware kernel extensions loaded.....
 
Hmmm, that's a shame. Did you have anything attached to your MBP? Was the Drobo app running? Something else, do you have any VM software installed? I had a BlackBook many moons ago with VMware installed, that would panic when the screen saver kicked in. Turned out the video driver did odd things with the VMware kernel extensions loaded.....

Yep, the drobo app is always running on my computer ever since I bought it..at least when its connected. I did have VMware on my mac before the clean install but it was torrented and I didn't feel like putting it back on my mac after the clean install since i wanted to limit the amount of pirated software on it since that could of been causing the problem. Now I have nothing but legit software on my mac and I still got the kernel panic :(
 
agentphish said:
Did you actually look in the console and not just look in the folder?

Just wanted to let you know that since my last message to you, I've had another kernel panic. When I did the hard restart the "report issue to apple" thing came up and I viewed the log and I saw it say something about "safari" I don't really know how to read a kernel panic log so I'm not sure what to say about it. I checked the log folder and It still didn't place the log there. I'm pretty confused. Next time it happens I'll be sure to copy and paste the log
 
I have the same laptop and have never had that happen.

Can u post the error the next time u get it?

Sun Jan 16 00:04:05 2011
panic(cpu 3 caller 0x2aab55): Kernel trap at 0x012dfd09, type 14=page fault, registers:
CR0: 0x80010033, CR2: 0x1f5aa06c, CR3: 0x00100000, CR4: 0x00000660
EAX: 0x1f5a9f80, EBX: 0x00000000, ECX: 0x0000000c, EDX: 0x1f5a9f00
CR2: 0x1f5aa06c, EBP: 0x834cbc18, ESI: 0x1f5a9f00, EDI: 0x6d142000
EFL: 0x00010246, EIP: 0x012dfd09, CS: 0x00000008, DS: 0x02e40010
Error code: 0x00000000

Backtrace (CPU 3), Frame : Return Address (4 potential args on stack)
0x834cba08 : 0x21b50c (0x5d4438 0x834cba3c 0x223974 0x0)
0x834cba58 : 0x2aab55 (0x59623c 0x12dfd09 0xe 0x596406)
0x834cbb38 : 0x2a09a8 (0x834cbb50 0xe3ff8001 0x834cbc18 0x12dfd09)
0x834cbb48 : 0x12dfd09 (0xe 0x48 0x834c0010 0x520010)
0x834cbc18 : 0x12fe657 (0x6d142000 0x1f5a9f00 0x0 0x0)
0x834cbc48 : 0x1308d0c (0x6d142000 0x1ee212dc 0x1f5a9f00 0x130889c)
0x834cbc78 : 0x1308e73 (0x1ee21000 0x6d142000 0x1ee21320 0x8)
0x834cbca8 : 0x12e246a (0x1ee21000 0x6d142000 0x834cbcd8 0x213ebb)
0x834cbcd8 : 0x53724b (0x6d142000 0xed69000 0xed69000 0x1)
0x834cbd28 : 0x5672a4 (0x6d142000 0xed69000 0xed69000 0x1)
0x834cbd88 : 0x286234 (0x6d142000 0xed69000 0x1 0x0)
0x834cbdf8 : 0x21d8ba (0x10d43168 0x10d3e384 0x10d43170 0x10d431a4)
0x834cbe38 : 0x210a3a (0x10d43100 0x834cbe7c 0xdc5c70c 0x834cbe70)
0x834cbe98 : 0x216c9d (0x10d43100 0x0 0x0 0x0)
0x834cbf18 : 0x294e13 (0x834cbf44 0x0 0x0 0x0)
0x834cbfc8 : 0x2a1018 (0xe381520 0x0 0x10 0x0)
Kernel Extensions in backtrace (with dependencies):
com.apple.driver.AppleIntelHDGraphics(6.2.6)@0x12de000->0x138cfff
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x99c000
dependency: com.apple.iokit.IONDRVSupport(2.2)@0x9cf000
dependency: com.apple.iokit.IOGraphicsFamily(2.2)@0x9ad000

BSD process name corresponding to current thread: Safari

Mac OS version:
10J567

Kernel version:
Darwin Kernel Version 10.6.0: Wed Nov 10 18:13:17 PST 2010; root:xnu-1504.9.26~3/RELEASE_I386
System model name: MacBookPro6,2 (Mac-F22586C8)

System uptime in nanoseconds: 25823182642747
unloaded kexts:
com.apple.driver.IOFireWireSerialBusProtocolSansPhysicalUnit 2.5.8 (addr 0x7bab8000, size 0x8192) - last unloaded 19553809943104
loaded kexts:
com.TrustedData.driver.VendorSpecificType00 1.3.7 - last loaded 19499803968617
com.DataRobotics.driver.iSCSIInitiator 1.4.31
com.apple.driver.AppleHWSensor 1.9.3d0
com.apple.driver.AppleBluetoothMultitouch 54
com.apple.driver.AGPM 100.12.19
com.apple.driver.AppleMikeyHIDDriver 1.2.0
com.apple.driver.AppleHDA 1.9.9f12
com.apple.driver.AppleMikeyDriver 1.9.9f12
com.apple.driver.AppleUpstreamUserClient 3.4.5
com.apple.driver.AppleMCCSControl 1.0.17
com.apple.driver.AudioAUUC 1.13
com.apple.driver.SMCMotionSensor 3.0.0d4
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AppleIntelHDGraphics 6.2.6
com.apple.driver.AppleIntelHDGraphicsFB 6.2.6
com.apple.kext.AppleSMCLMU 1.5.0d3
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AudioIPCDriver 1.1.6
com.apple.driver.ACPI_SMC_PlatformPlugin 4.5.0d5
com.apple.driver.AppleLPC 1.4.12
com.apple.GeForce 6.2.6
com.apple.driver.AppleGraphicsControl 2.8.68
com.apple.driver.AppleUSBTCButtons 200.3.2
com.apple.driver.AppleUSBCardReader 2.5.8
com.apple.driver.AppleUSBTCKeyboard 200.3.2
com.apple.driver.AppleIRController 303.8
com.apple.BootCache 31
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.iokit.SCSITaskUserClient 2.6.5
com.apple.iokit.IOAHCIBlockStorage 1.6.3
com.apple.driver.AppleUSBHub 4.1.7
com.apple.driver.AppleFWOHCI 4.7.1
com.apple.driver.AirPortBrcm43224 426.36.1
com.apple.iokit.AppleBCM5701Ethernet 2.3.9b6
com.apple.driver.AppleEFINVRAM 1.4.0
com.apple.driver.AppleSmartBatteryManager 160.0.0
com.apple.driver.AppleUSBEHCI 4.1.7
com.apple.driver.AppleAHCIPort 2.1.5
com.apple.driver.AppleACPIButtons 1.3.5
com.apple.driver.AppleRTC 1.3.1
com.apple.driver.AppleHPET 1.5
com.apple.driver.AppleSMBIOS 1.6
com.apple.driver.AppleACPIEC 1.3.5
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 105.13.0
com.apple.security.sandbox 1
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.11
com.apple.driver.AppleIntelCPUPowerManagement 105.13.0
com.apple.iokit.IOFireWireSerialBusProtocolTransport 2.0.1
com.apple.iokit.IOFireWireSBP2 4.0.6
com.apple.driver.AppleBluetoothHIDKeyboard 141
com.apple.driver.AppleHIDKeyboard 141
com.apple.driver.IOBluetoothHIDDriver 2.3.8f7
com.apple.driver.AppleMultitouchDriver 207.10
com.apple.driver.DspFuncLib 1.9.9f12
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.AppleSMBusController 1.0.8d0
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.iokit.IOSurface 74.2
com.apple.iokit.IOBluetoothSerialManager 2.3.8f7
com.apple.iokit.IOSerialFamily 10.0.3
com.apple.iokit.IOSCSIParallelFamily 2.0.1
com.apple.iokit.IOAudioFamily 1.8.0fc1
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleHDAController 1.9.9f12
com.apple.iokit.IOHDAFamily 1.9.9f12
com.apple.iokit.AppleProfileFamily 41
com.apple.driver.AppleSMC 3.1.0d3
com.apple.driver.IOPlatformPluginFamily 4.5.0d5
com.apple.driver.AppleSMBusPCI 1.0.8d0
com.apple.nvidia.nv50hal 6.2.6
com.apple.NVDAResman 6.2.6
com.apple.iokit.IONDRVSupport 2.2
com.apple.iokit.IOGraphicsFamily 2.2
com.apple.driver.BroadcomUSBBluetoothHCIController 2.3.8f7
com.apple.driver.AppleUSBBluetoothHCIController 2.3.8f7
com.apple.iokit.IOBluetoothFamily 2.3.8f7
com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.5
com.apple.iokit.IOUSBMassStorageClass 2.6.5
com.apple.driver.AppleUSBMultitouch 206.6
com.apple.iokit.IOUSBHIDDriver 4.1.5
com.apple.driver.AppleUSBMergeNub 4.1.5
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.5
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOAHCISerialATAPI 1.2.5
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.5
com.apple.iokit.IOUSBUserClient 4.1.5
com.apple.iokit.IOFireWireFamily 4.2.6
com.apple.iokit.IO80211Family 312
com.apple.iokit.IONetworkingFamily 1.10
com.apple.iokit.IOUSBFamily 4.1.7
com.apple.iokit.IOAHCIFamily 2.0.4
com.apple.driver.AppleEFIRuntime 1.4.0
com.apple.iokit.IOHIDFamily 1.6.5
com.apple.iokit.IOSMBusFamily 1.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 6
com.apple.driver.DiskImages 289
com.apple.iokit.IOStorageFamily 1.6.2
com.apple.driver.AppleACPIPlatform 1.3.5
com.apple.iokit.IOPCIFamily 2.6
com.apple.iokit.IOACPIFamily 1.3.0
 
I had another one a few hours the next day

Interval Since Last Panic Report: 399111 sec
Panics Since Last Report: 1
Anonymous UUID: C472DB13-019A-4A86-B5F1-D996A96062F1

Sat Jan 15 16:04:58 2011
panic(cpu 3 caller 0x2aab55): Kernel trap at 0xfff2f4f7, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0xfff2f4f7, CR3: 0x00100000, CR4: 0x00000660
EAX: 0x1a55af80, EBX: 0x00000000, ECX: 0x0000000c, EDX: 0x19e0b300
CR2: 0xfff2f4f7, EBP: 0x7422bc18, ESI: 0x19e0b300, EDI: 0x6bac0000
EFL: 0x00010246, EIP: 0xfff2f4f7, CS: 0x00000008, DS: 0x00000010
Error code: 0x00000010

Backtrace (CPU 3), Frame : Return Address (4 potential args on stack)
0x7422b9f8 : 0x21b50c (0x5d4438 0x7422ba2c 0x223974 0x0)
0x7422ba48 : 0x2aab55 (0x59623c 0xfff2f4f7 0xe 0x596406)
0x7422bb28 : 0x2a09a8 (0x7422bb40 0x8205300c 0x7422bc18 0xfff2f4f7)
0x7422bb38 : 0xfff2f4f7 (0xe 0xe3ff0048 0x6bac0010 0xc9c0010)
0x7422bc18 : 0x8233a657 (0x6bac0000 0x19e0b300 0x0 0x0)
0x7422bc48 : 0x82344d0c (0x6bac0000 0x195ce2dc 0x19e0b300 0x8234489c)
0x7422bc78 : 0x82344e73 (0x195ce000 0x6bac0000 0x195ce320 0x8)
0x7422bca8 : 0x8231e46a (0x195ce000 0x6bac0000 0x7422bcd8 0x213ebb)
0x7422bcd8 : 0x53724b (0x6bac0000 0xe44f5dc 0xe44f5dc 0x1)
0x7422bd28 : 0x5672a4 (0x6bac0000 0xe44f5dc 0xe44f5dc 0x1)
0x7422bd88 : 0x286234 (0x6bac0000 0xe44f5dc 0x1 0x0)
0x7422bdf8 : 0x21d8ba (0x19e79468 0xffa1a84 0x19e79470 0x19e794a4)
0x7422be38 : 0x210a3a (0x19e79400 0x7422be7c 0xc9aee18 0x7422be70)
0x7422be98 : 0x216c9d (0x19e79400 0x0 0x0 0x0)
0x7422bf18 : 0x294e13 (0x7422bf44 0x0 0x0 0x0)
0x7422bfc8 : 0x2a1018 (0x1a678a80 0x1 0x10 0x1a17a440)
Kernel Extensions in backtrace (with dependencies):
com.apple.driver.AppleIntelHDGraphics(6.2.6)@0x8231a000->0x823c8fff
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x7a646000
dependency: com.apple.iokit.IONDRVSupport(2.2)@0x81dd8000
dependency: com.apple.iokit.IOGraphicsFamily(2.2)@0x81e19000

BSD process name corresponding to current thread: Safari

Mac OS version:
10J567

Kernel version:
Darwin Kernel Version 10.6.0: Wed Nov 10 18:13:17 PST 2010; root:xnu-1504.9.26~3/RELEASE_I386
System model name: MacBookPro6,2 (Mac-F22586C8)

System uptime in nanoseconds: 49496849670762
unloaded kexts:
com.apple.driver.AppleWWANSupport 2.0.3b0 (addr 0x820e1000, size 0x12288) - last unloaded 44218792184688
loaded kexts:
com.TrustedData.driver.VendorSpecificType00 1.3.7 - last loaded 47669863948981
com.virginmobile.driver.Data 3.0.5
com.virginmobile.driver 3.0.5
com.DataRobotics.driver.iSCSIInitiator 1.4.31
com.apple.driver.StorageLynx 2.5.8
com.apple.driver.Oxford_Semi 2.5.8
com.apple.driver.LSI_FW_500 2.5.8
com.apple.driver.IOFireWireSerialBusProtocolSansPhysicalUnit 2.5.8
com.apple.driver.initioFWBridge 2.5.8
com.apple.driver.AppleBluetoothMultitouch 54
com.apple.driver.AppleHWSensor 1.9.3d0
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AGPM 100.12.19
com.apple.driver.AudioAUUC 1.13
com.apple.driver.AppleMikeyHIDDriver 1.2.0
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleUpstreamUserClient 3.4.5
com.apple.driver.AppleMikeyDriver 1.9.9f12
com.apple.driver.AppleIntelHDGraphics 6.2.6
com.apple.driver.AudioIPCDriver 1.1.6
com.apple.driver.AppleHDA 1.9.9f12
com.apple.driver.AppleMCCSControl 1.0.17
com.apple.driver.AppleIntelHDGraphicsFB 6.2.6
com.apple.driver.SMCMotionSensor 3.0.0d4
com.apple.iokit.AppleBCM5701Ethernet 2.3.9b6
com.apple.kext.AppleSMCLMU 1.5.0d3
com.apple.driver.AppleGraphicsControl 2.8.68
com.apple.GeForce 6.2.6
com.apple.driver.AirPortBrcm43224 426.36.1
com.apple.driver.ACPI_SMC_PlatformPlugin 4.5.0d5
com.apple.driver.AppleLPC 1.4.12
com.apple.driver.AppleUSBTCButtons 200.3.2
com.apple.driver.AppleUSBTCKeyboard 200.3.2
com.apple.driver.AppleUSBCardReader 2.5.8
com.apple.driver.AppleIRController 303.8
com.apple.iokit.SCSITaskUserClient 2.6.5
com.apple.BootCache 31
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.iokit.IOAHCIBlockStorage 1.6.3
com.apple.driver.AppleUSBHub 4.1.7
com.apple.driver.AppleFWOHCI 4.7.1
com.apple.driver.AppleUSBEHCI 4.1.7
com.apple.driver.AppleEFINVRAM 1.4.0
com.apple.driver.AppleSmartBatteryManager 160.0.0
com.apple.driver.AppleAHCIPort 2.1.5
com.apple.driver.AppleACPIButtons 1.3.5
com.apple.driver.AppleRTC 1.3.1
com.apple.driver.AppleHPET 1.5
com.apple.driver.AppleSMBIOS 1.6
com.apple.driver.AppleACPIEC 1.3.5
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 105.13.0
com.apple.security.sandbox 1
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.11
com.apple.driver.AppleIntelCPUPowerManagement 105.13.0
com.apple.iokit.IOFireWireSerialBusProtocolTransport 2.0.1
com.apple.iokit.IOFireWireSBP2 4.0.6
com.apple.driver.AppleMultitouchDriver 207.10
com.apple.nke.ppp 1.5
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.iokit.IOSurface 74.2
com.apple.iokit.IOBluetoothSerialManager 2.3.8f7
com.apple.driver.AppleBluetoothHIDKeyboard 141
com.apple.driver.AppleHIDKeyboard 141
com.apple.driver.IOBluetoothHIDDriver 2.3.8f7
com.apple.iokit.IOSCSIParallelFamily 2.0.1
com.apple.driver.DspFuncLib 1.9.9f12
com.apple.iokit.IOAudioFamily 1.8.0fc1
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleSMBusController 1.0.8d0
com.apple.iokit.IOSerialFamily 10.0.3
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.iokit.AppleProfileFamily 41
com.apple.driver.AppleHDAController 1.9.9f12
com.apple.iokit.IOHDAFamily 1.9.9f12
com.apple.iokit.IO80211Family 312
com.apple.iokit.IONetworkingFamily 1.10
com.apple.driver.AppleSMC 3.1.0d3
com.apple.driver.IOPlatformPluginFamily 4.5.0d5
com.apple.driver.AppleSMBusPCI 1.0.8d0
com.apple.nvidia.nv50hal 6.2.6
com.apple.NVDAResman 6.2.6
com.apple.iokit.IONDRVSupport 2.2
com.apple.iokit.IOGraphicsFamily 2.2
com.apple.driver.BroadcomUSBBluetoothHCIController 2.3.8f7
com.apple.driver.AppleUSBBluetoothHCIController 2.3.8f7
com.apple.iokit.IOBluetoothFamily 2.3.8f7
com.apple.driver.AppleUSBMultitouch 206.6
com.apple.iokit.IOUSBMassStorageClass 2.6.5
com.apple.iokit.IOUSBHIDDriver 4.1.5
com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.5
com.apple.driver.AppleUSBMergeNub 4.1.5
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.5
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOAHCISerialATAPI 1.2.5
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.5
com.apple.iokit.IOUSBUserClient 4.1.5
com.apple.iokit.IOFireWireFamily 4.2.6
com.apple.iokit.IOUSBFamily 4.1.7
com.apple.iokit.IOAHCIFamily 2.0.4
com.apple.driver.AppleEFIRuntime 1.4.0
com.apple.iokit.IOHIDFamily 1.6.5
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.TMSafetyNet 6
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 289
com.apple.iokit.IOStorageFamily 1.6.2
com.apple.driver.AppleACPIPlatform 1.3.5
com.apple.iokit.IOPCIFamily 2.6
com.apple.iokit.IOACPIFamily 1.3.0
System Profile:
Model: MacBookPro6,2, BootROM MBP61.0057.B0C, 2 processors, Intel Core i5, 2.4 GHz, 8 GB, SMC 1.58f15
Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 256 MB
Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.10.131.36.1)
Bluetooth: Version 2.3.8f7, 2 service, 19 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: SAMSUNG HM640JJ, 596.17 GB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfd100000
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0xfd110000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0xfd120000
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfa100000
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0xfa130000
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0236, 0xfa120000
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8218, 0xfa113000
FireWire Device: Rev2, Drobo, Up to 800 Mb/sec
 
Considering its 8 months old and I didn't purchase Apple care for it yet. Do you think the chances of me being able to get a new unit is good? The condition of it is great..looks brand new. Do you recommend me calling Apple first or taking it to a different store? The place I took it usually gives great service. On my previous MacBook it had a dead pixel when I bought it and 30 days after buying it they still gave me a new unit. But yeah, so basically I should go in demanding a new unit because the computer is faulty?

They vibe they gave me was that if they couldn't find a problem with their "tests" nothing was wrong.

Well, all I know is that their tests aren't infallible. As some above posters mentioned, it is true that kernel panics are not always due to hardware. In your case, however, with a clean installation, and no peripherals, there's a strong probability that your mac has a hardware glitch.

My friend's MacBook kept having a glitch that was unpredictable and difficult to repeat. The Geniuses kept telling him that nothing showed up on the tests. They even kept it overnight to run stress tests. Well, he kept bringing it in with the same problem until, finally, they basically refurbished the machine with a new logic board, etc. He hasn't had the glitch occur since.

I'm just saying that sometimes you have to be persistent. With your efforts at doing a clean install, I feel that you've proven the issue is not caused by anything you've done. At this point, it seems it's time for Apple to take care of it.
 
Well, all I know is that their tests aren't infallible. As some above posters mentioned, it is true that kernel panics are not always due to hardware. In your case, however, with a clean installation, and no peripherals, there's a strong probability that your mac has a hardware glitch.

My friend's MacBook kept having a glitch that was unpredictable and difficult to repeat. The Geniuses kept telling him that nothing showed up on the tests. They even kept it overnight to run stress tests. Well, he kept bringing it in with the same problem until, finally, they basically refurbished the machine with a new logic board, etc. He hasn't had the glitch occur since.

I'm just saying that sometimes you have to be persistent. With your efforts at doing a clean install, I feel that you've proven the issue is not caused by anything you've done. At this point, it seems it's time for Apple to take care of it.

Alrighty. And I don't remember if it was you or someone else who said that I should probably put back the stock parts before taking it back to Apple but I think I may do that. I'm 100% sure that the problems have been happening before even replacing one thing in my MacBook Pro but I'm not sure if they believe it. Plus, can't their tests detect if it was actually hardware related? They also kept my MacBook overnight for 3 days and said they couldn't find anything wrong. I think I want to keep everything inside it for now and make sure they see the logs (all 2 of them..and that they happened within hours of each other)
 
Alrighty. And I don't remember if it was you or someone else who said that I should probably put back the stock parts before taking it back to Apple but I think I may do that. I'm 100% sure that the problems have been happening before even replacing one thing in my MacBook Pro but I'm not sure if they believe it. Plus, can't their tests detect if it was actually hardware related? They also kept my MacBook overnight for 3 days and said they couldn't find anything wrong. I think I want to keep everything inside it for now and make sure they see the logs (all 2 of them..and that they happened within hours of each other)

Like I said, the tests are not perfect; they cannot show every little, possible hardware glitch. Also, glitches have a funny way of hiding themselves when the technician is looking.

Yes, I'm the one who advised you to put the stock parts back in. It's a silly thing, since most of the time the aftermarket parts are superior to what Apple stocks. They gave my friend a hard time because his drive wasn't stock. Even though every kind of possible test was run on the drive, and it showed not one bad sector, it was tainted in the eyes of the Apple people. :rolleyes:
 
Like I said, the tests are not perfect; they cannot show every little, possible hardware glitch. Also, glitches have a funny way of hiding themselves when the technician is looking.

Yes, I'm the one who advised you to put the stock parts back in. It's a silly thing, since most of the time the aftermarket parts are superior to what Apple stocks. They gave my friend a hard time because his drive wasn't stock. Even though every kind of possible test was run on the drive, and it showed not one bad sector, it was tainted in the eyes of the Apple people. :rolleyes:

Wow, I really wish I knew all this stuff before I did that clean install. I wish I knew how to check the logs before today. I could of looked at every single kernel panic and would of been able to tell for sure when they happened. I only have two panics in the log. Anywho, thanks so much for the help! I feel like I'm better prepared to duke this out with Apple before the 1 year limited warranty goes out.
 
Like I said, the tests are not perfect; they cannot show every little, possible hardware glitch. Also, glitches have a funny way of hiding themselves when the technician is looking.

Yes, I'm the one who advised you to put the stock parts back in. It's a silly thing, since most of the time the aftermarket parts are superior to what Apple stocks. They gave my friend a hard time because his drive wasn't stock. Even though every kind of possible test was run on the drive, and it showed not one bad sector, it was tainted in the eyes of the Apple people. :rolleyes:

What are the chances! I just got ANOTHER kernel panic when I was trying to reply to your msg. I was going to say that I did import my safari bookmarks to the new safari after doing the clean install. Wasn't sure if that could of caused it. So now 3 kernel panics within 2 days. For sure I've never had them happen this much.
 
I've just installed the stock ram on my mac and I'll be using it all day tomorrow to see if I get anymore kernel panics with the stock ram. If so, that pretty much confirms my case to the apple store.
 
I've heard of a lot of problems like this from these boards, friends,classmates, and colleagues. And they say macs are more reliable :rolleyes:
 
I've heard of a lot of problems like this from these boards, friends,classmates, and colleagues. And they say macs are more reliable :rolleyes:

Well, I still would say that I was left in way more headaches with my previous Dell.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.