Windows 10 guest completely locks up randomly

[jperlman]

Hi,

Right now I'm testing out Windows 10 for my company and I'm not really using it heavily but it's been completely locking up where nothing works. I have to kill the Virtual Box process to stop the vm.

When I view the logs of the crash the always end in

03:19:24.592200 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :=>DxgkDdiQueryCurrentFenceNew
03:19:24.592262 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :uncompleted fences, u32FenceSubmitted(276514), u32FenceCompleted(276513) u32FenceProcessed(276513)

I'm attaching the full log of a recent crash.

Thanks for any help you can give me.

Jonathan

[mpack]

I think you should raise a bugtracker ticket to describe this issue.

Having done that, and as a workaround for now, what happens if you set the number of CPUs to 1 in the VM recipe?

Please confirm that hitting the close button on the VM window does not close the VM (i.e. it is the VBox process which is locking up, not the guest OS).

[HM]

Have the same problem. Have been running Win 8.1 as guest successfully but the problem started when I upgraded to Win 10. Host is Ubuntu.

When the problem occur the CPU hogs and it is not possible to shut down the VM other than by killing virtualbox on host. And I do already have 1 CPU configured.

[jm_paulin]

I saw that a couple of times when I was running VirtualBox 4.3.30. I upgraded to VirtualBox 5.0.2 and did not see the problem yet. Might be worth a try.

Host is Ubuntu 14.04 LTS

[HM]

I have been running 5.0.2 so the problem is also in that version. But, I was running a single virtual CPU but when I tested to use two it has been running stable for a couple of days. Will let you know if this solved my problem or not in the long run.