Please help, I'm having Kernal Panics galore in OSX 10.4.11

Discussion in 'Mac Basics and Help' started by lavaman, Jan 4, 2010.

  1. lavaman macrumors newbie

    Joined:
    Jan 4, 2010
    #1
    Hello, I've searched and searched and can't seem to find an answer anywhere on the net so hopefully this wonderful forum will come to my rescue.

    I'm running OSX 10.4.11 on a Mac Pro Intell machine.

    On December 15th, I bought a "Logitech Performance mouse MX" and a few days later, I began getting kernal panic (You need to restart your computer) warnings. I thought it was the driver so I went and bought "Steermouse", removed the "Logitech Control Center" and it happened again a few days later. Then I got "USB Overdrive" and again, kernal panics. Now these have been happening sporadically since the 15th (I've probably had 15 or more since then) and sometimes they happen daily, sometimes only once a day and sometimes up to 4 a day.

    I called Apple last Tuesday to find out my Applecare had recently expired but the guy told me that kernal panics are usually an OS issue and I should "Archive and Install". I did that and everything was going great until Friday, when the kernal panics started up again. I've unplugged my mouse since but everyone has been telling me that it's not the mouse (since I've used 3 different drivers).

    I had 2 kernal panics yesterday and here is what my crash report said:
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

    Sun Jan 3 11:15:00 2010
    panic(cpu 0 caller 0x001416B5): zalloc: zone "kernel map entries" empty.
    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x4b7c37d8 : 0x128d0d (0x3cc65c 0x4b7c37fc 0x131f95 0x0)
    0x4b7c3818 : 0x1416b5 (0x3cd34c 0x3cd92c 0xc550870 0x1)
    0x4b7c3878 : 0x1418df (0x227de40 0x1 0x0 0x206)
    0x4b7c3898 : 0x163b26 (0x227de40 0x0 0x4b7c38c8 0x1a3736)
    0x4b7c38b8 : 0x163e3b (0x0 0x1908f48 0xb18b3000 0x0)
    0x4b7c38f8 : 0x16eeb2 (0x1908f3c 0x1909000 0xb18b2000 0x0)
    0x4b7c3a38 : 0x1840ab (0x1908f3c 0x4b7c3ad0 0x1000 0x0)
    0x4b7c3af8 : 0x1841f4 (0x1908f3c 0x4b7c3b48 0x1000 0x0)
    0x4b7c3b58 : 0x3a6255 (0x1908f3c 0x4b7c3bf8 0x1000 0x0)
    0x4b7c3bb8 : 0x3a6717 (0x1908f3c 0x4b7c3bf0 0x0 0x4b7c3bdc)
    0x4b7c3c28 : 0x3a5933 (0xb6e7380 0x1908f3c 0xb6e73e8 0x1)
    0x4b7c3ca8 : 0x39e932 (0xb6e7380 0x1908f3c 0xb6e73e8 0x1)
    0x4b7c3d58 : 0x39e3bc (0xb6e7380 0x0 0x13 0x1e)
    0x4b7c3d98 : 0x39eb8e (0xb6e7380 0x13 0x1e 0x1e)
    0x4b7c3dc8 : 0x39ebf3 (0xb6e7380 0x13 0x1e 0x1e)
    0x4b7c3de8 : 0x39ec86 (0xb6e7380 0x4b7c3e50 0x1e 0x3) Backtrace continues...

    Kernel version:
    Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386


    *********

    Sun Jan 3 23:15:53 2010
    panic(cpu 1 caller 0x001416B5): zalloc: zone "kernel map entries" empty.
    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x4b5237d8 : 0x128d0d (0x3cc65c 0x4b5237fc 0x131f95 0x0)
    0x4b523818 : 0x1416b5 (0x3cd34c 0x3cd92c 0x119625f0 0x1)
    0x4b523878 : 0x1418df (0x227de40 0x1 0x330000 0x200206)
    0x4b523898 : 0x163b26 (0x227de40 0x0 0x4b5238c8 0x1a3736)
    0x4b5238b8 : 0x163e3b (0x49ca8000 0x1908f48 0xb1b89000 0x0)
    0x4b5238f8 : 0x16eeb2 (0x1908f3c 0x1909000 0xb1b88000 0x0)
    0x4b523a38 : 0x1840ab (0x1908f3c 0x4b523ad0 0x1000 0x0)
    0x4b523af8 : 0x1841f4 (0x1908f3c 0x4b523b48 0x1000 0x0)
    0x4b523b58 : 0x3a6255 (0x1908f3c 0x4b523bf8 0x1000 0x0)
    0x4b523bb8 : 0x3a6717 (0x1908f3c 0x4b523bf0 0x0 0x4b523bdc)
    0x4b523c28 : 0x3a5933 (0xe4c1200 0x1908f3c 0xe4c1268 0x1)
    0x4b523ca8 : 0x39e932 (0xe4c1200 0x1908f3c 0xe4c1268 0x1)
    0x4b523d58 : 0x39e3bc (0xe4c1200 0x0 0x13 0x1e)
    0x4b523d98 : 0x39eb8e (0xe4c1200 0x13 0x1e 0x1e)
    0x4b523dc8 : 0x39ebf3 (0xe4c1200 0x13 0x1e 0x1e)
    0x4b523de8 : 0x39ec86 (0xe4c1200 0x4b523e50 0x1e 0x3) Backtrace continues...

    Kernel version:
    Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

    I did the research, did the disk utility, first aid, repaired the privileges, did a hardware test, diskwwarrior, called Logitech, Apple...

    Does anyone have any suggestions for me?

    Thank you in advance and Happy New Year to everyone. :)

    Wayne
     
  2. BlueRevolution macrumors 603

    BlueRevolution

    Joined:
    Jul 26, 2004
    Location:
    Montreal, QC
    #2
    Try retiring your mouse for a bit. Since the problem began with its installation, it may end with its removal — if you're lucky.

    Contrary to what the tech said, in my experience kernel panics are usually hardware-related, but OS reinstalls are definitely cheaper than new logic boards.
     
  3. chasemac macrumors 6502a

    chasemac

    Joined:
    Jan 30, 2005
    Location:
    In a house.
    #3
    I agree with retiring the mouse for awhile and also removing the mouse software you have installed. Monitor it again for a few days if you can. I would also do a full backup. If you get an error again then I would do a clean install. Then I would not add that mouse or software again for a few days to make sure there is no hardware issues.
     
  4. lavaman thread starter macrumors newbie

    Joined:
    Jan 4, 2010
    #4
    Thanks guys. Haven't had a single kernal panic since unplugging the mouse.
    Sucks though, since I LOVEd that mouse. Do any of you know the possible cause of the conflict? Should I return the mouse or upgrade to Snow Leopard?

    Thanks a million, this site is great!
     
  5. chasemac macrumors 6502a

    chasemac

    Joined:
    Jan 30, 2005
    Location:
    In a house.
    #5
    This is a tuff puzzle to solve. I happen to use a logitech mx1000 mouse (older version of yours) that I use with my Macbook Pro. I never installed the logitech software and it works fine. I am running snow leopard by the way. Since you like the mouse and want to use it you could try throwing a little more money at it and get SL. There may be an issue solved with certain kernel panics with the upgrade. Just make sure you do a good backup.
     

Share This Page