causes of constant kernel crashes on mac?

Hi all, anyone up to speed on kernel crashes and deciphering information on a mac? I keep getting relentless crashes and it is a nightmare!!! Continual crashes of the Ren

fluxsta wrote:Hi all, anyone up to speed on kernel crashes and deciphering information on a mac? I keep getting relentless crashes and it is a nightmare!!! Continual crashes of the Ren

OSX up to date?

If using an external USB Audio device, is it, or the Ren plugged into a USB 3.0 port?

Hi, thanks for respose, won't update to OsX Mavericks yet as not sure if MPC support. No, USB hub is 2.0. Will see when i get home if i have the MPC plugged into or the computers port, can't remember?

Please confirm exactly which OS version number you are using and your exact set up, otherwise it's impossible to offer any constructive advice. e.g

Mac OS version number
MPC Software version
MPC driver version
What other audio devices are attached and does the problem go away if you remove these?
USB hub or direct computer connection
Did your set up ever work correctly?

Assuming you only get problems when the MPC is attached, a kernel panic is most likely to be an audio driver conflict (I had this on Snow Leopard at one point), or an issue with the USB hub

Hi, at work at the moment but will recount as my memory allows.

Mac OSx Mountain lion 10.8
MPC version and firmware newest-all up to date
MPC via D Link 7 port USB hub (i think, not at home to check), but mayeb through Mac direct.

Yamaha 16 input desk > behringer firewire soundcard >mac

MPC audio direct through USB to Mac.

multiple USB synths connected to USB hub: novation basstation,waldorf blofeld, waldorf rocket, monome 256, Akai MPK mini keyboard

Set up has always worked, yes. One issue I did have was my other Akai mini keyboard, the editor kept opening as a max/msp patch, and i am led to believe that was maybe an audio driver conflict?

It appears the kernel crashes happen when i am running patches using max/msp and i am using my monome as well. This is integral to my set up to use my monome as well as the Ren at the same time, ad I have never had issues. After every crash, when rebooting the MPC software, a box appears saying that 'audio preferences have changed'. When I go to MPC preferences my soundcard shows up as it always has done?

When i am home, i will try and open MPC on its own and see if the kernel crash happens or i get the info asking me to change audio preferences.

I believ there is a conflict with max/msp. I uninstalled my MPK mini editor as i couldn't get it to open outside of Max.

fluxsta wrote:Hi, thanks for respose, won't update to OsX Mavericks yet as not sure if MPC support.

I've got Ren + Mav…works fine.

It may not help, but repair all your disk permissions, perhaps even going all out and doing it off the OS X DVD so you can do your Mac HD and any other drives if you use more than one HDD.

Read my first post, is your hub plugged into a USB 3.0 port?

I would wager the issue is somehow related to the hub, or 3.0.....

I have up to date Mountain Lion, Ren in USB 2.0 port, and zero issues.



Windows... now that's a different story..... My Surface Pro only has 1 USB port, and it is a 3.0..... It is a known issue in 3.0 that audio interfaces have issues (Ren is an audio interface). Apple of course fixed it it an up date to Mountain Lion (and Mav is of course fixed), Microsoft does not see it as an issue...... So I use ASIO4ALL drivers and use my Studio on the Surface Pro 2......

Hi guys
Thanks for the feedback. Won't update to mavericks, known issues with some max/msp patches that I use my monome with. Hub is 2.0, Ren goes straight to mac ports not hub. Received reply from akai who stated that as posted above disk permissions may do it. I believe the crash happens due to conflict with max/msp and running that with my monome grid in tandem with the Ren. Crashes rarely happen when the Ren is running by itself. Shame if I can't get it sorted as my monome is key to my set up as is the Ren. Will have some time tomorrow to do disk permissions and will see how it goes

Peace

I'd suggest not using a hub but plugging it in directly into a computer's USB port. Most controllers don't like being connected via a hub.

It is mate, but thanks

There appears to be two separate issues here - MPC Software crashes and kernel panics, most likely different remedies for each.

I would strip everything down and go very basic for a few days, see what happens and then re-introduce the other audio interfaces, hubs and other hardware one at a time giving a day or two gap between each new introduction.

Good call! I'm not boasting but I got a lot of hardware.!! Don't think I co,d go without for few days. My hunch is a conflict with max/msp. REN is plugged into Mac direct.

Your right, there are two issues, hadn't thought about it like that. In the process of moving so this situation will encourage me to 'go very basic'. I may well do a new install on my laptop as well and see what happens. That would at the very least rule out the hardware eh.

Thanks

Followed the tip about disk permissions and so far so good. Have kept the set up minimal, but I did open something complex and it seemed to hold without any crash. My monome works alongside but i daren't attempt any midi sync at the moment.

Peace y'all

The list below is from most common causes to less common. I'd guess it's either bad RAM, or the Ren's driver is ****. Try un-installing and re-installing the Ren driver first. Then perhaps look at the RAM.


• Defective or incompatible RAM often causes of kernel panics. Despite being a highly-reliable product, RAM can fail. Modern operating systems, like Mac OS X, are sensitive to RAM. Purchase additional RAM from either Apple or third parties who guarantee their RAM is compatible with Mac OS X, offer a liberal exchange policy, and provide a lifetime warranty should the RAM become defective or a later version of Mac OS X introduce incompatibilities.
• Incompatible, obsolete, or corrupted kernel extensions. If a third-party kernel extension or one of its dependencies is incompatible or obsolete with respect to the version of Mac OS X you are using, kernel panics may occur when the kernel executes such extensions. Likewise, if a kernel extension or one of its dependencies is corrupted, such as the result of hard disk corruption, kernel panics are likely to occur when the kernel attempts to load or execute such.
• Incompatible, obsolete, or corrupted drivers. Similar to kernel extensions, drivers for third-party hardware which are incompatible with the version of Mac OS X you are using, or which have become corrupted, will cause in kernel panics.
Hard disk corruption, including bad sectors, directory corruption, and other hard-disk ills.
• Incorrect permissions on System-related files or folders.
• Insufficient RAM and available hard disk space.
• Improperly installed hardware or software.
• Defective hardware or software. Hardware failures, including a defective CPU, or programming errors can result in kernel panics.
• Incompatible hardware. While rare, this is generally the result of a third-party hardware vendor’s product failing to properly respond to the kernel or a kernel extension in an expected way.