I just setup a new proxmox configuration and I am having issues with Windows Server 2019 stability randomly. Proxmox 7.3-4 and Windows Server 2019 Standard version 1809 with virtio 0.1.229.
I gave the system 4 cores on a 7950x with 16 gigs of ram and 300 gigs on nvme.
When I first set it up and tried to read a bunch of data over the network it just randomly restarted a few times (event 41 kernel-power).
I read somewhere that it can have to do with virtual memory on the OS when installing updates, so I figured why not try and increase it and I provided 16 gigs and I guess I had 1 more update to install so I did that. I first noticed Explorer.exe crashing when I tried right clicking on recycle bin to empty it out, and the screen would flash and the right click menu would disappear. I rebooted the vm and it went away. I ran memtest64 for a few hours to max out memory and see if anything was buggy in the vm, and it worked fine with no errors so I turned it off and let it sit assuming the problem was solved.
After walking away for a short time later I came back and my RDP was disconnected, and when I went to the console VNC I could see the mouse moving remotely but it was not responding. I rebooted VM and checked and Explorer.exe was crashed over and over until I restarted throw PVE web. I can't imagine that for any reason the vm started using a whole bunch of memory all the sudden to go over the limit during this time. Basically an idling computer.
I have run windows 10 a whole bunch on PVE but this is my first time virtualizing 2019 to try and implement into production. I have not ever had a problem like this before and I am wondering if there is some dependency I missed or something? I feel like 16 gigs of ram was overkill for a server that won't really do much but handle some quickbooks connections, but I could allow it to balloon higher if that is the issue for some reason?
Thanks!
I gave the system 4 cores on a 7950x with 16 gigs of ram and 300 gigs on nvme.
When I first set it up and tried to read a bunch of data over the network it just randomly restarted a few times (event 41 kernel-power).
I read somewhere that it can have to do with virtual memory on the OS when installing updates, so I figured why not try and increase it and I provided 16 gigs and I guess I had 1 more update to install so I did that. I first noticed Explorer.exe crashing when I tried right clicking on recycle bin to empty it out, and the screen would flash and the right click menu would disappear. I rebooted the vm and it went away. I ran memtest64 for a few hours to max out memory and see if anything was buggy in the vm, and it worked fine with no errors so I turned it off and let it sit assuming the problem was solved.
After walking away for a short time later I came back and my RDP was disconnected, and when I went to the console VNC I could see the mouse moving remotely but it was not responding. I rebooted VM and checked and Explorer.exe was crashed over and over until I restarted throw PVE web. I can't imagine that for any reason the vm started using a whole bunch of memory all the sudden to go over the limit during this time. Basically an idling computer.
I have run windows 10 a whole bunch on PVE but this is my first time virtualizing 2019 to try and implement into production. I have not ever had a problem like this before and I am wondering if there is some dependency I missed or something? I feel like 16 gigs of ram was overkill for a server that won't really do much but handle some quickbooks connections, but I could allow it to balloon higher if that is the issue for some reason?
Thanks!
Attachments
Last edited: