#5950 closed defect (fixed)
Windows Guest - changed number of processors - crashes at boot
| Reported by: | Rich | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 3.1.2 |
| Keywords: | windows guest processors boot crash | Cc: | |
| Guest type: | Windows | Host type: | Linux |
Description
Hi.
I run a Windows XP Pro guest in a Linux host with VB 3.1.2. Recently I've begun to have regular crashes everytime the guest boots. Once past the Windows splash screen I get a blue screen of death and the Windows reboots, ad infinitum. If I shut down the Vbox during the boot process when restarted Windows offers me the choice to boot at last good configuration. This works until I try to shut down. Shutting down brings me to a reboot and the process starts all over again.
A colleague has suggested that the problem is that I recently tried increasing the number of processors used by the XP guest to more than 1 in the Vbox settings. He remembers reading a post in the forums that explains this is a big mistake and that to fix this a couple of DLLs have to be replaced in the XP guest.
I've spent some time searching the forums and have found related topics but nothing that covers this explicitly. Does anyone remember a "bug" resolution or a forum post that deals with this problem ? Thanks, Rich
Attachments (1)
Change History (7)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Here's the relevant log file. I started the XP guest. Windows offered me a pre-boot menu where I selected "Use last good configuration." XP booted correctly. I requested XP to shut down. XP didn't shut down but rebooted.
At this point if left alone XP will boot until a blue screen and then reboot again, caught in a loop. By requesting the Vbox window to power off the XP while it is booting up this leads to XP offering the above listed pre-boot menu when next booted. This is the only way past the blue screen & reboot loop that I have found.
comment:3 by , 15 years ago
Hello. I've solved the problem by getting some helpful info from a forum moderator. This issue can be closed for me. Thanks, Rich
Your VBox.log file, preferably when the guest crashed, is missing.