[Solved] 0x000008e error when running XP in VB 6.1.4

[snowcool776]

I am having trouble with accessing my XP SP3 Guest recently on a Win10 Host.
When it logs on to the desktop, it crashes with this code:
STOP 0x0000008E
Logs are attached and a screenshot of the BSOD is also attached too.
I have tried reducing the memory to 512MB from 1024MB, clean booting the guest, and removing applications that may be causing the problem, all to no avail.
Thanks

[mpack]

00:00:11.233615 Host RAM: 3971MB (3.8GB) total, 1187MB available
...
00:00:11.838549 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)
00:00:11.838964 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)

Memory allocation is too close for comfort. I would reduce to 512MB RAM, 64MB graphics RAM (VRAM).

You can also disable 3D acceleration, see the user manual: there is no 3D acceleration for XP guests in VirtualBox 6.x.

p.s. We don't need to see the hardening log unless you have a hardening problem, and we never need to see 4 copies of the VM log! One copy is plenty.

[snowcool776]

Ok mpack, will only try to keep the logs to a minimum!
Trying the XP now without 3D Acceleration and downsized memory to 64MB and will report back results.
Fingers crossed!

[snowcool776]

Unfortunately, it still shows the 8E error, even after doing what you told me to do.
Log files are attached

[scottgus1]

This may not (in my less-than-experienced eyes) be a problem with Virtualbox, but with the guest OS itself.

Unless you are P2V-ing this XP OS (meaning bringing a copy of the XP from Physical PC to Virtual machine), BSODs in the guest OS usually mean something is wrong completely within the guest OS. Something wrong with host settings or Virtualbox would result in Virtualbox itself showing an error or crashing, not a guest BSOD.

If the guest's Virtualbox window is still open and the guest OS is doing something that it normally does on real PCs, such as displaying a BSOD, then the problem is inside the OS and you should troubleshoot directly in the guest OS as if the guest were a real PC and Virtualbox were not involved.

Google XP STOP 0x0000008E and fix inside the XP OS directly.

[snowcool776]

Looks like XP, as I guessed, had to be reinstalled due to GAs being duplicated and causing the BSOD.
I will report back once the installation is complete.

[snowcool776]

AFTER REINSTALLING WINDOWS XP, IT FINALLY WORKED! NO BSOD!!!
Can you mark the thread resolved?

[mpack]

Thanks for reporting back.