Memory protection exception on booting Ubuntu 16.04 VM

[fviktor]

Host OS: Windows 10 64 bit, Processor: Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz (12 CPUs), ~3.5GHz Memory: 32768MB RAM Available OS Memory: 32692MB RAM Page File: 9687MB used, 27869MB available

Guest OS: Ubuntu 16.04.3 amd64 desktop, new installation

Logs: ​https://www.dropbox.com/sh/mzdf371kdpecwcz/AAAvcNt4NIjOd4FqpqzKyrora/MemoryProtectionException1?dl=0

Ubuntu guest progresses to grub boot menu, then the VM crashes with memory protection exception during the early phase of Ubuntu startup.

Reproducibility: The problem happens many times in a row. If you restart VirtualBox Manager it seems to go away.

No dump yet. Enabled full dumps, will link that here next time it happens.

[fviktor]

Logs and screenshot in ZIP

[fviktor]

Links are dead and I cannot seem to edit the ticket description, sorry. Attached all the files in single ZIP instead.

[fviktor]

Crash happened again with full dump enabled, but no dump was saved by Windows. I got dumps for other crashed applications, so the registry settings seem to be good:

---

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps]
"DumpFolder"="C:\\Dumps"
"DumpCount"=dword:00000003
"DumpType"=dword:00000002

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\VirtualBox.exe]
"DumpFolder"="C:\\Dumps\\VirtualBox"
"DumpCount"=dword:00000003
"DumpType"=dword:00000002

---

Folder C:\Dumps\VirtualBox folder does exist. There is 400+ GB of free disk space on C:

Any ideas how to get a crash dump?

[fviktor]

First few attempts to start the VM crash. It is after booting the host OS. Then I can start and restart the VM with no problems.

Workaround: Changing any of the virtual hardware configuration (like removing AC97 audio or changing the virtual memory size by 64MB) seem to solve the problem temporarily, until the host is rebooted.

Observation is that the invalid address references is always 0x18, it does not change. So it is likely the same bug which is triggered all the time.