Nvidia drivers causing Kernel Panics

Here's a thread about users of Modo experiencing kernel panics:
http://forums.luxology.com/discussion/topic.aspx?id=4137&show
Users with nvidia cards report kernel panics after updating to 10.4.3. I'm using 10.4.5 and still getting them. Crash report states:
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x61099000
Apple has to address this. It's frustrating having the nvidia drivers tied to OS updates. Sounds great, but now I can't reinstall the old driver.

I sent a report here:
http://www.apple.com/macosx/feedback/
Is this the right place?

Similar Messages

  • Digidesign Drivers Causing Kernel Panics Regularly

    From the report:
    I'm getting several kernel panics every day from my Mbox 2 Mini. It usually occurs when running video on the web on youtube or megavideo.
    From the console:
    Kernel Extensions in backtrace (with dependencies):
    com.digidesign.mbox2.driver(8.0.0f1)@0x109e000->0x10c1fff
    dependency: com.apple.iokit.IOAudioFamily(1.7.6fc2)@0xbf8000
    dependency: com.apple.iokit.IOUSBFamily(4.0.2)@0xd4e000
    dependency: com.apple.driver.AppleUSBMergeNub(4.0.0)@0xef3000
    dependency: com.apple.kext.OSvKernDSPLib(1.3)@0xbf4000
    dependency: com.apple.iokit.IOPCIFamily(2.6)@0x926000
    dependency: com.apple.driver.AppleUSBComposite(3.9.0)@0xec8000
    This has been happening for several months now. I have taken my computer to the genius bar several times now, but each solution has not corrected the problem. My applecare is up so I can't really send it in, so I have to try and do everything myself now. I cannot call Digidesign either because they make you purchase phone support (!) for $40.
    Any ideas what I can do for this? I've reinstalled the both the OS and Protools/Digidesign Drivers a couple of times, nothing good yet.
    Thanks for any help.

    I am not sure what your goal actually is with setting up your system, but as far as Logic Pro as a slave for protools, your best luck is to have a dedicated second machine with protools to slave with Logic Pro on its own machine. Logic Pro and protools are notorious for not talking well together slaved on the same machine since protools uses rtas plugins and logic pro uses audio units or wrapped vst's to audio unit plugins.

  • Digidesign Drivers Causing Kernel Panics

    From the report:
    I'm getting several kernel panics every day from my Mbox 2 Mini. It usually occurs when running video on the web on youtube or megavideo.
    From the console:
    Kernel Extensions in backtrace (with dependencies):
    com.digidesign.mbox2.driver(8.0.0f1)@0x109e000->0x10c1fff
    dependency: com.apple.iokit.IOAudioFamily(1.7.6fc2)@0xbf8000
    dependency: com.apple.iokit.IOUSBFamily(4.0.2)@0xd4e000
    dependency: com.apple.driver.AppleUSBMergeNub(4.0.0)@0xef3000
    dependency: com.apple.kext.OSvKernDSPLib(1.3)@0xbf4000
    dependency: com.apple.iokit.IOPCIFamily(2.6)@0x926000
    dependency: com.apple.driver.AppleUSBComposite(3.9.0)@0xec8000
    This has been happening for several months now. I have taken my computer to the genius bar several times now, but each solution has not corrected the problem. My applecare is up so I can't really send it in, so I have to try and do everything myself now. I cannot call Digidesign either because they make you purchase phone support (!!!!) for $40.
    Any ideas what I can do for this? I've reinstalled the both the OS and Protools/Digidesign Drivers a couple of times, nothing good yet.
    Thanks for any help.

    Hi,
    Have you tried Updating to Leopard 10 5 8
    Here's the Combo Update Link:
    http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate
    Failing that or if you want to stay on 10 5 7 here's the Combo Update for 10 5 7
    http://support.apple.com/downloads/MacOS_X_10_5_7_ComboUpdate
    Try running that...
    Cheers

  • Mbox 2 Mini Drivers Causing Kernel Panics

    I'm getting several kernel panics every day from my Mbox 2 Mini. It usually occurs when running video on the web on youtube or megavideo.
    From the console:
    Kernel Extensions in backtrace (with dependencies):
    com.digidesign.mbox2.driver(8.0.0f1)@0x109e000->0x10c1fff
    dependency: com.apple.iokit.IOAudioFamily(1.7.6fc2)@0xbf8000
    dependency: com.apple.iokit.IOUSBFamily(4.0.2)@0xd4e000
    dependency: com.apple.driver.AppleUSBMergeNub(4.0.0)@0xef3000
    dependency: com.apple.kext.OSvKernDSPLib(1.3)@0xbf4000
    dependency: com.apple.iokit.IOPCIFamily(2.6)@0x926000
    dependency: com.apple.driver.AppleUSBComposite(3.9.0)@0xec8000

    What does the Mbox 2 Mini manufacturer say?
    For KPs, see these:
    What is a kernel panic,
    Technical Note TN2063: Understanding and Debugging Kernel Panics,
    Mac OS X Kernel Panic FAQ,
    Resolving Kernel Panics, and
    Tutorial: Avoiding and eliminating Kernel panics

  • Using 2 memory modules causes kernel panic

    In early 2009 I upgraded my memory from 512 to 2 GB, 2 modules of 1GB each. This past January (just shy of 2 years later) I got a kernel panic. I tested running with a single module, and one module caused panic, the other was fine. Both slots function with the good module. So I got two new matched replacement chips from OWC, put them in and got kernel panics during the boot process. Yesterday I spent testing memory configurations and found this:
    1. chip 1 alone runs fine and passes all Rember memory tests in slot 1.
    2. chip 2 alone runs fine in slot 1 and 2, passes all memory tests in slot 2.
    3. chips 1 and 2 together, in either slot, cause kernel panics before the OS is loaded.
    Has anyone seen this problem? Will it go away if I use top of the line (Apple) memory chips?
    When the kernel panics started back in January, an AppleCare advanced advisor said he had the same problem and he had to remove one module to stop the kernel panics. Running on 1GB doesn't work for me because I tend to max out the memory and programs like Mail, Safari, Photoshop, etc. become unreponsive all together.
    thanks -

    I have spent more time on the phone with OWC about this than I care to remember. Their latest request is that I use an eraser to clean the metal contacts on the chips; if that fails, I get to send the chips back. Whether I get a refund or yet another set of replacement chips, I don't know. They are not experts on Apple machines, that is clear.

  • RAID mirror with software utility caused kernel panic every time

    Using disc utility to make a mirror of 2 drives, click create and i get kernel panic and have to power off machine. if i try to start the machine with either of the two disks in it (together or individually) i get same kernel panic and have to power off.
    The disks are in an external storage array (sonnet d500). I have a second storage array with raided disks in and i have raided disk inside the mac too. these all work fine..
    originally 2 weeks ago i had the 2 disks working in a group of 4 disks set as a mirror of 2 striped disks. One disk in this setup failed and with this config you can never 'recover'or rebuild it - you get a degraded mirror and you can backup the data, but you must completely rebuild the raid again as the mirror of stripes never lets you add a new disk in again.period. not good.
    I replaced the failed disk and rebuilt the mirror of stripes. this lasted a day until a second disk failed (all 4 were bought at same time so i was kind of expecting that to happen once one failed).
    i replaced the second faulty hdd and thought about my disk usage and decided i would not make another mirror of stripes and i would make 2 mirrors instead for safe-ish storage and then transfer data to a striped raid set for editing from instead of direct from the mirror of stripes volume.
    i tried to delete the raid but got a kernel panic
    if i started the machine with any of the 4 disks i would get a kernel panic.
    i moved the disks one by one into an older G5 running Tiger and managed to erase the raid info on 2 of them. The two new ones had some strange raid info and the Tiger machien thought there was an extra disk in the machine and would not erase or partition or allow me to destroy the raid whatever i tried.
    I will be moving these now into an old XP PC to try to erase the boot records etc and erase them to be able to use them again in either mac pro or G5. painful..
    so.. i ended up with 2 erased drives and have 2 new drives with dodgy raid info that causes kernel panics on the leopard machine and wont go in the Tiger machine.
    The two erased drives are what ive now been trying to use in the mac pro to create a mirror - this now caused kernel panics when creating the mirror to start with and when installed in the machine at all. so i will be erasing them again in the tiger machine soon (its busy erasing with zeros another new disk that i added to the Tiger machine 2 weeks ago which seems to have some fault when raided!!! but thats another story).
    so.. is anyone else having problems with creating basic mirror in 10.5.4 or is it just me??
    i have a sonnet tempo e4p card with 2 external sata disk enclosures, latest firmware for the e4p card. all other previously existing raid volumes are working fine. i have one set of 2 striped disks, one set of 3 striped disks and one set of 2 stripes which are mirrored - all happy and working fine. but i cant make a new mirror of 2 disks...
    I phoned Apple support and they said all raid info was kept on the disk itself and nothing on the actual machine and suggested i take the machine to an apple care centre for some tlc (although its disk i am having a problem with). since all my other disk arrays work fine i don't really want to rebuild the whole machine from scratch if i can avoid it.
    Any suggestions of what i can try ??

    well it turns out the new disk i bought just werent any good. my g5 powermac raid mirror issue was related to one new disk with lots of bad blocks (speed tools showed that up) so i have learnt my lesson on cheap non raid disks for raid..
    am waiting on a couple of new ultrastar enterprise disks to tuen up so i can go back to the macpro and try to add a mirror again.
    i am still stuck wih several new disks that i cannot format now in the macpro on leopard or on the g5 powermac with tiger.
    ive tried softraid and that cant do it, speedtools pcformat util cant do it, disk utility crashes when i try to eras them and diskutil from termianl starts then doenst get anywhere and my pc sata card doesnt work so my last resort pc option still doesnt help me clear the partition map on these drives - ones that diskutility on leopard made for me - and drives which still cause kernel panics on the macpro if i put them in it..
    here is what diskutil says on my g5:
    /dev/disk0
    #: type name size identifier
    0: GUIDpartitionscheme *465.8 GB disk0
    1: EFI 200.0 MB disk0s1
    2: Apple_RAID 465.4 GB disk0s2
    3: Apple_Boot 128.0 MB disk0s3
    /dev/disk1
    #: type name size identifier
    0: Applepartitionscheme *233.8 GB disk1
    1: Applepartitionmap 31.5 KB disk1s1
    2: Apple_HFS Macintosh HD 233.6 GB disk1s3
    /dev/disk2
    #: type name size identifier
    0: *465.4 GB disk2
    /dev/disk3
    #: type name size identifier
    0: Applepartitionscheme *931.5 GB disk3
    1: Applepartitionmap 31.5 KB disk3s1
    2: Apple_HFS backup1T 931.4 GB disk3s3
    /dev/disk4
    #: type name size identifier
    0: Applepartitionscheme *931.5 GB disk4
    1: Applepartitionmap 31.5 KB disk4s1
    2: Apple_HFS tempi 931.4 GB disk4s3
    disk0 is the one with the bad partition info.
    it thinks it has a double raid as the console shows on startup:
    (both store45 and cache it thinks are on this disk - cache was my old mirror of stripes set on other machine, store45 was new name for my mirror, so seems like it hadnt deleted the original raid partition info before making new info which now kernel panics)
    Jul 18 18:48:05 localhost kernel[0]: AppleRAID::degradeSet - starting the set "STORE45" (B9C48619-6B2C-4547-A01E-4864754EA7E2).
    Jul 18 18:48:35 localhost kernel[0]: AppleRAID::degradeSet - starting the set "CACHE" (64F914A5-5556-4A44-AEE2-DC437868766B).
    Jul 18 18:48:35 localhost kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002c2 detected for set "STORE45" (C0E139A4-2A6D-49C6-8F77-202AF7F9285D), member 50207BE5-E487-410E-8E8E-C4C4DCD2687B, set byte offset = 999527018496.
    Jul 18 18:48:35 localhost kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002c2 detected for set "CACHE" (64F914A5-5556-4A44-AEE2-DC437868766B), member C0E139A4-2A6D-49C6-8F77-202AF7F9285D, set byte offset = 999527018496.
    so currently i have 2 new 500gb disks which cant be partitioned back to anything at all on either machine. looks like i will have to buy a new pc to reformat them..
    any suggestions of how to clear the partition map info and get them back to freespace ??

  • PS Extended CS6 causing kernel panics

    I've been getting one or two a week. Haven't figured out yet what triggers it, but it only happens in CS6. I did recently reinstall the entire OS, so that's clean. Here's the latest panic info the reboot generates to send to Apple. Doesn't mean anything to me, other than the panic notation near the top of the info tells you what it thinks happened.
    Interval Since Last Panic Report:  141469 sec
    Anonymous UUID:                    44199F46-5B6B-42C5-9E13-29CB09291223
    Mon Sep 24 14:40:11 2012
    panic(cpu 2 caller 0xffffff80002094e7): "thread_invoke: preemption_level -1, possible cause: unlocking an unlocked mutex or spinlock"@/SourceCache/xnu/xnu-1504.15.3/osfmk/kern/sched_prim.c:1471
    Backtrace (CPU 2), Frame : Return Address
    0xffffff8149e83d70 : 0xffffff8000204d15
    0xffffff8149e83e70 : 0xffffff80002094e7
    0xffffff8149e83ef0 : 0xffffff8000209acb
    0xffffff8149e83f60 : 0xffffff800053b02d
    0xffffff8149e83fa0 : 0xffffff80002c8527
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    10K549
    Kernel version:
    Darwin Kernel Version 10.8.0: Tue Jun  7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64
    System model name: MacPro5,1 (Mac-F221BEC8)
    System uptime in nanoseconds: 26760035257178
    unloaded kexts:
    com.apple.iokit.IOFireWireSBP2          4.0.6 (addr 0xffffff7f80e4a000, size 0x73728) - last unloaded 25651433036012
    loaded kexts:
    com.aladdin.kext.aksfridge          1.0.2
    com.dvdfab.kext.fabio          1
    com.hzsystems.terminus.driver          4
    com.microsoft.driver.MicrosoftKeyboardUSB          8.2
    com.microsoft.driver.MicrosoftKeyboard          8.2
    com.Logitech.Control Center.HID Driver          3.6.0
    com.apple.filesystems.afpfs          9.7.1 - last loaded 23445647212129
    com.apple.nke.asp_tcp          5.0
    com.apple.driver.AppleHWSensor          1.9.3d0
    com.apple.driver.AppleTyMCEDriver          1.0.2d2
    com.apple.driver.AGPM          100.12.31
    com.apple.driver.AppleUpstreamUserClient          3.5.7
    com.apple.driver.AppleMCCSControl          1.0.20
    com.apple.driver.AppleMikeyHIDDriver          1.2.0
    com.apple.kext.ATIFramebuffer          6.3.6
    com.apple.driver.AppleHDA          2.0.5f14
    com.apple.driver.AppleMikeyDriver          2.0.5f14
    com.apple.driver.AudioAUUC          1.57
    com.apple.filesystems.ntfs          3.4
    com.apple.ATIRadeonX3000          6.3.6
    com.apple.filesystems.autofs          2.1.0
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.AudioIPCDriver          1.1.6
    com.apple.driver.ACPI_SMC_PlatformPlugin          4.7.0a1
    com.apple.driver.AppleLPC          1.5.1
    com.apple.iokit.IOAHCIBlockStorage          1.6.4
    com.apple.iokit.SCSITaskUserClient          2.6.8
    com.apple.BootCache          31.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.driver.AppleFWOHCI          4.7.3
    com.apple.driver.AppleUSBOHCI          4.2.0
    com.apple.driver.AppleUSBHub          4.2.4
    com.apple.driver.AirPortBrcm43224          428.42.4
    com.apple.driver.AppleAHCIPort          2.1.7
    com.apple.driver.Intel82574L          2.1.8b1
    com.apple.driver.AppleUSBEHCI          4.2.4
    com.apple.driver.AppleUSBUHCI          4.2.0
    com.apple.driver.AppleEFINVRAM          1.4.0
    com.apple.driver.AppleRTC          1.3.1
    com.apple.driver.AppleHPET          1.5
    com.apple.driver.AppleACPIButtons          1.3.6
    com.apple.driver.AppleSMBIOS          1.7
    com.apple.driver.AppleACPIEC          1.3.6
    com.apple.driver.AppleAPIC          1.4
    com.apple.driver.AppleIntelCPUPowerManagementClient          142.6.0
    com.apple.security.sandbox          1
    com.apple.security.quarantine          0
    com.apple.nke.applicationfirewall          2.1.14
    com.apple.driver.AppleIntelCPUPowerManagement          142.6.0
    com.apple.driver.AppleProfileReadCounterAction          17
    com.apple.driver.DspFuncLib          2.0.5f14
    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.IONDRVSupport          2.2.1
    com.apple.driver.AppleSMBusController          1.0.10d0
    com.apple.kext.ATI5000Controller          6.3.6
    com.apple.kext.ATISupport          6.3.6
    com.apple.iokit.IOFireWireIP          2.0.3
    com.apple.iokit.IOSurface          74.2
    com.apple.iokit.IOBluetoothSerialManager          2.4.5f3
    com.apple.iokit.IOSerialFamily          10.0.3
    com.apple.iokit.IOAudioFamily          1.8.3fc2
    com.apple.kext.OSvKernDSPLib          1.3
    com.apple.driver.AppleHDAController          2.0.5f14
    com.apple.iokit.IOGraphicsFamily          2.2.1
    com.apple.iokit.IOHDAFamily          2.0.5f14
    com.apple.iokit.AppleProfileFamily          41
    com.apple.driver.AppleSMC          3.1.0d5
    com.apple.driver.IOPlatformPluginFamily          4.7.0a1
    com.apple.driver.AppleSMBusPCI          1.0.10d0
    com.apple.driver.BroadcomUSBBluetoothHCIController          2.4.5f3
    com.apple.driver.AppleUSBBluetoothHCIController          2.4.5f3
    com.apple.driver.IOBluetoothHIDDriver          2.4.5f3
    com.apple.iokit.IOBluetoothFamily          2.4.5f3
    com.apple.iokit.IOUSBHIDDriver          4.2.0
    com.apple.driver.AppleUSBMergeNub          4.2.4
    com.apple.driver.AppleUSBComposite          3.9.0
    com.apple.driver.XsanFilter          402.1
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          2.6.8
    com.apple.iokit.IOBDStorageFamily          1.6
    com.apple.iokit.IODVDStorageFamily          1.6
    com.apple.iokit.IOCDStorageFamily          1.6.1
    com.apple.iokit.IOFireWireFamily          4.2.6
    com.apple.iokit.IOAHCISerialATAPI          1.2.6
    com.apple.iokit.IOSCSIArchitectureModelFamily          2.6.8
    com.apple.iokit.IO80211Family          320.1
    com.apple.iokit.IOUSBUserClient          4.2.4
    com.apple.iokit.IOAHCIFamily          2.0.6
    com.apple.iokit.IONetworkingFamily          1.10
    com.apple.iokit.IOUSBFamily          4.2.4
    com.apple.driver.AppleEFIRuntime          1.4.0
    com.apple.iokit.IOHIDFamily          1.6.6
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          6
    com.apple.driver.DiskImages          289.1
    com.apple.iokit.IOStorageFamily          1.6.3
    com.apple.driver.AppleACPIPlatform          1.3.6
    com.apple.iokit.IOPCIFamily          2.6.5
    com.apple.iokit.IOACPIFamily          1.3.0
    Model: MacPro5,1, BootROM MP51.007F.B03, 6 processors, 6-Core Intel Xeon, 3.33 GHz, 16 GB, SMC 1.39f11
    Graphics: ATI Radeon HD 5770, ATI Radeon HD 5770, PCIe, 1024 MB
    Memory Module: global_name
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.10.131.42.4)
    Bluetooth: Version 2.4.5f3, 2 service, 12 devices, 1 incoming serial ports
    Network Service: Ethernet 2, Ethernet, en1
    PCI Card: pci104c,823f, sppci_ieee1394openhci, Slot-3@6,0,0
    PCI Card: pci1033,35, sppci_usbopenhost, Slot-3@8,0,0
    PCI Card: pci1033,e0, USB Enhanced Host Controller, Slot-3@8,0,1
    PCI Card: pci1033,35, sppci_usbopenhost, Slot-4@11,0,0
    PCI Card: pci1033,35, sppci_usbopenhost, Slot-4@11,0,1
    PCI Card: pci1033,e0, USB Enhanced Host Controller, Slot-4@11,0,2
    PCI Card: ATI Radeon HD 5770, sppci_displaycontroller, Slot-1
    Serial ATA Device: HL-DT-ST DVD-RW GH61N
    Serial ATA Device: HL-DT-ST BD-RE  GGW-H20L
    Serial ATA Device: WDC WD1001FALS-41Y6A1, 931.51 GB
    Serial ATA Device: Hitachi HDS722020ALA330, 1.82 TB
    Serial ATA Device: WDC WD3200AAKS-00VYA0, 298.09 GB
    USB Device: Hub, 0x0409  (NEC Corporation), 0x005a, 0xfd300000 / 2
    USB Device: EIZO USB HID Monitor, 0x056d  (Eizo), 0x0002, 0xfd330000 / 3
    USB Device: USB 2.0 Hub [MTT], 0x1a40  (TERMINUS TECHNOLOGY INC.), 0x0101, 0x40400000 / 2
    USB Device: HASP4 USB 1.33, 0x0529  (Aladdin Knowledge Systems), 0x0001, 0x00200000 / 3
    USB Device: SII Smart Label Printer 200, 0x0619  (Seiko Instruments Inc.), 0x0104, 0x00100000 / 2
    USB Device: HASP4 USB 1.33, 0x0529  (Aladdin Knowledge Systems), 0x0001, 0xff100000 / 2
    USB Device: HASP HL 3.25, 0x0529  (Aladdin Knowledge Systems), 0x0001, 0xfe200000 / 2
    USB Device: Natural® Ergonomic Keyboard 4000, 0x045e  (Microsoft Corporation), 0x00db, 0x1a200000 / 2
    USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x5a100000 / 2
    USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x8215, 0x5a110000 / 3
    USB Device: USB Receiver, 0x046d  (Logitech Inc.), 0xc52f, 0x1d100000 / 2
    FireWire Device: built-in_hub, Up to 800 Mb/sec
    FireWire Device: unknown_device, 0xD016, Up to 200 Mb/sec

    Only OS bugs, driver bugs, or hardware problems can cause kernel panics.
    Yes, that is normally the case. I brought this up here because while working in PS is the only time this happens. I know it doesn't make sense, but there it is.
    Not sure why the crash report stated 10.8.0. It's incorrect on two counts. For one, I'm working in Snow Leopard, 10.6.8. I do have Mountain Lion installed on a separate drive for testing, but that already is at 10.8.2. Regardless, it's not the OS I was even in, so I don't know why it reported 10.8.0 as the kernel.
    Anyway, I noticed (after posting this of course) that there was a 13.0.1 update for PS CS6. I applied that and we'll see how it goes from there as the update is noted as fixing a number of crashing problems.

  • Airport causing kernel panics and kp in safe boot.

    Last week I got my first kernel panic in years. It happened while I was asleep and checking an extrenal drive for bad blocks with TechTool. It turns out that the drive indeed had bad blocks and found that the cpu was shut down when I awoke. I started up the computer and it wasn't able to stay on for more than 10 min max before the next kernel panic. I checked here for more advice on kernel panics and started to try to narrow the number of culprits. Everything was unplugged and still kp. Instaled a new drive with a week older system from Time Machine and still kp. Reset NVRAM and replaced pyhsical RAM and still kp. Removed the Airport Extreme card and still kp. Booted into Safe Mode after all of the previously mentioned and still kp. I'm now going to take the drive and swap it into another body that I have to see if the root is actually on the drive on the physical hardware of the cpu.
    I was interested in this thread and read all of the links that jpl posted. Airport causing Kernel Panic (?) Jason then replied that it had been solved due to a "permissions problem" I wish he gave more info on what exactly he did to resolve the problem as it's been almost a week now without any work being done for me.
    I've also noticed this very strange behavior that might shed some light onto the issue. When I open System Prefs and close the window there is a strange colored pattern that will always flash after the window has been closed. I tried to post it to my me page but for somereason it wouldn't play for me so there's that and the YouTube version too.
    https://www.me.com/gallery/#100008/Prefs%20Screen
    http://www.youtube.com/watch?v=2zrTt88YdBo
    In addition when the computer has started up and the system loads. Checking Activity Monitor shows that there are 50 or more threads active for the the kernel_task. Inspecting this doesn't seem to show any useful information.
    Finally here are a few of the recent crashes I hope that someone might be able to shed some light on this extremely frustrating problem for me.
    Tue Oct 25 18:54:16 2011
    panic(cpu 0 caller 0x000AE584): "Uncorrectable machine check: pc = 00000000000A388C, msr = 0000000000141000, dsisr = 42000000, dar = 0000000000272008\n" "  AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000\n" "     L2FIR = 0000000000000000,  BusFir = 0000000080000000\n"@/SourceCache/xnu/xnu-1228/osfmk/ppc/trap.c:975
    Latest stack backtrace for cpu 0:
          Backtrace:
             0x0009AD18 0x0009B6BC 0x00029DC4 0x000AE584 0x000AE804 0x000B22F8
    Proceeding back via exception chain:
       Exception state (sv=0x2fc12c80)
          PC=0x000A388C; MSR=0x00141000; DAR=0x00272008; DSISR=0x42000000; LR=0x000A37C8; R1=0x2E947B40; XCP=0x00000008 (0x200 - Machine check)
          Backtrace:
    0x00000000 0x000A09C8 0x0009E2EC 0x0006B3C0 0x0006C728 0x0003BE1C
             0x0029361C 0x0029364C 0x0030924C 0x000B24C8 0x00000000
       Exception state (sv=0x249dba00)
          PC=0x9195435C; MSR=0x0000F030; DAR=0x00272000; DSISR=0x42000000; LR=0x00001FA8; R1=0xBFFFFB00; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: PubSubAgent
    Mac OS version:
    9A581
    Kernel version:
    Darwin Kernel Version 9.0.0: Tue Oct  9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
    Tue Oct 25 19:09:54 2011
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000FFFFFFFF PC=0x0000000000040DE4
    Latest crash info for cpu 0:
       Exception state (sv=0x3c19ca00)
          PC=0x00040DE4; MSR=0x00001030; DAR=0xFFFFFFFF; DSISR=0x40000000; LR=0x00040D94; R1=0x33B63D50; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x0293EA14 0x0004147C 0x0001EB60 0x00025960 0x000B264C 0x00000000
    Proceeding back via exception chain:
       Exception state (sv=0x3c19ca00)
          previously dumped as "Latest" state. skipping...
       Exception state (sv=0x3297b500)
          PC=0x919419D8; MSR=0x0000D030; DAR=0x0073C000; DSISR=0x42000000; LR=0x91948900; R1=0xF00807A0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: mdworker
    Mac OS version:
    9A581
    Kernel version:
    Darwin Kernel Version 9.0.0: Tue Oct  9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): copyin/out has no recovery point
    Latest stack backtrace for cpu 0:
          Backtrace:
             0x0009AD18 0x0009B6BC 0x00029DC4 0x000AEB88 0x000B22F8
    Proceeding back via exception chain:
       Exception state (sv=0x3c19ca00)
          PC=0x00040DE4; MSR=0x00001030; DAR=0xFFFFFFFF; DSISR=0x40000000; LR=0x00040D94; R1=0x33B63D50; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x0293EA14 0x0004147C 0x0001EB60 0x00025960 0x000B264C 0x00000000
       Exception state (sv=0x3297b500)
          PC=0x919419D8; MSR=0x0000D030; DAR=0x0073C000; DSISR=0x42000000; LR=0x91948900; R1=0xF00807A0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: mdworker
    Wed Oct 26 15:31:02 2011
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000FFFFFFFF PC=0x0000000000040DE4
    Latest crash info for cpu 0:
       Exception state (sv=0x3c19ca00)
          PC=0x00040DE4; MSR=0x00001030; DAR=0xFFFFFFFF; DSISR=0x40000000; LR=0x00040D94; R1=0x33B63D50; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x0293EA14 0x0004147C 0x0001EB60 0x00025960 0x000B264C 0x00000000
    Proceeding back via exception chain:
       Exception state (sv=0x3c19ca00)
          previously dumped as "Latest" state. skipping...
       Exception state (sv=0x3297b500)
          PC=0x919419D8; MSR=0x0000D030; DAR=0x0073C000; DSISR=0x42000000; LR=0x91948900; R1=0xF00807A0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: mdworker
    Mac OS version:
    9A581
    Kernel version:
    Darwin Kernel Version 9.0.0: Tue Oct  9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): copyin/out has no recovery point
    Latest stack backtrace for cpu 0:
          Backtrace:
             0x0009AD18 0x0009B6BC 0x00029DC4 0x000AEB88 0x000B22F8
    Proceeding back via exception chain:
       Exception state (sv=0x3c19ca00)
          PC=0x00040DE4; MSR=0x00001030; DAR=0xFFFFFFFF; DSISR=0x40000000; LR=0x00040D94; R1=0x33B63D50; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x0293EA14 0x0004147C 0x0001EB60 0x00025960 0x000B264C 0x00000000
       Exception state (sv=0x3297b500)
          PC=0x919419D8; MSR=0x0000D030; DAR=0x0073C000; DSISR=0x42000000; LR=0x91948900; R1=0xF00807A0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: mdworker
    Wed Oct 26 22:17:42 2011
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000010 PC=0x0000000000082EF8
    Latest crash info for cpu 0:
       Exception state (sv=0x2514ea00)
          PC=0x00082EF8; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x00082ECC; R1=0x24F6BB60; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x00000000 0x000848C0 0x00077BD0 0x0007823C 0x0007920C 0x0006B718
             0x0006C728 0x00296378 0x0030924C 0x000B24C8 0x00000000
    Proceeding back via exception chain:
       Exception state (sv=0x2514ea00)
          previously dumped as "Latest" state. skipping...
       Exception state (sv=0x2509d500)
          PC=0x9194AF64; MSR=0x0000D930; DAR=0xE1000000; DSISR=0x42000000; LR=0x9194CC90; R1=0xBFFFE9A0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: launchd
    Mac OS version:
    9A581
    Kernel version:
    Darwin Kernel Version 9.0.0: Tue Oct  9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
          Backtrace:
             0x0009AD18 0x0009B6BC 0x00029DC4 0x000AEA90 0x000B22F8
    Proceeding back via exception chain:
       Exception state (sv=0x2514ea00)
          PC=0x00082EF8; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x00082ECC; R1=0x24F6BB60; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x00000000 0x000848C0 0x00077BD0 0x0007823C 0x0007920C 0x0006B718
             0x0006C728 0x00296378 0x0030924C 0x000B24C8 0x00000000
       Exception state (sv=0x2509d500)
          PC=0x9194AF64; MSR=0x0000D930; DAR=0xE1000000; DSISR=0x42000000; LR=0x9194CC90; R1=0xBFFFE9A0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: launchd
    Thu Oct 27 11:28:35 2011
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000004 PC=0x00000000000848E0
    Latest crash info for cpu 0:
       Exception state (sv=0x248ff500)
          PC=0x000848E0; MSR=0x00009030; DAR=0x00000004; DSISR=0x42000000; LR=0x000848AC; R1=0x30063BB0; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x000848C0 0x00077BD0 0x0007823C 0x0007920C 0x0006B718 0x0006C728
             0x00296378 0x0030924C 0x000B24C8 0x00000000
    Proceeding back via exception chain:
       Exception state (sv=0x248ff500)
          previously dumped as "Latest" state. skipping...
       Exception state (sv=0x248fd280)
          PC=0x9194AF64; MSR=0x0000D030; DAR=0xE1000000; DSISR=0x42000000; LR=0x9194CC90; R1=0xBFFFE7F0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: launchd
    Mac OS version:
    9A581
    Kernel version:
    Darwin Kernel Version 9.0.0: Tue Oct  9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
          Backtrace:
             0x0009AD18 0x0009B6BC 0x00029DC4 0x000AEA90 0x000B22F8
    Proceeding back via exception chain:
       Exception state (sv=0x248ff500)
          PC=0x000848E0; MSR=0x00009030; DAR=0x00000004; DSISR=0x42000000; LR=0x000848AC; R1=0x30063BB0; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x000848C0 0x00077BD0 0x0007823C 0x0007920C 0x0006B718 0x0006C728
             0x00296378 0x0030924C 0x000B24C8 0x00000000
       Exception state (sv=0x248fd280)
          PC=0x9194AF64; MSR=0x0000D030; DAR=0xE1000000; DSISR=0x42000000; LR=0x9194CC90; R1=0xBFFFE7F0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: launchd
    Thanks in advance,
    Max

    My vision is pretty poor, still cant see it, but...
    At this point I think you should get Applejack...
    http://www.macupdate.com/info.php/id/15667/applejack
    After installing, reboot holding down CMD+s, (+s), then when the DOS like prompt shows, type in...
    applejack AUTO
    Then let it do all 6 of it's things.
    At least it'll eliminate some questions if it doesn't fix it.
    The 6 things it does are...
    Correct any Disk problems.
    Repair Permissions.
    Clear out Cache Files.
    Repair/check several plist files.
    Dump the VM files for a fresh start.
    Trash old Log files.
    First reboot will be slower, sometimes 2 or 3 restarts will be required for full benefit... my guess is files relying upon other files relying upon other files! :-)
    Disconnect the USB cable from any Uninterruptible Power Supply so the system doesn't shut down in the middle of the process.

  • Scanner Causing Kernel Panics

    I have an old Agfa SnapScan 1212u USB scanner and up until today it has worked fine. Then suddenly it started causing Kernal Panics. It happens about 30% of the time. It scans the first 10% then throws up the Kernel Panic message and I'm forced to restart. I have run the Disk Repair Utility, repaired permissions, reinstalled the Agfa Scanwise driver, deleted all scanner related preferences and disconnected all other USB devices but nothing seems to work. The only software update I've done recently is the August and Java Security updates. Could either of these things be the problem? This is the first time I've had Kernel Panics on my Mac Mini. I doubt it's caused by the ram. It has worked flawlessly since I put in the 1GB module in July.
    Does anyone have any ideas?
    Cheers
    djon

    Well, I downloaded Vuescan and set it up but now I have another problem. Vuescan constantly crashes. Sometimes it crashes when I'm changing settings and sometimes is crashes after a scan. I set the memory settings very high so it shouldn't be a memory issue. I've tried just about everything to get this scanner working with Vuescan. I even installed a fresh copy of Panther on my Firewire drive but it only reduced the crashes not eliminate them. I'd like to get Vuescan working because it seems to make better scans than Scanwise did. At least it doesn't cause Kernel Panics. Does anyone have any idea what's going on? I'm beginning to think that it might be a hardware problem with the scanner.
    djon

  • Battery Update Causing Kernel Panics?

    It seems that ever since I installed the Battery Update it's been causing Kernel Panics on my MBP. Three since yesterday in fact. Has anyone else been experiencing this?
    MacBook Pro 1.83 GHz   Mac OS X (10.4.9)   1 GB RAM, 80 GB HDD, ATI Radeon X1600

    Hmm I have seen multiple posts on the computer not booting the OS (gets to the grey apple with spinning gear screen) but so far I think you are the first I have seen reporting kernel panics.
    Can you boot to the install cd? I'd try running the disk utility from the install disk and verify/repair permissions and verify the disk as well. (repair disk if verification fails)
    Here is an article that may help ya:
    Resolve startup issues and perform disk maintenance with Disk Utility and fsck
    http://docs.info.apple.com/article.html?artnum=106214

  • Readynas duo mounted over ethernet causes kernel panics

    I've found out what is causing kernel panics on my machines, but i'm not sure how to resolve it. I have a g4 laptop and a new mac mini, both mount the readynas via mount_afp using a LoginHook. When the laptop or the mini go to sleep, the ethernet connection is powered off and at some point the readynas goes to sleep as well. So, when the laptop/mini wake from sleep, they have trouble re-establishing the mount to the readynas (as it needs time to spin it's drives up) and then the laptop/mini kernel panic...shouldn't this really be just a lost connection message, rather than a full fledged panic!

    This is where we have a difference of opinion...If i can mount an external box over ethernet/firewire/usb and it causes the machine to kernel panic, then the software is not robust enough to handle the exception cases. Running 10.4.x for years with the same external hardware never yielded such results.

  • External LaCie Multi Recorder causing kernel panics since reloading OS

    I just replaced my main internal hd with a new 1TB WD Caviar Black. I migrated all of my user information from my old drive via Time Machine & all seemed well. Since I did a fresh, zero out data install of the OS on the new drive, I need to reinstall my programs. Some of my older programs are kept on DVD-RAM disks that I've had since my old G4. To access these files I use my LaCie Multi recorder which was working fine prior to the HD switch.
    When I put my DVD-RAM disk into the drive it's now causing kernel panics.
    Anyone know what could have caused this or how I might correct the problem?
    Thanks.

    Okay, it seems that I've got a bad disk. I connected the drive to my laptop & used another dvd & all worked as it should. Put my program back-up disk in & it caused a panic.
    New question, is there any way to repair the disk?
    I've got DiskWarrior & TechTool Deluxe but I'm not sure how I might go about the repair as the panic occurs while the drive is trying to access the disk.

  • Rt3062 causing kernel panics

    Hi all,
    I've got an rt3062 chipset wireless card and it's been causing kernel panics ever since the upgrade to linux-3.0.
    I was using the driver and firmware supplied by ralink and compiling it as the rt3562sta driver and it used to work great but it doesnt seem to support anything higher than kernel 2.6.39.
    I'm not exactly sure which error logs to post, so...
    Anybody else having this issue? and maybe find a workaround?
    Thanks

    I am using the same combination, successfully, with kernel 3.0.7-1. I do not recall having to do anything special to get it to work.
    06:00.0 Network controller: Ralink corp. Device 3062
        Subsystem: Ralink corp. Device 3062
        Flags: bus master, slow devsel, latency 32, IRQ 19
        Memory at fbdf0000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 3
        Kernel driver in use: rt2860
        Kernel modules: rt3562sta, rt2800pci
    Tim

  • ITunes causing kernel panics because I'm streaming to multiple Airplay Speakers?

    Any idea what is causing kernel panics that seems to have started when I began streaming to multiple Airplay Speakers?  iTunes is listed as the culprit in the crash report.

    My question:  is there a way to select multiple speakers from AppleTV for Airplay?
    Unfortunately not.

  • 10.7.5 causes kernel panics!!! Mac Mini issue?

    After updating my Mac Mini (late-2009, 2.53GHz core 2 duo, 4GB ram, no mods) to Lion 10.7.5, the message "You need to restart your computer. Shut down by holding the power button down, then restart" appears when shutting down, spawning a kernel panic. These have been submitted to Apple through the normal method. There are no other symptoms, but irrespective of this my Mac does not shut down correctly under 10.7.5 and kernal panics should not be happening. I've reverted to 10.7.4 now which solves the problem.
    Other users have reported this, such as 'stuckis' on a MacMini 2011, 2,5 Core i5 - this user even downloaded the update a second time and the problem reappeared.
    Given it happens on different model Mac Minis, I think the update is the source of the problem (at least on Mini models). Have any other users seen this issue??
    Apple's track record isn't great at the moment - I had to uninstall Mountain Lion because it was causing major kernel panics when attempting to shut down my Mac (probably caused by the use of a Samsung TV as a monitor - if I was cynical I'd say it was deliberate by Apple over their ongoing mobile phone battles), so upgrading to ML at the moment isn't a solution.

    Yep, read most of those when trying to sort a similar problem when I upgraded to Mountain Lion. I managed to narrow down the problem a bit, but given it only happened after the upgrade (and nothing else had changed) it was almost certainly something in Mountain Lion that caused it. As it turns out it looks like it was related to using a Samsung TV as a monitor or possibly nvidia drivers under ML. I've love to know if these issues have been resolved, because I thought ML was excellent.
    That said, given ML is already up to version .3 it seems to me there must have been a number of issues with it, and maybe these have sneaked down into Lion now? As for Lion on my Mac, downgrading to 10.7.4 fixes the problem, no more KPs, so as far as I can see it has to be OS related.
    The impression I get is that recent OS releases from Apple have not been tested very well, particularly with slightly older models such as mine. I've always thought the one of the good things about Apple was the longevity of their machines (I was using a perfectly good 2001 G4 Powermac before I got my Mac Mini in 2009!!).
    Rant over! I'll read the tutorial you've kindly provided the link for and perhaps try updating again...
    Message was edited for spelling! by: BigBadDavid

Maybe you are looking for