Windows 10 Guest Display Driver crash

[AlainDM]

Hi,

I have been running Windows 10 for a while as guest OS.
No real problems, until recently. I think after upgrading to VBox 5.0.10 r104061, and updating the VBox additions on the guest machine.
Since then the diplay driver crashes several times a day.
I tried uninstalling VB Additions complete (using /uninstall) and re-installing them. Works... For a couple of hours

Even simply re-installing (and even not rebooting) the Additions is enough to bring the display driver back. For a couple of hours.

The settings for the display: 256MB video memeory, 1 monitor, 2D acceleration ON,
NO 3D acceleration (when that is switched on, Win10 hangs on startup after login).

Is this a known problem?

By the way: Host OS is Linux Mint 17.
Graphics Card is NVidia Quadro 4000 - driver version 352.63 (recommended)

[socratis]

Even simply re-installing (and even not rebooting) the Additions is enough to bring the display driver back.

Why do you believe that it is the GAs specifically that cause the instability? Any indications? What does "bring the display driver back" mean?

Please read the following: Minimum information needed for assistance. As far as the VBox.log.zip goes, here's what you do:
- Start the VM.
- Wait for the crash.
- Right-click on the VM in the VirtualBox Manager.
- Select "Show Log..."
- Save it, ZIP it and attach it in your response.

[AlainDM]

The Guest screen is in AutoScale mode, and maximized. (not full screen)
Suddenly, the screen size changes (less wide and somewhat higher) and Win10 pops up a message saying the display driver has stopped working (or something similar)
After re-installing the GAs, the screen size returns to the earlier correct size automatically.

I attached a log file (happened 15 min ago)

[basti107]

Same Problem here.
In the Guests device-manager the "VirtualBox Graphics Adapter for Windows8" shows an exclamationmark and i can't change resolution to the desired 1400x900.

[socratis]

@basti107
This is not the same problem. The OP talks about a crash in the driver. You have a different problem, which I've seen several times in the forums. Search for it and either look at other threads, or open a new one. Oh, and next time that you post a log, please shut down the guest before doing so.

@AlainDM
I couldn't really find anything weird in your logs, with the exception that you have 6 cores which you assign all to your guest. I would assign a maximum of 4 or 5, otherwise your host will starve. Give it a shot and see if that fixes it. Other than that, I haven't seen the problem that you describe before, so others might be able to help you. Of course the same advice about completely shutting down the guest before you zip the log applies as well.

[AlainDM]

The Linux Host is coping well, actually.
I started of with 4 CPU's and gradually brought it up to 6.
As a matter of fact I run 2 Windows machines next to eacht other on it, and still no issues.

I'll set up a new Win10 Guest from scratch, and see what happens to that one.

[socratis]

I'll set up a new Win10 Guest from scratch, and see what happens to that one.

That's a really good idea. If you see the same behavior with the fresh install, and no one else has given you any ideas/solutions, then you should be heading over to the Bugtracker and search for an existing bug report or file a new one.

[TNComputerGuy]

What I did to remedy the situation is change all of my power settings to "High Performance" and set everything not to turn off. Haven't had a single crash since.

Hope this helps someone else.

[AlainDM]

Actually I got some more details about this.
I upgraded to the latest (Debian) build (Version 5.0.12 r104815), and did some more testing.

I have 2 Win10 Clients running on the same (Linux Mint) guest.
Both were set up from scratch (i.e. no upgrade).
One client is set to have 3D acceleration “on”, the other one is not.

The one with 3D acceleration “on” is not experiencing any problems, the other one is.
The latter crashes several times a day, while the first keeps running happily.

Now, problem solved, then? Not exactly.
With 3D on, Remote Desktop Connections fail to work. Remoting in on a machine takes very long, and when it finally comes up, the remote display is complete garbage.
I tried playing around with the RDP display settings, but without any luck.
With 3D off, this issue isn’t there.

I don’t have a clue what the problem is, and don’t seem to find anything about that on Internet.

[DeanS]

What I did to remedy the situation is change all of my power settings to "High Performance" and set everything not to turn off. Haven't had a single crash since.

Hope this helps someone else.

Where are the power settings?

[AlainDM]

Power settings are in Control panel.

Anyhows, I don't experience any problems any more. For other reasons I had to tebuild a new Win10 VM and now things are running OK.
There were a couple of updates on both Win10 and VBox, ofcourse as well.

Display Settings for the Win10 client:
- Memory 256MB
3D-accel OFF, 2D-video ON