Kernel Panic with 10.6.1 disk utility

On the kids' iMac (20" unibody) after upgrading to 10.6.1, the boot camp partition would no longer boot (failed with a BSOD in WinXP), so I deleted it with the Boot Camp Assistant. Now, when running Disk Utility, in either "fix" or "verify" disk permissions, I get a kernel panic. This is not the case with my MBP, which I also upgraded to 10.6. Any ideas?

No dice. It gets to approximately the same place every time and panics, whether on Verify or Repair. I can run the Disk Utility from the Snow Leopard install CD and it completes fine. This is basically a plain vanilla factory Leopard installation that was upgraded to Snow Leopard, ostensibly without incident. I have no idea what could be going on.

Similar Messages

Kernel Panics with Toast 8

I kept getting kernel panics with iDVD and Toast 7. I upgraded to the iLife '08 and Toast 8, did all the software updates, and firmware updates to the DVD burner, but I'm still getting kernel panics. The computer's a PowerMac G5 dual 2.0 GHz, 3 GB RAM, LaCie Lightscribe DVD dual-layer burner.
Any ideas?
TIA

all software is up to date.
iDVD 5 is not compatible with Mac OS X 10.5 (Leopard). While this article indicates that the application may simply quit, other issues could also appear.
http://docs.info.apple.com/article.html?artnum=306062
Again, no mention of kernel panics, but Roxio has yet to release an update to Toast 7 to make it compatible with Mac OS X 10.5 (Leopard). An update is planned for the future.
http://kb.roxio.com/content/kb/Jam/000056T?set-locale=en
The text of the kernel panic itself may help some more knowledgeable people here to help determine what piece may be causing the trouble. Or if both crashes are related or separate. You can find the text of the panic in the Console utility.
-Doug

Frequent kernel panics with MPB 2.0 with 2GB RAM

I have been having frequent kernel panics with my MPB. I have 2GB of RAM that came pre-installed from the factory. This seems to happen most often when I am using external firewire drives. Has anyone out there had similar problems?

I've done the permission repairs. Also zapped the
PRAM. Ran the hardware test off the installer DVD
and it immediately came back with an error code
(4MEM/1/60000000:) and told me to contact Applecare.
I called Applecare and they were not very helpful.
The operator I spoke with had no idea what the
error code meant. He told me that RAM either works
or it doesn't. The PRAM zap was done at his
suggestion. Hasn't changed a thing. The kernel
panics have only grown more steady over the past
couple of weeks. More frustrating are frequent and
repeated application crashes (even simple stuff like
Safari, Mail, Address Book and Preview). Applecare
suggested I do a clean install of the OS. But it
sounds like a hardware issue to me. The app crashes
are occurring in different accounts on my MPB. I
don't want to spent a half-day reinstalling all of
my software only to have the issues continue. I'm
going to try to re-seat the RAM and then make an
appointment at the genius bar to have them take a
look at this. It had been running perfectly for the
first few weeks.
If you had an error code during the Hardware Test your MBP has a problem. The 4MEM/1/60000000: maybe linked to bad RAM or not seated correctly. If not seated correctly it will not boot, so it sounds like a bad RAM slot or memory stick.
William

Mac OS 10.5.6 downloaded Firefox 3.6.13 Came as .dmg When I try to launch it says "Not Recognized". Right click for "Open With" refers me to Disk Utility when same results "Not Recognized"

About my Mac > G5 Desktop OS 10.5.6
Want to upgrade to Firefox 3.6.13
The download comes as a compressed file in .dmg format. When I attempt to launch the .dmg file to decompress I get a error message that says: The following disk images failed to mount: Image > Firefox 3.6.13 Reason > Not Recognized. When I right click to see what opening app it is directed to it says: Open with "DiskImageMounter (default). Disk Utility is offered as another opening resource when I direct the file to Disk Utility and go to Menu Bar select "File" then select "Open Disk Image" (or Cmd + "O") I get the same result. Have tried downloading the file twice more and get the same results

Vk2mh it sounds like the download was not complete or corrupted. Where are you downloading the update from? Have you tried downloading again?

Kernel Panic with AppleIntelCPUPowerManagement on Macbook Pro Retina 15

Hello,
I'm getting Kernel Panic with grey "Death Screen". This happends 5 times. On 5-th of January (3 times) and on 8-th (2 times).
All the cases according to Consol reports have similar symphtoms:
panic(cpu 2 caller 0xffffff802aeb7e75): Kernel trap at 0xffffff7face2557e, type 13=general protection, registers:
Kernel Extensions in backtrace:
com.apple.driver.AppleIntelCPUPowerManagement(196.0)[F79878E3-8CF9-3ACF-B578-2CE 754CA61F8]@0xffffff7face0e000->0xffffff7face36fff
This line (besides many others) is different in reports
BSD process name corresponding to current thread: WindowServer (2 times)
And other one quicklookd, WebProcess and Web Service.
I sent all reports to Apple Support as MAC OS asked me about. BTW I can publish them again here.
Firstly, may be it's possible to figure out the reason of panics: Is this the SW or HW problem?
Guys at service told me to bring Macbook AS IS. But if this is the SW problem I can clean / reinstall OS etc. myself.
And (after cleaning and/or reinstalling) if the problem is in HW I'll be getting panics again. So I can bring to service Macbook with new history of panics.
So what is the probability of HW problem in such a case. When all reports point to the same .kext file.
Thank You in advance.
Cheers,
Victor
P.S.: Computer is new, I didn't change configuration, OS etc.
Installed programs under question: m3tag (Tag Editor - recompiled by somebody from WIndows program with some similar to CrossOver env.)
Adobe FlashPlayer Plugin

Thanks for reply.
Exactly - MP3Tag Wineskin port. I also think that here is the reason. This port is up-to-date (10.8.2 compatible) but very inacurate - I found many garbage in MP3Tag package. And the original Windows program is very old - 1984(?).
I removed this program from computer and I have to get a try for some period of time.

