virtualbox.org

After last Windows 10 updates VirtualBox regularly falls

No visible reasons found, this may happen either with high guest activitity or no activity at all. Fall may happen in 10 minutes after VM start, or after several hours, but anyway 4-5 times a day.

Processor is Intel i5

First big clue:

orgaNaft wrote:After last Windows 10 updates

Pick one VM. Please right-click the VM in the main Virtualbox window's VM list, choose Show Log.

Search the far left tab's log for this text:

Attempting fall back to NEM

If you find it, Hyper-V is enabled and needs to be disabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

If you don't find that text, save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.

Thanks for the reply. No, this message is not listed. Last text is:

06:23:15.504596
06:23:15.504598 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 00000000000031e4!!!
06:23:15.504627
06:23:15.504627 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffcd8021862
06:23:15.504633 ExceptionInformation[0]=0000000000000000
06:23:15.504637 ExceptionInformation[1]=0000000000000000

Here's a log file

Thanks for the log. The VM ran for almost 6-1/2 hours before crashing, so it's probably not a VM OS issue.

The crashing module was VboxDD.dll. I don't know what this module does, but as a guess, if it's involved in 'D'irect-'D'rawing the VM for 3D acceleration, which is enabled in the VM, maybe the new video install is having trouble. This is pure guesswork, though.

orgaNaft wrote:After last Windows 10 updates

Did you re-install Virtualbox? If these updates were a major update, Virtualbox often doesn't survive those.

Try uninstalling Virtualbox and reboot the host using the 'shutdown -r -t 2' command in the command prompt or the Run... box. Then reinstall Virtualbox using right-click-Run-As-Administrator, even if your account has admin privileges.

scottgus1 wrote:The crashing module was VboxDD.dll.

According to Binaries overview, VBoxDD.dll contains the ring-3 part of (nearly) all virtual devices, so it could generally be in the context of graphics, audio, networking, storage, input, etc. devices, you name it. But you guessed it right nonetheless: The thread name was "VMSVGA FIFO". (*)

(*) BTW, don't get confused by the thread name: The Graphics Controller was correctly configured as VBoxSVGA.

Thanks, fth0, for illuminating me! So the video setup and 3D acceleration is glitching, at least in this log.

orgaNaft, 3D acceleration uses the host video drivers. Try a reinstall of Virtualbox and the host video drivers.

06:23:15.505207 Thread name: VMSVGA FIFO

This is going in my log reader!