I have just installed Guest Additions.
I've just got the following error message:
I can't figure out exactly what I did to get this.
How to fix?
π
Display driver has stopped responding and has been disabled
Display driver has stopped responding and has been disabled
I have a fresh Win10 guest.
I have just installed Guest Additions.
I've just got the following error message:
I can't figure out exactly what I did to get this.
How to fix?
π
I have just installed Guest Additions.
I've just got the following error message:
I can't figure out exactly what I did to get this.
How to fix?
π
-
Ken Hagan
- Posts: 43
- Joined: 1. Oct 2009, 17:42
- Primary OS: Debian other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows (various)
- Location: UK
Re: Display driver has stopped responding and has been disab
I don't think you've done anything wrong. (I get the same messages from time to time.) As I understand it, Windows will stop using a display driver if it takes more a certain time to perform some tasks.
This is quite an old feature: https://support.microsoft.com/en-us/kb/2665946. However, the timeout mentioned in that article is 2 seconds and I'm fairly sure that my VM is not noticeably stalling *at all*, let alone for 2 seconds, so perhaps they have changed this value in the latest Win10 (November 2015) update.
The replacement driver is a simple one based on a framebuffer, which visibly crawls. I assume that the only way to recover acceptable performance is to reboot the VM.
This is quite an old feature: https://support.microsoft.com/en-us/kb/2665946. However, the timeout mentioned in that article is 2 seconds and I'm fairly sure that my VM is not noticeably stalling *at all*, let alone for 2 seconds, so perhaps they have changed this value in the latest Win10 (November 2015) update.
The replacement driver is a simple one based on a framebuffer, which visibly crawls. I assume that the only way to recover acceptable performance is to reboot the VM.