Skip navigation
This discussion is archived

kernel panic: hardware or software related

2642 Views 8 Replies Latest reply: Nov 8, 2008 6:37 PM by njtreehugger RSS
njtreehugger Level 1 Level 1 (0 points)
Currently Being Moderated
Oct 21, 2008 9:37 PM
I had two kernel panic incidents recently. I know that most kernel panics are related to hardware. I have not 3rd party ram and only my monitor, keyboard (apple) and mouse installed. That is, no additional usb or firewire devices. I understand that faulty ram is one possibility and that ram tests may not fully diagnose the problem. I tested my ram with rember and the techtools that I got with my applecare (runs out march 2009.) I was not able to boot into the techtools DVD so had to run it off of the harddrive after updating. I ran rember with the finder still active (there is the option to run rember without the finder running). The memory tests in rember and techtools passed which I understand may not tell me much. I have not yet run the memory test off of my install disks.

Before updating to 10.4.11 using the combo updater, I booted from my install disk and repaired the drive (it was ok) and repaired permissions (from the install disk). I did the same two tasks from the install disk after the updates, although I let a couple of days pass before doing these tasks. After reading in another forum that repairing permissions from the install disk (os 10.4.5) might have caused some problems, I just repaired permissions while running from my day-to-day account.

I have decent backups.

I thought I'd run my two kernel panics by you folk in this forum to see if anyone has any suggestions.

*kernel panic #1*

I got this kernel panic the other day on shutting down. That is I shut down using the shutdown command in the apple menu then got the kernel panick The only new thing that I had done (asides from finally updating to macosx 10.4.11 and the latest security patch) was that I had my idisk set to automatic, so the mirror agent was active. I have shut down a couple of times since with out kernel panic.

Mon Oct 20 14:00:51 2008
panic(cpu 0 caller 0x001A49CB): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x10100697, CR3: 0x00da5000, CR4: 0x000006e0
EAX: 0x30000001, EBX: 0x100fffff, ECX: 0x038c7800, EDX: 0x00000000
CR2: 0x10100697, EBP: 0x1cb6bbf8, ESI: 0x045e2b80, EDI: 0x03840000
EFL: 0x00010202, EIP: 0x005db87f, CS: 0x00000008, DS: 0x036a0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x1cb6ba18 : 0x128d0d (0x3cc65c 0x1cb6ba3c 0x131f95 0x0)
0x1cb6ba58 : 0x1a49cb (0x3d2a94 0x0 0xe 0x3d22b8)
0x1cb6bb68 : 0x19b3a4 (0x1cb6bb78 0x45e2b80 0xe 0x3b0048)
0x1cb6bbf8 : 0x5d28da (0x3840000 0x38c7800 0x38c7804 0x1)
0x1cb6bc38 : 0x5e9a4f (0x38c7800 0x1b05f000 0x1cb6bc68 0x3bf4e3)
0x1cb6bc68 : 0x5d1b7b (0x38c7800 0x1b05f000 0x38c7804 0x12db2d)
0x1cb6bc88 : 0x3b5499 (0x38c7800 0x4b069c 0x1cb6bcd8 0x0)
0x1cb6bca8 : 0x187b8a (0x38c7800 0x3842e10 0x1d 0x1cb6bcd8)
0x1cb6bcf8 : 0x12b502 (0x38d38a8 0x3d0156c 0x9 0x11cc32)
0x1cb6bd38 : 0x11f1f0 (0x38d3800 0x1cb6bdcc 0x24 0x0)
0x1cb6bd78 : 0x12b6e5 (0x38d3800 0x10000 0x0 0x1cb6bd88)
0x1cb6bda8 : 0x1494a1 (0x1cb6bdcc 0x24 0x0 0x0)
0x1cb6bdf8 : 0x120221 (0x3842e10 0x1 0x1cb6be18 0x0)
0x1cb6be18 : 0x12248f (0x3842e10 0x1 0x1cb6be68 0x140a17)
0x1cb6be68 : 0x123691 (0x30fd4f8 0x35cf 0x1b36e350 0x3130cb0)
0x1cb6bea8 : 0x13a7c4 (0x30fd4f8 0x3f 0x0 0x387d5dc) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleIntelGMA950(4.5.8)@0x5cb000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x591000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.8)@0x5a1000
dependency: com.apple.iokit.IONDRVSupport(1.4.8)@0x5bc000

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

kernel panic #2

