Running VirtualBox machine causes Blue Screen of Death on host Windows 7 PC
VirtualBox has now twice caused a BSOD on my host operating system Windows 7. The first time I was running VirtualPC so thought the two Virtual Systems together might have caused the issue, but this time it was just VirtualBox.
I didn't get the error code.
Has anyone had similar problems?
windows-7 virtualbox bsod
edited Dec 6 '13 at 1:51
karel
9,21793138
asked Aug 3 '12 at 17:01
Toby AllenToby Allen
1,54932243
add a comment |
VirtualBox has now twice caused a BSOD on my host operating system Windows 7. The first time I was running VirtualPC so thought the two Virtual Systems together might have caused the issue, but this time it was just VirtualBox.
I didn't get the error code.
Has anyone had similar problems?
windows-7 virtualbox bsod
edited Dec 6 '13 at 1:51
karel
9,21793138
asked Aug 3 '12 at 17:01
Toby AllenToby Allen
1,54932243
This sounds like a bug with Virtual Box have you reported it to Oracle?
– Ramhound
Aug 3 '12 at 17:08
Can you find the BSOD dump files and check for anything related to this event?
– Darius
Aug 3 '12 at 17:14
There is not enough details to give you an accurate answer: what is the Bug Check Code (i.e.: Stop 0X blah blah blah)?
– climenole
Aug 4 '12 at 17:38
add a comment |
VirtualBox has now twice caused a BSOD on my host operating system Windows 7. The first time I was running VirtualPC so thought the two Virtual Systems together might have caused the issue, but this time it was just VirtualBox.
I didn't get the error code.
Has anyone had similar problems?
windows-7 virtualbox bsod
edited Dec 6 '13 at 1:51
karel
9,21793138
asked Aug 3 '12 at 17:01
Toby AllenToby Allen
1,54932243
VirtualBox has now twice caused a BSOD on my host operating system Windows 7. The first time I was running VirtualPC so thought the two Virtual Systems together might have caused the issue, but this time it was just VirtualBox.
I didn't get the error code.
Has anyone had similar problems?
windows-7 virtualbox bsod
windows-7 virtualbox bsod
edited Dec 6 '13 at 1:51
karel
9,21793138
asked Aug 3 '12 at 17:01
Toby AllenToby Allen
1,54932243
edited Dec 6 '13 at 1:51
karel
9,21793138
asked Aug 3 '12 at 17:01
Toby AllenToby Allen
1,54932243
edited Dec 6 '13 at 1:51
karel
9,21793138
edited Dec 6 '13 at 1:51
karel
9,21793138
edited Dec 6 '13 at 1:51
karel
9,21793138
9,21793138
asked Aug 3 '12 at 17:01
Toby AllenToby Allen
1,54932243
asked Aug 3 '12 at 17:01
Toby AllenToby Allen
1,54932243
asked Aug 3 '12 at 17:01
Toby AllenToby Allen
1,54932243
1,54932243
This sounds like a bug with Virtual Box have you reported it to Oracle?
– Ramhound
Aug 3 '12 at 17:08
Can you find the BSOD dump files and check for anything related to this event?
– Darius
Aug 3 '12 at 17:14
There is not enough details to give you an accurate answer: what is the Bug Check Code (i.e.: Stop 0X blah blah blah)?
– climenole
Aug 4 '12 at 17:38
add a comment |
This sounds like a bug with Virtual Box have you reported it to Oracle?
– Ramhound
Aug 3 '12 at 17:08
Can you find the BSOD dump files and check for anything related to this event?
– Darius
Aug 3 '12 at 17:14
There is not enough details to give you an accurate answer: what is the Bug Check Code (i.e.: Stop 0X blah blah blah)?
– climenole
Aug 4 '12 at 17:38
This sounds like a bug with Virtual Box have you reported it to Oracle?
– Ramhound
Aug 3 '12 at 17:08
This sounds like a bug with Virtual Box have you reported it to Oracle?
– Ramhound
Aug 3 '12 at 17:08
Can you find the BSOD dump files and check for anything related to this event?
– Darius
Aug 3 '12 at 17:14
Can you find the BSOD dump files and check for anything related to this event?
– Darius
Aug 3 '12 at 17:14
There is not enough details to give you an accurate answer: what is the Bug Check Code (i.e.: Stop 0X blah blah blah)?
– climenole
Aug 4 '12 at 17:38
There is not enough details to give you an accurate answer: what is the Bug Check Code (i.e.: Stop 0X blah blah blah)?
– climenole
Aug 4 '12 at 17:38
add a comment |
6 Answers
6
active
oldest
votes
What is the configuration of your Win-7 machine? VirtualBox is a huge resource drainer. Even with 4GB RAM and a 3.2 ghz dual-core, it lags when I try to run anything on the host and guest at the same time. Also, check your onboard graphics-memory, and read this manual carefully for anything that might apply to your architecture:
https://www.virtualbox.org/wiki/Technical_documentation
answered Aug 4 '12 at 16:21
Prahlad YeriPrahlad Yeri
6031615
add a comment |
I tried all of the above mentioned answers, none of them worked.
So I found out the Hyper-V in windows 7 and higher (in my case it is windows 10) is the culprit!
I disabled the Hyper-V services as below and the issue is fixed!
Follow the following steps:
Find the "Turn windows features on or off" from control panel (or type windows features in windows search box)
Uncheck the "Hyper-V" feature from the list
edited May 23 '17 at 14:47
captncraig
3172410
answered Oct 23 '16 at 23:47
InkHeartInkHeart
50142
3
+1. Works for me on Windows 10 (winver 1607) and VirtualBox 5.1.26
– honzakuzel1989
Sep 7 '17 at 5:50
3
+1, this saved my life on Windows 10. I am running Docker (that uses Hyper-V) and Oracle VM VirtualBox and they don't fit together well. Is there anywhere we could report this as an issue so that future generations wouldn't have to suffer this pain?
– eddyP23
Sep 27 '17 at 9:12
1
This solution fixed my VirtualBox 5.2 on Windows 10. Thanks
– Strabek
Dec 11 '17 at 14:23
I have the same problem with VBox causing an occasional BSOD, but in my case the Hyper-V is NOT installed (already unchecked in the list of features, like suggested here). So, I don't know what I am supposed to do, in light of the fact that I cannot work without the VBox for the docker machine I need for the current local project run...
– TheCuBeMan
Sep 5 '18 at 12:01
add a comment |
This happens many times, especially when running more than one virtual machine at a time. I.e. two Linux virtual machines, etc.
I looked at the dumps and it's definitely Virtual Box (at least as recent as 4.3.4). I've see it with single as well as multiple Windows 7 VMS also.
Doesn't occur frequently, and I prefer Vbox over VMWare, so I continue to use. I usually just restart and everything is fine.
Also:
In particular, VirtualBox SATA drivers are causing BSOD, so default to IDE.
edited Dec 5 '13 at 23:02
random♦
12.8k84757
answered Dec 5 '13 at 18:52
CampbellusCampbellus
6112
add a comment |
None of the above has worked for me. However, this simple trick allowed me to run the troubled VM:
- Run the machine in headless start mode (Go to start and then choose headless start from the drop-down list)
- After the machine cleans the cache and shows the login screen at the little window of VBox page, click on show machine (the green arrow in the main menu).
Make sure to backup your important files :)
edited Dec 21 '16 at 16:18
Burgi
3,88992543
answered Dec 21 '16 at 15:47
Ayman SabbahAyman Sabbah
111
add a comment |
Another option is to try Hyper-V itself. Search for Hyper-V Manager.
Hyper-V Manager
answered Nov 5 '17 at 18:33
Alejandro G. CarlsteinAlejandro G. Carlstein
1
Could you say why it is better?
– Toto
Nov 5 '17 at 19:48
add a comment |
In my case the other VMs had created a virtual switch on the nic driver.
I went and removed all the non-standard settings on the adapter and let the OS auto-detect it and configure as if it was a new start up. (After disabling Hyper-V and Virtual Box which had been set up natively on the PC.)
Then I was able to fire up vagrant and get things to work. I was using Vagrant 1.9.6 and VBox 5.1.28.
Hope this helps someone else.
answered Dec 8 '17 at 15:31
htm11hhtm11h
1076
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f457281%2frunning-virtualbox-machine-causes-blue-screen-of-death-on-host-windows-7-pc%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
What is the configuration of your Win-7 machine? VirtualBox is a huge resource drainer. Even with 4GB RAM and a 3.2 ghz dual-core, it lags when I try to run anything on the host and guest at the same time. Also, check your onboard graphics-memory, and read this manual carefully for anything that might apply to your architecture:
https://www.virtualbox.org/wiki/Technical_documentation
answered Aug 4 '12 at 16:21
Prahlad YeriPrahlad Yeri
6031615
add a comment |
What is the configuration of your Win-7 machine? VirtualBox is a huge resource drainer. Even with 4GB RAM and a 3.2 ghz dual-core, it lags when I try to run anything on the host and guest at the same time. Also, check your onboard graphics-memory, and read this manual carefully for anything that might apply to your architecture:
https://www.virtualbox.org/wiki/Technical_documentation
answered Aug 4 '12 at 16:21
Prahlad YeriPrahlad Yeri
6031615
add a comment |
What is the configuration of your Win-7 machine? VirtualBox is a huge resource drainer. Even with 4GB RAM and a 3.2 ghz dual-core, it lags when I try to run anything on the host and guest at the same time. Also, check your onboard graphics-memory, and read this manual carefully for anything that might apply to your architecture:
https://www.virtualbox.org/wiki/Technical_documentation
answered Aug 4 '12 at 16:21
Prahlad YeriPrahlad Yeri
6031615
What is the configuration of your Win-7 machine? VirtualBox is a huge resource drainer. Even with 4GB RAM and a 3.2 ghz dual-core, it lags when I try to run anything on the host and guest at the same time. Also, check your onboard graphics-memory, and read this manual carefully for anything that might apply to your architecture:
https://www.virtualbox.org/wiki/Technical_documentation
answered Aug 4 '12 at 16:21
Prahlad YeriPrahlad Yeri
6031615
answered Aug 4 '12 at 16:21
Prahlad YeriPrahlad Yeri
6031615
answered Aug 4 '12 at 16:21
Prahlad YeriPrahlad Yeri
6031615
answered Aug 4 '12 at 16:21
Prahlad YeriPrahlad Yeri
6031615
6031615
add a comment |
add a comment |
I tried all of the above mentioned answers, none of them worked.
So I found out the Hyper-V in windows 7 and higher (in my case it is windows 10) is the culprit!
I disabled the Hyper-V services as below and the issue is fixed!
Follow the following steps:
Find the "Turn windows features on or off" from control panel (or type windows features in windows search box)
Uncheck the "Hyper-V" feature from the list
edited May 23 '17 at 14:47
captncraig
3172410
answered Oct 23 '16 at 23:47
InkHeartInkHeart
50142
3
+1. Works for me on Windows 10 (winver 1607) and VirtualBox 5.1.26
– honzakuzel1989
Sep 7 '17 at 5:50
3
+1, this saved my life on Windows 10. I am running Docker (that uses Hyper-V) and Oracle VM VirtualBox and they don't fit together well. Is there anywhere we could report this as an issue so that future generations wouldn't have to suffer this pain?
– eddyP23
Sep 27 '17 at 9:12
1
This solution fixed my VirtualBox 5.2 on Windows 10. Thanks
– Strabek
Dec 11 '17 at 14:23
I have the same problem with VBox causing an occasional BSOD, but in my case the Hyper-V is NOT installed (already unchecked in the list of features, like suggested here). So, I don't know what I am supposed to do, in light of the fact that I cannot work without the VBox for the docker machine I need for the current local project run...
– TheCuBeMan
Sep 5 '18 at 12:01
add a comment |
I tried all of the above mentioned answers, none of them worked.
So I found out the Hyper-V in windows 7 and higher (in my case it is windows 10) is the culprit!
I disabled the Hyper-V services as below and the issue is fixed!
Follow the following steps:
Find the "Turn windows features on or off" from control panel (or type windows features in windows search box)
Uncheck the "Hyper-V" feature from the list
edited May 23 '17 at 14:47
captncraig
3172410
answered Oct 23 '16 at 23:47
InkHeartInkHeart
50142
3
+1. Works for me on Windows 10 (winver 1607) and VirtualBox 5.1.26
– honzakuzel1989
Sep 7 '17 at 5:50
3
+1, this saved my life on Windows 10. I am running Docker (that uses Hyper-V) and Oracle VM VirtualBox and they don't fit together well. Is there anywhere we could report this as an issue so that future generations wouldn't have to suffer this pain?
– eddyP23
Sep 27 '17 at 9:12
1
This solution fixed my VirtualBox 5.2 on Windows 10. Thanks
– Strabek
Dec 11 '17 at 14:23
I have the same problem with VBox causing an occasional BSOD, but in my case the Hyper-V is NOT installed (already unchecked in the list of features, like suggested here). So, I don't know what I am supposed to do, in light of the fact that I cannot work without the VBox for the docker machine I need for the current local project run...
– TheCuBeMan
Sep 5 '18 at 12:01
add a comment |
I tried all of the above mentioned answers, none of them worked.
So I found out the Hyper-V in windows 7 and higher (in my case it is windows 10) is the culprit!
I disabled the Hyper-V services as below and the issue is fixed!
Follow the following steps:
Find the "Turn windows features on or off" from control panel (or type windows features in windows search box)
Uncheck the "Hyper-V" feature from the list
edited May 23 '17 at 14:47
captncraig
3172410
answered Oct 23 '16 at 23:47
InkHeartInkHeart
50142
I tried all of the above mentioned answers, none of them worked.
So I found out the Hyper-V in windows 7 and higher (in my case it is windows 10) is the culprit!
I disabled the Hyper-V services as below and the issue is fixed!
Follow the following steps:
Find the "Turn windows features on or off" from control panel (or type windows features in windows search box)
Uncheck the "Hyper-V" feature from the list
edited May 23 '17 at 14:47
captncraig
3172410
answered Oct 23 '16 at 23:47
InkHeartInkHeart
50142
edited May 23 '17 at 14:47
captncraig
3172410
edited May 23 '17 at 14:47
captncraig
3172410
edited May 23 '17 at 14:47
captncraig
3172410
3172410
answered Oct 23 '16 at 23:47
InkHeartInkHeart
50142
answered Oct 23 '16 at 23:47
InkHeartInkHeart
50142
answered Oct 23 '16 at 23:47
InkHeartInkHeart
50142
50142
3
+1. Works for me on Windows 10 (winver 1607) and VirtualBox 5.1.26
– honzakuzel1989
Sep 7 '17 at 5:50
3
+1, this saved my life on Windows 10. I am running Docker (that uses Hyper-V) and Oracle VM VirtualBox and they don't fit together well. Is there anywhere we could report this as an issue so that future generations wouldn't have to suffer this pain?
– eddyP23
Sep 27 '17 at 9:12
1
This solution fixed my VirtualBox 5.2 on Windows 10. Thanks
– Strabek
Dec 11 '17 at 14:23
I have the same problem with VBox causing an occasional BSOD, but in my case the Hyper-V is NOT installed (already unchecked in the list of features, like suggested here). So, I don't know what I am supposed to do, in light of the fact that I cannot work without the VBox for the docker machine I need for the current local project run...
– TheCuBeMan
Sep 5 '18 at 12:01
add a comment |
3
+1. Works for me on Windows 10 (winver 1607) and VirtualBox 5.1.26
– honzakuzel1989
Sep 7 '17 at 5:50
3
+1, this saved my life on Windows 10. I am running Docker (that uses Hyper-V) and Oracle VM VirtualBox and they don't fit together well. Is there anywhere we could report this as an issue so that future generations wouldn't have to suffer this pain?
– eddyP23
Sep 27 '17 at 9:12
1
This solution fixed my VirtualBox 5.2 on Windows 10. Thanks
– Strabek
Dec 11 '17 at 14:23
I have the same problem with VBox causing an occasional BSOD, but in my case the Hyper-V is NOT installed (already unchecked in the list of features, like suggested here). So, I don't know what I am supposed to do, in light of the fact that I cannot work without the VBox for the docker machine I need for the current local project run...
– TheCuBeMan
Sep 5 '18 at 12:01
3
3
+1. Works for me on Windows 10 (winver 1607) and VirtualBox 5.1.26
– honzakuzel1989
Sep 7 '17 at 5:50
+1. Works for me on Windows 10 (winver 1607) and VirtualBox 5.1.26
– honzakuzel1989
Sep 7 '17 at 5:50
3
3
+1, this saved my life on Windows 10. I am running Docker (that uses Hyper-V) and Oracle VM VirtualBox and they don't fit together well. Is there anywhere we could report this as an issue so that future generations wouldn't have to suffer this pain?
– eddyP23
Sep 27 '17 at 9:12
+1, this saved my life on Windows 10. I am running Docker (that uses Hyper-V) and Oracle VM VirtualBox and they don't fit together well. Is there anywhere we could report this as an issue so that future generations wouldn't have to suffer this pain?
– eddyP23
Sep 27 '17 at 9:12
1
1
This solution fixed my VirtualBox 5.2 on Windows 10. Thanks
– Strabek
Dec 11 '17 at 14:23
This solution fixed my VirtualBox 5.2 on Windows 10. Thanks
– Strabek
Dec 11 '17 at 14:23
I have the same problem with VBox causing an occasional BSOD, but in my case the Hyper-V is NOT installed (already unchecked in the list of features, like suggested here). So, I don't know what I am supposed to do, in light of the fact that I cannot work without the VBox for the docker machine I need for the current local project run...
– TheCuBeMan
Sep 5 '18 at 12:01
I have the same problem with VBox causing an occasional BSOD, but in my case the Hyper-V is NOT installed (already unchecked in the list of features, like suggested here). So, I don't know what I am supposed to do, in light of the fact that I cannot work without the VBox for the docker machine I need for the current local project run...
– TheCuBeMan
Sep 5 '18 at 12:01
add a comment |
This happens many times, especially when running more than one virtual machine at a time. I.e. two Linux virtual machines, etc.
I looked at the dumps and it's definitely Virtual Box (at least as recent as 4.3.4). I've see it with single as well as multiple Windows 7 VMS also.
Doesn't occur frequently, and I prefer Vbox over VMWare, so I continue to use. I usually just restart and everything is fine.
Also:
In particular, VirtualBox SATA drivers are causing BSOD, so default to IDE.
edited Dec 5 '13 at 23:02
random♦
12.8k84757
answered Dec 5 '13 at 18:52
CampbellusCampbellus
6112
add a comment |
This happens many times, especially when running more than one virtual machine at a time. I.e. two Linux virtual machines, etc.
I looked at the dumps and it's definitely Virtual Box (at least as recent as 4.3.4). I've see it with single as well as multiple Windows 7 VMS also.
Doesn't occur frequently, and I prefer Vbox over VMWare, so I continue to use. I usually just restart and everything is fine.
Also:
In particular, VirtualBox SATA drivers are causing BSOD, so default to IDE.
edited Dec 5 '13 at 23:02
random♦
12.8k84757
answered Dec 5 '13 at 18:52
CampbellusCampbellus
6112
add a comment |
This happens many times, especially when running more than one virtual machine at a time. I.e. two Linux virtual machines, etc.
I looked at the dumps and it's definitely Virtual Box (at least as recent as 4.3.4). I've see it with single as well as multiple Windows 7 VMS also.
Doesn't occur frequently, and I prefer Vbox over VMWare, so I continue to use. I usually just restart and everything is fine.
Also:
In particular, VirtualBox SATA drivers are causing BSOD, so default to IDE.
edited Dec 5 '13 at 23:02
random♦
12.8k84757
answered Dec 5 '13 at 18:52
CampbellusCampbellus
6112
This happens many times, especially when running more than one virtual machine at a time. I.e. two Linux virtual machines, etc.
I looked at the dumps and it's definitely Virtual Box (at least as recent as 4.3.4). I've see it with single as well as multiple Windows 7 VMS also.
Doesn't occur frequently, and I prefer Vbox over VMWare, so I continue to use. I usually just restart and everything is fine.
Also:
In particular, VirtualBox SATA drivers are causing BSOD, so default to IDE.
edited Dec 5 '13 at 23:02
random♦
12.8k84757
answered Dec 5 '13 at 18:52
CampbellusCampbellus
6112
edited Dec 5 '13 at 23:02
random♦
12.8k84757
edited Dec 5 '13 at 23:02
random♦
12.8k84757
edited Dec 5 '13 at 23:02
random♦
12.8k84757
12.8k84757
answered Dec 5 '13 at 18:52
CampbellusCampbellus
6112
answered Dec 5 '13 at 18:52
CampbellusCampbellus
6112
answered Dec 5 '13 at 18:52
CampbellusCampbellus
6112
6112
add a comment |
add a comment |
None of the above has worked for me. However, this simple trick allowed me to run the troubled VM:
- Run the machine in headless start mode (Go to start and then choose headless start from the drop-down list)
- After the machine cleans the cache and shows the login screen at the little window of VBox page, click on show machine (the green arrow in the main menu).
Make sure to backup your important files :)
edited Dec 21 '16 at 16:18
Burgi
3,88992543
answered Dec 21 '16 at 15:47
Ayman SabbahAyman Sabbah
111
add a comment |
None of the above has worked for me. However, this simple trick allowed me to run the troubled VM:
- Run the machine in headless start mode (Go to start and then choose headless start from the drop-down list)
- After the machine cleans the cache and shows the login screen at the little window of VBox page, click on show machine (the green arrow in the main menu).
Make sure to backup your important files :)
edited Dec 21 '16 at 16:18
Burgi
3,88992543
answered Dec 21 '16 at 15:47
Ayman SabbahAyman Sabbah
111
add a comment |
None of the above has worked for me. However, this simple trick allowed me to run the troubled VM:
- Run the machine in headless start mode (Go to start and then choose headless start from the drop-down list)
- After the machine cleans the cache and shows the login screen at the little window of VBox page, click on show machine (the green arrow in the main menu).
Make sure to backup your important files :)
edited Dec 21 '16 at 16:18
Burgi
3,88992543
answered Dec 21 '16 at 15:47
Ayman SabbahAyman Sabbah
111
None of the above has worked for me. However, this simple trick allowed me to run the troubled VM:
- Run the machine in headless start mode (Go to start and then choose headless start from the drop-down list)
- After the machine cleans the cache and shows the login screen at the little window of VBox page, click on show machine (the green arrow in the main menu).
Make sure to backup your important files :)
edited Dec 21 '16 at 16:18
Burgi
3,88992543
answered Dec 21 '16 at 15:47
Ayman SabbahAyman Sabbah
111
edited Dec 21 '16 at 16:18
Burgi
3,88992543
edited Dec 21 '16 at 16:18
Burgi
3,88992543
edited Dec 21 '16 at 16:18
Burgi
3,88992543
3,88992543
answered Dec 21 '16 at 15:47
Ayman SabbahAyman Sabbah
111
answered Dec 21 '16 at 15:47
Ayman SabbahAyman Sabbah
111
answered Dec 21 '16 at 15:47
Ayman SabbahAyman Sabbah
111
111
add a comment |
add a comment |
Another option is to try Hyper-V itself. Search for Hyper-V Manager.
Hyper-V Manager
answered Nov 5 '17 at 18:33
Alejandro G. CarlsteinAlejandro G. Carlstein
1
Could you say why it is better?
– Toto
Nov 5 '17 at 19:48
add a comment |
Another option is to try Hyper-V itself. Search for Hyper-V Manager.
Hyper-V Manager
answered Nov 5 '17 at 18:33
Alejandro G. CarlsteinAlejandro G. Carlstein
1
Could you say why it is better?
– Toto
Nov 5 '17 at 19:48
add a comment |
Another option is to try Hyper-V itself. Search for Hyper-V Manager.
Hyper-V Manager
answered Nov 5 '17 at 18:33
Alejandro G. CarlsteinAlejandro G. Carlstein
1
Another option is to try Hyper-V itself. Search for Hyper-V Manager.
Hyper-V Manager
answered Nov 5 '17 at 18:33
Alejandro G. CarlsteinAlejandro G. Carlstein
1
answered Nov 5 '17 at 18:33
Alejandro G. CarlsteinAlejandro G. Carlstein
1
answered Nov 5 '17 at 18:33
Alejandro G. CarlsteinAlejandro G. Carlstein
1
answered Nov 5 '17 at 18:33
Alejandro G. CarlsteinAlejandro G. Carlstein
1
1
Could you say why it is better?
– Toto
Nov 5 '17 at 19:48
add a comment |
Could you say why it is better?
– Toto
Nov 5 '17 at 19:48
Could you say why it is better?
– Toto
Nov 5 '17 at 19:48
Could you say why it is better?
– Toto
Nov 5 '17 at 19:48
add a comment |
In my case the other VMs had created a virtual switch on the nic driver.
I went and removed all the non-standard settings on the adapter and let the OS auto-detect it and configure as if it was a new start up. (After disabling Hyper-V and Virtual Box which had been set up natively on the PC.)
Then I was able to fire up vagrant and get things to work. I was using Vagrant 1.9.6 and VBox 5.1.28.
Hope this helps someone else.
answered Dec 8 '17 at 15:31
htm11hhtm11h
1076
add a comment |
In my case the other VMs had created a virtual switch on the nic driver.
I went and removed all the non-standard settings on the adapter and let the OS auto-detect it and configure as if it was a new start up. (After disabling Hyper-V and Virtual Box which had been set up natively on the PC.)
Then I was able to fire up vagrant and get things to work. I was using Vagrant 1.9.6 and VBox 5.1.28.
Hope this helps someone else.
answered Dec 8 '17 at 15:31
htm11hhtm11h
1076
add a comment |
In my case the other VMs had created a virtual switch on the nic driver.
I went and removed all the non-standard settings on the adapter and let the OS auto-detect it and configure as if it was a new start up. (After disabling Hyper-V and Virtual Box which had been set up natively on the PC.)
Then I was able to fire up vagrant and get things to work. I was using Vagrant 1.9.6 and VBox 5.1.28.
Hope this helps someone else.
answered Dec 8 '17 at 15:31
htm11hhtm11h
1076
In my case the other VMs had created a virtual switch on the nic driver.
I went and removed all the non-standard settings on the adapter and let the OS auto-detect it and configure as if it was a new start up. (After disabling Hyper-V and Virtual Box which had been set up natively on the PC.)
Then I was able to fire up vagrant and get things to work. I was using Vagrant 1.9.6 and VBox 5.1.28.
Hope this helps someone else.
answered Dec 8 '17 at 15:31
htm11hhtm11h
1076
answered Dec 8 '17 at 15:31
htm11hhtm11h
1076
answered Dec 8 '17 at 15:31
htm11hhtm11h
1076
answered Dec 8 '17 at 15:31
htm11hhtm11h
1076
1076
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f457281%2frunning-virtualbox-machine-causes-blue-screen-of-death-on-host-windows-7-pc%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
This sounds like a bug with Virtual Box have you reported it to Oracle?
– Ramhound
Aug 3 '12 at 17:08
Can you find the BSOD dump files and check for anything related to this event?
– Darius
Aug 3 '12 at 17:14
There is not enough details to give you an accurate answer: what is the Bug Check Code (i.e.: Stop 0X blah blah blah)?
– climenole
Aug 4 '12 at 17:38