VirtualBox causing kernel panic in Mavericks, even when not running?

Question

VirtualBox causing kernel panic in Mavericks, even when not running?

My MPB keeps freezing and shutting down. Am I reading this error message correctly? That the problem is VirtualBox? The confusing thing is, VirtualBox isn't even running! ***?

Anonymous UUID: C6177B41-BD2D-8A6B-B2A0-40DBAEDC1E85

Wed Jul 9 22:47:12 2014

panic(cpu 4 caller 0xffffff80038dc24e): Kernel trap at 0xffffff7f8445d110, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0xffffff7f8445d110, CR3: 0x0000000006456000, CR4: 0x00000000001606e0

RAX: 0xffffff7f8445d110, RBX: 0xffffff8017136800, RCX: 0x0000000001000000, RDX: 0x0000000000000000

RSP: 0xffffff811101bdf8, RBP: 0xffffff811101be30, RSI: 0xffffff8017136800, RDI: 0xffffff8016b6b000

R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0xffffff811101bcd0, R11: 0xffffffffffffffff

R12: 0xffffff811101be0c, R13: 0x0000000000000001, R14: 0xffffff801995eab0, R15: 0xffffff8016b6b000

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

Fault CR2: 0xffffff7f8445d110, Error code: 0x0000000000000011, Fault CPU: 0x4 Kernel NX fault

Backtrace (CPU 4), Frame : Return Address

0xffffff811101ba80 : 0xffffff8003822f79

0xffffff811101bb00 : 0xffffff80038dc24e

0xffffff811101bcd0 : 0xffffff80038f3746

0xffffff811101bcf0 : 0xffffff7f8445d110

0xffffff811101be30 : 0xffffff7f84206b2a

0xffffff811101be60 : 0xffffff8003cb1223

0xffffff811101bec0 : 0xffffff7f84206b91

0xffffff811101bf10 : 0xffffff7f8420b265

0xffffff811101bf40 : 0xffffff8003a2f442

0xffffff811101bfb0 : 0xffffff80038d7417

Kernel Extensions in backtrace:

com.apple.iokit.IONetworkingFamily(3.2)[6777EB73-6474-3540-8CAB-B8A1C06D1CD9]@0 xffffff7f841fe000->0xffffff7f84229fff

com.apple.driver.AirPort.Brcm4331(700.20.22)[53C8CC6E-DD01-3DE9-AF8E-B82DA264D0 55]@0xffffff7f842a2000->0xffffff7f84495fff

dependency: com.apple.iokit.IO80211Family(640.36)[F68A75CA-FCD3-35FC-B87B-33ED98EB4625]@0xf fffff7f8422a000

dependency: com.apple.iokit.IONetworkingFamily(3.2)[6777EB73-6474-3540-8CAB-B8A1C06D1CD9]@0 xffffff7f841fe000

dependency: com.apple.iokit.IOPCIFamily(2.9)[4662B11D-2ECA-315D-875C-618C97CDAB2A]@0xffffff 7f83e02000

BSD process name corresponding to current thread: kernel_task

Mac OS version:

13E28

Kernel version:

Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64

Kernel UUID: BBFADD17-672B-35A2-9B7F-E4B12213E4B8

Kernel slide: 0x0000000003600000

Kernel text base: 0xffffff8003800000

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

System uptime in nanoseconds: 3832524015743

last loaded kext at 861158055719: com.apple.filesystems.smbfs 2.0.2 (addr 0xffffff7f85257000, size 335872)

loaded kexts:

org.virtualbox.kext.VBoxNetAdp 4.3.12

org.virtualbox.kext.VBoxNetFlt 4.3.12

foo.tap 1.0

org.virtualbox.kext.VBoxUSB 4.3.12

foo.tun 1.0

org.virtualbox.kext.VBoxDrv 4.3.12

com.Cycling74.driver.Soundflo

Unable to gather system configuration information.Model: MacBookPro9,1, BootROM MBP91.00D3.B08, 4 processors, Intel Core i7, 2.6 GHz, 8 GB, SMC 2.1f175

Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In

Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3431554638424455302D474E2D4620

Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3431554638424455302D474E2D4620

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.98.100.22)

Bluetooth: Version 4.2.6f1 14216, 3 services, 23 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en1

Serial ATA Device: APPLE HDD HTS727575A9E362, 750.16 GB

Serial ATA Device: MATSHITADVD-R UJ-8A8

USB Device: Hub

USB Device: FaceTime HD Camera (Built-in)

USB Device: Hub

USB Device: Apple Internal Keyboard / Trackpad

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

USB Device: IR Receiver

Thunderbolt Bus: MacBook Pro, Apple Inc., 25.1

Posted on Jul 9, 2014 11:01 PM

Reply

Answer 1

Kappy

Level 10

361,741 points

Jul 9, 2014 11:15 PM in response to benjaminallison

I don't see any indication that VB is causing the panic from the partial log you posted. If VB is the cause it would because of the extensions installed. But the only way to know with certainty is to uninstall VB completely and restart the computer.

The dependencies suggest an issue with the networking hardware. You might run the AHT to check for hardware errors. Run the long test for several hours.

Using Apple Hardware Test

How to invoke and interpret the Apple hardware tests | MacFixIt - CNET Reviews

Intel-based Macs- Using Apple Hardware Test

Reply

Answer 2

Jul 9, 2014 11:26 PM in response to Kappy

AHT says everything's fine.

I've been having problems with my ram (three beeps). I got it reseated but apparently it's still sitting in the socket somewhat loosely. Could it be a ram issue?

Reply

Answer 3

Jul 10, 2014 3:20 AM in response to benjaminallison

Virtual Machine software including VirtualBox installs kernel extensions to enable it to provide networking services for the virtual machines it runs this amongst other things allows the VM to share the network connection with the host Mac.

These extensions would be running even when the main VirtualBox application is not and even when no VM is running. The fact that these extensions are listed at the bottom along with reference to networking nearer the top might point to a problem with these extensions. However all the loaded kernel extensions are listed so in this case the VirtualBox extensions should be listed even if innocent.

It would appear you are running version 4.3.12 of VirtualBox which is the current version. I am also running this on a couple of Mavericks machines. One has not had any problems and the other every so often does crash and reboot. I have not yet satisfied myself that VirtualBox is the guilty part on my crashing Mac. It would actually be running a VM when it crashed as it is doing so 100% of the time.

In my case I also have a USB Ethernet interface connected only on the crashing Mac and this requires an additional kernel extension, it could be that which is guilty rather than VirtualBox itself - in my case.

Are you using WiFi on this Mac? If not is it turned on even if not being used? If you don't need WiFi then it would be worth making sure it is turned off. This is with regards to the fact it is listed at the top of your crash report.

Reply

Answer 4

Barney-15E

Level 10

112,518 points

Jul 10, 2014 4:23 AM in response to benjaminallison

Replace the original RAM and Test.

That RAM is not spec’d for a Mac. While it looks the same, it is not.

Yours is 1.5V and all the RAM from OWC or Crucial indicates 1.35v RAM

MemoryTen has RAM for that model, but it is not what you have installed. This is the correct RAM: http://www.memoryx.com/apple4gb1600s.html

This is what you have: http://www.memoryx.com/cwm.html

Note that it doesn’t indicate compatibility with any product, much less Apple products.

When buying RAM for a Mac, always use the source’s memory configurator lookup functions. MemoryTen does sell good, compatible RAM, but you need to purchase the correct RAM for a Mac. Trying to match the RAM specs will almost always fail.

Reply