WinXP guest BSOD after start from saved state in 5.1.2

[tico-tico]

After I update from 5.0.26 to 5.1.2 my WinXP guest is BSODing just after start from saved state.

[Socratis]

What happens if you discard the saved state first? Generally speaking it's best if you don't upgrade VirtualBox while your VMs have saved states. If you do not want to lose what you have in the saved state, downgrade to 5.0.26, shut down the VM and then upgrade to 5.1.2.

[tico-tico]

Tried again 5 updates later.

I have a WinXP VM with saved running state, it works in v5.0.30.

1. In 5.0.30. Removed snapshot, turned VM off.
2. Installed 5.1.12 on host. Started VM, updated VM Additions, saved state, made snapshot. The same BSOD in guest after restoring the state.

[tico-tico]

After returning to Virtualbox 5.0 the VM won't start at all. It says Failed to load unit 'cpum' (VERR_INVALID_FLAGS).

[boxer01]

Should work now with 5.1.24.

[tico-tico]

What should work? The BSOD is still alive and kicking.

[vbdm_l]

The problem is present in 5.2.4 too. It seems I've found workaround (or solution):

1. Uninstall AMD processor driver (and delete amdppm.sys from system32\drivers)
2. Uninstall AMD Overdrive driver (and delete aoddriver2.sys from system32\drivers)
3. Uninstall AMD Code Analyst and CA's drivers pcore.sys and caprof.sys (and check that this drivers was deleted)
4. Change type of computer from APCI to Standard (so there's only 1 CPU/core for the system)

The problem was solved at this point. So I've tried to revert system to ACPI MP. Is seems that machine works OK now with multiprocessor core.

I think no.4 was not necessary, but it helped to reveal problems with Code Analyst drivers in my case, so it can help to find problems with other drivers.

[vbdm_l]

There was no one BSOD since my last comment.