Skip navigation

Kernel panic (maybe because of filevalut 2 ??)

876 Views 22 Replies Latest reply: Nov 26, 2012 11:54 AM by tom3f RSS
1 2 Previous Next
tom3f Level 1 Level 1 (0 points)
Currently Being Moderated
Oct 23, 2012 12:43 PM

Hello, few weeks ago I started to get kernel panic at boot. It happens 2-3 times per week. I didn't notice any other problems with my mac. When system is running everythink is ok and I never get kernel panic. This happens only during boot, immediately after I put password to my drive crypted by filevalut 2. I don't know if the filevalut is the reason but I started to get this kernel panics week after I crypted my drive. I tried reinstall my system to fresh crypted partition but it doesn't help. Do you think that filevalut can be a reason of this ?? I noticed from logs that every time it looks like different error (Last loaded kext is every time different).


Here are log information from console (I have only this one for now because I reinstall system)


Interval Since Last Panic Report:  363537 sec

Panics Since Last Report:          -1

Anonymous UUID:                    217F93A8-F28F-16A3-A6F5-7E2FADB96199



Tue Oct 23 09:10:19 2012

panic(cpu 0 caller 0xffffff8009cb7bd5): Kernel trap at 0xffffff8009c2da10, type 13=general protection, registers:

CR0: 0x000000008001003b, CR2: 0xffffff80eb60d000, CR3: 0x000000000c8a0000, CR4: 0x0000000000000660

RAX: 0x0000000000000001, RBX: 0xffffff801bbce550, RCX: 0x0000000009000000, RDX: 0xffffff80e55a1078

RSP: 0xffffff80f0dfbe50, RBP: 0xffffff80f0dfbe80, RSI: 0xffffff80e55a1068, RDI: 0x0000000000000000

R8:  0xffffff800a2bec60, R9:  0x00000000fffffffe, R10: 0x00000000001d9cc4, R11: 0x0000000000000000

R12: 0xffffff800a2bebe8, R13: 0xffffff801bbca030, R14: 0x01ffff801bbca000, R15: 0x0000000000000000

RFL: 0x0000000000010002, RIP: 0xffffff8009c2da10, CS:  0x0000000000000008, SS:  0x0000000000000000

Fault CR2: 0xffffff80eb60d000, Error code: 0x0000000000000000, Fault CPU: 0x0



Backtrace (CPU 0), Frame : Return Address

0xffffff80f0dfbaf0 : 0xffffff8009c1d626

0xffffff80f0dfbb60 : 0xffffff8009cb7bd5

0xffffff80f0dfbd30 : 0xffffff8009cce4ed

0xffffff80f0dfbd50 : 0xffffff8009c2da10

0xffffff80f0dfbe80 : 0xffffff800a02e1e9

0xffffff80f0dfbec0 : 0xffffff800a02ca47

0xffffff80f0dfbf30 : 0xffffff800a02d3a2

0xffffff80f0dfbf70 : 0xffffff800a031e99

0xffffff80f0dfbfb0 : 0xffffff8009cb26b7



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: 69A5853F-375A-3EF4-9247-478FD0247333

Kernel slide:     0x0000000009a00000

Kernel text base: 0xffffff8009c00000

System model name: MacBook6,1 (Mac-F22C8AC8)



System uptime in nanoseconds: 1639501555

last loaded kext at 249631853:          196.0.0 (addr 0xffffff7f8bac9000, size 20480)

loaded kexts:          196.0.0          602.15.22          2.4.1          2.0.19          1.6.1          5.2.5          5.4.0          161.0.0          1.5          1.7          1.6          1.9          1.6          1.6          4.0.39          2          196.0.0          500.15          2.2.1          3.0          5.4.0          2.2.9          1.6.1          1.8.0          1.1          220          1.0.0d1          7          344          1.8          28.21          1.6          2.7.2          1.4          1.0

System Profile:

Model: MacBook6,1, BootROM MB61.00C8.B00, 2 processors, Intel Core 2 Duo, 2.26 GHz, 8 GB, SMC 1.51f53

Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x0198, 0x393930353432382D3030352E4130324C4620

Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x0198, 0x393930353432382D3030352E4130324C4620

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (

Bluetooth: Version 4.0.9f33 10885, 2 service, 11 devices, 1 incoming serial ports

Network Service: Ethernet, Ethernet, en0

Serial ATA Device: TOSHIBA MK2555GSXF, 250.06 GB

Serial ATA Device: MATSHITADVD-R   UJ-898

USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x24400000 / 2

USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0237, 0x04600000 / 2

USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06100000 / 2

USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8218, 0x06130000 / 3

MacBook, OS X Mountain Lion (10.8.2)
  • Linc Davis Level 10 Level 10 (107,520 points)
    Currently Being Moderated
    Oct 23, 2012 5:17 PM (in response to tom3f)

    Decrypt the volume and see whether the panics stop.

  • etresoft Level 7 Level 7 (23,880 points)
    Currently Being Moderated
    Oct 23, 2012 5:28 PM (in response to tom3f)

    Why are you booting 2-3 times per week? How old is this computer? I have found that notebook hard drives have a tendency to start failing at or around 3 years of age.

  • etresoft Level 7 Level 7 (23,880 points)
    Currently Being Moderated
    Oct 24, 2012 4:29 AM (in response to tom3f)

    tom3f wrote:


    It's because I turn my computer off every day. I know that is possible to let it in sleep mode but why ?


    Most people would say they know it is possible to turn it off every day, but then ask why.


    If i remove power adapter than during night i loose 10% off battery and I don't want to let my computer still pluged in electricity.


    Why not? Don't buy that 2nd cup of coffee today and with all that extra expense, you will still be money ahead for the year.


    You didn't answer the question about how old your machine is. Hard drives are mechanical (well some of them) and they wear out (all of them). Turning your computer off and on every day is that much more taxing. Chances are your hard drive is failing.

  • Linc Davis Level 10 Level 10 (107,520 points)
    Currently Being Moderated
    Oct 24, 2012 5:51 AM (in response to tom3f)

    The panics are not caused by third-party software. You seem to have ruled out system corruption as the cause. That leaves only hardware failure and an OS bug as possilibilities. The last panic suggests that your hard drive is malfunctioning, or has malfunctioned recently. You can try any or all of the following:


    1. Run the Apple Hardware Test.
    2. Erase the volume and restore from a backup.
    3. Take the machine to an Apple Store for testing.
  • etresoft Level 7 Level 7 (23,880 points)
    Currently Being Moderated
    Oct 24, 2012 6:09 AM (in response to tom3f)

    Apple doesn't make the hard drive. I just replace them at the first sign of trouble. It is the quickest, easiest, and cheapest repair you can do.

  • Linc Davis Level 10 Level 10 (107,520 points)
    Currently Being Moderated
    Nov 16, 2012 5:35 AM (in response to tom3f)

    My MBP is older than yours. I'm running the same version of OS X, and I'm using FileVault. I have no problems.

  • etresoft Level 7 Level 7 (23,880 points)
    Currently Being Moderated
    Nov 16, 2012 6:02 AM (in response to tom3f)

    tom3f wrote:


    After few weeks of testing without FileValut 2 everything is working perfect. So problem is only in OS X Mountain Lion. It's sad that apple forgets to older machines and new system is optimized only for new Macbooks.

    Mountain Lion is irrelevant. FileVault is going to be more stress on the hard drive. Plus you are booting up every day which is very stressful. Your hard drive is simply worn out. Get a new one.

1 2 Previous Next


More Like This

  • Retrieving data ...

Bookmarked By (0)


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