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

User profile for user: Balaamsdonkey
Balaamsdonkey Author
User level: Level 1
14 points

Kernel Panic

Can someone tell me if the kernel Panic in question is hardware or software based? Can you also identify the areas that indicate which?


Thank you!


Thu Oct 17 17:02:28 2013

Machine-check capabilities 0x0000000000000c09:

family: 6 model: 58 stepping: 9 microcode: 21

Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz

9 error-reporting banks

threshold-based error status present

extended corrected memory error handling present

Processor 0: no valid machine-check state

Processor 1: no valid machine-check state

Processor 2: machine-check status 0x0000000000000005:

restart IP valid

machine-check in progress

MCA error-reporting registers:

IA32_MC0_STATUS(0x401): 0xf600004000040150 valid

MCA error code: 0x0150

Model specific error code: 0x0004

Other information: 0x00000040

Threshold-based status: Undefined

Status bits:

Processor context corrupt

ADDR register valid

Error enabled

Uncorrected error

Error overflow

IA32_MC0_ADDR(0x402): 0x0000000110290265

IA32_MC1_STATUS(0x405): 0x1980000000000000 invalid

IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid

IA32_MC3_STATUS(0x40d): 0x0000000000000000 invalid

IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid

IA32_MC5_STATUS(0x415): 0x0020000000000000 invalid

IA32_MC6_STATUS(0x419): 0x0020000000000000 invalid

IA32_MC7_STATUS(0x41d): 0x0020000000000000 invalid

IA32_MC8_STATUS(0x421): 0x0020000000000000 invalid

Processor 3: machine-check status 0x0000000000000005:

restart IP valid

machine-check in progress

MCA error-reporting registers:

IA32_MC0_STATUS(0x401): 0xf600004000040150 valid

MCA error code: 0x0150

Model specific error code: 0x0004

Other information: 0x00000040

Threshold-based status: Undefined

Status bits:

Processor context corrupt

ADDR register valid

Error enabled

Uncorrected error

Error overflow

IA32_MC0_ADDR(0x402): 0x0000000110290265

IA32_MC1_STATUS(0x405): 0x1980000000000000 invalid

IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid

IA32_MC3_STATUS(0x40d): 0x0000000000000000 invalid

IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid

IA32_MC5_STATUS(0x415): 0x0020000000000000 invalid

IA32_MC6_STATUS(0x419): 0x0020000000000000 invalid

IA32_MC7_STATUS(0x41d): 0x0020000000000000 invalid

IA32_MC8_STATUS(0x421): 0x0020000000000000 invalid

Processor 4: no valid machine-check state

Processor 5: no valid machine-check state

Processor 6: no valid machine-check state

Processor 7: no valid machine-check state

panic(cpu 4 caller 0xffffff80046b91b9): "Machine Check at 0x78303e676e697274, registers:\n" "CR0: 0x0000000080010033, CR2: 0x000000010bb03ff8, CR3: 0x000000008cb2900d, CR4: 0x00000000001606e0\n" "RAX: 0x3730303078302c38, RBX: 0x0000002300000000, RCX: 0x3230303700000000, RDX: 0x2eeb85c802a4bab3\n" "RSP: 0x303078302c313230, RBP: 0xb0e53bc000000000, RSI: 0x0000002300000023, RDI: 0x000000230000000f\n" "R8: 0xb0e543582eeb843d, R9: 0x10f4680000008001, R10: 0x0bb03ff8b0e54218, R11: 0x0000020600000000\n" "R12: 0x0000001b00000000, R13: 0x02a4cea100000000, R14: 0x00000000ffffff80, R15: 0x046cf4d000000000\n" "RFL: 0x303130666678302c, RIP: 0x78303e676e697274, CS: 0x0000000000003030, SS: 0x0000000000003730\n" "Error code: 0x733c3e79656b2f3c\n"@/SourceCache/xnu/xnu-2050.48.11/osfmk/i386/trap_native.c: 280

Backtrace (CPU 4), Frame : Return Address

0xffffff807e105f20 : 0xffffff800461d636

0xffffff807e105f90 : 0xffffff80046b91b9

0xffffff807e106100 : 0xffffff80046cf4df



BSD process name corresponding to current thread: LogosIndexer



Mac OS version:

12F37



Kernel version:

Darwin Kernel Version 12.5.0: Mon Jul 29 16:33:49 PDT 2013; root:xnu-2050.48.11~1/RELEASE_X86_64

Kernel UUID: B1B58405-A2B2-3C44-B25D-495053D52AB5

Kernel slide: 0x0000000004400000

Kernel text base: 0xffffff8004600000

System model name: MacBookPro9,1 (Mac-4B7AC7E43945597E)



System uptime in nanoseconds: 1591720801525

last loaded kext at 265211821517: com.apple.filesystems.msdosfs 1.8.1 (addr 0xffffff7f86a07000, size 65536)

last unloaded kext at 326590975856: com.apple.driver.AppleFileSystemDriver 3.0.1 (addr 0xffffff7f8691c000, size 8192)

loaded kexts:

com.apple.driver.AudioAUUC 1.60

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.driver.AGPM 100.13.12

com.apple.driver.X86PlatformShim 1.0.0

com.apple.filesystems.autofs 3.0

com.apple.iokit.IOBluetoothSerialManager 4.1.7f2

com.apple.driver.AppleMikeyHIDDriver 124

com.apple.driver.AppleHDA 2.4.7fc2

com.apple.GeForce 8.1.6

com.apple.iokit.IOUserEthernet 1.0.0d1

com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.1.7f2

com.apple.driver.AppleUpstreamUserClient 3.5.12

com.apple.driver.SMCMotionSensor 3.0.3d1

com.apple.driver.AppleMCCSControl 1.1.11

com.apple.driver.AppleMuxControl 3.4.5

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.ApplePolicyControl 3.4.5

com.apple.driver.AppleSMCLMU 2.0.3d0

com.apple.driver.AppleMikeyDriver 2.4.7fc2

com.apple.driver.AppleLPC 1.6.3

com.apple.driver.AppleSMBusPCI 1.0.11d1

com.apple.driver.AppleIntelHD4000Graphics 8.1.6

com.apple.driver.AppleIntelFramebufferCapri 8.1.6

com.apple.driver.AppleSMCPDRC 1.0.0

com.apple.driver.AppleUSBTCButtons 237.1

com.apple.driver.AppleIRController 320.15

com.apple.driver.AppleUSBTCKeyboard 237.1

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 34

com.apple.iokit.SCSITaskUserClient 3.5.6

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCIBlockStorage 2.3.5

com.apple.driver.AppleUSBHub 623.4.4

com.apple.driver.AppleSDXC 1.4.3

com.apple.iokit.AppleBCM5701Ethernet 3.6.2b4

com.apple.driver.AirPort.Brcm4331 615.20.17

com.apple.driver.AppleFWOHCI 4.9.9

com.apple.driver.AppleAHCIPort 2.6.6

com.apple.driver.AppleUSBEHCI 621.4.6

com.apple.driver.AppleUSBXHCI 630.4.5

com.apple.driver.AppleSmartBatteryManager 161.0.0

com.apple.driver.AppleACPIButtons 1.8

com.apple.driver.AppleRTC 1.5

com.apple.driver.AppleHPET 1.8

com.apple.driver.AppleSMBIOS 1.9

com.apple.driver.AppleACPIEC 1.8

com.apple.driver.AppleAPIC 1.7

com.apple.driver.AppleIntelCPUPowerManagementClient 214.0.0

com.apple.nke.applicationfirewall 4.0.39

com.apple.security.quarantine 2.1

com.apple.driver.AppleIntelCPUPowerManagement 214.0.0

com.apple.kext.triggers 1.0

com.apple.iokit.IOSerialFamily 10.0.6

com.apple.driver.DspFuncLib 2.4.7fc2

com.apple.iokit.IOAudioFamily 1.9.2fc7

com.apple.kext.OSvKernDSPLib 1.12

com.apple.nvidia.gk100hal 8.1.6

com.apple.NVDAResman 8.1.6

com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.1.7f2

com.apple.iokit.IOSurface 86.0.4

com.apple.driver.X86PlatformPlugin 1.0.0

com.apple.driver.AppleBacklightExpert 1.0.4

com.apple.iokit.IOBluetoothFamily 4.1.7f2

com.apple.driver.AppleGraphicsControl 3.4.5

com.apple.driver.AppleHDAController 2.4.7fc2

com.apple.iokit.IOHDAFamily 2.4.7fc2

com.apple.driver.AppleSMC 3.1.5d4

com.apple.driver.AppleSMBusController 1.0.11d1

com.apple.iokit.IOAcceleratorFamily 74.15

com.apple.iokit.IONDRVSupport 2.3.7

com.apple.iokit.IOGraphicsFamily 2.3.7

