VirtualBox

Opened 10 years ago

Closed 10 years ago

#12875 closed defect (duplicate)

Windows ME Bluescreen on 4.3.10 / 4.3.8

Reported by: S.Seide Owned by:
Component: other Version: VirtualBox 4.3.10
Keywords: windows me bluescreen protection error Cc:
Guest type: Linux Host type: Windows

Description

After an update of Virtualbox 4.3.6 to 4.3.10 my Windows ME VM stopped working. During a normal startup (after selecting "Normal Start" within the Windows Start Menu) i get a Bluescreen "While initializing device NTKERN - Windows protection error. You need to restart your computer. System angehalten."

Selecting "Safe Mode" at Windows start the system works without problem (no bluescreen).

The problem exists with:
virtualbox-4.3_4.3.10-93012~Ubuntu~raring_amd64.deb
virtualbox-4.3_4.3.8-92456~Ubuntu~raring_amd64.deb

Workaround:
going back to 4.3.6 the VM works as expected.

Virtualbox Host:
Ubuntu Linux 13.10 (x86_64)
Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz

Attachments (4)

winme_crash_4.3.10.png (25.4 KB ) - added by S.Seide 10 years ago.
Screenshot Windows Bluescreen
BOOTLOG.PRV (8.8 KB ) - added by S.Seide 10 years ago.
Windows Bootlog of start with bluescreen
VBox-winme-safemode_ok.log (92.0 KB ) - added by S.Seide 10 years ago.
Virtualbox Log of Windows Safe Mode startup (working)
VBox-normal-logged_crash.log (91.5 KB ) - added by S.Seide 10 years ago.
Virtualbox Log of Windows Normal Mode with Logging startup (blue screen)

Download all attachments as: .zip

Change History (5)

by S.Seide, 10 years ago

Attachment: winme_crash_4.3.10.png added

Screenshot Windows Bluescreen

by S.Seide, 10 years ago

Attachment: BOOTLOG.PRV added

Windows Bootlog of start with bluescreen

by S.Seide, 10 years ago

Attachment: VBox-winme-safemode_ok.log added

Virtualbox Log of Windows Safe Mode startup (working)

by S.Seide, 10 years ago

Virtualbox Log of Windows Normal Mode with Logging startup (blue screen)

comment:1 by michaln, 10 years ago

Resolution: duplicate
Status: newclosed

This ticket is a duplicate of #12240. The key symptom is "IEM: rdmsr(0x1b) -> GP(0)" in VBox.log.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use