Kernel Panics with 10.4.7.

So, did anyone else SUDDENLY get Kernel Panics with the 10.4.7?

Hi, Anapharya.
No kernel panics on my Macs after 10.4.7 Update.
See my "Resolving Kernel Panics" FAQ. This FAQ includes step-by-step instructions for identifying and resolving some of the most common causes of kernel panics.
My FAQ is a roadmap: start at the beginning and work through to the end, including the "If all else fails..." section if a cause or resolution is not found in an earlier troubleshooting step therein.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Can I fix a disk with this message?-Disk Utility can't repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.

Can I fix a disk with this message?
Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.

Some problems can indeed be fixed this way. But working from Recovery_HD or Disk Warrior DVDs and working in the restricted environment those provide can be difficult. You can literally spend days working on this problem (while your regular work is unavailable) only to discover the old drive is unsalvageable.
There is no way to know up front whether you are facing a major Hardware failure or a minor software glitch, or something in between. Often you are forced to work from the drive you no longer trust. I continue to recommend you do this work from a different, fully functioning Mac OS X booted from a different drive.
If you have had the foresight to (as The hatter often recommends) clone your virgin install onto another drive for use in such situations, you will be able to recover from such problems in record time. If not, my previous recommendations stands:
Buy a new Drive. Or two. Install Mac OS X from scratch on a new drive, and get your Mac running again. Later, you can use the full power of Mac OS X to attempt to rescue your data, if needed. Then Zero the old drive, to see if it can hold data again reliably.
If the old drive eventually provides some needed data, and is salvageable, Merry Christmas.

Kernel panic with larch5.3 building CD!

Hi, could someone kindly help this.
I got the kernel panic with larch5.3 building CD. I didn't get any error messages during the creating. The error message of starting system is in belowing words.
:: Initializing writable layer for union (overlay)
/init: 193: /tfs/system/usr/bin/lzop: not found
/init: 193: /tfs/system/bin/tar not found
:Setting up union file system
unionfs: error accessing lower directory '/tfs/overlay' (error -2)
unionfs: read_super: error while parsing options (err= -2)
:: End of live system set-up
:: Initramfs Completed - control passing to kinit
Kernel panic - not syncing: Attempted to kill init!

Hi gradgrind, Thanks for your reply. Yes, I have added aufs, eject packages. But it seems still cannot work. Sorry for many troubles.
One think. When I create the iso file, it gives a warning message.
// Build without a profile? [y/N]: y
// ***** Creating live CD from system at ''
// This will delete EVERYTHING under ::: /.larch/cd :::
// I really mean it ... Are you sure you want to do this?
[y/N]: y
WARNING:
You seem to have installed a package containing modules
which aren't compatible with your kernel.
Please check that this won't cause problems.
Maybe you need the corresponding package
for your kernel?
chroot: cannot change root directory to pacman: No such file or directory
Package:
Continue? [y/N]: y
// Kernel version: 2.6.27-ARCH
// -> regenerating kernel dependencies
Using aufs
// copying cd-root to /.larch/cd
// copying kernel from /boot to /.larch/cd/boot/vmlinuz
// ... using vmlinuz26
// calling gen_larch_init to generate the initramfs
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]

Kernel Panic with Stripes

I've got a 3 year old 15" macbook pro that went into Kernel Panic with Stripes today. There was nothing plugged in except for a power supply. My wife said it was in sleep mode and then she opened it up and displayed the following screen.
/___sbsstatic___/migration-images/migration-img-not-avail.png
I've rebooted it a few times and the same thing keeps happening. I also plugged it into another machine and mounted it as a firewire drive and am currently copying all the files over to another drive.
Anyone have any ideas?
Thanks.

Bad or incompatible RAM is the most common cause of KP's. It could just need to be reset……. to make sure there's a good connection.
But, in your case.....Video Card? Just guessing from the stripes. Pay heed to running the +Apple Hardware Test+ in the following link.
Here's a great site for Resolving Kernel Panics. Please do all the steps in order, even if you don't think you need to do a certain step.
Here's a great MacFixIt article.
 Good Luck! DALE

Kernel panics with external mouse in clamshell mode

