Black Screen on W10x64 after 5.2.28 update (#18592)

[socratis]

---

ModEdit; related ticket: #18592: OpenGL has performance and drawing issues after 6.0.6 update.

---

I updated VB from 5.2.26 to 5.2.28 yesterday and My W10x64 guest goes to black screen after some time not working in it
It probably goes to sleep mode, but never comes back alive when I return.
I tried to scale screen, mount CD, but no joy
I read thru forums and tried to turn off 3D acceleration, but then machine started and menu items were empty, windows did not really work.
any idea what can I do? Should I try VB6 ?
I have attached logfile as well

[maker675]

Windows 10 latest.

Since installing 5.2.28 (OSX, Macbook Pro 15") get black screen in Windows 10 when 3D acceleration enabled in Display preferences.

Each time this happens (it doesn't happen immediately after booting) have to force power down and start over. (So now have turned it off.)

Any ideas how to fix?

(Some logs from earlier attached.)

[TheRedhead]

I have been seeing a similar issue with the 6.0.X series as well.

After your suggestions, I disabled 3d and the video has been stable since yesterday which is an improvement.

[JonasBerlin]

I have the same exact problem. When it happened last time I was in Visio and you can see that Windows and Visio are still fine even though the screen is black, as the pointer changes when you mouse over the location where the drawing is. You can also tell that it processes ctrl-alt-delete correctly as the pointer changes appropriately.

Jonas

[socratis]

It probably goes to sleep mode

Disable all power savings modes, screensavers, screen locks, etc. There's no point if your host is still alive and kicking, you're not getting any power savings, only trouble.

[GASTAN]

Well I ended up just doing that, so far so good, but it's a shame and bug in my eyes.
and it was not happening in 5.2.26.
also I turned off 3D accel and reinstalled tools

[Air Force One]

I created a ticket because I have the same issue with new different versions. Take a look and make some enhancements if necessary.

[maker675]

Good job.

My logs contained those Open GL warnings too.

[folj]

I also got a black screen for the first time on my Windows 10 guest after updating to 5.2.28, and see some OpenGL errors. VM was still running even with the black screen, since I could restart it blindly with Win+X+arrow keys.

[socratis]

I merged the two posts "Black Screen on W10x64 after 5.28 update" by "GASTAN" and "since installing 5.2.28 get black screen with 3D acceleration" by "maker675", and moved it to the "Windows Guests" area where it belongs.

Added ticket information, although the post from boxer01/"Air Force One" seems to be for 6.0.6. It still remains to be seen if it is indeed the same issue. For the moment, I'm assuming it is...

[Air Force One]

As I wrote in the ticket, I first found this behavior in the 6.0.6 version, but afterwards tested and see it again in versions 5.2.28, 5.2.29 and 6.0.7. So there were changes in all branches. Another important thing: my older system with Windows 8.1 host and Windows 7 guest isn’t affected, probably because the OpenGL support is not so good there, so there are no possibilities there for some bugs and optimizations.

[socratis]

I first found this behavior in the 6.0.6 version, but afterwards tested and see it again in versions 5.2.28, 5.2.29 and 6.0.7.

You're right, I should have paid closer attention to the ticket, mea culpa...

[Air Force One]

@socratis: don’t worry, no animals were harmed… and so on.

As I wrote in the ticket: on current 5.2.29 it takes 75 seconds from the start to the desktop appearance. And I need another 20 seconds to get reaction from the windows explorer window I open as a first action in the VM. On the current 6.0.7 it is 70 seconds plus another 10 seconds. On the older version (5.2.22, 5.2.26 or 6.0.4) with the same host, guest and VM I need just 35 seconds to start the VM and everything works and reacts just immediately. So you can really see the slowness here even without the chronograph.

[socratis]

Post a ZIPPED VBox.log. I'll compare them with mine.

When I'm done with the 118 VirtualBox related tabs that I have open at the moment and I need to read/evaluate/analyze/reply to...

[Air Force One]

@socratis: I put my logs and comments into the linked ticket, so you and everybody else could see it there.