Win 10 guest reboots ~60 secs on W7 host since 5.1.12/14

[Papolytic]

Host: win 7 pro 64, Guest 1 : Win 10 64 pro / Guest 2 : Ubuntu 16.04 LTS 64.

I can see one thing that got fixed for me on this release: When I tried to delete a snapshot on the very last one (.12 and .13) I would get a freeze at 36% each time, either VM. But: It's no longer a problem.

I've not yet backed up my VM's today but will try my bug https://www.virtualbox.org/ticket/16381 to see if that one is still alive. I suspect it is. Ever since the 2 separate installs during VM guest tools , I've had the Win 10 crash within 60 seconds of startup. I'll report back.

Edit: Yes, bug https://www.virtualbox.org/ticket/16381 is still there in 5.1.14..

Edit::

It was recommended by @socratis that I move this here. I'd filed a bug. I doubt it was looked at. I think it is much like a topic further down the page that sort of pins it on build 15002 (of the fast ring). I went a bit further and tried a regular copy of win 10 (just a plain old win 10 build) 64 bit, and had the same problem. There is a logfile in my bug 16381. I also figured out a "few things". The problem seems related to the 5.1.12+ video driver (3d/2d accel) because:

1) I managed to uninstall the video drivers back to VESA and it works fine without them.
2) I uninstalled all guesttools, and installed build 15007 of Win 10 64 pro.
3) Then I unpacked all the guesttools so I could pick & choose the drivers.
4) I installed them one by one from ones I was least suspicious of (network, etc) to ones I was most suspicious of.
5) Only the video driver causes a reboot within 60 seconds.

Symptoms (put in a better framework)
a) Boots normally, allows login
b) Resolution is ~1280 x 800 or so.
c) After ~60 seconds (it varies ~+- 60 seconds), the screen goes to smallest possible size (640x480) and then it reboots and goes into troubleshooting mode.

Things of note:
a) Since 5.1.12 (or was it .10?) There have been 2 additional installs that occur while installing the guest tools in W10.
b) UAC forces them to your attention.
c) One says something about Graphics driver, and so does the other I think about GLX. YOu have to say "yes" or the install procedure dumps you.
d) After you boot into the guest with the new guest tools, the reboots begin. I can't help but think the two UAC popups are in some way part of what becomes the problem.

If you just go into device manager without any guest tools installed, and right click "Display adapter" and say update, you can update it by pointing into the unzipped guest tools and avoid any UAC challenges, and in fact, it all seems to work better. No reboots. That's where I've at now which is so-so for me, but probably not for anyone really wanting to *Use* windows 10. I'm just lightly tracking it in a VM, so am not horribly upset by these things, but I'd love to see it addressed.

I *think* this is related in some way to a bug further down the page: viewtopic.php?f=2&t=81362. Sorry I didn't notice that first but mine might add a little more in the way of symptom explanations to the issue.

[socratis]

The log you provided has something weird. According to the description in the bug report, it is "Partial (last 1/2) of log from crash this morning (12-Jan-2017)". Half-logs are as good as empty-logs

So, in order to get the full picture, and since 5.1.14 came out try with that:

1. Start the VM. Not from a saved or paused state. Clean start.
2. Take the steps required to generate/observe the error. In your case, wait till you get to the "Repair" screen of Windows.
3. Shut down the VM (if it hasn't aborted by itself). Not saved, not paused. Completely shut down. If you can't shut it down by normal means, close the VM window and select "Power off".
4. Right-click on the VM in the VirtualBox Manager. Select "Show Log..."
5. Save it (just the first log), zip it and attach it in your response (see the "Upload attachment" tab below the reply form).

[Papolytic]

I can give that a shot tonight after work. I'll kick off a backup of the VM before I head out now.

Thanks.

[Papolytic]

Much like taking a car in and trying to get it to make "that noise" in front of a mechanic, I'm not having any luck repeating my problem with 5.1.14 at this point. I decided to clone it (non-linked) so I wouldn't mess up the original, did a complete add of the 5.1.14 guesttools in W10 suspect guest and reboot.

No point in attaching a logfile since I can't find the problem now. Maybe it was accidentally fixed in 5.1.14 and since I've been keeping so many in-between builds/testBuilds around , I *might* have put the wrong set of guest tools into the directory, but whatever: I can't repeat it right now.

Well: I'd rather have it working (as long as it's reliable) than not, so I'm not going to complain unless it does go south at some point again. If there's a problem, I'll attach the logfile here as a zip.

Thanks.

[socratis]

Good to know. Make sure you report it on the ticket, so it can be closed as "Works for me".

[Papolytic]

Good to know. Make sure you report it on the ticket, so it can be closed as "Works for me".

I tried to do that, checked the proper boxes, etc, but I suspect I've no permissions to do so. Could you mark that as closed for me?

Many thanks either way.