Virtualbox crashed host
Virtualbox crashed host
VirtualBox seem to crash my machine, machine went unexpected shutdown and all virtualbox vms went offline, does anyone have an idea?
- Attachments
-
crash report.txt- (4.66 KiB) Downloaded 10 times
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtualbox crashed host
The Windows 10 version is rather old, 1607, and the crash report does not mention Virtualbox. The crashing module, if I read the report correctly, is 'MBAMService.exe', which is MalwareBytes, I think. 'NETIO.SYS' had something to do with it, too.
I'm not sure what else to do, but if this crash only occurs while Virtualbox is running, I'd suppose that Virtualbox's activities are triggering an incompatibility between Windows and somethin else, maybe Malwarebytes. Try removing Malwarebytes and see if the host continues to crash.
Also, what version of Virtualbox were you running?
I'm not sure what else to do, but if this crash only occurs while Virtualbox is running, I'd suppose that Virtualbox's activities are triggering an incompatibility between Windows and somethin else, maybe Malwarebytes. Try removing Malwarebytes and see if the host continues to crash.
Also, what version of Virtualbox were you running?
Re: Virtualbox crashed host
No, my machine is Windows Server 2016, I'm reading this crash file from my main PC.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtualbox crashed host
If "pool request" refers to memory pools, then this may indicate a lack of RAM in the host. Without a log we can only speculate.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtualbox crashed host
And please clarify your use of the word "machine". Both the host PC and the VM or Guest are "machines", and we can't tell which you are referring to.
The posted BSOD crash log says:
I gather this log was from a host PC crash, due to this from you:
A VM crashed, and all the other VMs died too.
So please clarify if you are referring to a host PC BSOD or a VM BSOD.
And, like Mpack says, provide a VM log: Start the VM from full power off, not save-state. Run until you see the problem happen, then shut down the VM from within the VM OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.
The posted BSOD crash log says:
Which Google et al says is 10 v1607, not Server 2016.Windows 10 Kernel Version 14393
I gather this log was from a host PC crash, due to this from you:
There is another way to read this:Skely wrote:VirtualBox seem to crash my machine, machine went unexpected shutdown and all virtualbox vms went offline
A VM crashed, and all the other VMs died too.
So please clarify if you are referring to a host PC BSOD or a VM BSOD.
And, like Mpack says, provide a VM log: Start the VM from full power off, not save-state. Run until you see the problem happen, then shut down the VM from within the VM OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.