Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: Oral B.
Oral B. Author
User level: Level 1
5 points

What Causes These Kernel Panics?

Hey everyone! So since i installed Mountain Lion on my Mac Mini (2010 model), I've been having some issues. About 3/4 times I start it up in the morning, it has a kernel panic anywhere from once to three times. It usually boots up though after a few. So far, I've tried:


Verify and repair disc permissions (On the HDD and Time Machine)

Verify and repaired disc (On the HDD and Time Machine)

Booting up without the time machine disc connected

Used Apples hardware test


I thought doing all this would fix the issue, but it still happens. Does anyone know how I can fix these?

2010 Mac Mini, Mac OS X (10.6.5)

Posted on Jan 22, 2013 9:02 AM

Reply
Question marked as Top-ranking reply
User profile for user: CT
CT
User level: Level 7
24,167 points

Posted on Jan 22, 2013 9:05 AM

You will probably have to post the panic logs for someone with expertise to analyze.


This is worth a look:


OS X: About kernel panics


charlie


P.S. Thanks for all you do for dental hygiene!

View in context
5 replies
Sort By: 
User profile for user: KarenSelena
KarenSelena
User level: Level 4
1,977 points

Jan 22, 2013 9:09 AM in response to Oral B.

Kernel Panics can be caused by either software issues, or hardware issues. They are not always easy to diagnose what is causing the issue. It could even be caused by a device you have connected, like a "printer with a hardware issue".


Running the Apple Hardware Test in Loop mode, and often assist in diagnosing these intermittent issues.


Check out this web site - http://www.thexlab.com/faqs/kernelpanics.html.



BOOTING TO APPLE HARDWARE TEST - CONTINUOUS LOOP MODE ---

HT1509 - Intel-based Macs: Using Apple Hardware Test


Many times, running the "quick" test, or the "extended" test, may not give you any error results. Many intermittent issues, may need to have the hardware test to run in loop mode, before it detects any error, and therefore running the Apple Hardware Test in Loop Mode overnight is an excellent troubleshooting step for finding intermittent hardware problems.

In continuous Loop Mode, the test will run continuously until a problem is found or is stopped by clicking Stop Test or by using the Command-period keyboard shortcut. If a problem is found, the test will cease to loop, indicating the problem it found. If the test fails, be sure to write down the exact message associated with the failure. Looping mode could be helpful in diagnosing a fault that may be heat related or when the fault occurs randomly.-------

-- Insert your install disk 1 into the optical drive

-- shut down computer

-- restart computer holding down the D key until you see a screen with an icon of a computer appear ***NOTE if this does not boot you to the apple hardware test, try restarting computer holding down the "option" key instead, then click the right arrow to get the hardware test

-- select English as your language and press enter

-- The Apple Hardware Test console appears. You can choose what sort of test or tests to perform: basic or select the "Perform extended testing"

-- press and hold down the option key and the "L" key...then select the extended test. This will make the test go into Loop mode

-- look over the test results and make notes of any errors that may be logged

-- to exit out of the test, press the escape key

Reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,703 points

Jan 22, 2013 12:12 PM in response to Oral B.

If you have more than one user account, you must be logged in as an administrator to carry out these instructions.

Launch the Console application in any of the following ways:


☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)


☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.


☞ Open LaunchPad. Click Utilities, then Console in the icon grid.


Select the most recent panic log under System Diagnostic Reports. Post the entire contents — the text, please, not a screenshot. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header and body of the report, if it’s present (it may not be.) Please don't post shutdownStall, spin, or hang reports.

Reply
User profile for user: Oral B.
Oral B. Author
User level: Level 1
5 points

Jan 24, 2013 10:40 AM in response to Linc Davis

Thank you, this is what I found, it was labeled as a "Saved panic report from kernel". Is this the right one?




Mon Jan 21 10:38:47 2013

panic(cpu 1 caller 0xffffff80042b7bd5): Kernel trap at 0xffffff800422d507, type 13=general protection, registers:

CR0: 0x000000008001003b, CR2: 0x00007fff6f7ca15c, CR3: 0x0000000006f17000, CR4: 0x0000000000000660

RAX: 0xffffff800b0c7aa0, RBX: 0xffffff800b0c7aa0, RCX: 0xffffff80439abfc0, RDX: 0xffffff80439a8000

RSP: 0xffffff80439abe00, RBP: 0xffffff80439abe40, RSI: 0x01ffff800b035550, RDI: 0xffffff800b0c7aa0

R8: 0xffffff800b0c7c68, R9: 0xffffffffffffffff, R10: 0x00000000ffffffff, R11: 0x00000000ffffff80

R12: 0xffffff80048bebe8, R13: 0x0000000000000000, R14: 0x01ffff800b035550, R15: 0x0000000000000000

RFL: 0x0000000000010086, RIP: 0xffffff800422d507, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0x00007fff6f7ca15c, Error code: 0x0000000000000000, Fault CPU: 0x1



Backtrace (CPU 1), Frame : Return Address

0xffffff80439abaa0 : 0xffffff800421d626

