Opened 7 years ago
Last modified 7 years ago
#17182 new defect
Black screen on Windows10 host vm 5.2.0
Reported by: | hekmo | Owned by: | |
---|---|---|---|
Component: | 3D support | Version: | VirtualBox 5.2.0 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | other |
Description
In a host Windows 10 Pro versión 1709, compilatión 16299.19 running W10 vm's, a black screens appears and don't show desk or logon. When im try to Close the vm, w10 desktop appears all grey but correctly showed.
Deactivating 3D acceleratión all W10 vm's run ok.
Attachments (4)
Change History (7)
by , 7 years ago
by , 7 years ago
by , 7 years ago
comment:1 by , 7 years ago
by , 7 years ago
comment:3 by , 7 years ago
00:00:04.518024 Guest OS type: 'Windows10_64' 00:00:06.599759 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)
Any reason why you decided to go against the proposed defaults of 2048 MB assigned to the guest? Your host can certainly afford it.
00:00:06.599754 NumCPUs <integer> = 0x0000000000000001 (1) 00:00:07.545127 CPUM: Physical host cores: 4
You can certainly afford another CPU assigned to your guest. It's going to perform much, much better.
00:00:04.524928 File system of 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' (DVD) is ntfs
If you don't use the GAs CD, eject it. Don't keep it there at all times, it can cause problems.
00:00:40.445414 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\nvwgf2umx.dll': rcNt=0xc0000190 00:00:40.731705 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\nvd3dumx.dll': rcNt=0xc0000190
Your Nvidia drivers are being rejected due to inappropriate signing. Update your drivers. And read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues to understand the issue and get some ideas on how to fix it.
Finally, can I suggest something? It's usually better and faster, if issues like this one (configuration, question) get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".
You need to post a ZIPPED VBox.log.