and now, it is booting (some other problems are present, like the chkdsk at every boot, but at least it boots !). But first ensure if the Hardware virtualization is turned on in your BIOS. Everything was working fine until one day when i started getting the blue screen. I was working on 64 bit Ubuntu on Windows 10 using VirtualBox machine. I only know that my VAIO was only giving BSOD with the first two only. Solved Well I was dealing with the same problem. I don't know which one was the needed one for me, since I "zero-ed" all of the, both in the CurrentControlSet and in ControlSet2. Since I tried with no success the above two, I've searched around a little bit more and found another hint from another user in another website, mentioning also the following interfaces to be "zero-ed":Īliide, amdide, atapi, cmdide, iastor (may not exists), iastorV, intelide, LSI_SAS, msahci, pciide and viaide HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ \Start ) /videos/searchqvirtualbox+windows+7+64+bit+blue+screen&qpvtvirtualbox+windows+7+64+bit+blue+screen&FORMVDRE the physicial disk is a SATA SSD and a Lenovo x201s laptop. (nobody of you said that the key to "zero" is the Start value. This all started when I added a USB Linksys Wifi dongle to the guest.Your precious information made me able to have my virtualized VAIO notebook reborn.įor further users facing the same problem I have to integrate the information included here with the following keys I had to reset to "zero" value, beside intelide and msahci. I have ran Vbox on this system since i got it 5 years ago and never had any issues. I just dont understand why this is happening now. The guest ran for about 10 minutes then show the BSOD. I lowered the display video memory to 8mb and disabled 2d and 3d accelaration. The host system froze and now blue screen appeared. The first run had the Guest system the display video memory was set to 28mb. I see the windows startup screen and right before I would notmally see the login screen it gives me the blue screen with the. vhd image of the two partitions of the laptops hard drive and saved it to an external hard drive. 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). To recover your files instead of trying to repair the boot step failure, one thing that probably you could do is insert an ISO containing a Windows installation to perform a reinstallation of your OS in the virtual machine (ensure in BIOS that the CD-Rom boots before the HDD), this way your files from the corrupted installation will be kept in. The host PC only shows the bluescreen when I start the guest. I have a Dell Inspiron laptop running 64-bit Windows 7 on 3GB RAM and an Intel Core2 T7200 processor. In the bottom panel of BlueScreenView it is highlighting: I have only been able to attach 2 of the 3 log files and the. I have attached the log files from Vbox and also the minidump. I have re-installed a fresh copy of Windows 7 onto the base system and the same error is occurring. Mint 18.1 Cinnamon crashes when running in VirtualBox with 3D Acceleration Enabled. Windows XP guest virtual machine: (vhd) Gives no display in Normal mode, Ok in safe mode. I just dont understand why it would suddenly do this. Host OS: Windows 10 64 bits PRO RAM: 16GB CPU: i5 8400 GPU: GTX 1060 6GB. If anyone can shed some light onto what is causing the crash it would be much appreciated. I have attached the log files and the minidump. The host system is running Windows 7 Home Premium 64 bit Service Pack 1, 4gb RAM, NVIDIA GeForce 9500.Īll these were loading and running fine until about two days ago when the whole system would blue screen. I also had other guest systems for Windows XP and Windows 7. I have been running the Kali Linux VM image downloaded from the official web site for some time now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |