Opened 10 years ago
Closed 8 years ago
#13833 closed defect (obsolete)
Digitial Guardian Agent + VirtualBox = BSOD
Reported by: | Suo | Owned by: | |
---|---|---|---|
Component: | host support | Version: | VirtualBox 4.3.22 |
Keywords: | Digital Guardian Agent DGAgent dgmaster.sys BSOD Blue Screen SUPHardenedVerifyProcess-win SUPR3HardenedMain-win | Cc: | |
Guest type: | all | Host type: | Windows |
Description
I can start the VirtualBox Manager, but when I attempt to start a VM, the Windows host blue screens. An attempt to fix this crash with dgmaster.sys was made in changeset 53021 ( https://www.virtualbox.org/changeset/53021/vbox ) but I am still seeing issues in VirtualBox 4.3.22 on Windows 7 x64. The only workaround I have found is to revert to 4.3.12. Unfortunately, VBox.log is not written before the system halts.
Attachments (7)
Change History (16)
by , 10 years ago
Attachment: | VBox 4.3.22 DG BSOD.jpg added |
---|
comment:1 by , 10 years ago
The crash occurs in a Digital Guardian driver, you should contact them. Read this
comment:2 by , 10 years ago
I've made some improvements to the code I suspect triggers the dgmaster.sys crash. Could you try out this build and see if it helps, or at least produces a VBoxStartup.log file: https://www.virtualbox.org/download/testcase/VirtualBox-4.3.27-99267-Win.exe
by , 10 years ago
Attachment: | VirtualBox-4.3.27-99267-Win with DG Whitelist VBoxStartup.log added |
---|
by , 10 years ago
Attachment: | VirtualBox-4.3.27-99267-Win with DG Whitelist.png added |
---|
comment:3 by , 10 years ago
I currently have a whitelist in place so Digital Guardian will not interfere with VirtualBox. I will test again on Monday without the whitelist. Normally Digital Guardian is not detectable, but, as a result of having VirtualBox whitelisted in Digital Guardian, VirtualBox can see that Digital Guardian is installed, so it triggers VB's DG workaround, which appears to have a bug in it that causes the hardening check to fail.
Failed to open a session for the virtual machine Ubuntu 14.04. The virtual machine 'Ubuntu 14.04' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\VirtualBox VMs\Ubuntu 14.04\Logs\VBoxStartup.log'. Result Code: E_FAIL (0x80004005) Component: Machine Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
by , 10 years ago
Attachment: | VirtualBox-4.3.27-99267-Win with DG Active VBoxStartup.log added |
---|
comment:4 by , 10 years ago
We took out the whitelist and get the dgmaster.sys BSOD with VirtualBox build 99267.
comment:6 by , 10 years ago
I am also experiencing this exact issue with Digital Guardian. Let me know what might be useful, if anything. When I reproduced the issue, it was difficult to recover from the BSoD because the system faltered such that the screen was flashing and the power button did not interrupt the "seizure". I'll see if I can attach a video of it because it's at least entertaining.
by , 10 years ago
Attachment: | VBoxStartup.log VirtualBox-5.0.0_RC1-100731-Win.zip added |
---|
VBoxStartup.log from VirtualBox-5.0.0_RC1-100731-Win with VirtualBox whitelisted in Digital Guardian
comment:7 by , 10 years ago
I tried again with the latest build (VirtualBox-5.0.0_RC1-100731-Win) and the verification still fails:
Error -5673 in supR3HardNtChildPurify! (enmWhat=5) supHardenedWinVerifyProcess failed with Unknown Status -5673 (0xffffe9d7): NtAllocateVirtualMemory
comment:8 by , 8 years ago
We received an update from Digital Guardian, version 6.23.0835, that resolves the problem. I am now able to run VirtualBox 5.1.4 with this new version of Digital Guardian.
comment:9 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Closing as Digital Guardian seems to have sorted out the problem.
Photo of the BSOD