BSODs starting Virtualbox VMs

Hi experts!

Oracle VM VirtualBox v5.0.20r106931 installed on build 14332 this week.

BSODs when starting both custom and preconstructed VMs - in this case a lucid puppy linux 5.2.0 from Puppy Linux | VirtualBoxes - Free VirtualBox® Images as well as a elementaryos linux vdi made under an earlier windows10 (created Dec 28 2015)

Virtualbox logs included in BSOD debug zipfile

A few seconds after starting the VM, a BSOD occurs, which seemed to take a very long time to complete the WER process and reboot.

DESKTOP-HBE5NTE-01_05_2016_183139_58.zip

Hi Fafhrd,

Unfortunately I see that with a few crashes no minidump has been saved.

Code:

Event[902]:   Log Name: System    Microsoft-Windows-WER-SystemErrorReporting   Date: 2016-04-29T18:32:19.707   Event ID: 1005   Task: N/A   Level: Error   Opcode: N/A   Keyword: Classic   User: N/A   User Name: N/A   Computer: DESKTOP-HBE5NTE   Description:  Unable to produce a minidump file from the full dump file.  Event[902]:   Log Name: System    Microsoft-Windows-WER-SystemErrorReporting   Date: 2016-04-29T18:32:19.707   Event ID: 1005   Task: N/A   Level: Error   Opcode: N/A   Keyword: Classic   User: N/A   User Name: N/A   Computer: DESKTOP-HBE5NTE   Description:  Unable to produce a minidump file from the full dump file.

When I take a look at the dump it immediately says memory corruption (I won't go into the why part), however as you're running the TP version it is difficult to say if it is a problem in the drivers of VirtualBox or the Memory Management of Windows.

Is VirtualBox upgraded to the newest version or is it a clean install of it?

Thanks for that axe0.

It was a new download - I wasn't sure if It was an upgrade for the following reasons - I looked for Virtualbox in the start menu apps before, didn't see it and downloaded the installer and ran it, only afterwards I realised that it was entered on the apps list as "Oracle VM Virtualbox".

I am not sure if Virtualbox survives an insider upgrade, or not. I believe that the Virtualbox installer itself removes prior installations on a fresh install, doesn't it?

When I've finished with the laptop tonight I'll try to reproduce the BSOD and run the debug data collector again immediately after rebooting.

It's not the end of the world - I only wanted to run a lightweight linux to use an old (equally lightweight) scanner, which I know runs fine without any installation under Puppy Linux. Curse that damn WDDM!

I believe that the Virtualbox installer itself removes prior installations on a fresh install, doesn't it?

Normally installers do so to prevent problems, however usually a reboot is required to finish the process.

DESKTOP-HBE5NTE-01_05_2016_231959_78.zip

Well, it certainly had a reboot between reinstall and the latest BSOD this time!

I looked at the latest dump just for grins. It says

Code:

BugCheck 3B, {c0000096, ffffcd801ba3f890, ffffcd8068c6ada0, 0}  *** WARNING: Unable to verify timestamp for VMMR0.r0 *** ERROR: Module load completed but symbols could not be loaded for VMMR0.r0 Probably caused by : memory_corruption

Searching on the bugcheck 3B, I found several threads which ended up being a defective CPU. Problems with VT-x support.

Sounds like a good time to run Prime95 and Memtest86+ (overnight).

Stress testing seem to have passed OK, will have to run Memtest tonight.



Cannot recall another BSOD since I got this Compaq Presario CQ57 in August 2012 with Win 7 Home >Win 8 Pro >Win 8 MCE, >Win 8.1 Pro > Win 10 (insider) Normally cool and steady, it's no speed demon though!

I don't believe a memory test would be necessary, but if you want to run it no problem

Do you have another system with Windows 10 TP installed or know someone who does? So we can test if this problem is due to VirtualBox or a bug in the memory management. With a bug in the memory management it doesn't necessarily have to crash at the other system too with the same software, with a problem in VirtualBox it does which I believe it is even though you're running the unstable version of Windows.

Not another with x64.

I have another system with 14332 x86 installed (only 2GB RAM), so not really enough to test a VM in Virtualbox, but I have another partition on this laptop with 10586 x86 running, which I can try as you suggest.

I can also upgrade this x86 to 14332 on the laptop to do a more direct comparison afterwards.

However, a busy UK Bank Holiday May Fayre today so I might prefer to do my testing in the beer tent instead! Not a good Idea to take the laptop along.

Keep us posted on how it is going