Sample Aid
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

kernal crashes

Discussion in 'Mac OS' started by wgc, Sep 13, 2010.

  1. wgc

    wgc New Member

    I'm experiencing daily Kernal crashes. I've got a FF800 with the most recent drivers, and am running Logic 8.0.2 on Leopard 10.5.8. I also have a separate drive running 10.6.4. and Logic 9.1.1. I ALSO have an M-audio Profire 610 that I use with both OS's occasionally. In ALL these scenarios, Logic has kernal crashes that usually stem from CPU spikes and firewire bus choking/digital pops clicks etc. I usually run my buffer at 128 although I've had it happen at 256 as well I believe. This can happen sometimes when I'm even just playing Superior drums (in 9.1.1. 64 bit with the 32 bit bridge open for Superior)

    Anyway, after one of the crashes I looked at my system profiler to see my RAM, thinking perhaps I have a bad RAM chip. The computer erroneously reported 8 gigs when I have 10 installed. So I restarted and it said 10 gigs. I've pulled out and reseated all the RAM. I'm still getting the crashes. I haven't been able to run Apple Hardware Test app to check RAM. But, does anyone else have any thoughts or suggestions? Am I on the right track here?

    Best,

    Kurt
     
  2.  
  3. georgelegeriii

    georgelegeriii Senior member

    Have you tried to delete the M-Audio drivers and interface from the system and just used internal audio for a day, to test it. M-Audio drivers tend to be pretty spotty.

    Also, be VERY careful with the FW and M-Audio devices. the "never seems to be read" manual clearly states 2 things: 1) Don't use the power adapter if you are on a normal FW port, and 2) NEVER unplug the FW cable when your system is turned on. It can blow your logic board.
     
  4. wgc

    wgc New Member

    George, Thanks for the reply. I'm aware of the FW dangers of unplugging, and using with the power chord. However, the crashes are happening even when I'm NOT using the M-audio, but using my Fireface 800. You think the m-audio drivers could still be causing havoc even though they're not in use? As a side note as well, this morning when I'm booted into Snow Leopard, it's still reading my system RAM as 8 gigs instead of 10. Very weird.
     
  5. JuanTahnahmahrah

    JuanTahnahmahrah Senior member

    Reduce your memory chips to the smallest size you can boot from, and then exchange each of your chips to make sure each (or each pair) will boot properly. The fact your systems is not "seeing" 2GB of installed memory is not a good thing.
     
  6. georgelegeriii

    georgelegeriii Senior member

    The other thing to try: reseat your ram.

    Also, if you go under your apple menu, select, "About this mac", then "More Info", you will see a whole list of info about your hardware. If you select: Memory" you can see what ram is in what slot. Keep an eye on that, it will tell you which slot the ram is disappearing in. (well, that would be if you see all the ram one minute, then when you boot the next day it's missing).

    As for the FW issue, yea, completely remove the M-Audio drivers and see. When you get the kernel panic, have you ever taken a close look at exactly what it says? You might see the offending piece of software listed there.

    Were you trying to run both FW devices as an aggregate device?

    Anyways, a few more suggestions, good luck... this kind of thing drives me crazy.
     
  7. wgc

    wgc New Member

    George, I should clarify. It's not that ram is disappearing, but one time it's read as a 2 gig chip, which it is, and sometimes it will only read as 1 gig. This is ocurring with both ram chips of the pair. Hence, why sometimes my system says I have 8 gigs vs 10 gigs...So my question. Do you think the ram is flakey, or it's some hardware issue. I did re-seat all the ram chips as you had suggested. Any other thoughts?
     
  8. georgelegeriii

    georgelegeriii Senior member

    Bizarre.

    Do you know what slots in your ram slots it is> Does it change or are they always the same slots?

    To answer your question: yes, something is wrong, maybe ram, maybe logic board, but it will take more research to figure it out.

    Keep your eyes on the slots to see if you can figure out which ram sticks are "changing" amounts.
     

Share This Page