BSOD when Starting Windows XP (32-bit VM) on Windows 10

[JanHO]

I get a BSOD screen when attempting to start a VM.
Error displayed is STOP: 0x0000007B (0xF78A6528,0xC0000034,0x00000000,0x00000000)
I had this previously running. Now it won't.

I have re-installed Oracle VM VirtualBox. I am now on the latest version Version 6.1.28 r147628 (Qt5.6.2) and have re-installed the vmdk.
I get the same error even if I try to start in safe mode as well.

The last line in the VBox.log is:
00:28:27.537423 ERROR [COM]: aRC=VBOX_E_NOT_SUPPORTED (0x80bb0009) aIID={13a11514-402e-022e-6180-c3944de3f9c8} aComponent={GuestWrap} aText={Invalid status level defined: 0}, preserve=false aResultDetail=0

Log file attached.

The last lines in the VBoxHardening.log are:
5c0c.320c: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 0000000000000b84 (hFile=0000000000000d40) with 0xc0000022 -> STATUS_TRUST_FAILURE
5c0c.320c: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\tzres.dll [avoiding WinVerifyTrust]
5c0c.320c: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 0000000000000d40 (hFile=0000000000000b84) with 0xc0000022 -> STATUS_TRUST_FAILURE

Hardening log file attached.

I am not sure if any of this helps.

Thanks

[mpack]

Stop 0x7B is very well known, discussed on these forums many times. It means that XP can't find the boot drive or volume it was previously using. It happens most often when you P2V, or when you change the disk controller in the VM.

The naming of objects inside the VM tells me that this was not always a VirtualBox VM, in fact it was probably a VMWare VM. VMWare defaults to LsiLogic SCSI controllers for XP, VirtualBox defaults to IDE. This would be the controller change.

[AndyCot]

If it was working with 6.1.26 then go back as 6.1.28 has bugs. Also there are later versions of Virtualbox available via the test build page, https://www.virtualbox.org/wiki/Testbuilds

[mpack]

Please stop offering that up as a panacea. I'm not aware of any problem in 6.1.28 that results in stop 0x7B BSOD screens in XP guests.

[AndyCot]

What about the text "I had this previously running. Now it won't." ?

[mpack]

What about the text "I had this previously running. Now it won't." ?

What VM error does that NOT refer to?

In any case the VM was running. The fact that it BSODed with a stop 0x7B shows that. That's a guest OS error, not a VM error.

[scottgus1]

@AndyCot:
I'll also add that this:

I get a BSOD screen when attempting to start a VM.
Error displayed is STOP: 0x0000007B (0xF78A6528,0xC0000034,0x00000000,0x00000000)

is an error message from XP. In order for XP to display this message, the Virtualbox VM "container" would have to be running correctly so that a process in the VM OS could run and display an error from the VM's OS.

In short, this:

I had this previously running. Now it won't.

does not always mean the Virtualbox VM is not able to start. Such a report has to be further diagnosed to determine exactly what is not running. We run into this all the time on the forums. You'll see that too as you continue to help people.