SYSTEM_SERVICE_EXCEPTION (ntoskrnl) on virtualization software other than Hyper-V

System specs: https://pastebin.com/AGNZgAUT

Hello.

I tried using some virtualization software (VMware, Nox App Player, and Hyper-V) with Intel VT-x enabled, however with everything except Hyper-V, I get a bluescreen for ntoskrnl.exe, under the bug check string “SYSTEM_SERVICE_EXCEPTION” with a stop code of 0x0000003b.

Minidump of one of the crashes: https://files.catbox.moe/ptk8he.dmp

Android Studio Got Blank While Running the App in Emulator which enables Windows Hyper-V Platform

Launch the Android Studio in Windows 10 Enterprise edition

To Run the Emulator Run Apps and Features -> Program Features -> Install Windows Features on -> Check the Windows Feature Hyper-Visor Platform

Run the Emulator -> Emulator is running

After that run the application on that device. It Got Struck and android studio shows black screen I couldnt see any option Its totally block the Entire system . Only way to escape from this , Restart the system

Can anyone solve this issues?

Hyper-V virtual network switch

So this might be a very basic and very stupid question but for the life of me I can not find an explanation on the web anywhere as to how this should work.

I have a very basic Hyper-V setup on my Windows 10 machine. I have two VM’s one is a Mikrotik image and the other is lUbuntu. At this point I’m working on the most basic network configuration. I want the Mikrotik to behave as a router and firewall between the lUbuntu system and the outside.

I have two virtual network switches (VS) setup in Hyper-V. First the default switch (call it Outside) and second an internal switch (call it Inside) I created. The Mikrotik box has two VNIC’s setup that are connected to the two switches. It acts as a DHCP-server on the VNIC which is connected to the Inside VNS.

If I look at my Host system (the Windows 10 I’m running the Hyper-V on) I see the expected two virtual switches as NIC’s one vEthernet (Inside) and one vEthernet (Outside).

The issue I have is that the (Inside) NIC has a APIPA address. When I try to get it to renew the adress using ipconfig /renew the command times out. At the same time the Lubuntu system which has one VNIC which is connected to the (Inside) VS works just fine and gets an IP address from the appropriate pool right away.

So my first question is why does the Host system not behave appropriately with regards to a Hyper-V Virtual switch?

How to solve Event IDs 16945 in the System logs Hyper-V MAC conflicts

After 3 years of running perfectly with Hyper-V I am all of a sudden having network problems with Hyper-V on win 2012 R2. I set up my servers 3 years ago and never had these problem until this week.

About the time I started having problems I started for the first time seeing these events in the logs. Event IDs 16945 in the System logs. “MAC conflict: A port on the virtual switch has the same MAC as one of the underlying team members on Team Nic Microsoft Network Adapter Multiplexor Driver.”

This command shows I have the same MAC address for the first three entries.

get-netadapter | sort macaddress

pNIC2

tNIC1

vNIC1

pNIC1

pNIC1 and pNIC2 are the physical network adapters tNIC1 is the the NIC team of the two physical NICs pNIC1 and pNIC2 in Switch Independent, Dynamic load balancing, standby adapters none. vNIC1 is the virtual NIC of the server.

The servers have one Virtual switch, vSwitch1, connection type External network – Microsoft Network Adapter Driver and Allow management OS to share network adapter. No vlans are used and the only extensions checked is the MS filtering platform.

I have 4 identical servers hardware and software set up this way. Running get-netadapter | sort macaddress on each of the 4 servers shows the exact same thing. The first three adapters have the same MAC address on all 4 servers but the MAC address on the different servers are all different. In other words there are no server to server MAC address conflicts.

Server 1 pNIC1    Intel(R) 82576 Gigabit Dual Port Net...      12 Up           00-25-90-2D-68-1A         1 Gbps tNIC1    Microsoft Network Adapter Multiplexo...      16 Up           00-25-90-2D-68-1A         2 Gbps vNIC1    Hyper-V Virtual Ethernet Adapter #2          19 Up           00-25-90-2D-68-1A        10 Gbps pNIC2    Intel(R) 82576 Gigabit Dual Port N...#2      13 Up           00-25-90-2D-68-1B         1 Gbps  Server 2 pNIC1    Intel(R) 82576 Gigabit Dual Port Net...      12 Up           00-25-90-2C-6A-64         1 Gbps tNIC1    Microsoft Network Adapter Multiplexo...      16 Up           00-25-90-2C-6A-64         2 Gbps vNIC1    Hyper-V Virtual Ethernet Adapter #2          19 Up           00-25-90-2C-6A-64        10 Gbps pNIC2    Intel(R) 82576 Gigabit Dual Port N...#2      13 Up           00-25-90-2C-6A-65         1 Gbps  Server 3 Name     InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed ----     --------------------                    ------- ------       ----------             --------- pNIC2    Intel(R) 82576 Gigabit Dual Port N...#2      13 Up           00-25-90-4D-65-2A         1 Gbps tNIC1    Microsoft Network Adapter Multiplexo...      16 Up           00-25-90-4D-65-2A         2 Gbps vNIC1    Hyper-V Virtual Ethernet Adapter #2          19 Up           00-25-90-4D-65-2A        10 Gbps pNIC1    Intel(R) 82576 Gigabit Dual Port Net...      12 Up           00-25-90-4D-65-2B         1 Gbps  Server 4 Name     InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed ----     --------------------                    ------- ------       ----------             --------- pNIC1    Intel(R) 82576 Gigabit Dual Port Net...      12 Up           00-25-90-4D-40-E6         1 Gbps tNIC1    Microsoft Network Adapter Multiplexo...      16 Up           00-25-90-4D-40-E6         2 Gbps vNIC1    Hyper-V Virtual Ethernet Adapter #2          19 Up           00-25-90-4D-40-E6        10 Gbps pNIC2    Intel(R) 82576 Gigabit Dual Port N...#2      13 Up           00-25-90-4D-40-E7         1 Gbps  I read where it is common and OK to see the same MAC address on one of the vNICs and one of the pNICs, but that it isn't OK for a pNIC to have the same address as the NIC team tNIC1. https://serverfault.com/questions/702570/server-2012-r2-hyper-v-virtual-switch-host-mac-address-conflict-331flr 

What do I need to do to resolve the conflicts and keep them from happening?

I researched how to set these MAC address’s manually and know how to do that including making sure I use MAC address’s outside of the dynamic range set on the vSwitch, but I would like to get some feed on this before making those changes and wondering why after all of these years this just started happening?

Thank you!