VirtualBox 6.1 crashes with 0x0000 when 3D acceleration is enabled

[hasikada]

VirtualBox 6.1 crashes with 0x0000 when 3D acceleration is enabled

Virtual Box: 6.1.4-136177
Host OS: Windows 10 1809 (OS Build 17763.1039)
Guest OS: Ubuntu 16.04.6 LTS
Guest Addition installed

Please, check attached log (zipped).

Thank you

Adam

[snowcool776]

I am having the same problem with my WinXP SP3 Guest running on a Win10 1909 Host.
The error seems to be caused by the discontinuation of software virtualization in VB 6.1

I am trying to get mine up and its been a real pain in the rear because it worked in 6.0. Socratis, what do you think that may be causing this users error and mine?

For now, I would say reinstall the guest OS.

[mpack]

The OP has a hardening problem, probably an unsigned graphics DLL. Reinstalling the guest OS will do nothing, and it has nothing to do with VT-x.

FAQ: Diagnosing VirtualBox Hardening Issues.

FAQ: I have a 64bit host, but can't install 64bit guests. (VT-x/AMD-v problems).

[snowcool776]

Oh, Ok.
Thanks mpack.
Looks like I'm going to have to uninstall and reinstall the GAs.

[hasikada]

It's hardering problem, VBoxHardening.log attached (zipped)

Code: Select all

41e0.41e4: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 90149 ms, the end);
41cc.41d0: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 90903 ms, the end);

Latest drivers installed: Device Manager -> Display Adapters -> Intel(R) HD Graphics 630 -> Driver tab -> Update Driver

Code: Select all

Intel(R) HD Graphics 630
Driver Date: 26.06.2019
Driver Version: 26.10.100.7623
Digital Signer: Microsoft Windows Hardware Compatibility Publisher

VM powered down and restarted
VirtualBox-6.1.4-136177-Win.exe fully uninstalled/installed using "Run as adminstrator"
Hyper-V disabled

Still crashes

[mpack]

It's hardering problem, VBoxHardening.log attached (zipped)

Thanks for the log. It looks like you're another McAfee victim. See the hardening log already referenced above.

It is not necessary to run VirtualBox (the manager?) using "Run as administrator", that is only ever required for installation, and maybe also for installing the extension pack. The VM is run as a separate process, so it's doubtful that running the manager with admin rights will have any useful effect on that.

[msn]

whosever figured running VirtualBox in admin mode, I am thankful. Today my computer installed some updates and suddenly VirtualBox start crashing at the beginning.
After running it as admin, I am able to open it now. (Not using McAfee)
Last update I suspect from today was:
Thunderbolt Software - Intel Corporation - 3.43 MB - Version: 17.4.80.550
I reported issue here
viewtopic.php?f=6&t=97212

[hasikada]

Please, could you check new attached logs. Is it still McAfee issue?

[mpack]

You can check that for yourself. Search for "supR3HardenedWinFindAdversaries", which occurs a couple of pages down in the log. The number next to it should be 0x00 (that's 0 using hex notation). If it's not zero then it will list all of the likely conflicts, all of the drivers named "mfe...." are McAfee.

Look - I'll put it plainly: uninstall McAfee completely. It's snake oil. Windows 10 has perfectly adequate AV protection built in, it doesn't need help from third party companies with a vested interest in implying that the AV problem remains unsolved.

[hasikada]

Thank you for explanation. I found it. Yes it's McAffe issue again!