Random shutdowns (kernel panics) on new iMac running Mavericks

Question

Level 1

5 points

Random shutdowns (kernel panics) on new iMac running Mavericks

Hi,

I have a brand new iMac 3.4 GHz Intel Core i5, 28gb RAM, OSX 10.9.2 at work which has been running for just over 2 weeks. During that time I have experience 17 kernel panics that appear to have no pattern to them at all. Today I have had 2, one when using iMessage and one whilst using Photoshop CC.

The latest panic text is below I would appreciate it if someone could take a look and give me an insight into what might be causing it. The only real non-Mac software that I have installed is the Creative Cloud Suite – InDesign, Illustrator, Photoshop, Acrobat and Bridge along with Extensis Suitcase Fusion 5.

I am connected to an Exchange server for works email via wifi (not LAN).

If there are any other questions just let me know.

Anonymous UUID: D932AC27-89C2-A594-7A00-6212712D2B48

Tue Mar 25 11:05:54 2014

panic(cpu 2 caller 0xffffff801d6dbe2e): Kernel trap at 0xffffff7f9eaa5eb5, type 13=general protection, registers:

CR0: 0x000000008001003b, CR2: 0x000000010e92b000, CR3: 0x00000000202f0000, CR4: 0x00000000001606e0

RAX: 0xffffff7f9ead8860, RBX: 0xffffff80571a0e00, RCX: 0xffffff8055e8c004, RDX: 0x0000000000000017

RSP: 0xffffff8356383e00, RBP: 0xffffff8356383e20, RSI: 0x0000000000000041, RDI: 0xffffff80571a0e00

R8: 0x000000000000ce58, R9: 0xffffff801dccb540, R10: 0x0000000000000000, R11: 0xffffff801dc89ce8

R12: 0x0000000000000041, R13: 0x000000000000001f, R14: 0xffffff8055e8c004, R15: 0x0000000000000017

RFL: 0x0000000000010246, RIP: 0xffffff7f9eaa5eb5, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0x000000010e92b000, Error code: 0x0000000000000000, Fault CPU: 0x2

Backtrace (CPU 2), Frame : Return Address

0xffffff8332b95df0 : 0xffffff801d622fa9

0xffffff8332b95e70 : 0xffffff801d6dbe2e

0xffffff8332b96040 : 0xffffff801d6f3326

0xffffff8332b96060 : 0xffffff7f9eaa5eb5

0xffffff8356383e20 : 0xffffff7f9eaa5e45

0xffffff8356383e60 : 0xffffff7f9ea853dd

0xffffff8356383eb0 : 0xffffff7f9ea7ca38

0xffffff8356383ee0 : 0xffffff7f9ea7c9cf

0xffffff8356383ef0 : 0xffffff7f9ea7ae09

0xffffff8356383f30 : 0xffffff7f9eab9df7

0xffffff8356383f50 : 0xffffff7f9eab9da6

0xffffff8356383f70 : 0xffffff7f9eab9e1c

0xffffff8356383f90 : 0xffffff7f9eab9f10

0xffffff8356383fb0 : 0xffffff801d6d6ff7

Kernel Extensions in backtrace:

com.apple.iokit.IOBluetoothFamily(4.2.3f10)[87FE20F9-499A-3125-B216-F9120B6D4AB 5]@0xffffff7f9ea75000->0xffffff7f9eb11fff

dependency: com.apple.iokit.IOUSBFamily(675.4.0)[5C861553-BC5A-3979-A6B4-58C57879DD40]@0xff ffff7f9e5d7000

dependency: com.apple.iokit.IOReportFamily(23)[D203F7D3-47CA-382B-B401-8535CD4CBC49]@0xffff ff7f9e924000

BSD process name corresponding to current thread: kernel_task

Mac OS version:

13C64

Kernel version:

Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64

Kernel UUID: 9FEA8EDC-B629-3ED2-A1A3-6521A1885953

Kernel slide: 0x000000001d400000

Kernel text base: 0xffffff801d600000

System model name: iMac14,2 (Mac-27ADBB7B4CEE8E61)

System uptime in nanoseconds: 3354856553384

last loaded kext at 1419078968318: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f9fc49000, size 49152)

last unloaded kext at 1521192698035: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f9fc49000, size 32768)

loaded kexts:

com.apple.filesystems.smbfs 2.0.1

com.apple.driver.AppleBluetoothMultitouch 80.14

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.iokit.IOBluetoothSerialManager 4.2.3f10

com.apple.filesystems.autofs 3.0

com.apple.driver.AudioAUUC 1.60

com.apple.driver.AGPM 100.14.15

com.apple.driver.ApplePlatformEnabler 2.0.9d1

com.apple.driver.X86PlatformShim 1.0.0

com.apple.driver.AppleMikeyHIDDriver 124

com.apple.driver.AppleMikeyDriver 2.6.0f1

com.apple.driver.AppleHDA 2.6.0f1

com.apple.iokit.IOUserEthernet 1.0.0d1

com.apple.driver.AppleUpstreamUserClient 3.5.13

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.3f10

com.apple.driver.AppleHWAccess 1

com.apple.GeForce 8.2.4

com.apple.driver.AppleBacklight 170.3.5

com.apple.driver.AppleMCCSControl 1.1.12

com.apple.driver.AppleLPC 1.7.0

com.apple.driver.AppleThunderboltIP 1.1.2

com.apple.driver.AppleSMCLMU 2.0.4d1

com.apple.driver.AppleIntelHD5000Graphics 8.2.4

com.apple.driver.AppleIntelFramebufferAzul 8.2.4

com.apple.iokit.SCSITaskUserClient 3.6.6

com.apple.driver.AppleUSBODD 3.4.1

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 35

com.apple.driver.AppleUSBHub 666.4.0

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCIBlockStorage 2.5.1

com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2

com.apple.driver.AppleAHCIPort 3.0.0

com.apple.driver.AppleSDXC 1.5.2

com.apple.driver.AirPort.Brcm4360 831.21.63

com.apple.driver.AppleUSBXHCI 670.4.0

com.apple.driver.AppleACPIButtons 2.0

com.apple.driver.AppleRTC 2.0

com.apple.driver.AppleHPET 1.8

com.apple.driver.AppleSMBIOS 2.1

com.apple.driver.AppleACPIEC 2.0

com.apple.driver.AppleAPIC 1.7

com.apple.nke.applicationfirewall 153

com.apple.security.quarantine 3

com.apple.driver.AppleBluetoothHIDKeyboard 170.15

com.apple.driver.AppleHIDKeyboard 170.15

com.apple.driver.IOBluetoothHIDDriver 4.2.3f10

com.apple.driver.AppleMultitouchDriver 245.13

com.apple.iokit.IOSerialFamily 10.0.7

com.apple.kext.triggers 1.0

com.apple.driver.DspFuncLib 2.6.0f1

com.apple.vecLib.kext 1.0.0

com.apple.iokit.IOAudioFamily 1.9.5fc2

com.apple.kext.OSvKernDSPLib 1.14

com.apple.iokit.IOBluetoothFamily 4.2.3f10

com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.3f10

com.apple.driver.AppleSMBusPCI 1.0.12d1

com.apple.iokit.IOAcceleratorFamily 98.14

com.apple.nvidia.driver.NVDAGK100Hal 8.2.4

com.apple.nvidia.driver.NVDAResman 8.2.4

com.apple.driver.AppleHDAController 2.6.0f1

com.apple.iokit.IOHDAFamily 2.6.0f1

com.apple.driver.AppleBacklightExpert 1.0.4

com.apple.driver.AppleSMBusController 1.0.11d1

com.apple.driver.X86PlatformPlugin 1.0.0

com.apple.driver.IOPlatformPluginFamily 5.7.0d10

com.apple.driver.AppleThunderboltEDMSink 2.1.3

com.apple.driver.AppleSMC 3.1.8

com.apple.iokit.IOSurface 91

com.apple.AppleGraphicsDeviceControl 3.4.35

com.apple.iokit.IOAcceleratorFamily2 98.14

com.apple.iokit.IONDRVSupport 2.4.1

com.apple.iokit.IOGraphicsFamily 2.4.1

com.apple.driver.AppleUSBMergeNub 650.4.0

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.6.6

com.apple.iokit.IOBDStorageFamily 1.7

com.apple.iokit.IODVDStorageFamily 1.7.1

com.apple.iokit.IOCDStorageFamily 1.7.1

com.apple.driver.AppleThunderboltDPInAdapter 3.1.7

com.apple.driver.AppleThunderboltDPOutAdapter 3.1.7

com.apple.driver.AppleThunderboltDPAdapterFamily 3.1.7

com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5

com.apple.iokit.IOUSBMassStorageClass 3.6.0

com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6

com.apple.driver.AppleUSBComposite 656.4.1

com.apple.iokit.IOUSBUserClient 660.4.2

com.apple.driver.AppleThunderboltNHI 2.0.1

com.apple.iokit.IOThunderboltFamily 3.2.7

com.apple.iokit.IOEthernetAVBController 1.0.3b4

com.apple.iokit.IOAHCIFamily 2.6.5

com.apple.iokit.IO80211Family 630.35

com.apple.driver.mDNSOffloadUserClient 1.0.1b5

com.apple.iokit.IONetworkingFamily 3.2

com.apple.iokit.IOUSBFamily 675.4.0

com.apple.driver.AppleEFINVRAM 2.0

com.apple.driver.AppleEFIRuntime 2.0

com.apple.iokit.IOHIDFamily 2.0.0

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 278.11

com.apple.kext.AppleMatch 1.0.0d1

com.apple.security.TMSafetyNet 7

com.apple.driver.AppleKeyStore 2

com.apple.driver.DiskImages 371.1

com.apple.iokit.IOStorageFamily 1.9

com.apple.iokit.IOReportFamily 23

com.apple.driver.AppleFDEKeyStore 28.30

com.apple.driver.AppleACPIPlatform 2.0

com.apple.iokit.IOPCIFamily 2.9

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.pthread 1

com.apple.kec.corecrypto 1.0

iMac, OS X Mavericks (10.9.2)

Posted on Mar 25, 2014 4:20 AM

Reply

Answer 1

Barney-15E

Level 10

123,020 points

Mar 25, 2014 4:37 AM in response to markbird

Since that panic wasn't caused by any third-party kernel extensions, that leaves hardware (or some obscure bug--unlikely but possible).

Hardware problems are commonly caused by RAM, but could be anything externally attached.

Since Apple doesn't sell an iMac with 28GB of RAM, it is likely the RAM you added may be the problem.

Replace the orginal RAM and test, or run Rember to check. A pass doesn't mean it is good. The only positive test result is if it fails.

Reply

Answer 2

markbird Author

Level 1

5 points

Mar 25, 2014 6:27 AM in response to Barney-15E

Thanks Barney, I've tested the memory with Rember and it passed. Maybe I should run a hardware test too?

Rember Test Results

All tests passed!

Total built-in memory: 28 GB

This is the total amount of physical memory that the computer has installed. If this figure is not showing the correct amount of memory there may be a problem with one or more installed DIMMS.

Available memory: 22818 MB

Available memory is the amount of physical memory that is currently not in use by any other processes. All available memory will be used for testing when the "All" option is selected. To increase the amount of available memory, you can restart your computer before testing. If you are familiar with the command line (CLI), you can run memtest (the core of Rember) in single-user mode. See Rember help, or http://www.memtestosx.org for more information.

Requested amount: All MB

The total amount of memory requested for testing by the Rember application. Not all requested memory can be allocated for testing. See information on "Available memory" for more information.

Memory allocated for testing: 22818 MB

This is the total amount of memory that memtest was able to allocate for testing. See "Available memory" section for more information.

-------

Loops selected: 1

Total loops selected by user for testing. All loops should complete when testing is successful. Test failure when the "Continue on Error" preference is selected will cancel tests before this number of loops has been completed. Users can also cancel testing before this number is reached.

Loops completed: 1

Total loops completed by memtest. Note that the Rember is not always able to identify how many loops ran. If there are discrepancies between this and the loops selected, the log should be examined to determine exactly how many loops were performed.

-------

Total execution time: All tests passed! Execution time: 6277 seconds

This is the total amount of time that it took to execute the selected tests. Execution time may vary from system to system, and is provided as a guide for determining how long users can expect tests to run based on the amount of memory installed on the system.

Testing start time: 2014-03-25 11:39:15 +0000

Testing end time: 2014-03-25 13:23:59 +0000

Rember version: 0.3.7b Memtest version: 4.22

Reply

Answer 3

Barney-15E

Level 10

123,020 points

Mar 25, 2014 5:53 PM in response to markbird

Yes, run the Apple Hardware Tests, but again, any positive results are suspect. Only negative results can be trusted.

Reply

Answer 4

markbird Author

Level 1

5 points

Mar 25, 2014 11:41 PM in response to Barney-15E

Thanks Barney, I will do that later but I'm not sure i understand what you mean. Surely it's possible that the RAM isn't the problem so I don't understand why any positive results would be suspect?

Reply

Answer 5

Barney-15E

Level 10

123,020 points

Mar 26, 2014 4:10 AM in response to markbird

markbird wrote:

Thanks Barney, I will do that later but I'm not sure i understand what you mean. Surely it's possible that the RAM isn't the problem so I don't understand why any positive results would be suspect?

You can never trust a "Passing" hardware test. You can only be certain if they fail. They just are not robust enough to check everything, especially RAM checks. You cannot test RAM that is in use. There is always some RAM being used by the OS, so there is no way to test every bit of it.

Reply

Answer 6

Jul 23, 2015 6:06 PM in response to markbird

@Markbird I have just resolved a long standing kernel panic problem. It was driving me crazy and a lot of the info I found online did not help me to resolve it. (I had tried disconnecting peripherals, RAM, and turning off web extensions) The next step was deciphering the reports that are sent to Apple but that was beyond me.

In the end it was a demo version of Suitcase 5 that was causing it, even though I didn't use it, it must have been running things in the background. I stumbled on to it by going to the Finder menu/Go/Library (hold down option to see it)/Logs/DiagnosticReports.

There were a few 'crash' things in the folder but I noticed that items related to Suitcase kept recurring. So I uninstalled it...properly using their 'uninstall' tool (not just by dragging it to the trash)...and it seems to be smooth sailing after almost a year of regular crashes (I'm more tolerant than I should be!). I subsequently went through and upgraded any other drivers and weeded out unused software. Also made sure that unwanted things weren't automatically starting up on logon (Apple/SystemPreferences/Users&Groups/User/LoginItems).

By reports kernel panics are difficult to diagnose so I don't know if this will help you. But I'm writing this for you and anyone else because its a simple way to eliminate potential problems. Good luck.

Reply