Opened 8 years ago
Closed 7 years ago
#15780 closed defect (duplicate)
Virtualbox causes SYSTEM SERVICE EXCEPTION on Windows 10
Reported by: | joaogvieira | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.1.2 |
Keywords: | VM Windows 10 | Cc: | joaogvieira@… |
Guest type: | Windows | Host type: | Windows |
Description
I'm trying to start my Windows 7 Virtual Machine on Windows 10 however Im getting the blue screen about System Service Exception and the Windows 10 is being restarted.
Attachments (5)
Change History (16)
by , 8 years ago
by , 8 years ago
Attachment: | VBox.log.2 added |
---|
by , 8 years ago
Attachment: | VBox.log.1 added |
---|
by , 8 years ago
Attachment: | VBox.log.3 added |
---|
by , 8 years ago
Attachment: | VBoxHardening.log added |
---|
follow-up: 2 comment:1 by , 8 years ago
comment:2 by , 8 years ago
follow-up: 4 comment:3 by , 8 years ago
Could you compress it and put it on a server and tell me the URL? Contact me via email at frank _dot_ mehnert _at_ oracle _dot_ com.
follow-up: 5 comment:4 by , 8 years ago
Replying to frank:
Could you compress it and put it on a server and tell me the URL? Contact me via email at frank _dot_ mehnert _at_ oracle _dot_ com.
I'm copying to the server and will send you the link soon. Thanks.
comment:5 by , 8 years ago
Replying to joaogvieira:
Replying to frank:
Could you compress it and put it on a server and tell me the URL? Contact me via email at frank _dot_ mehnert _at_ oracle _dot_ com.
I'm copying to the server and will send you the link soon. Thanks.
Hi, did you get my email? Thanks in advance.
comment:6 by , 8 years ago
For the record, we received the dump and analyzed it. VirtualBox is trying to change the CR4 value but the host crashes try to do so. The reason is most likely that Hyper-V is active. Please try to disable Hyper-V. This seems to be the same problem as described here.
comment:7 by , 8 years ago
I have had this exact problem today.
- VirtualBox 5.1.4 (x64)
- Windows 10 Enterprise LTSB 2016 (1607) 64-bit
I am pretty sure it's Hyper-V.
Virtualbox should check for the presence of Hyper-V (It's been in Windows since 7) and warn the user, in my opinion, because I've never had a hard crash in Windows 10 before and it lost some of my work.
follow-up: 10 comment:8 by , 8 years ago
Same as above:
I have had this exact problem today.
VirtualBox 5.1.4 (x64)
Windows 10 Enterprise LTSB 2016 (1607) 64-bit
Uninstalling Hyper-V solved the problem.
I've never had a hard crash in Windows 10 before and it lost some of my work.
comment:10 by , 8 years ago
Replying to NewPaul:
Same as above:
I have had this exact problem today.
VirtualBox 5.1.4 (x64)
Windows 10 Enterprise LTSB 2016 (1607) 64-bitUninstalling Hyper-V solved the problem.
I've never had a hard crash in Windows 10 before and it lost some of my work.
"Uninstalling Hyper-V solved the problem."
This action solved my problem.
Thanks
jowquim
comment:11 by , 7 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Closing as duplicate of #16801.
Could you provide a kernel dump for the BSOD? See here.