Windows 7 Host and Linux guest, BSOD on host

[Trent]

I ran 4.3.12 for quite awhile. After I jumped to 4.3.20, I am now getting BSOD every now and then. I've done a memory scan, just to be sure I don't have failing RAM. Anything else I can do to get more information?

I'm not sure if the windows event viewer files are useful or not, but I'm attaching them.

[Trent]

Event viewer logs

[Mihai Hanor]

There's nothing useful in your saved event log. Attach a BSOD minidump and a Vbox.log file of your VM. Describe what's the guest OS that you're using and what you're doing when the issue occurs.

[elenst]

I am getting BSOD whenever I attempt to start a Linux guest on my Windows 7 64bit host on any VirtualBox version higher than 4.3.12. I tried several 4.3.X versions, and now also 5.0.6, all with the same result:

• VirtualBox Manager starts all right;
• I select a VM from the list, run 'Start' => BSOD

It happens both with my old VMs created with 4.3.12 or earlier, and brand new VMs created with 5.0.6. VBox.log is not created. Minidump is attached.

After rolling back to 4.3.12 everything works again.

I searched and found multiple complaints about problems on Windows hosts with VirtualBox > 4.3.12, but could not figure whether the problems had ever been solved.

[elenst]

Minidump after attempt to start Linux guest on Windows 7 host

[Mihai Hanor]

elenst, your Windows 7 is not up to date with the Microsoft updates. Also, you're running an old version of CryptoPro, which is incompatible with newer versions of VirtualBox.

[amedvedev]

This dump doesn't contain information related to VirtualBox. There is the signs of memory corruption, but there is not information who corrupted the memory. It will be useful if you run it under a Driver Verifier to track a memory corruption. Enable it using the command

verifier.exe /standard

(see ​here). Also it will be useful if you collect a full memory dump as defined here (scroll down to the Windows part).

Note: you need to have at least 25Gb of available disk space on disk c:\ to collect a memory dump.