[Solved] Blue Screen shutdown
Posted: 7. Dec 2017, 23:40
I am having a BIG problem with VirtualBox. Please read all as it is a history of the problem.
I use VM sparingly when I need to do something with Linux, an old DOS application, or a Win7 Application. It has been several months since I have had to do use either. A few days ago I had the need and launched the VM. No problem on launch. Started one of the OS that I have used several times. I got the blue screen and the message that the "PC had run into a problem .." and started a status dump. I rebooted the machine, got to the desktop with all icons, BUT could not launch ANY application. I got a a dialog box about .Net framework and could not exit the dialog box. Basically froze the machine. The only way to out was to reboot the machine. This behavior occurred every time I rebooted.
I restarted the machine but logged in as a different user with administrative privileges. This user did not have the problem. I removed VM from the system and rebooted andlogged into the machine as the original user. The problem did not re-occur. I installed VM ver 2.0 No problem. Launched VM and it came up with the same clients as I had before. Attempted to launch a client and again got the Blue Screen and a core dump. Rebooting created the same behavior as before. Fixed using the same procedure as above.
Rebooted and logged into as original user and installed VM 5.1. Same problem. Blue Screen and fixed as before. Rebooted, reinstalled VM and attempted installation of new OS. As soon as the client was started I got the Blue SCREEN. Fixed again and rebooted.
Logged into as original user and installed VM 2.2. No problem. Attempted install of new client. Same problem as before. Fixed as before.
Installed Hyper-V (ugh). The Dos, Win7 and Linux clients I was using under VM worked. No problem. I also installed a new client. No problem.
I read the info on HARDENING but this doesn't seem to apply since the clients that run on HYPER-V don't run on VM.
Update: I wrote the above several days ago but did not publish it. I have updated to the FALL Creator Version of Windows 10 and still get the same behavior. In addition, the HYPER-V now kills the use of the network adapter connection (typical Microsoft). Disabling their Virtual Switch Manager and enabling he original adapter cured that.
I would really like to use VM (old one or new one). Any Suggestions??
I use VM sparingly when I need to do something with Linux, an old DOS application, or a Win7 Application. It has been several months since I have had to do use either. A few days ago I had the need and launched the VM. No problem on launch. Started one of the OS that I have used several times. I got the blue screen and the message that the "PC had run into a problem .." and started a status dump. I rebooted the machine, got to the desktop with all icons, BUT could not launch ANY application. I got a a dialog box about .Net framework and could not exit the dialog box. Basically froze the machine. The only way to out was to reboot the machine. This behavior occurred every time I rebooted.
I restarted the machine but logged in as a different user with administrative privileges. This user did not have the problem. I removed VM from the system and rebooted andlogged into the machine as the original user. The problem did not re-occur. I installed VM ver 2.0 No problem. Launched VM and it came up with the same clients as I had before. Attempted to launch a client and again got the Blue Screen and a core dump. Rebooting created the same behavior as before. Fixed using the same procedure as above.
Rebooted and logged into as original user and installed VM 5.1. Same problem. Blue Screen and fixed as before. Rebooted, reinstalled VM and attempted installation of new OS. As soon as the client was started I got the Blue SCREEN. Fixed again and rebooted.
Logged into as original user and installed VM 2.2. No problem. Attempted install of new client. Same problem as before. Fixed as before.
Installed Hyper-V (ugh). The Dos, Win7 and Linux clients I was using under VM worked. No problem. I also installed a new client. No problem.
I read the info on HARDENING but this doesn't seem to apply since the clients that run on HYPER-V don't run on VM.
Update: I wrote the above several days ago but did not publish it. I have updated to the FALL Creator Version of Windows 10 and still get the same behavior. In addition, the HYPER-V now kills the use of the network adapter connection (typical Microsoft). Disabling their Virtual Switch Manager and enabling he original adapter cured that.
I would really like to use VM (old one or new one). Any Suggestions??