Skip navigation

Urgent: Your Computer restarted because of a problem

1055 Views 14 Replies Latest reply: Feb 6, 2014 8:44 AM by Grant Bennet-Alder RSS
xxxkwxxx Calculating status...
Currently Being Moderated
Sep 17, 2013 1:14 AM

When i was using my MacBookPro (mid-2010 model), it got shut down with no clues and then it restarted with this message. It happened repeatedly today and i could not use the macbook in any ways.

 

Here are what i have already done:

  • restart the mac pro in safe mode and install the updates (OSX 10.85)
  • Attempted to reset the mac pro's PRAM but failed. After i hit Command + Option + P + R, the mac book cannot rest the PRAM. There was only a 'bimp' sound which occurs seconds after seconds.
  • I try to run an Apple hardware test but it is not available in the mid-2010 model

 

Guys i am hopeless. I dont really know what happened to my mac. Is it some kind of hardware problem?
Below is the panic log and i hope someone can read this for me.

 

Tue Sep 17 15:21:43 2013

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

CR0: 0x0000000080010033, CR2: 0x00007fff8e50aac8, CR3: 0x0000000020c42000, CR4: 0x0000000000000660

RAX: 0xfff7ff800b9a8740, RBX: 0x000000000000000d, RCX: 0xffffff80074bdd30, RDX: 0x000000000000000d

RSP: 0xffffff80ee723690, RBP: 0xffffff80ee7236b0, RSI: 0xffffff800b9a3f40, RDI: 0xffffff80074bdd30

R8:  0xffffff800b9b82f8, R9:  0xffffff8018808c18, R10: 0xffffff80074bdc60, R11: 0x0000000000000202

R12: 0x0000000000000000, R13: 0xffffff80190c8b90, R14: 0x0000000000000032, R15: 0xffffff8018808c18

RFL: 0x0000000000010206, RIP: 0xffffff8006e884f2, CS:  0x0000000000000008, SS:  0x0000000000000000

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

 

 

Backtrace (CPU 1), Frame : Return Address

0xffffff80ee723330 : 0xffffff8006e1d626

0xffffff80ee7233a0 : 0xffffff8006eb8655

0xffffff80ee723570 : 0xffffff8006ece17d

0xffffff80ee723590 : 0xffffff8006e884f2

0xffffff80ee7236b0 : 0xffffff8006e805d0

0xffffff80ee7239d0 : 0xffffff8007186402

0xffffff80ee723a00 : 0xffffff80070ff390

0xffffff80ee723ab0 : 0xffffff8006f134b6

0xffffff80ee723b00 : 0xffffff80071bfaf6

0xffffff80ee723ba0 : 0xffffff8006e5c875

0xffffff80ee723bf0 : 0xffffff8006e5bd83

0xffffff80ee723c30 : 0xffffff8006e5f703

0xffffff80ee723d90 : 0xffffff8006e630ca

0xffffff80ee723f20 : 0xffffff8006eb8aa0

0xffffff80ee723fb0 : 0xffffff8006ece0a1

 

 

BSD process name corresponding to current thread: ifcstart

 

 

Mac OS version:

12E55

 

 

Kernel version:

Darwin Kernel Version 12.4.0: Wed May  1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64

 

Kernel slide:     0x0000000006c00000

Kernel text base: 0xffffff8006e00000

System model name: MacBookPro7,1 (Mac-F222BEC8)

 

 

System uptime in nanoseconds: 37513607305

last loaded kext at 1647149029: com.apple.driver.AppleUSBTCButtons          237.1 (addr 0xffffff7f88b68000, size 20480)

loaded kexts:

com.apple.driver.AppleUSBTCButtons          237.1

com.apple.driver.AppleIRController          320.15

com.apple.driver.AppleUSBTCKeyEventDriver          237.1

com.apple.driver.AppleUSBTCKeyboard          237.1

com.apple.driver.AppleUSBCardReader          3.1.7

com.apple.iokit.SCSITaskUserClient          3.5.5

com.apple.driver.XsanFilter          404

com.apple.iokit.IOAHCIBlockStorage          2.3.1

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.AppleFWOHCI          4.9.6

com.apple.driver.AirPort.Brcm4331          615.20.17

com.apple.driver.AppleUSBHub          5.5.5

com.apple.iokit.AppleBCM5701Ethernet          3.6.1b4

com.apple.driver.AppleAHCIPort          2.5.2

com.apple.driver.AppleEFINVRAM          1.7

com.apple.driver.AppleUSBEHCI          5.5.0

com.apple.driver.AppleUSBOHCI          5.2.5

com.apple.driver.AppleSmartBatteryManager          161.0.0

com.apple.driver.AppleRTC          1.5

com.apple.driver.AppleHPET          1.8

com.apple.driver.AppleACPIButtons          1.7

com.apple.driver.AppleSMBIOS          1.9

com.apple.driver.AppleACPIEC          1.7

com.apple.driver.AppleAPIC          1.6

com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0

com.apple.nke.applicationfirewall          4.0.39

com.apple.security.quarantine          2.1

com.apple.driver.AppleIntelCPUPowerManagement          196.0.0

com.apple.driver.AppleUSBMultitouch          237.3

com.apple.iokit.IOUSBHIDDriver          5.2.5

com.apple.iokit.IOSCSIBlockCommandsDevice          3.5.5

com.apple.iokit.IOUSBMassStorageClass          3.5.1

com.apple.driver.AppleUSBMergeNub          5.5.5

com.apple.driver.AppleUSBComposite          5.2.5

com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.5

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

com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.5

com.apple.iokit.IOFireWireFamily          4.5.5

com.apple.iokit.IO80211Family          530.4

com.apple.iokit.IOUSBUserClient          5.5.5

com.apple.iokit.IOEthernetAVBController          1.0.2b1

com.apple.iokit.IONetworkingFamily          3.0

com.apple.iokit.IOAHCIFamily          2.3.1

com.apple.driver.AppleMCP89RootPortPM          1.11

com.apple.iokit.IOUSBFamily          5.6.0

com.apple.driver.NVSMU          2.2.9

com.apple.driver.AppleEFIRuntime          1.7

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

com.apple.iokit.IOPCIFamily          2.7.3

com.apple.iokit.IOACPIFamily          1.4

com.apple.kec.corecrypto          1.0

MacBook Pro, OS X Mountain Lion (10.8.5)
  • Linc Davis Level 10 Level 10 (107,710 points)

    restart the mac pro in safe mode and install the updates (OSX 10.85)

     

    Both panic reports show that you were running 10.8.4, so the installation wasn't successful.

     

    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 (after erasing the startup volume) may solve a problem that isn't solved by reinstalling in place, without erasing.

     

    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.

  • Grant Bennet-Alder Level 8 Level 8 (48,110 points)

    Both panic logs you posted show:

    Mac OS version:

    12E55

    That is 10.8.4

    Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
  • Grant Bennet-Alder Level 8 Level 8 (48,110 points)
    Currently Being Moderated
    Sep 20, 2013 10:14 AM (in response to xxxkwxxx)

    THAT log shows you have installed 10.8.5.

     

    Panics that show a Trend (in about the same part of Mac OS X, or for the same reasons) may indicate damage to your Mac OS X image.

     

    You have panics in three different parts of Mac OS X.  This NON-Trend may indicate a RAM Memory problem. If you have ever considered a RAM Memory upgrade from your current 2*2GB, now may be a good time.

     

    http://www.datamemorysystems.com/apple-macbook-pro-intel-core-i5-2-4ghz-15-mc371 ll/a-mid-2010-memory-upgrades/

     

    OWC/Macsales has special 8GB DIMMs for a maximum of 16GB, but they are pricey.

     

    Otherwise, consider setting up all night memory testing to see if an error will show itself.

    Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
  • Grant Bennet-Alder Level 8 Level 8 (48,110 points)
    Currently Being Moderated
    Sep 21, 2013 12:51 PM (in response to xxxkwxxx)

    The US Military measured, analyzed, and have methods to predict Mean Time Between Failure in electronic systems. Based on their techniques, the memories are still the most likely failure point.

     

    But this is based on a large sample. You do not have large sample, you have one Mac. So anything could be the problem.

    Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
  • Grant Bennet-Alder Level 8 Level 8 (48,110 points)

    The abreviation of panic reports are often caused by memory problems.

    Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
  • Grant Bennet-Alder Level 8 Level 8 (48,110 points)

    You have a lot of third-party add-ons loaded. Your panics continue to indicate a NON-trend, which correlates very strongly with memory problems.

    Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
  • jdz30307 Calculating status...

    I have a very similar, new, expensive Imac with exactly the same problem!  Did you ever get an answer from Apple?  Very frustrating.

  • Grant Bennet-Alder Level 8 Level 8 (48,110 points)

    jdz30307-

    exactly the same problem

    Kernel Panic is not ONE problem -- it is hundreds to thousands of different problems.

     

    Assuming anything based on someone else's kernel panic reports make no sense.

     

    You would be best served by:

     

    • Taking full advantage of your 90 days of free telephone support to work with a trained Apple representative

    • Visiting the genius Bar of your local Apple Store

    • Starting a new thread on the iMac forum with a catchy title, and a complete description of your Hardware and a copy of your panic log.

    Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers

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.