Windows 10: Resource Exhaustion (VM issue) on new W10 Install

Can anyone please help me with the following?

Upgraded an 8.1 install to W10 and since have been having issues with virtual memory / resource errors. This normally requires the closure of all apps / progs but this morning the PC shut down as a result.

On checking eventvwr I uncovered the following:





Now as far as I can see the VM settings are fine. This is a reasonably capable desktop running 6GB ram that suffered no such issues under W8.1.

Any ideas appreciated as this is the other half's PC I upgraded for her and it's not gone down well!

Mods: Hope this is in the right place not being a BSOD issue - please move accordingly if not *Smile

:)

 

Windows 10 OEM Key

would the same apply if I used the OEM key on a VM?

For instance If i install W10 and a VM and then later on delete the VM and then install W10 on the PC directly.

 

Windows 10 DHCP decline loop

My new Windows 10 Home install in a VM has started refusing to connect to the Internet. I am using "Bridged Mode" for the network connection. W10 installed from MSDN Iso onto a new Virtual Box hosted
machine

I have Wireshark running on the VM Host.

W10 issues a DHCP request, It is granted one by the router

The DHCP is acknowledged

A number of packet exchanges take place using the IP address

M-SEARCH * HTTP/1.1

Host: 239.255.255.250:1900

ST: uuid:98ebada5-b544-5d4f-8e69-3dcb2c014014

Man: "ssdp:discover"

MX: 3

None of these are responded to

W10 issues a DCHP decline and reverts to a 168.254.x.x address

The whole Cycle repeats forever getting a different IP address each time from my router

When I switch the VM to NAT mode then it connects correctly.

This started happening after I connected my host laptop to a different network which changed the DHCP address range.

If relevant I am using Avast AV on my W10 guest but it makes no difference if I disable it.

 

No word on this?

Happened again today and I noticed at the time there was >3GB physical Ram still available!

Something screwy happening...

 

According to your screenshot, it looks like you had at least 200GB of virtual memory allocated, which is quite a lot. You might want to do a clean install.

 

200 Gb? Where is that showing?

I've tweaked the VM settings but still seeing issues. Just caught it mid slow down and discovered this:

https://i.imgur.com/weucjC7.jpg

That process running up > 2.5gb memory is Facebook running in Edge. Is this the cause, and if so why? Just keeps climbing until things crash.