VirtualBox: Windows XP BSOD 0x0000007B

Question

[edit] Quick answer from comment which I believe is true:

There is probably no realistic answer when the computer hardware does not support hardware virtualization. You will need to upgrade the machine to do what you want.

---

I tried to install Windows XP x86 in Oracle VirtualBox v6.0.14

After (seemingly) successful installation, on first (and each) boot BSOD with 0x0000007B occurs, which indicates that Windows is not seeing the disk hardware it was installed on.

Multiple posts across Internet report that problem gets resolved with Storage Device Controller set to IDE PIIX3. Some reported PIIX4, also try-to-pick-what-works-for-you has been suggested. https://forums.virtualbox.org/viewtopic.php?t=57466#p266748 gives somewhat opposite info:

There can be many reasons why it can't find the boot disk: the disk controller type change is one of them (it usually isn't necessary to play around with different IDE chipsets, PIIX4 should be fine

I have tried all three PIIX4, PIIX3, ICH6 available,
tried reinstalling from scratch with PIIX3 selected before I run VM for the first time,
— I get the same 0x0000007B

The difference is that people mostly run into 0x0000007B on migrating/upgrading, whereas I get it on fresh installation.

Host OS: antiX 19 GNU/Linux which is Debian 10 Buster with runit instead of systemd
Hardware: Lenovo 3000 G530 laptop, 2008 manufacture year, hardware virtualization is not supported.

Also I wonder:

1. Settings → System → Motherboard → Chipset
   PIIX3 and ICH9 are available,
   — this PIIX3 and PIIX3 of Storage Device Controller — are these settings interdependent?
2. Why only 32-bit options for guest machines for all OSes are available whereas the host is 64-bit?

Answer 1

Ripped from https://www.minitool.com/backup-tips/0x0000007b.html :

"What Causes the BSOD 0x0000007B?

The STOP 0x0000007B error often occurs on Blue Screen of Death. So what causes the BSOD 0x0000007B? The causes are shown below:

Missing or corrupted bootloader files.
Incorrect BIOS configuration.
Boot sector virus.
Damaged Registry.
Corrupted EFI bootloader.
Hard drive failure.

"

Means: turn on the virtualization on, check hw-settings (not more than 4gb RAM f.ex.), look about cpu-settings, and so on. then check your ISO or Image, then check your virtual harddisk (you may want to recreate it to make sure, everything is ok - an doublecheck the path).

If you like to, just recreate the whole maschine, sometimes it helps. :)

Answer 2

The solution is to add an IDE controller and select your Windows XP iso and do NOT use an SCSI controller.

If you already have the SCSI controller, DELETE it and add the IDE instead.