system_service_exception
system_service_exception
Hi
Trying to run VirtualBox on latest build of Windows 10 (14316) - have installed the test build of virtual box (106359) and it installs and runs fine
I then create a new virtual machine - default settings - and it creates okay
But as soon as I start it - I then get BSOD with system_service_exception error
The WER log for blue screen is below:-
Problem signature
Problem Event Name: BlueScreen
Code: 3b
Parameter 1: c0000096
Parameter 2: ffffa601e01c9890
Parameter 3: ffffa601e124fc70
Parameter 4: 0
OS version: 10_0_14316
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.14316.2.0.0.256.48
Locale ID: 2057
Extra information about the problem
Bucket ID: 0x3B_VMMR0!unknown_function
Anything else I can provide to help fix it please let me know
Thanks
Trying to run VirtualBox on latest build of Windows 10 (14316) - have installed the test build of virtual box (106359) and it installs and runs fine
I then create a new virtual machine - default settings - and it creates okay
But as soon as I start it - I then get BSOD with system_service_exception error
The WER log for blue screen is below:-
Problem signature
Problem Event Name: BlueScreen
Code: 3b
Parameter 1: c0000096
Parameter 2: ffffa601e01c9890
Parameter 3: ffffa601e124fc70
Parameter 4: 0
OS version: 10_0_14316
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.14316.2.0.0.256.48
Locale ID: 2057
Extra information about the problem
Bucket ID: 0x3B_VMMR0!unknown_function
Anything else I can provide to help fix it please let me know
Thanks
Re: system_service_exception
any vbox logs I can find attached
Re: system_service_exception
I also met this bluescreen problem, please help.
Re: system_service_exception
I too get the Blue screen, with W10 14316, and VB 106359.
The VB manager starts OK but a little way into starting a VM the BSOD occurs.
Event log: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000096, 0xffffde8148e1c890, 0xffffde81458cbc70, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\041116-13453-01.dmp. Report Id: c2e4beb3-ff18-458d-890a-cdac899241f9.
However i tried reinstalling, just to see. Everytime I try to install 106359, I get this messagebox:
"
Error renaming connection.
Cannot rename this connection. A connection with the name that specified already exists. Specify a different name.
"
'OK' only.
I have only one VB connection: "VirtualBox Host-only Ethernet adaptor".
Event viewer: "Product: Oracle VM VirtualBox 5.0.17 -- Installation failed."
I wonder if this error eventually triggers the BSOD.
Andy
Playing with fire with all these test builds!
The VB manager starts OK but a little way into starting a VM the BSOD occurs.
Event log: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000096, 0xffffde8148e1c890, 0xffffde81458cbc70, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\041116-13453-01.dmp. Report Id: c2e4beb3-ff18-458d-890a-cdac899241f9.
However i tried reinstalling, just to see. Everytime I try to install 106359, I get this messagebox:
"
Error renaming connection.
Cannot rename this connection. A connection with the name that specified already exists. Specify a different name.
"
'OK' only.
I have only one VB connection: "VirtualBox Host-only Ethernet adaptor".
Event viewer: "Product: Oracle VM VirtualBox 5.0.17 -- Installation failed."
I wonder if this error eventually triggers the BSOD.
Andy
Playing with fire with all these test builds!
Re: system_service_exception
Problem now gone, after removing HyperV (which I had enabled as an alternative when having issues with hardening).
See Ticket #15268.
Looks like a clash between different virtual machine host engines.
Now using VB 5.0.18 without issues.
See Ticket #15268.
Looks like a clash between different virtual machine host engines.
Now using VB 5.0.18 without issues.
-
- Oracle Corporation
- Posts: 2973
- Joined: 19. Dec 2007, 15:45
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Any and all
- Contact:
Re: system_service_exception
This actually looks like a bug in Hyper-V.
When you have Hyper-V enabled on the host, VirtualBox won't be able to use hardware virtualization but should still run 32-bit guest using software virtualization. When you disable Hyper-V, VirtualBox will switch back to using hardware virtualization.
Could you please happen what happens when you run the previously troublemaking VM with Hyper-V disabled on the host *and* hardware virtualization disabled in VirtualBox? Does it still crash or not? (If it crashes, it's our problem, if it doesn't, it's Microsoft's.)
When you have Hyper-V enabled on the host, VirtualBox won't be able to use hardware virtualization but should still run 32-bit guest using software virtualization. When you disable Hyper-V, VirtualBox will switch back to using hardware virtualization.
Could you please happen what happens when you run the previously troublemaking VM with Hyper-V disabled on the host *and* hardware virtualization disabled in VirtualBox? Does it still crash or not? (If it crashes, it's our problem, if it doesn't, it's Microsoft's.)
Re: system_service_exception
sorry can't test now as ended up going back to Hyper-V as never got a response on forum and was in a hurry to get on
Re: system_service_exception
Thank you guys! It was solution for me to disable hyper virtualization. Now vm is running normal.
Re: system_service_exception
Encountering similar problem. Had HyperV activated, then switched off, but problem persists. When running a Ubuntu 14 64bit on Windows 10 Pro, windows crashes with error system_service_error. Any help?
Re: system_service_exception
Same issue - completely disabling HyperV in Windows Features and restarting the computer stopped Virtualbox from causing a BSOD, however now I can't start my previously working Ubuntu64 VM any more - checking with a startup ISO revealed that the machine now believes the host system to be i686, and no longer can see that it is x86-64.
ETA: VT-x/AMD-V seems to still be enabled. Something else must be grabbing it. This all seems to have started after I installed the Android dev components to MS Visual Studio... sigh.
ETA: VT-x/AMD-V seems to still be enabled. Something else must be grabbing it. This all seems to have started after I installed the Android dev components to MS Visual Studio... sigh.
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: system_service_exception
You've already found what grabbing "exclusively" VT-x. The MS-studio uses Hyper-V for the emulation. And Hyper-V doesn't share cooperatively VT-x (aka taking turns).jokergirl wrote:Something else must be grabbing it. This all seems to have started after I installed the Android dev components to MS Visual Studio... sigh.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.