Windows ME BlueScreen during boot after update -- again as of VBox 4.3.8 [FIXED IN SVN]

[S.Seide]

After updating VirtualBox from version 4.2.18 to 4.3.0 my Windows ME VM does not start anymore. During boot it crashes with an blue screen:

While initializing device NTKERN Windows protection error. You need to restart your computer. System angehalten.

Switching back to VirtualBox 4.2.18 the same VM starts again without any problem.

VirtualBox 4.3.0-89960~Ubuntu~quantal, deb-Package from Oracle

Host: Linux 3.5.0-42 (x86_64), Xubuntu 64Bit

Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz

Guest: Windows Millenium Edition, all patches installed

512MB RAM, 1 CPU, VT-x, Nested Paging, PAE/NX, no IO-APIC

[S.Seide]

VirtualBox Logfile

[S.Seide]

WinME BOOTLOG.TXT - Crash with VBOX 4.3.0

[S.Seide]

WinME BOOTLOG.TXT - normal start after downgrade to VBox 4.2.18

[Petr Vones]

See #12227

[Frank Mehnert]

Should be fixed in VBox 4.3.2.

[hqngl]

Persists in 4.3.2

[Frank Mehnert]

hqngl, please attach a VBox.log file from such a VM session running on VBox 4.3.2.

[hqngl]

VBox.log of BSOD in Windows ME on Xubuntu 13.10 x64 Host

[hqngl]

Replying to frank:

hqngl, please attach a VBox.log file from such a VM session running on VBox 4.3.2.

Attached log from Xubuntu 13.10 x64 host.

Some additional info on the bug:

• Same error with Windows 7 x64 Host
• Only occurs if hardware virtualization is enabled
• VirtualBox until 4.2.8 works fine
• Bug occurs first in 4.3.0 Beta 1

Thanks for looking into this issue.

[Klaus Espenlaub]

That line explains it all...

00:00:05.034819 IEM: rdmsr(0x1b) -> GP(0)

The guest OS accesses accessing IA32_APIC_BASE_MSR, and VirtualBox 4.3 doesn't let it. So this is one of the issues where the new checks are too restrictive.

[bird]

Bug in the apic device emulation. Fixed will be shipped in 4.3.4.

[scop]

I'm seeing the exact same issue with VirtualBox 4.3.10 on a couple of Fedora 20 hosts, one 32-bit and another 64-bit. Disabling hardware virtualization works around it.

[scop]

VirtualBox 4.3.10 Windows ME BSOD log from a Fedora 20 x86_64 host

[Kamil Jońca]

I can confirm this issue in 4.3.10. I *think* than in 4.3.6 worked properly.

[Andreu Cladera]

I also have this issue with VirtualBox 4.3.10 on Ubuntu 13.10 (64 bits). Guest OS is Windows 7 Prof (32 bits). Disabling VT-x solves the problem.

[foulsoft]

Well done Andreu,

Disabling VT-x solves the problem also for me Windows7 Prof (64 bits)). Thank you :)

[foulsoft]

Well done Andreu,

Disabling VT-x solves the problem also for me Windows7 Prof (64 bits)). Thank you :)

Just I forgot one thing to say : it was for Windows7 Prof (64 bits) Guest OS is WindowsME (Windows Millenium Edition) where I usually faced NTKERN error... :)

[Frank Mehnert]

Disabling VT-x is only a workaround. This has to be properly fixed.

[Andreu Cladera]

Replying to frank:

Disabling VT-x is only a workaround. This has to be properly fixed.

I agree this must be properly fixed. The problem also occurs with guest Windows 8.1 (64 bits) and I can't disable VT-X for this OS.

[Frank Mehnert]

Please attach a VBox.log file for your Windows 8.1 guest. I think this problem is different from the Windows ME problem.

[Andreu Cladera]

Blue screen installing Windows 8.1 Pro (64) on VirtualBox 4.3.10. Host is Ubuntu 13.10 (64 bits)

[Andreu Cladera]

Doing a little search, I found that maybe my issue is related to #12876.

[bird]

Next release contains a workaround both issues reported here.