I have a couple of Windows 10 VMs setup to run on my Windows 10 host in Virtual Box.
Since this morning each of them will go to the windows loading screen, then either BSOD with a "KERNEL SECURITY" error or it'll resize and go to the screen capture I have attached. Once out of every few attempts it will log in but the performance is incredibly slow. Yesterday they would launch and work without a problem.
Hyper-V is disabled, I turned off 3D Acceleration, 4 processors are being used. Any ideas? Only change between yesterday and today is I installed a VPN last night as part of my continued layered security plan. I have tried launching with the VPN on and off but I do not believe it is impacting the VMs
I have also attached the log from the most recent run of this VM
Windows 10 VMs Crashing and Poor Performance
Windows 10 VMs Crashing and Poor Performance
- Attachments
-
- Machine-2020-05-18-11-12-10.zip
- (31.72 KiB) Downloaded 5 times
-
- Broken VM.JPG (65.22 KiB) Viewed 1001 times
Last edited by CVice on 18. May 2020, 18:39, edited 1 time in total.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Windows 10 VMs Crashing and Poor Performance
I don't know what you did to it, but the log provided is garbage - unreadable. Please just zip and attach the log, we don't need you to process it for us in any other way. In particular we don't need you to turn it into a PDF.
Re: Windows 10 VMs Crashing and Poor Performance
My bad - I updated the zip file so now it just contains the .logmpack wrote:I don't know what you did to it, but the log provided is garbage - unreadable. Please just zip and attach the log, we don't need you to process it for us in any other way. In particular we don't need you to turn it into a PDF.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Windows 10 VMs Crashing and Poor Performance
You have allocated 100% of available cores to the VM, leaving none for the host. Trying reducing it to 2 cores.
Also, you have Hyper-v enabled. Most likely you need to disable this to make VirtualBox happy, if you leave it enabled then VirtualBox performance will be glacial.
It may also be worth enabling 3D acceleration: it should give a nice experience. Update the Guest Additions too.
Also, you have Hyper-v enabled. Most likely you need to disable this to make VirtualBox happy, if you leave it enabled then VirtualBox performance will be glacial.
Related FAQ (especially posts #2 and beyond): FAQ: I have a 64bit host, but can't install 64bit guests.00:00:02.100667 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:02.143389 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
It may also be worth enabling 3D acceleration: it should give a nice experience. Update the Guest Additions too.
Re: Windows 10 VMs Crashing and Poor Performance
I usually run 3D Acceleration but I disabled to try to get this machine to launch. I have turned off HyperV in my windows features and restarted multiple times so Im not sure why it thinks it is enabled.mpack wrote:You have allocated 100% of available cores to the VM, leaving none for the host. Trying reducing it to 2 cores.
Also, you have Hyper-v enabled. Most likely you need to disable this to make VirtualBox happy, if you leave it enabled then VirtualBox performance will be glacial.Related FAQ (especially posts #2 and beyond): .00:00:02.100667 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:02.143389 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
It may also be worth enabling 3D acceleration: it should give a nice experience. Update the Guest Additions too.
I am reading over the linked document now. Thanks for the help so far.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 10 VMs Crashing and Poor Performance
Center on the 'device guard' and 'Core Isolation Details' tests, and the bcdedit command in the second post in the tutorial.