Yosemite 10.10.5 - Kernel Instability and Crash

[BitMangler]

It's possible that your developers are already aware of this crash. Unfortunately, I'm in midst of critical timeline of another SW dev project, but thought I would report this problem anyway.

I installed VirtualBox 5.0.16 on the OsX-Yosemite 10.10.5 system, (which, BTW, did also have Fusion 7.1.2 installed on it). It was after the VirtualBox installation that the kernel instabilities were introduced. The complete system lockups, where 2 of the 3 monitors would immediately go black, leaving desktop still showing on a 3rd monitor, on a 2nd GTX-980, were traced to VirtualBox as the culprit, by using your Un-Installer to remove VirtualBox and it's KEXT(s) from the system. There have been no more kernel instabilities since the complete VirtualBox removal.

It is important to note, that VirtualBox is causing OsX kernel instabilities, even when no virtual machines are running on the system. (No VMware VMs, nor VBox VMs). Thus you have a very insiduous problem going on within your KEXTs for OsX. That's because after 10 crashes, and inspecting the OsX System Logs, there are common messages produced in that log, which would give clue to the fact that VirtualBox had any problem, OR that any other OsX driver or subsystem had any problem. That's why I used the word "insidious". However, the impact can be devastating for those whom try to utilize VirtualBox for some type of production level system.

Hardware: CPU Hexacore 3970X (Extreme) Sabertooth X79 Mobo 64 GB DDR 2 NVidia GTX-780 Misc SSDs OsX 10.10.5 (Yosemite)

This instability ALSO exhibits itself on a MacMini (Apple) Mid 2013 with 4 core...also with VMware Fusion 7.1.2. Same symptoms, but needs more stressing of CPUs to exhibit the kernel crash. Multiple streams of audio processing were also involved in 2 crashes.

My intution: This instability seems to be related to some type of low level video processing, like potentially GPU raster operations or video buffer movements, possibly your code which is virtualizing the display (if that's possible without VMs running). The bug can occur with VMs running, but most of the crashes I experienced, were with NO VMs running.

Our resolution: For now...we have removed VirtualBox from every development system we have.

Sorry, that I do not currently have the bandwidth to aid/assist more in your tracking this down. I almost didn't report at all. I just don't have time for it...but I know the nature of this bug is very nasty.

[BitMangler]

3rd paragraph, 3rd sentence should read:

That's because after 10 crashes, and inspecting the OsX System Logs, there are "NO" common messages produced in that log, which would give clue to the fact that VirtualBox had any problem, OR that any other OsX driver or subsystem had any problem.

[Frank Mehnert]

To be honest we are not aware of such instabilities. First, the common denominator on your system seems to be VMware Fusion. There might be a problem if the kernel drivers of both products are installed at the same time on the same system, I don't know. Second, if no VirtualBox VM is working then no graphics or low-level video processing is done. Third, you talk about log files which hint that this is a VirtualBox problem. I would like to see at least one of those files, otherwise there is nothing we can do for you.

[Frank Mehnert]

Oh, and a crash report would be even more helpful.

[Frank Mehnert]

No feedback at all. Please reopen if you can provide the requested information.