Originally, I got quick BSODs, but after using RegEditPE to copy over the System branch from the fresh installation’s registry, it gets to where it shows a mouse pointer, shows a green-blue screen and then crashes, seemingly right before the “Loading personal settings…” pop-up box, which is right before the desktop shows.
Now I want move the old system over, but it crashes during booting, even when choosing Safe Mode. I proved that 32-bit XP can be installed on the newer computer by doing a fresh installation (XP SP2 CD-ROM, no extra drivers). I am trying to move a 32-bit Windows XP Home system from an Intel D875PBZ motherboard (Pentium 4, PATA HDD) to a Gigabyte GA-78LMT-USB3 (AMD, 64-bit, quad core, PATA HDD) without losing any programs/settings. Which crashes XP from transport to another compi I have had AHCI driver, soundcard, lan, change IntelAMD, or even a defect new motherboard, It is one device, which makes this crash. Make a try also with msconfig in comandline, Diagnosestart. When for some reason you really need to transport XP, just disable on the old compi nearly every device in Device ManagerĪnd in Bios, all what is not needed for an emergency boot. and set up a fresh XP, this will run stable. Sometimes F8 helps.įor most people I think, it is not a good idea to tranport a working XP to another compi. I overcome this problem, just using boot via USB or via nvme. When this happens very early in boot process, you get BSOD 7B,īut this can also happen later, I have had the same symptoms as described here on the Baytrail compi. When you want to tranport a working XP from one compi to another, Go to your BIOS and make sure that you are supposed to see what you're supposed to get.Paragon Rescue Kit works good, but only on the same compi later. They build the same computers for efficiency, but they cripple some of their cheaper models because of marketing. On the other hand, HP has been known to tweak the configuration in the BIOS to cripple some cheaper models, on purpose. I don't see any signs that this is a nested VM as mpack suggested. Also known as "won't work".Īs far as the discrepancy between what the CPU can do, and what's reported that the CPU can do.
Many AVAST files were already installed before the crash. All the files in that subdirectory, however, could be accessed from C:\. I entered Windows XP in safe mode twice since the crash and found only the "MyDocuments" subdirectory not showing any files. Attached below is the only log file this web page would allow me to upload. It was my first download using the guest and I did not think using the host at that time would be a problem. I was making some text entries into a notepad-like file in the Windows 10 host during the download when the crash occurred. The box of text that appeared told me to contact you. My Windows XP guest crashed while downloading AVAST anti-virus software.