This actually happened twice put I only have one crash log. I think that the reason why I only had one crash log is because after the second kernel panic, I had to boot into safe mode to get rid of my icalalarm scheduler from my login items because of some conflict. Anyway, the scenario is that I am using firefox 3.0 (I have the latest version) and then open google earth. After I try to open google earth, I get kernel panic.

Tue Oct 21 21:18:35 2008
panic(cpu 0 caller 0x001A49CB): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x30100697, CR3: 0x00da5000, CR4: 0x000006e0
EAX: 0x30000001, EBX: 0x300fffff, ECX: 0x00000000, EDX: 0x0362f800
CR2: 0x30100697, EBP: 0x1cbcbcb8, ESI: 0x03b40000, EDI: 0x03b40000
EFL: 0x00010202, EIP: 0x005db87f, CS: 0x00000008, DS: 0x1cbc0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x1cbcbad8 : 0x128d0d (0x3cc65c 0x1cbcbafc 0x131f95 0x0)
0x1cbcbb18 : 0x1a49cb (0x3d2a94 0x0 0xe 0x3d22b8)
0x1cbcbc28 : 0x19b3a4 (0x1cbcbc38 0x3710000 0xe 0x48)
0x1cbcbcb8 : 0x5dc781 (0x3b40000 0x202 0x1cbcbd28 0x120a26)
0x1cbcbd18 : 0x3b311f (0x3b40000 0x31d39c5 0x24 0x3cb1f8c)
0x1cbcbd68 : 0x18a309 (0x3b40000 0x7 0x44637c0 0x2)
0x1cbcbdb8 : 0x12b4ee (0x4463798 0x3cb1f64 0x0 0x0)
0x1cbcbdf8 : 0x124b17 (0x4463700 0x0 0x34 0x1cbcbedc)
0x1cbcbf08 : 0x195f2e (0x1cbcbf44 0x0 0x0 0x0)
0x1cbcbfc8 : 0x19b81e (0x3141e88 0x0 0x19e0b5 0x3a170e0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffef1b8
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleIntelGMA950(4.5.8)@0x5cb000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x591000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.8)@0x5a1000
dependency: com.apple.iokit.IONDRVSupport(1.4.8)@0x5bc000

Kernel version:
Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386
mac mini 1.66 GHz Intel Core Duo, Mac OS X (10.4.11), 1.5 GB Ram
  • Boece Level 5 Level 5 (6,245 points)
    Currently Being Moderated
    Oct 22, 2008 6:40 AM (in response to njtreehugger)
    RAM is certainly first on the list of causes for kernel panics.

    You are fortunate that the memory test was able to find it; often RAM problems are undetectable via any test program and then the only way to detect the RAM problem is to swap out RAM until the problem goes away.
    Leopard 10.5.4: Mini C2D 1.83 1G; Mini CD 1.83 2G; iBook G4 800, 640M, 10.3.9, Dell 1704-FPV, NeoOffice, Firefox3, Thunderbird, Parallels, SwiftPublisher
  • kzac2 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 8, 2008 3:55 AM (in response to njtreehugger)
    I am having the identical problem with my 2007 mac mini 1.8 ghz.
    Initially my mini failed at he grey screen and I had to use my Power mac and firewire to see and reformat the hard drive. That done I completely reloaded my standard install disks and ran all of the updates. Finally I installed Leopard and installed all of its updates. Now the system will randomly hang with the identical error message presented here. Usually when it hangs the upper 1/3 of the screen turns light gray. It requires a reboot from the power switch to get the system to work again as the keyboard and mouse are completely unresponsive when this occurs. This is most annoying and disappointing. Good thing is my mini is only 11 months old so its in warranty
    Mac Mini, Mac OS X (10.5.5), Stock
  • iSMH Level 5 Level 5 (4,310 points)
    Currently Being Moderated
    Nov 8, 2008 5:33 PM (in response to kzac2)
    kzac2-


    I would take it into your local Apple Store or Apple Service Provider. If you don't know where they are, you can locate a one here: http://www.apple.com/buy/locator/service/

    You can also call AppleCare at 1-800-275-2273, but you may be charged if your Apple product is out of warranty.
    2.4Ghz 20inch Aluminum iMac, Macbook Air, Pismo G3, Mac OS X (10.5.5), iPhone 3G, iPod Classic, 4G Nano. I have a dogcow tatoo on my ankle. Really.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.