XP guest BSOD and won't boot after trying to install Avira

[doveman]

I've just done a fresh install of XP (using a custom-made Post-SP3 nlited with Driverpacks ISO) which seemed fine, but when I tried to install Avira Free it BSOD with Driver_IRQL_NOT_LESS_OR_EQUAL, STOP D1 (7C90FE77, 0A, 08, 7C90FE77).

The Vbox (which is running on a Win7 x64 host with 8GB) is set to 768MB, 2 CPU, 128MB VRAM, 2D & 3D acceleration, RDP enabled and Guest Additions (including Direct3D, installed from Safe Mode) are installed.

Now the guest won't even boot and is just showing the animated boot screen.

[Perryg]

This doesn't seem to be an issue for VirtualBox, but rather Microsoft or Avira or whom ever made the nlite package.
You might be able to get it back if you can boot in safe mode and uses the Windows system restore to point in time before you installed Avira.

[doveman]

Well if Vbox can't cope with Windows it's not much use to me! I'm not sure what stage it was at when it BSOD, but Avira certainly hadn't got very far into the install.

Anyway, I've got another nlited XP guest which is working with both Avira and Outlook Security, but it was only installed with single processor ACPI so I had to do a fresh install to get the multi-processor ACPI installed, so I know there's no particular conflict between nlited XP and Avira. I've also got this combination installed on a real multi-processor PC with no problems, so the multi-processor HAL isn't the issue either, so the only thing I can think of is Vbox.

I've tried booting into Safe Mode and uninstalling Guest Additions and unticking 3D Acceleration, but then I just get "PAGE_FAULT_IN_NONPAGED_AREA" STOP 50 (8FE9AB48, 0, 806E787B, 0) when booting. I'll try the snapshot I made before trying to install Avira and also try it on another host to see if it makes any difference.

[Perryg]

Well if Vbox can't cope with Windows it's not much use to me!

No one said that VirtualBox can't cope with Windows. What I said was the issue you are having does not appear to be related to VirtualBox.
If you want to run a custom version of Windows you must be able to handle the issues that arise from doing so.

[doveman]

You said "this does not appear to be an issue with Virtualbox, but rather Microsoft" implying that it's was their fault this isn't working (or Avira's, or mine for using nlite).

Anyway, I've explained why it does in fact appear to be an issue with Virtualbox (i.e. this problem doesn't manifest when doing the same thing on a real box).

[mpack]

Doesn't matter. We only support official Windows distros here. Since we don't know what went into (or got left out of) an nLited version we can't support it even if we wanted to.

Show this problem happening with an official Windows version, and then we can talk... though you should IMHO start by talking to Avira I would think, since you seem to be saying that the issue is confined to them.

[doveman]

Fair enough.

I don't think it's reasonable to believe that Avira might be incompatible with XP running the multiprocessor HAL (which must be the most commonly used these days) though and I've had no problems with Avira in an nlited single processor HAL-XP (or an nlited multi-processor HAL-XP on real hardware) so the issue in fact seems confined to Virtualbox.

[vbox4me2]

Most common streaming mistakes,
usb drivers
nvidia drivers
include auto detect for hardware that isn't there but gets installed anyway
anti virus stuff while windows is still busy determining whats there (too early)
wrong sata drivers

[doveman]

Maybe, but irrelevant as my single-processor HAL XP installed from my nlited ISO is working fine, so clearly there's nothing wrong with it or anything missing that Vbox needs.

[Perryg]

It's not so much what VirtualBox needs as it is what the virus software is trying to do with the drivers. BSOD usually comes from software trying to attach to protected memory (memory that the system is using for something else) or a driver issue.
Some do not play well in a virtual environment. Its the same with all of hypervisors. Some of the companies have gone so far as to create an additional one just for virtual environments. Now add to that the custom built Windows and there is no way that anyone could track this down.
If one causes issues then try a different one. Microsoft Security Essentials works in a Windows guest as does AVG.