Opened 8 years ago
Closed 8 years ago
#16495 closed defect (worksforme)
VirtualBox causes BSOD after installing visual studio 2015
| Reported by: | Leossl | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.14 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description
My system: Windows 10 Pro 64 Bit + Visual Studio 2012 I have installed Virtualbox(last version) and everything was fine. Everything worked good. I decided to install Visual Studio 2015 Enterprise 64 bit. After that, VirtualBox causes BSOD. Only Virtualbox presented problem. The problem was so critical that I had to switch to Hyper-V. Please, I need VirtualBox.
Attachments (4)
Change History (11)
by , 8 years ago
| Attachment: | CapturarVB.JPG added |
|---|
by , 8 years ago
| Attachment: | CapturarVB2.JPG added |
|---|
comment:1 by , 8 years ago
You need to disable Hyper-V, remove it completely. They don't like each other. Hyper-V permanently takes over VT-x and doesn't let anyone else use it.
PS. Your first 3 screenshots are exactly the same...
comment:2 by , 8 years ago
When I had this problem I did not use Hyper-V, but it already comes installed in Windows. I had the problem the very moment I installed the VS2015. I think it modified something or updated the windows. This change made VirtualBox stop working.
Sorry for the repeated pictures
comment:3 by , 8 years ago
Previous System Working: Windows 10 Pro 64 + VS2012 + Hyper-V (inactive) + VirtualBox (Active)
System Not Working: Windows 10 Pro 64 + VS2015 + Hyper-V (inactive) + VirtualBox (Active)
one month later: Atual System Working: Windows 10 Pro 64 + VS2015 + Hyper-V (active)
comment:4 by , 8 years ago
Hi. It has been exactly the same to me. After installing Visual Studio 2015, a BSOD occurs when trying to open the machine from VirtualBox. ALL my work is contained in that machine. I need help as soon as possible !!! Grateful in advance for the help they can offer me.
My current OS is W10 Professional 64 bit. 8GB RAM. + VS2015 + Hyper-V (inactive) + VirtualBox 5.1.14 r112924
comment:5 by , 8 years ago
Solved. It was enough to disable Hyper-V. The following command in Power Shell (with elevated permissions) allows you to do it with ease.
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V-All
Thank you so much Socratis!!!.
comment:6 by , 8 years ago
Yes, I've trying to tell it to Leossi that opened the bug, but I'm not sure if he tried it or not. VS2015 (re-)activates Hyper-V. You got to make absolutely sure that it is not enabled, and you have to (sometimes) cold boot your computer.
comment:7 by , 8 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Please reopen if still relevant.
BSOD Report 1