com.apple.driver.IOPlatformPluginFamily 5.4.1d11

com.apple.iokit.IOFireWireIP 2.2.5

com.apple.driver.AppleThunderboltDPInAdapter 2.5.0

com.apple.driver.AppleThunderboltDPAdapterFamily 2.5.0

com.apple.driver.AppleThunderboltPCIDownAdapter 1.3.2

com.apple.driver.AppleUSBMultitouch 237.3

com.apple.iokit.IOUSBHIDDriver 623.4.0

com.apple.driver.AppleUSBMergeNub 621.4.6

com.apple.driver.AppleUSBComposite 621.4.0

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.5.6

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.5

com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.6

com.apple.driver.AppleThunderboltNHI 1.9.2

com.apple.iokit.IOThunderboltFamily 2.7.7

com.apple.iokit.IOEthernetAVBController 1.0.2b1

com.apple.iokit.IO80211Family 530.5

com.apple.iokit.IONetworkingFamily 3.0

com.apple.iokit.IOUSBUserClient 630.4.4

com.apple.iokit.IOFireWireFamily 4.5.5

com.apple.iokit.IOAHCIFamily 2.5.1

com.apple.iokit.IOUSBFamily 630.4.5

com.apple.driver.AppleEFINVRAM 2.0

com.apple.driver.AppleEFIRuntime 2.0

com.apple.iokit.IOHIDFamily 1.8.1

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 220.3

com.apple.kext.AppleMatch 1.0.0d1

com.apple.security.TMSafetyNet 7

com.apple.driver.DiskImages 345

com.apple.iokit.IOStorageFamily 1.8

com.apple.driver.AppleKeyStore 28.21

com.apple.driver.AppleACPIPlatform 1.8

com.apple.iokit.IOPCIFamily 2.8

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.corecrypto 1.0

OS X Mountain Lion (10.8.4)

Posted on Oct 17, 2013 3:54 PM

Reply
5 replies
User profile for user: Balaamsdonkey
Balaamsdonkey Author
User level: Level 1
14 points

Oct 17, 2013 4:28 PM in response to Tlix

I've had some others indicate it was hardware based. Pointing specifically to:


Processor 4: no valid machine-check state

Processor 5: no valid machine-check state

Processor 6: no valid machine-check state

Processor 7: no valid machine-check state


and the part that starts with:


panic(cpu 4 caller 0xffffff80046b91b9): "Machine Check at 0x78303e676e697274,



Are those misleading?

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

Oct 17, 2013 7:15 PM in response to Balaamsdonkey

That panic was not caused by third-party software. If the problem is recurrent, the possibilities are:


  1. A stale or corrupt kernel cache
  2. A damaged OS X installation
  3. A fault in a peripheral device, if any
  4. Corrupt non-volatile memory (NVRAM)
  5. An internal hardware fault (including incompatible memory)
  6. An obscure bug in OS X


You may already have ruled out some of these.

Rule out #1 by booting in safe mode and then rebooting as usual. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.

You can rule out #2 and #3 by reinstalling the OS and testing with non-essential peripherals disconnected and aftermarket expansion cards removed, if applicable. Sometimes a clean reinstallation may solve a problem that isn't solved by reinstalling in place.


Corrupt NVRAM, which rarely causes panics, can be ruled out by resetting it.


If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications for your model.


The Apple Hardware Test or Apple Diagnostics, though generally unreliable, will sometimes detect a fault. A negative test can't be depended on. Run the extended version of the test.


In the category of obscure bugs, reports suggest that FileVault may trigger kernel traps under some unknown conditions. Most, though not all, of these reports seem to involve booting from an aftermarket SSD. If those conditions apply to you, try deactivating FileVault.

Connecting more than one display is another reported trigger for OS X bugs.

If your system is not fully up to date, running Software Update might get you a bug fix.


In rare cases, a malformed network packet from a defective router or other network device can cause panics. Such packets could also be sent deliberately by a skillful attacker. This possibility is something to consider if you run a public server that might be the target of such an attack.


If none of the above applies, make a "Genius" appointment at an Apple Store to have the machine tested. You may have to leave it there for several days. There isn't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it's likely to be repeated at the store. Otherwise you may be told that nothing is wrong.


Print the first page of the panic report and bring it with you.


Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you know how to restore, and you have at least two independent backups.) Don’t erase the recovery partition, if present.


Keeping your confidential data secure during hardware repair


*An SSD doesn't need to be zeroed.

Reply

Kernel Panic

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