BSOD referencing VMMR0.r0 Win7 32 host, OSX 10.6.5 client

[matt breit]

Hello, I am running into an intermittent BSOD with the above configuration. I've done troubleshooting to disable any and all HW (USB, 3d acceleration, etc.), EXCEPT the CD/DVD Rom drive (that is tomorrow's test). But the minidumps always reference VMMR0.R0 and ntkrnlpa.exe. Some google searches recommended turning off the 'allow computer to turn off power' switches in device manager. will check this also tomorrow and report back.

In the meantime I wanted to drop a note in case anyone else has seen this before.

thanks!

-Matt

[matt breit]

Latest minidump

[matt breit]

Hi guys, I found this comment in vmmr0.cpp below. I was wondering if this might be related. The WinDbg session on my dump file mentions that the IRQ could be too high (not less than or equal to...)

651 /* 652 * Run guest code using the available hardware acceleration technology. 7c2a982c vboxsync 2007-09-21 18:27:48 +0000 653 * 654 * Disable interrupts before we do anything interesting. On Windows we avoid 655 * this by having the support driver raise the IRQL before calling us, this way 96f2751e vboxsync 2008-10-23 08:33:55 +0000 656 * we hope to get away with page faults and later calling into the kernel. 362c5a5c vboxsync 2007-09-14 17:53:56 +0000 657 */ 658 case VMMR0_DO_HWACC_RUN:

[matt breit]

Latest VB log and matching minidump from today's BSOD.

[Klaus Espenlaub]

Apple's licensing conditions do not allow running OSX on non-Apple hardware.