Windows 10 crashes when updating to Creators (Version 1703, Build 15063) on 3840x2160 resolution

[merced]

My host OS was Windows 10 x64 version 1607 (Build 14393). VirtualBox version is 5.1.18. Hardware configurations of my PC are:
CPU Core-i7 4720HQ, 16GB memory, NVidia Geforce GTX 860M display card, with resolution 3840x2160.
I have created a VM in VirtualBox. The guest OS was Windows 10 x86 version 1607 (Build 14393). The guest additions software was installed successfully on it. 2 CPU cores and 3GB memory were allocated to the guest OS. The display options were: 256MB display memory, 2D/3D accelerator enabled, scaling factor 100% (i.e. the resolution in guest OS was 3840x2160 too.) The guest OS worked well.
I upgraded my host OS to Windows 10 Creators x64 version 1703 (Build 15063) last week. The host OS works well. However when I upgraded the guest OS in that VM, the setup program crashes. After several experiments, I found that the setup would success if I modify the scaling factor to 200% (i. e. the resolution in guest OS is 1920x1080), and that it would fail if the scaling factor is 100%. After I upgrade the guest OS to version 1703, the OS starts and runs successfully when I keep the scaling factor as 200% unmodified. If it is modified to 100%, the OS crashes in the startup stage. The error message is SYSTEM THREAD EXCEPTION NOT HANDLED. The module is dxgkrnl.sys
Yesterday I updated VitrualBox and the guest additions in the guest OS to version 5.1.20, but the problem remains.
Has anyone else encountered this problem?

[merced]

The bug ramains when updated to 5.1.22

[Blackhorse]

i have the same problem. Screensize is 2560x1440.

[Blackhorse]

My environment:
The Host is a Lenovo Thinkpad T430 with Intel(R) HD Graphics 4000, Windows 7, x64, SP1. External Monitor 2560x1440.
Guest ist Windows 10 Pro, x64, Version 1703, Build 15063
VirtualBox Version 5.1.22, Guest Settings: 256MB Display Memory, 3D Acceleration enabled.

[merced]

i have the same problem. Screensize is 2560x1440.

I have just done some additional tests.
The smallest scaling factor can be set in Windows 10 Version 1703 guest is 162% on my laptop, the resolution of which is 2370x1333. The OS crashes in booting stage when I set the scaling factor to 161%.
I found this threshold by binary search.

[Blackhorse]

I used 2370x1333 as starting point for my tests.
The guest runs in a window, scaling factor is 100%, Auto-resize Guest Display is on. So i can change the resolution by enlarging or shrinking the window just by mouse movement.
I have recognized that the wide does not matter, the maximum screen size of 2560 works fine. But when i set the height to 1340 then Windows 10 crashes at reboot.
So resolution 2560x1339 works fine, resolution 2560x1340 crashes.
Its ever the same error, BugCheck 0x7E during resize, which can be seen in the VBox.log

[steveoracle]

Same issue here. When screen resolution is 2580x1369 or 1920x1440, Windows 10 crashes on startup. (Still trying to find a resolution that works)

If I load windows into safe mode and remove guest editions it boots up fine. That will be what the log shows at the end.

Edit: It looks like the theory mentioned before is height > 1339 is causing the crash

Host:
Macbook Pro Sierra
16GB RAM
512GB SSD

[Blackhorse]

I have found an "alleviation" for this problem. I force Windows 10 guest to boot in Base video mode.

To activate this: msconfig / Boot / select: "Base video" and also: "Make all boot settings permanent". This forces to start with 1024x768 resolution.

With this setting the Windows 10 - 1703 guest boots up on my 2560x1440 monitor without BSOD. After the system is up i press Host+F to switch to full screen.
For me this works as an interim, hope the boot problem with large monitors will be fixed soon.

[merced]

This solution works for me too.
Hope the bug will be fixed soon.

[merced]

To activate this: msconfig / Boot / select: "Base video" and also: "Make all boot settings permanent". This forces to start with 1024x768 resolution.

It seems that this bug does not occur again after patching the KB4020102 on Windows 10 Creators (1703).
The URL of patch: https://support.microsoft.com/en-us/hel ... -kb4020102
If Windows Update is enabled on Windows 10 Creators, it can download and install this patch automatically now.

After patching it, you can enter msconfig / Boot, uncheck "Base video", and check "Make all boot settings permanent"

[Blackhorse]

Hello merced, thanks for the info.
KB4020102 fixes the problem for me too.