![virtualbox windows 7 64 bit blue screen virtualbox windows 7 64 bit blue screen](https://i.ytimg.com/vi/uZyShJdAud8/maxresdefault.jpg)
since Windows XP is 32-bit only, it isn’t necessarily required. After (seemingly) successful installation, on first (and each) boot BSOD with 0x0000007B occurs, which indicates that Windows is not seeing the disk hardware it was installed on. As can be seen above, I have had no trouble of this kind with Windows NT 4.0, nor with 3.11 Windows for Workgroups. I tried to install Windows XP x86 in Oracle VirtualBox v6.0.14.
![virtualbox windows 7 64 bit blue screen virtualbox windows 7 64 bit blue screen](https://i.ytimg.com/vi/9-ZGT6T65VA/maxresdefault.jpg)
![virtualbox windows 7 64 bit blue screen virtualbox windows 7 64 bit blue screen](https://blog.dummzeuch.de/wp-content/uploads/2017/08/Virtualbox-settings-Win81-64.png)
I still have the same boot problem with 64 or 32 MB RAM. I should mention that I have VirtualBox set as Windows 3.x and have left all settings as default for this system except for experimenting with 128 MB of RAM. I have attached a screenshot of this blue screen to this message. My host is a Mandriva 2010.2 linux 64-bit machine on an Asus M4A78-E motherboard with an AMD Phenom 9600 Quad-core processor and 4 gigs of ram and the version of VirtualBox installed is 4.0.4 PUEL (I need USB on most of my VMs). I obtained this from a very reputable site, and their other Windows VDI's have been faultless. Save the far left tabs log, zip the log file, and post the zip file, using the forums Upload Attachment tab. Please right-click the VM in the main Virtualbox windows VM list, choose Show Log. My copy of NT 3.51 was not manually installed the usual way but rather was downloaded as a ready-made VDI virtual file. If not possible, close the Virtualbox window for the VM with the Power Off option set. The file ntoskrnl.exe is also mentioned 29 times. The words include STOP, INACCESSIBLE_BOOT_DEVICE, and "Restart and set the recovery options in the system control panel". When it comes to trying to start Windows NT 3.51, however, it fails every time with a boot-time blue screen full of numbers and letters and some words. 1 Low on RAM or computer resources It is the first thing you need to check when you get the Blue Screen error after running the VirtualBox. When you are done highlight 'offline hive' and click 'File' 'Unload Hive'. Select 'offline hive' and now you will be able to modify your registry keys as explained above. Enter a placeholder name once prompted, like 'offline hive'. I am running VirtualBox 6.1.24 on Windows 10 Pro 64-Bit and have managed to successfully set up the following guests : Windows 2.0, 3.0, 3.1, 3.11, 95B, 95C, 98SE, ME, NT 4.0, 2000, XP Pro, Vista Ultimate, 7, and 8.1. Navigate to WindowsSystem32config and load 'SYSTEM'. Hopefully there will be a fix because I would like to use the VirtualBox Guest Additions that I don't know how to install on a Live CD.Screenshot 115819.png (47.15 KiB) Viewed 5217 timesI posted about this topic earlier (in a post about two related topics) but I thought I could make it clearer by giving it its own title. I am fully able to boot the ReactOS 0.4.4 Live CD, maybe because the Live CD already has an hive that works? Not sure if this is related with VirtualBox or maybe with the fact my CPU doesn't support hardware virtualization? When I first boot ReactOS it works and displays the OOBE app, but when booting a second time it fails loading the hive. I suppose that after the first boot of ReactOS, the hive gets somehow corrupted. But after the OOBE, instead of a BSOD, the bootloader displays the message: Importing binary hive failed! I installed ReactOS again on a new harddrive.When I run ReactOS in debug mode and with the COM port enabled I saw that an operation with the hive has failed (it checked whetever some numbers were what ReactOS expected), then it did an int3 software breakpoint and went into a kernel debugger. The first time I installed ReactOS on the hard disk, then when booting the hard disk I got the graphical OOBE wizard (where I set the time, set the name and password of accounts. Im using Windows 7 圆4 (have also tried Vista 圆4) as my host, with XP Professional SP3 (x86) as my guest OS. I used the ReactOS 0.4.5 Boot CD on VirtualBox 4.x.x and 5.1.22 and I get exactly the same thing stated in this thread.