0xffffff80439abb10 : 0xffffff80042b7bd5

0xffffff80439abce0 : 0xffffff80042ce4ed

0xffffff80439abd00 : 0xffffff800422d507

0xffffff80439abe40 : 0xffffff800422e74f

0xffffff80439abec0 : 0xffffff800422da0c

0xffffff80439abf00 : 0xffffff800421c7f7

0xffffff80439abf20 : 0xffffff7f8524f63f

0xffffff80439abf40 : 0xffffff7f85248ad5

0xffffff80439abf60 : 0xffffff800423dcde

0xffffff80439abfb0 : 0xffffff80042b26b7

Kernel Extensions in backtrace:

com.apple.driver.AppleUSBHub(5.2.5)[A70C7553-FFEA-355F-A292-6E2B0023FADD]@0xfff fff7f85246000->0xffffff7f8525afff

dependency: com.apple.iokit.IOUSBFamily(5.4.0)[C3094550-7F58-3933-A4F7-CD33AE83F8B9]@0xffff ff7f850d6000



BSD process name corresponding to current thread: kernel_task



Mac OS version:

Not yet set



Kernel version:

Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64

Kernel UUID: (I blocked out these numbers, if they're important I can post them).

Kernel slide: 0x0000000004000000

Kernel text base: 0xffffff8004200000

System model name: Macmini4,1 (Mac-F2208EC8)



System uptime in nanoseconds: 2261911175

last loaded kext at 1044744481: com.apple.driver.CoreStorageFsck 274.7 (addr 0xffffff7f85baf000, size 102400)

loaded kexts:

com.apple.driver.CoreStorageFsck 274.7

com.apple.driver.AppleFileSystemDriver 3.0.1

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 34

com.apple.driver.AppleIRController 320.15

com.apple.iokit.SCSITaskUserClient 3.5.1

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCIBlockStorage 2.2.2

com.apple.driver.AppleSDXC 1.2.2

com.apple.iokit.AppleBCM5701Ethernet 3.2.5b3

com.apple.driver.AppleFWOHCI 4.9.6

com.apple.driver.AppleAHCIPort 2.4.1

com.apple.driver.AirPort.Brcm4331 602.15.22

com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0

com.apple.driver.AppleUSBHub 5.2.5

com.apple.driver.AppleEFINVRAM 1.6.1

com.apple.driver.AppleUSBEHCI 5.4.0

com.apple.driver.AppleUSBOHCI 5.2.5

com.apple.driver.AppleRTC 1.5

com.apple.driver.AppleHPET 1.7

com.apple.driver.AppleACPIButtons 1.6

com.apple.driver.AppleSMBIOS 1.9

com.apple.driver.AppleACPIEC 1.6

com.apple.driver.AppleAPIC 1.6

com.apple.nke.applicationfirewall 4.0.39

com.apple.security.quarantine 2

com.apple.driver.AppleIntelCPUPowerManagement 196.0.0

com.apple.driver.CoreStorage 274.7

com.apple.iokit.IOSCSIBlockCommandsDevice 3.5.1

com.apple.iokit.IOUSBHIDDriver 5.2.5

com.apple.iokit.IOUSBMassStorageClass 3.5.0

com.apple.driver.AppleUSBMergeNub 5.2.5

com.apple.driver.AppleUSBComposite 5.2.5

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.5.1

com.apple.iokit.IOBDStorageFamily 1.7

com.apple.iokit.IODVDStorageFamily 1.7.1

com.apple.iokit.IOCDStorageFamily 1.7.1

com.apple.iokit.IOAHCISerialATAPI 2.5.0

com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.1

com.apple.iokit.IOEthernetAVBController 1.0.2b1

com.apple.iokit.IOFireWireFamily 4.5.5

com.apple.iokit.IOAHCIFamily 2.2.1

com.apple.iokit.IO80211Family 500.15

com.apple.iokit.IONetworkingFamily 3.0

com.apple.driver.AppleMCP89RootPortPM 1.11

com.apple.iokit.IOUSBUserClient 5.2.5

com.apple.iokit.IOUSBFamily 5.4.0

com.apple.driver.NVSMU 2.2.9

com.apple.driver.AppleEFIRuntime 1.6.1

com.apple.iokit.IOHIDFamily 1.8.0

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 220

com.apple.kext.AppleMatch 1.0.0d1

com.apple.security.TMSafetyNet 7

com.apple.driver.DiskImages 344

com.apple.iokit.IOStorageFamily 1.8

com.apple.driver.AppleKeyStore 28.21

com.apple.driver.AppleACPIPlatform 1.6

com.apple.iokit.IOPCIFamily 2.7.2

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.corecrypto 1.0

Reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,703 points

Jan 24, 2013 11:23 AM in response to Oral B.

There are other reports of kernel panics like this one with FileVault. The cause seems to be an OS bug that only affects certain models and/or aftermarket SSD's. Make sure your system is fully updated. If it is, the only workaround I know of is to deactivate FileVault.

Reply

What Causes These Kernel Panics?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up