Windows 10 Insider - Not booting correctly with GA Video Driver

[bhahlen]

As reported in https://www.virtualbox.org/ticket/15973 Using Fedora 25. Just upgraded to VirtualBox 5.1.16. Installed GA 5.1.16 Guest Settings: 2D Acceleration enabled 3D Acceleration disabled

Windows 10 refuses to boot, with the Video driver installed. After two tries, using Basic Video Driver works.

Relevant lines from log file (also attached):

00:00:07.649607 RTC: period=0x200 (512) 64 Hz
00:00:07.689199 VBVA: InfoScreen: [0] @0,0 3840x2025, line 0x3c00, BPP 32, flags 0x1
00:00:07.689219 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007f9078000000 w=3840 h=2025 bpp=32 cbLine=0x3C00 flags=0x1
00:00:07.689250 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=3840x2025, Sending to async-handler
00:00:07.689364 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=3840x2025
00:00:07.689375 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=3840x2025
00:00:07.689620 GUI: UIFrameBufferPrivate::performResize: Size=3840x2025, Directly using source bitmap content
00:00:07.694329 GIM: HyperV: Guest indicates a fatal condition! P0=0x7e P1=0xffffffffc0000005 P2=0xfffff807d604e92b P3=0xffff8c0106b45cd8 P4=0xffff8c0106b45510
00:00:09.134352 NAT: Link up
00:00:10.146743 AHCI#0: Reset the HBA
00:00:10.147380 AHCI#0: Port 0 reset
00:00:11.354005 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:00:20.399165 GIM: HyperV: Reset initiated through MSR
00:00:20.399202 Changing the VM state from 'RUNNING' to 'RESETTING'

Enabling 3D Acceleration gives a "System Exception Thread not handled" error.

[bhahlen]

VirtualBox Log file

[bhahlen]

Just updated to 15055, still have the same issue.

[Legorol]

I have the same problem, first described in ticket #15973 and now in this ticket. Recent Windows 10 Insider builds do not boot with current Guest Additions video driver.

My environment:

• VirtualBox 5.1.16 and Guest Additions 5.1.16
• Host: Windows 10 Pro version 1607 (public build 14393)
• Guest: Windows 10 Pro insider build 15048

[bhahlen]

This still happens with 5.1.18 and GA 5.1.18

[Dmitrii Grigorev]

@bhahlen and @Legorol. Thank you for the info!

The attached log tells that BugCheck 0x7E happens while processing the first request to resize virtual display to 3840x2025. To continue analysis kernel memory dump for your Win10 guest is required. Please attach (or share somethere) such 'memory.dmp' file.

Also, please put detailed info about your graphics hardware into description of this ticket.

[bhahlen]

How can I create such a memory.dmp file? Or is that automatically generated? And if so, where?

I am running Fedora 25 on a XPS15-9550, with a nVidia GTX 960M and Intel HD Graphics 530. Guest runs with 128MB Video Memory and 2D Acceleration enabled.

[Dmitrii Grigorev]

Replying to bhahlen:

How can I create such a memory.dmp file? Or is that automatically generated? And if so, where?

I am running Fedora 25 on a XPS15-9550, with a nVidia GTX 960M and Intel HD Graphics 530. Guest runs with 128MB Video Memory and 2D Acceleration enabled.

Here is the instructions to configure your guest ​https://msdn.microsoft.com/en-us/library/windows/hardware/ff542953(v=vs.85).aspx, please choose 'kernel memory dump', restart your guest and reproduce that crash.
Waiting for you memory.dmp!

[bhahlen]

I have, but I can't upload it here, so I put it on my own site. Here is the link: ​https://www.benweb.eu/tmp/vbox/memory.dmp

[Dmitrii Grigorev]

Replying to bhahlen:

I have, but I can't upload it here, so I put it on my own site. Here is the link: ​https://www.benweb.eu/tmp/vbox/memory.dmp

Microsoft did not yet shared symbol files for your super-new Insider build 15058 :), even OS kernel symbols are not available yet, so windbg says:

SYMSRV: ​https://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/C200033256954855A26CFB0BE1AD7FC01/ntkrnlmp.pdb not found

Will see what happened nevertheless...

[bhahlen]

If it is any consoloation, it also happened on 15055, 15052, and 15048 :-)

[Dmitrii Grigorev]

Replying to bhahlen:

If it is any consoloation, it also happened on 15055, 15052, and 15048 :-)

Ok, for now the best should be 15048 - the recent "Slow ring" build, just checked that OS kernel symbols are available on Microsoft's server.
So, please, get new kernel memory dump and share it as before.

Thank you in advance!

[bhahlen]

I tried getting a new memory dump, but my VM was just upgraded to 15061, and I don't seem to able to generate one. I will try a few more times, but it could be a bit.

[bhahlen]

After updating to 15063, I got a new memory dump: ​https://www.benweb.eu/tmp/vbox/MEMORY20170326.DMP

[Dmitrii Grigorev]

Replying to bhahlen:

After updating to 15063, I got a new memory dump: ​https://www.benweb.eu/tmp/vbox/MEMORY20170326.DMP

That kernel memory dump is Ok, thank you!

It reveals BUGCHECK 0x7e caused by 'Access violation' somethere in OS kernel code. Will see how VirtualBox can be involved into that problem...

nt!KiExceptionDispatch+0xc2
nt!KiPageFault+0x217
dxgkrnl!TdrIsEnabled+0x5e8fd
dxgkrnl!DxgkUnreferenceDxgResource+0x229d3
cdd!BootGraphicsUpdateThread+0xa5
nt!PspSystemThreadStartup+0x47
nt!KiStartSystemThread+0x16

[Frank Mehnert]

Still reproducible?

[Dmitrii Grigorev]

Could you download and check a test build 115855 (or higher) from https://www.virtualbox.org/wiki/Testbuilds ? It contain fixes relevant to the problem.
Just checked that on my HW the Windows Insider 15063 (32-bits version) always boots without problems with GA 115855 installed.

[Chadwick Robbert]

It is also happening with Windows 10 guest version 1703 build 15063 with VirtualBox Version 5.1.26 r117224. If there are any specific logs required, please let me know the procedure. I can do my best.

[Dmitrii Grigorev]

If someone still can reproduce the problem, appropriate VBox.log and kernel memory dump is requried to continue analysis.