Have had more than 6 kernel panics; usually after waking; always in clamshell mode when using a Logitech wireless mouse (with or w/o software loaded) or Kensington USB trackball (with driver loaded but not worth using w/o driver). Does not happen with Apple USB mouse. Does not happen in laptop mode -- haven't tried laptop mode w/external mouse. Always on work Ethernet when in clamshell mode.
Has occurred w/OS 10.4.9 and 10.4.10. Have run extended Apple hardware test w/no results.
Have removed Logitech “LCC” file from user/library/application enhancers.
Have experienced panics w/a variety of apps open/active, including just Safari.
Any help greatly appreciated.
Here are panic logs:
==
panic(cpu 1 caller 0x003BDEB0): OSObject::refcount: Attempting to retain a freed object
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x362f3bb8 : 0x128d08 (0x3cb134 0x362f3bdc 0x131de5 0x0)
0x362f3bf8 : 0x3bdeb0 (0x3f0f9c 0x3f0f78 0x50efa04 0x4d609c0)
0x362f3c18 : 0x3c0d3b (0x4b62740 0x4ae958 0x28 0x3c09c4)
0x362f3c48 : 0x3c0e94 (0x4fd91c0 0x4d609c0 0x0 0x3c10ef)
0x362f3c68 : 0x3c188a (0x4d609c0 0x0 0x0 0x0)
0x362f3ca8 : 0x3c18f7 (0x4d609c0 0x4fd92c0 0x4fe32c0 0x1628d8)
0x362f3ce8 : 0x38663c (0x4d41800 0x0 0x362f3d28 0x3c1002)
0x362f3d08 : 0x389e5b (0x4d28480 0x4fe3040 0x0 0x4d28480)
0x362f3d28 : 0x3b1448 (0x4d28480 0x4fe3040 0x362f3d58 0x3bdfd9)
0x362f3d78 : 0x188511 (0x4d28480 0x52d89b4 0x52d89c8 0x11cc32)
0x362f3db8 : 0x12b4c3 (0x54b61b4 0x52d8998 0x0 0x0)
0x362f3df8 : 0x124b17 (0x54b6100 0x0 0x18 0x362f3edc)
0x362f3f08 : 0x195a42 (0x362f3f44 0x0 0x0 0x0)
0x362f3fc8 : 0x19b21e (0x55283e0 0x0 0x19e0b5 0x55283e0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0220508
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
==
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000000, CR3: 0x00e7d000, CR4: 0x000006e0
EAX: 0x0501cb40, EBX: 0x00000018, ECX: 0x004ae958, EDX: 0x050137a0
CR2: 0x00000000, EBP: 0x36473c48, ESI: 0x00000003, EDI: 0x06b5b7c0
EFL: 0x00010202, EIP: 0x00000000, CS: 0x00000008, DS: 0x00000010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x36473a18 : 0x128d08 (0x3cb134 0x36473a3c 0x131de5 0x0)
0x36473a58 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
0x36473b68 : 0x19ada4 (0x36473b80 0x206 0x36473bd8 0x1416ad)
0x36473c48 : 0x3c0e94 (0x6b5b7c0 0x4d8ab00 0x0 0x3c10ef)
0x36473c68 : 0x3c188a (0x4d8ab00 0x0 0x0 0x0)
0x36473ca8 : 0x3c18f7 (0x4d8ab00 0x6b5b940 0x6a21080 0x1628d8)
0x36473ce8 : 0x38663c (0x4d659c0 0x0 0x36473d28 0x3c1002)
0x36473d08 : 0x389e5b (0x4d44200 0x6b40100 0x0 0x4d44200)
0x36473d28 : 0x3b1448 (0x4d44200 0x6b40100 0x36473d58 0x3bdfd9)
0x36473d78 : 0x188511 (0x4d44200 0x53e7cb4 0x53e7cc8 0x11cc32)
0x36473db8 : 0x12b4c3 (0x5d579b4 0x53e7c98 0x0 0x0)
0x36473df8 : 0x124b17 (0x5d57900 0x0 0x18 0x36473edc)
0x36473f08 : 0x195a42 (0x36473f44 0x0 0x0 0x0)
0x36473fc8 : 0x19b21e (0x553c820 0x0 0x19e0b5 0x553c820) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb02203c8
==
panic(cpu 1 caller 0x001A429B): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000000, CR3: 0x00eac000, CR4: 0x000006e0
EAX: 0x05f522c0, EBX: 0x00000010, ECX: 0x004ae958, EDX: 0x05f522a0
CR2: 0x00000000, EBP: 0x364cbc48, ESI: 0x00000002, EDI: 0x05f7a040
EFL: 0x00010202, EIP: 0x00000000, CS: 0x00000008, DS: 0x00000010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x364cba18 : 0x128d08 (0x3cb134 0x364cba3c 0x131de5 0x0)
0x364cba58 : 0x1a429b (0x3d0e4c 0x1 0xe 0x3d0670)
0x364cbb68 : 0x19ada4 (0x364cbb80 0x202 0x364cbbd8 0x1416ad)
0x364cbc48 : 0x3c0e94 (0x5f7a040 0x4e040c0 0x0 0x3c10ef)
0x364cbc68 : 0x3c188a (0x4e040c0 0x0 0x0 0x0)
0x364cbca8 : 0x3c18f7 (0x4e040c0 0x5f9ffc0 0x5f9fcc0 0x1628d8)
0x364cbce8 : 0x38663c (0x4dfef40 0x0 0x364cbd28 0x3c1002)
0x364cbd08 : 0x389e5b (0x4dd4400 0x5f9fb00 0x0 0x4dd4400)
0x364cbd28 : 0x3b1448 (0x4dd4400 0x5f9fb00 0x364cbd58 0x3bdfd9)
0x364cbd78 : 0x188511 (0x4dd4400 0x56f88b4 0x56f88c8 0x11cc32)
0x364cbdb8 : 0x12b4c3 (0x51c6cb4 0x56f8898 0x0 0x0)
0x364cbdf8 : 0x124b17 (0x51c6c00 0x0 0x18 0x364cbedc)
0x364cbf08 : 0x195a42 (0x364cbf44 0x0 0x0 0x0)
0x364cbfc8 : 0x19b21e (0x55adea0 0x0 0x19e0b5 0x4c7bd08) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb011e3e8
==
panic(cpu 0 caller 0x00194914): pmap no pv_e's
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x3647bd28 : 0x128d08 (0x3cb134 0x3647bd4c 0x131de5 0x0)
0x3647bd68 : 0x194914 (0x3ce7d4 0x90cd3000 0x0 0x0)
0x3647bdf8 : 0x160ab6 (0x536c488 0x90cd3000 0x0 0xe2f9)
0x3647bf48 : 0x1a450e (0x13e0ce4 0x90cd3000 0x0 0x5)
0x3647bfc8 : 0x19acd4 (0x557cae0 0x0 0x19e0b5 0x4c8e4c0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffff8b8
==
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x0000002b, CR3: 0x00eae000, CR4: 0x000006e0
EAX: 0x05230e40, EBX: 0x00000020, ECX: 0x004b0958, EDX: 0xffffffff
CR2: 0x0000002b, EBP: 0x364abc48, ESI: 0x00000004, EDI: 0x0526dc40
EFL: 0x00010202, EIP: 0x003c1ca8, CS: 0x00000008, DS: 0x019e0010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x364aba28 : 0x128d08 (0x3cc0a4 0x364aba4c 0x131de5 0x0)
0x364aba68 : 0x1a4a55 (0x3d24b8 0x0 0xe 0x3d1cdc)
0x364abb78 : 0x19aeb4 (0x364abb90 0x1 0x364abb98 0x28)
0x364abc48 : 0x3c1e04 (0x526dc40 0x4f98200 0x0 0x3c205f)
0x364abc68 : 0x3c27fa (0x4f98200 0x0 0x0 0x0)
0x364abca8 : 0x3c2867 (0x4f98200 0x52e0080 0x5267c40 0x1628d8)
0x364abce8 : 0x38759c (0x4f92f40 0x0 0x364abd28 0x3c1f72)
0x364abd08 : 0x38adbb (0x4f91f80 0x5237440 0x0 0x4f91f80)
0x364abd28 : 0x3b23a8 (0x4f91f80 0x5237440 0x364abd58 0x3bef49)
0x364abd78 : 0x188511 (0x4f91f80 0x5a074b4 0x5a074c8 0x11cc32)
0x364abdb8 : 0x12b4c3 (0x5a070b4 0x5a07498 0x0 0x0)
0x364abdf8 : 0x124b17 (0x5a07000 0x0 0x18 0x364abedc)
0x364abf08 : 0x195a42 (0x364abf44 0x0 0x0 0x0)
0x364abfc8 : 0x19b32e (0x570c6c0 0x0 0x19e0b5 0x5332828) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb011e3e8
==
NOTE: This last one occurred with Kensington USB Trackball mouse and MouseWorks installed, after working successfully most of the day. Previous kernel panics were w/Logitech wireless mouse.
==
panic(cpu 1 caller 0x001A4A55): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000028, CR3: 0x0195d000, CR4: 0x000006e0
EAX: 0x0000001c, EBX: 0x05811020, ECX: 0x004b0958, EDX: 0x00417e60
CR2: 0x00000028, EBP: 0x370dbb28, ESI: 0x00000008, EDI: 0x004b0958
EFL: 0x00010206, EIP: 0x00390660, CS: 0x00000008, DS: 0x02490010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x370db8f8 : 0x128d08 (0x3cc0a4 0x370db91c 0x131de5 0x0)
0x370db938 : 0x1a4a55 (0x3d24b8 0x1 0xe 0x3d1cdc)
0x370dba48 : 0x19aeb4 (0x370dba60 0x780 0x0 0x200ab)
0x370dbb28 : 0x3c1cab (0x5811020 0x4b0958 0x120 0x3c1934)
0x370dbb58 : 0x3c1e04 (0x6093600 0x5d27c00 0x24 0x19a216)
0x370dbb78 : 0x387604 (0x5d27c00 0x24 0x370dbbb8 0x6c9dfc0)
0x370dbb98 : 0x38bfd4 (0x5d20c00 0x57be1e0 0x370dbbd8 0x3c3913)
0x370dbbf8 : 0x38aed3 (0x5d20c00 0x6d11f40 0x0 0x6048a00)
0x370dbc38 : 0x38b280 (0x6d11f40 0x4 0x0 0x6d0d040)
0x370dbc78 : 0x38b2dd (0x57c0de0 0x6d11f40 0x3b0bba 0x6d0d040)
0x370dbca8 : 0x38b331 (0x57c0de0 0x6d11f40 0x3b0bba 0x6d0d040)
0x370dbce8 : 0x3b1bce (0x57c0de0 0x6d11f40 0x3b0bba 0x6d0d040)
0x370dbd38 : 0x18c2fa (0x576d728 0x63c3094 0x63c30b0 0x6b967f8)
0x370dbdb8 : 0x12b4c3 (0x63c305c 0x657c7a4 0x370dbdf8 0x11e042)
0x370dbdf8 : 0x124b17 (0x63c3000 0x5768600 0x6816f48 0x0)
0x370dbf08 : 0x195a42 (0x370dbf44 0x0 0x0 0x0) Backtrace continues...

Greetings.
I'm having the same problem as Beanfield. I'm using a MX620 Logitech Wireless Laser Mouse, and it produces several problems under Mac OS X 10.4.10. The micro receiver is plugged to the rear of my iMac Intel Dual Core and altough I've switched it to the USB ports of my Apple Keyboard it still happens.The Kernel Panics (with the Grey Screen of Death) happen mostly when the mouse awakes the computer. Very often, when right clicking or single clicking items, the menus appear and disappear. Dragging items becomes impossible and even after restarting the iMac the problem persists.
It also interfers with the keyboard: sometimes the cursor blinks when moving and when I press any key on the keyboard, it resumes its normal activity. Recently I've added 1 G of RAM, but I've excluded it from the problem since it worked normaly with my now defunt Mighty Mouse. Also, I bought a 500 G Lacie external drive that works very well.
I'm getting very frustrated since this problems began only a few weeks after my purchases, which took in account full compatibility with my system. All drivers are correctly installed so...what's happening?
Best Regards
Pedro

Kernel panics with external Apple modem

This question has been raised before, but I'm revisiting it in hopes someone may have found a solution.
I'm getting frequent freezes and failures to awake from sleep, and a number of kernel panics that always implicate the faxmodem:
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleSM56KUSBAudio(1.9.14)@0x6d364000->0x6d37efff
dependency: com.apple.iokit.SM56KUSBAudioFamily(1.5.10)@0x6d34d000
dependency: com.apple.iokit.IOUSBFamily(3.1.5)@0x602000
com.apple.driver.AppleUSBUHCI(3.1.5)@0x8e1000->0x8eefff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x631000
dependency: com.apple.iokit.IOUSBFamily(3.1.5)@0x602000
com.apple.iokit.IOUSBFamily(3.1.5)@0x602000->0x629fff
When the USB modem is not connected I do not get these KPs.
Apparently there is a firmware conflict between this old Apple modem (I bought it for another machine in 2006) and Intel-based duo-core machines. The Apple Store people tell me the newest Apple USB modems are the same, that is, they have not been updated.
Any ideas? Do I have to buy another fax modem? I just use it for faxes.
Thanks.

Greetings.
I'm having the same problem as Beanfield. I'm using a MX620 Logitech Wireless Laser Mouse, and it produces several problems under Mac OS X 10.4.10. The micro receiver is plugged to the rear of my iMac Intel Dual Core and altough I've switched it to the USB ports of my Apple Keyboard it still happens.The Kernel Panics (with the Grey Screen of Death) happen mostly when the mouse awakes the computer. Very often, when right clicking or single clicking items, the menus appear and disappear. Dragging items becomes impossible and even after restarting the iMac the problem persists.
It also interfers with the keyboard: sometimes the cursor blinks when moving and when I press any key on the keyboard, it resumes its normal activity. Recently I've added 1 G of RAM, but I've excluded it from the problem since it worked normaly with my now defunt Mighty Mouse. Also, I bought a 500 G Lacie external drive that works very well.
I'm getting very frustrated since this problems began only a few weeks after my purchases, which took in account full compatibility with my system. All drivers are correctly installed so...what's happening?
Best Regards
Pedro

Problem with kernel panic message - Cannot boot from disk or usb

Hi Everyone,
I was wondering if someone could help me with a problem I've been trying to tackle for the last few days. I have a 24" iMac 2.33 Ghz Dual Core, with 2 gigs of RAM. A couple of days ago my computer crashed, and when I tried to boot up again I got the infamous grey screen kernel panic message ("You need to restart your computer..."). What's worse is that I get the same message when I try booting from my external drive and the installation disk itself.
I've basically planned on formatting since it's been a while anyway, but since I can't boot from my external drive or the installation disk that came with my computer these are not options at the moment. I can only get into the computer via safe mode. I've used disk utility to verify the disk, and it comes up with no errors. Anyways, I'd really appreciate if anyone had any advice on this. I've scoured the internet for advice about kernel panic messages, and they all suggest booting from disk or external drive etc., which is not a possibility for me right now.
Thanks

If you get a panic when trying to boot from the installation disc, and the disc is not scratched or dirty, then you have a hardware fault.
Make a "Genius" appointment at an Apple Store to have the machine tested.
Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to bare metal from any of them.) Don’t erase the recovery partition, if present.
*An SSD doesn't need to be zeroed.
There are several ways to back up a Mac that is unable to fully boot. You need an external hard drive to hold the backup data.
1. Boot into Recovery (command-R at startup) or from a local Time Machine backup volume (option key at startup.) Launch Disk Utility and follow the instructions in the support article linked below, under “Instructions for backing up to an external hard disk via Disk Utility.”
How to back up and restore your files
2. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire or Thunderbolt cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
How to use and troubleshoot FireWire target disk mode
3. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.

MORE kernel panics with 10.4.5

ok so i posted that i had kernel panics after updating to 10.4.1 etc. and after i installed the newest security update to 10.4.5 the kernel panics stopped...for half a month. now all of a sudden as april hits my screen keeps having little mini freezes(the curser freezes..then moves again after like 5 seconds..then another few seconds later my screen works again. grr. well apparently i also had "graphics card" panics the past 2 days. now as i mentioned i updated the security update and it fixed the driver issues that were mentioned as a problem with nvidia geforce2 graphics cards. now NOTHING has been changed on my comp and the panics are listing graphics cards as the i had before(listed below)
now as i type this i have had like 5 freeze ups. i have tried running disk utility and fixed permissions. and after i restarted after kp my screen was ALL messed up and showing lines and much stuff itwouldnt show icons unless i moused over them but my desktop pic wasnt complete either
Sun Apr 2 00:01:46 2006
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000026FC634E PC=0x0000000026F21E14
Latest crash info for cpu 0:
Exception state (sv=0x26D4F780)
PC=0x26F21E14; MSR=0x00009030; DAR=0x26FC634E; DSISR=0x40000000; LR=0x26F2282C; R1=0x12133B40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x26F236C4 0x26F2282C 0x26F3226C 0x26F15078 0x26F13D08 0x002EA4B8
0x0008C904 0x000291C0 0x000233AC 0x000AC02C 0x01C7E760
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x26eff000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x2227b000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x22212000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x22236000
dependency: com.apple.NVDAResman(4.1.8)@0x2c476000
Proceeding back via exception chain:
Exception state (sv=0x26D4F780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x27127500)
PC=0x9000B1E8; MSR=0x0000F030; DAR=0x1C2083E4; DSISR=0x42000000; LR=0x9000B13C; R1=0xBFFFEA40; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.5.0: Sun Jan 22 10:38:46 PST 2006; root:xnu-792.6.61.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x000A8384 0x000ABD00
Proceeding back via exception chain:
Exception state (sv=0x26D4F780)
PC=0x26F21E14; MSR=0x00009030; DAR=0x26FC634E; DSISR=0x40000000; LR=0x26F2282C; R1=0x12133B40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x26F236C4 0x26F2282C 0x26F3226C 0x26F15078 0x26F13D08 0x002EA4B8
0x0008C904 0x000291C0 0x000233AC 0x000AC02C 0x01C7E760
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x26eff000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x2227b000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x22212000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x22236000
dependency: com.apple.NVDAResman(4.1.8)@0x2c476000
Exception state (sv=0x27127500)
PC=0x9000B1E8; MSR=0x0000F030; DAR=0x1C2083E4; DSISR=0x42000000; LR=0x9000B13C; R1=0xBFFFEA40; XCP=0x00000030 (0xC00 - System ca`

hey thanks for your words of wisdom i will work thru to the best of my ability. my post wasnt complete as i would have liked it as my comp was driving me beyond insane so i just posted and quit to "walk away lest i KILL the machine". so i will add to it now. had another kp same ostensible reason. however after i restarted this morning the machine has been acting normal. so at least that allows me to go thru and try some trouble shooting things.
i have tech tool pro 4.1.1 which i believe is the newest update or at least as new as needed for compatibility and such. i ran it with no reported issues. i also have disk warrior(latest update) and ran that with no reported issues(tho i have heard that the new tech tool is superior). i DO have an external drive(maxtor one touchII). which before a driver upgrade was a source of issue with my system. but that was resolved easily. THEN i updated to the newest system point updates(10.4.1-10.4.4) and had problems with KP again IMMEDIATELY. listing grapics card as problem. well as update 10.4.5 listed nvidia graphics card driver updates in its list of features i managed(with much trouble) to update. still issues till i installed the security update then everything was honkydorey for about 20 days or so then all of a sudden graphics card issues. i WAS wondering if driver support problems could have damaged the card?
also however i remembered that i hadnt updated the system on my external(which i primarily use for storage and backup but my father installed Tiger on) OH says I that is still using the system that conflicts with the graphics card i will upgrade that...well i cant seem to do so. when i try to install the newest updates(one at a time 10.4.1-10.4.5) onto that system it starts to check the configurations and then suddenly says the installation failed/had errors and to try again. i assume that the packages are ok as they are the ones i borrowed from my father (since i was unable to download myself due to graphics card driver issues) to update my main comp and that worked fine.
i have at this point disconnected my external drive(temporarrily) as i suspect this contributes to the problem(not sure yet) but i would like to fix the problem not just avoid it.
i wouldnt have any problem wiping the system off of my external and just using it as storage again but i am not sure how to safely do that without losing my other files (i have over 19thousand music files(all legally bought tunes) stored there from loading my cd collection onto my comp. and not enuf room on my main comp to store them of course) i wonder if perhaps creating a file OUTSIDE they system for the music files should keep them safe? also how do i UNINSTALL a system? i have never done such a thing. or is there a better solution to update the system on my external?
thank you in advance for any advice you may have for me. and again thanks for the advice listed in the previous posts...i will definitly delve further into that.
imac 15 flat panel Mac OS X (10.4.5) maxtor OT2 300Gb external hd,ipod photo,isight

Kernel Panic with DiskWarrior 4.1

After upgrading my MacBook Pro (MacBookPro3,1 with 2GB RAM) to 10.5.3, DiskWarrior 4.1 will reliably trigger a kernel panic when trying to rebuild the directory of the partition on my external FireWire drive that is used for Time Machine backups. The KP happens every time at the end of Step 9 (Waiting for Mac OS X Services to complete). (I should also mention that Step 5 (Locating directory data) is now glacially slow, but eventually completes.) This partition also holds a bootable backup of my system made with SuperDuper. Since there are effectively 2+ copies of everything on my Mac placed on this drive, the file count is over 1.3 million. The text from the panic log is given below.
Wed May 28 22:19:34 2008
panic(cpu 1 caller 0x001A8CD4): Kernel trap at 0x08000004, type 13=general protection, registers:
CR0: 0x8001003b, CR2: 0x0010c2a4, CR3: 0x0143a000, CR4: 0x00000660
EAX: 0x04776fc0, EBX: 0x047d8600, ECX: 0x0bbc1f20, EDX: 0x0476f700
CR2: 0x0010c2a4, EBP: 0x34c33f38, ESI: 0x00000000, EDI: 0xe00002c2
EFL: 0x00010286, EIP: 0x08000004, CS: 0x00000008, DS: 0x0bbc0010
Error code: 0x00000000
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x34c33d08 : 0x12b0fa (0x459294 0x34c33d3c 0x133243 0x0)
0x34c33d58 : 0x1a8cd4 (0x4627fc 0x8000004 0xd 0x461f98)
0x34c33e38 : 0x19ede5 (0x34c33e50 0x6 0x34c33f38 0x8000004)
0x34c33e48 : 0x8000004 (0xe 0x130048 0x10 0xbbc0010)
0x34c33f38 : 0x348da5eb (0x47d8600 0x348da382 0x0 0x5)
0x34c33f78 : 0x13eb1d (0xaed8e00 0x0 0x1a236f 0xbbc1f20)
0x34c33fc8 : 0x19ebdc (0x0 0x0 0x1a20b5 0x41d5c80)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.alsoft.Preview(4.1)@0x348d7000->0x348ddfff
dependency: com.apple.iokit.IOStorageFamily(1.5.2)@0x72c000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9D34
Kernel version:
Darwin Kernel Version 9.3.0: Fri May 23 00:49:16 PDT 2008; root:xnu-1228.5.18~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)
I booted my Intel Mac mini from the DiskWarrior 4.1 CD (since the CD won't boot the MBP) and tried to rebuild the FireWire disk's directory from there, but the operation fails with a 2154 error (low on RAM error message). I then erased the Time Machine partition and backed up the MacBook Pro to it again using SuperDuper only (Time Machine is off for now). Now with only ~650,000 files on the partition, DiskWarrior will rebuild the directory with no complaints. This partition showed no errors in Disk Utility before being erased.
This machine is otherwise flawless with 10.5.3 under moderately heavy usage and these DiskWarrior operations worked flawlessly under 10.5.2. Is anyone else experiencing this?

PFloyd1973,
That exact Kernal Panic happened on my system and the backtrace reported the same fault.
You should forward this information to Alsoft. After reading your post I sent an email with a copy of the Kernel Panic.
I have my doubts that DiskWarrior is designed (or should be used) to rebuild the directory of a volume which contains a Time Machine Backup. I graphed the directory before attempting a rebuild, and somewhere around 37% was out of order. I just wanted to see what would happen when I tried the rebuild and was not surprised when I got a Kernel Panic.
;~)

Kernel Panics with Mountain Lion

Hello everyone!
I am having some problems with my Macbook Pro. I purchased it in late 2010 for school and ever since I upgraded the software to Mountain Lion, I've noticed some kernel panic crashes. Around April, shortly after upgrading, I noticed that it was crashing once a day. That progressed to crashing every hour. After checking the Console Log, I realized that an antivirus program I installed (Sophos) was constantly scanning every time it crashed. After I uninstalled it, I had no more crashes until very recently.
Now my MBP is back to crashing once every few hours. Based on the panic report, is this possibly related to the known graphics card problem with this model? If so, then why has it not surfaced until after I upgraded? I'm really hoping that is not the case. I tried going into Safe Mode and fixing the disk permissions and that doesn't seem to have affected anything.
Attached is the most recent report.
Any help is appreciated!
Interval Since Last Panic Report: 126084 sec
Panics Since Last Report:          1
Anonymous UUID:                    21E2CC7C-B250-62A1-C464-153B2E11FA3E
Fri Nov 7 16:37:24 2014
panic(cpu 2 caller 0xffffff7f83ebcf1a): "GPU Panic: [<None>] 3 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff807e3a9000 0x0a5480a2, D0, P2/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.5/src/AppleM uxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 2), Frame : Return Address
0xffffff807d73b190 : 0xffffff8001c1d636
0xffffff807d73b200 : 0xffffff7f83ebcf1a
0xffffff807d73b2d0 : 0xffffff7f824d988c
0xffffff807d73b390 : 0xffffff7f825ac85a
0xffffff807d73b3d0 : 0xffffff7f825ac8b8
0xffffff807d73b440 : 0xffffff7f82872280
0xffffff807d73b570 : 0xffffff7f825d5345
0xffffff807d73b590 : 0xffffff7f824e065f
0xffffff807d73b640 : 0xffffff7f824de0f6
0xffffff807d73b840 : 0xffffff7f824df03e
0xffffff807d73b920 : 0xffffff7f8338efc0
0xffffff807d73b960 : 0xffffff7f8339edf7
0xffffff807d73b980 : 0xffffff7f833cde1f
0xffffff807d73b9c0 : 0xffffff7f833cde7d
0xffffff807d73ba00 : 0xffffff7f833a4bcf
0xffffff807d73ba50 : 0xffffff7f8336f022
0xffffff807d73bae0 : 0xffffff7f8336adba
0xffffff807d73bb10 : 0xffffff7f8336897b
0xffffff807d73bb40 : 0xffffff800206ec83
0xffffff807d73bbc0 : 0xffffff8002070d13
0xffffff807d73bc20 : 0xffffff800206e74f
0xffffff807d73bd70 : 0xffffff8001c98c21
0xffffff807d73be80 : 0xffffff8001c20b4d
0xffffff807d73beb0 : 0xffffff8001c10448
0xffffff807d73bf00 : 0xffffff8001c1961b
0xffffff807d73bf70 : 0xffffff8001ca6546
0xffffff807d73bfb0 : 0xffffff8001ccf473
      Kernel Extensions in backtrace:
         com.apple.driver.AppleMuxControl(3.4.5)[4F710151-D347-301D-A0BA-81791B3E8D4D]@0 xffffff7f83eaf000->0xffffff7f83ec1fff
            dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[B5B1F368-132E-3509-9ED5-93270E3ABB DD]@0xffffff7f83eaa000
            dependency: com.apple.iokit.IOPCIFamily(2.8)[6C1D646D-7E5E-3D7F-A557-2CBA398FF878]@0xffffff 7f82248000
            dependency: com.apple.driver.AppleGraphicsControl(3.4.5)[4A2C8548-7EF1-38A9-8817-E8CB34B8DC A6]@0xffffff7f83e96000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[A35915E8-C1B0-3C0F-81DF-5515BC9002FC]@0xfffff f7f821f3000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[F16E015E-1ABE-3C40-AC71-BC54F4BE442E]@0xff ffff7f82464000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[9928306E-3508-3DBC-80A4-D8F1D87650D7]@0 xffffff7f82421000
         com.apple.NVDAResman(8.1.6)[39D35403-42FB-3F08-999C-9866938D6B3A]@0xffffff7f824 78000->0xffffff7f8271bfff
            dependency: com.apple.iokit.IOPCIFamily(2.8)[6C1D646D-7E5E-3D7F-A557-2CBA398FF878]@0xffffff 7f82248000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[F16E015E-1ABE-3C40-AC71-BC54F4BE442E]@0xff ffff7f82464000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[9928306E-3508-3DBC-80A4-D8F1D87650D7]@0 xffffff7f82421000
         com.apple.nvidia.nv50hal(8.1.6)[BF3CC142-4112-3E23-BCE2-CDCFD5811DDA]@0xffffff7 f82727000->0xffffff7f829fafff
            dependency: com.apple.NVDAResman(8.1.6)[39D35403-42FB-3F08-999C-9866938D6B3A]@0xffffff7f824 78000
            dependency: com.apple.iokit.IOPCIFamily(2.8)[6C1D646D-7E5E-3D7F-A557-2CBA398FF878]@0xffffff 7f82248000
         com.apple.GeForce(8.1.6)[8D728212-9DE5-349D-ABF3-7989F0C4BC29]@0xffffff7f8334c0 00->0xffffff7f83419fff
            dependency: com.apple.NVDAResman(8.1.6)[39D35403-42FB-3F08-999C-9866938D6B3A]@0xffffff7f824 78000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[F16E015E-1ABE-3C40-AC71-BC54F4BE442E]@0xff ffff7f82464000
            dependency: com.apple.iokit.IOPCIFamily(2.8)[6C1D646D-7E5E-3D7F-A557-2CBA398FF878]@0xffffff 7f82248000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[9928306E-3508-3DBC-80A4-D8F1D87650D7]@0 xffffff7f82421000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
12F45
Kernel version:
Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root:xnu-2050.48.12~1/RELEASE_X86_64
Kernel UUID: EA38B02E-2B88-309F-BA68-1DE29F605DD8
Kernel slide:     0x0000000001a00000
Kernel text base: 0xffffff8001c00000
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 24995919148983
last loaded kext at 17474708640311: com.apple.driver.AppleUSBCDC 4.1.23 (addr 0xffffff7f84007000, size 16384)
last unloaded kext at 17534809298032: com.apple.driver.AppleUSBCDC 4.1.23 (addr 0xffffff7f84007000, size 12288)
loaded kexts:
com.apple.filesystems.smbfs 1.8.4
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.iokit.IOBluetoothSerialManager 4.1.7f4
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AGPM 100.13.14
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleHDA 2.4.7fc4
com.apple.GeForce 8.1.6
com.apple.driver.AppleUpstreamUserClient 3.5.12
com.apple.driver.AppleLPC 1.6.3
com.apple.driver.AppleIntelHDGraphics 8.1.6
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.1.7f4
com.apple.driver.SMCMotionSensor 3.0.3d1
com.apple.driver.AppleMikeyDriver 2.4.7fc4
com.apple.driver.AppleSMBusPCI 1.0.11d1
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.ApplePolicyControl 3.4.5
com.apple.driver.AppleSMCLMU 2.0.3d0
com.apple.driver.AppleIntelHDGraphicsFB 8.1.6
com.apple.driver.AppleMuxControl 3.4.5
com.apple.driver.AppleMCCSControl 1.1.11
com.apple.driver.AppleUSBTCButtons 237.1
com.apple.driver.AppleIRController 320.15
com.apple.driver.AppleUSBCardReader 3.3.1
com.apple.driver.AppleUSBTCKeyboard 237.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 34
com.apple.iokit.SCSITaskUserClient 3.5.6
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.3.5
com.apple.driver.AppleUSBHub 635.4.0
com.apple.driver.AirPort.Brcm4331 615.20.17
com.apple.driver.AppleFWOHCI 4.9.9
com.apple.driver.AppleAHCIPort 2.6.6
com.apple.iokit.AppleBCM5701Ethernet 3.6.2b4
com.apple.driver.AppleUSBEHCI 621.4.6
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 1.8
com.apple.driver.AppleRTC 1.5
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 1.9
com.apple.driver.AppleACPIEC 1.8
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 214.0.0
com.apple.nke.applicationfirewall 4.0.39
com.apple.security.quarantine 2.1
com.apple.driver.AppleIntelCPUPowerManagement 214.0.0
com.apple.iokit.IOSerialFamily 10.0.6
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 2.4.7fc4
com.apple.iokit.IOAudioFamily 1.9.2fc7
com.apple.kext.OSvKernDSPLib 1.12
com.apple.nvidia.nv50hal 8.1.6
com.apple.NVDAResman 8.1.6
com.apple.iokit.IOFireWireIP 2.2.5
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.1.7f4
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.4.1d13
com.apple.iokit.IOSurface 86.0.4
com.apple.iokit.IOBluetoothFamily 4.1.7f4
com.apple.driver.AppleHDAController 2.4.7fc4
com.apple.iokit.IOHDAFamily 2.4.7fc4
com.apple.driver.AppleSMC 3.1.5d4
com.apple.driver.AppleGraphicsControl 3.4.5
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IONDRVSupport 2.3.7
com.apple.driver.AppleSMBusController 1.0.11d1
com.apple.iokit.IOGraphicsFamily 2.3.7
com.apple.iokit.IOUSBMassStorageClass 3.5.2
com.apple.driver.AppleUSBMultitouch 237.3
com.apple.iokit.IOUSBHIDDriver 623.4.0
com.apple.driver.AppleUSBMergeNub 621.4.6
com.apple.driver.AppleUSBComposite 621.4.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.5.6
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOSCSIBlockCommandsDevice 3.5.6
com.apple.iokit.IOAHCISerialATAPI 2.5.5
com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.6
com.apple.iokit.IOUSBUserClient 630.4.4
com.apple.iokit.IO80211Family 530.5
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IOAHCIFamily 2.5.1
com.apple.iokit.IOEthernetAVBController 1.0.2b1
com.apple.iokit.IONetworkingFamily 3.0
com.apple.iokit.IOUSBFamily 635.4.0
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 1.8.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 220.3
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.DiskImages 345
com.apple.iokit.IOStorageFamily 1.8
com.apple.driver.AppleKeyStore 28.21
com.apple.driver.AppleACPIPlatform 1.8
com.apple.iokit.IOPCIFamily 2.8
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0

You have the MacBookPro6,2—the Edsel of Macs. It may have the logic-board defect that was covered by this recall.
Make a "Genius" appointment at an Apple Store, or go to another authorized service provider, to have the machine tested. The routine hardware diagnostics used by service providers do not detect the fault. There is a specific test for this issue that Apple calls "VST" (for "Video Switching Test.") Ask for it. A "Failed" result means that the fault is present. However, according to reports, some units may pass the test, and yet still be deemed eligible for repair under the program. Your experience may vary.
Print the first page of the panic report, if any, and the support page linked above, and bring them with you.
Note that the recall only applies within three years of purchase. After that, Apple may refuse the service. In that case, you may be quoted a price of about $300 (in the U.S.) for a "depot repair," which involves shipping the unit to a central repair facility and takes about two weeks. For that flat fee, anything found wrong with it should be fixed, not just the logic board.
The model was discontinued on February 24, 2011, so the recall has nominally ended. Some units may have been sold after that date by Apple as refurbished, or by resellers as new, and they might still be covered.
Residents of the EU may be entitled to warranty service for up to six years after purchase.
Some owners report that their unit was repaired under the program after the deadline had passed. Others report that the repair was covered by the extended warranty from a credit-card issuer. Again, your experience may vary.
Sometimes the replacement part is also defective, so be prepared for that possibility. If you decide to pay for a new logic board, test thoroughly during the 90-day warranty period on the repair. Some owners have reported that they went through as many as three replacement boards before getting one that worked.
If it's too late for your unit to be repaired free of charge, and you don't want to pay for the service, you may (or may not) be able to stop the panics by disabling automatic graphics switching. To use the discrete graphics processor, you'll need a third-party utility to switch to it manually.
Often the problems start after an OS upgrade. If the upgrade was recent, and you have backups, then you can revert to a previous OS X version.
If you're dissatisfied with Apple's response, please keep in mind that no one here represents the company or can help with customer-service issues.
Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
*An SSD doesn't need to be zeroed.

Kernel Panic with 10.6.1 disk utility

Similar Messages

Maybe you are looking for