Virtualbox 6.1.32 is restarting my windows 10 pro host

[magnolia]

I recently downloaded VirtualBox 6.1.32 on WIndows 10 Pro and since then i notice my computer just randomly restarts. The restarts happen often usually within a few hours and it continues to restart. Computer is very beefy with 64GB memory and 12 core Xeon processors, so am not sure what is the issue really. I only have 1 VM turned on.

I turned off VirtualBox and no more restarts.

Is this a known issue? How do i resolve this?

[scottgus1]

Sounds like your host computer is blue-screening with automatic restart. Virtualbox doesn't normally blue-screen the host, but it does rarely happen, if something isn't quite right on the host, like a mad stick of RAM or an incompatibility with another driver.

Use Windows methods and web-searches to pin down why the blue-screen is happening and what code it is.

[magnolia]

Sounds like your host computer is blue-screening with automatic restart. Virtualbox doesn't normally blue-screen the host, but it does rarely happen, if something isn't quite right on the host, like a mad stick of RAM or an incompatibility with another driver.

Use Windows methods and web-searches to pin down why the blue-screen is happening and what code it is.

I did not mention blue screen..it just restarts
Computer is way beefer than what virtualbox is
Without virtualbox, computer works great as normal
With virtualbox on, random restarts every couple of hours
No errors anywhere, no warning anywhere

This is a bug

[scottgus1]

I did not mention blue screen

I know you didn't. That's why I said, "Sounds like..."

Virtualbox does not randomly restart a host PC. I and gobs of others have run Virtualbox VMs on all sorts of host PCs for days on end without problems.

However, if the host PC has drivers or other software that are incompatible with Virtualbox, or a hardware glitch that is only triggered when the PC is stressed, the host PC could randomly reboot when the incompatibilities/glitch arise. And Windows is often configured to automatically reboot during a bluescreen, often without even showing the bluescreen, only recording the bluescreen data in the Event Viewer (hint hint).

This is a bug

You've provided zero evidence that this reboot is coming from Virtualbox, only your personal observation that the reboot happens only when a Virtualbox VM is running. I'm not saying the reboot is not happening, or that the reboot is not happening when a Virtualbox VM is running. But your unproven statement does not prove Virtualbox is causing the reboot. So far we have no evidence of a bug.

If you continue to object to my calling this reboot a 'bluescreen' because you can't see the blue screen, which can happen, see above, then let me rephrase:

Use Windows methods and web-searches to pin down why the blue-screen reboot is happening and what code it is.

So this time, if you want help, stop correcting me on semantics and do what you were told. Find and provide evidence of your assertion, or even better, the cause of the reboot.

Without evidence we can do nothing to help.

[magnolia]

This is 1000% sure the reboot happens because of virtualbox
You mentioned you use virtualbox on many hosts and no issue, but did you install Virtualbox 6.1.32? Are the host pcs windows 10 pro?

I have not used virtualbox on this computer for years. I downloaded Virtualbox 6.1.32 and then my computer restarts randomly. I then stopped virtualbox and my computer has not restarted. I tried this 2 and same result.

Maybe i don't have evidence to show other than my statements, but please at least check my statements. I know there are many ifs and buts, but we can go with probability at least. What are odds it is not virtualbox? close to zero?

[scottgus1]

did you install Virtualbox 6.1.32? Are the host pcs windows 10 pro?

Yes and yes, though I personally haven't run a 6.1.32 VM for long periods of time. However, the forum hasn't blown up with dozens of 6.1.32 users on 10 hosts reporting random rebooting. 6.1.32 has been out for a while: if this was a 'bug' in 6.1.32 it extremely likely would have shown up before now. Probability therefore predicts that this is a problem with your specific host, per the possible problems mentioned above, not in a 'bug' in 6.1.32 that hasn't showed up yet.

Not to say that there could not be a 6.1.32 bug that your particular computer is able to trigger. As mentioned before, we have no evidence of this bug, or even why the reboot happens. You must provide the evidence. Example: I state that outside my window is a cherry tree. You have no way to test that statement. I can provide a picture of the tree, though, then you can test it. We don't see this happening anywhere else, except through the possible reboot causes mentioned above, which can happen under any Virtualbox version, because of host incompatibilities or glitches.

This falls back to you needing to troubleshoot your PC using Microsoft help channels and determine the reason the computer thinks it's rebooting.

[mpack]

Probability therefore predicts that this is a problem with your specific host

This.

Usually this problem comes down to resource usage and some hardware problem with same, for example a bad bank of RAM that most apps don't care about because they dont touch that part of RAM.

Correlation is not causation. Not even when the correlation is 1000%.

And yes, I'm using 6.1.32. As mods we typically install new versions on the day of release (that was in late January), how else can we test the claims people make about it?

I note also that I see no VM log here, so how do we even know how much RAM you are allocating?