Starting Windows 10 VM reboots entire system.

[kalfun]

I'm new to unraid and I followed this video by Spaceinvader One. I have the bare metal Windows 10 set up, and I have the VM portion set up as well (correctly, I hope). But every time I start the VM, the entire system reboots.

 

Specs:

OS: Unraid 6.6.6

CPU: Threadripper 1950x stock clocks (3.4GHz)

Motherboard: ASRock x399 Taichi

Cooling: Custom Watercooled loop

GPU: 1x Asus GTX 1080ti, 1x EVGA GTX 1070ti

RAM: 32GB

PSU: EVGA 850W

 

I posted in Reddit yesterday, and I figured I'll post here too. Someone asked me to run this command on putty and start the VM after:

tail -f /var/log/syslog

And I got the following: 

Jan 17 12:43:11 tower dnsmasq[31396]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify
Jan 17 12:43:11 tower dnsmasq-dhcp[31396]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
Jan 17 12:43:11 tower dnsmasq-dhcp[31396]: DHCP, sockets bound exclusively to interface virbr0
Jan 17 12:43:11 tower dnsmasq[31396]: reading /etc/resolv.conf
Jan 17 12:43:11 tower dnsmasq[31396]: using nameserver 192.168.1.1#53
Jan 17 12:43:11 tower kernel: virbr0: port 1(virbr0-nic) entered disabled state
Jan 17 12:43:11 tower dnsmasq[31396]: read /etc/hosts - 2 addresses
Jan 17 12:43:11 tower dnsmasq[31396]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jan 17 12:43:11 tower dnsmasq-dhcp[31396]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jan 17 12:43:24 tower sshd[32034]: Accepted none for root from 192.168.1.126 port 58248 ssh2
Jan 17 12:44:26 tower kernel: vfio-pci 0000:09:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Jan 17 12:44:26 tower kernel: br0: port 2(vnet0) entered blocking state
Jan 17 12:44:26 tower kernel: br0: port 2(vnet0) entered disabled state
Jan 17 12:44:26 tower kernel: device vnet0 entered promiscuous mode
Jan 17 12:44:26 tower kernel: br0: port 2(vnet0) entered blocking state
Jan 17 12:44:26 tower kernel: br0: port 2(vnet0) entered forwarding state
Jan 17 12:44:28 tower avahi-daemon[5176]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe34:84ad.
Jan 17 12:44:28 tower avahi-daemon[5176]: New relevant interface vnet0.IPv6 for mDNS.
Jan 17 12:44:28 tower avahi-daemon[5176]: Registering new address record for fe80::fc54:ff:fe34:84ad on vnet0.*.
Jan 17 12:44:29 tower kernel: vfio-pci 0000:09:00.0: enabling device (0000 -> 0003)
Jan 17 12:44:29 tower kernel: vfio_ecap_init: 0000:09:00.0 hiding ecap 0x19@0x900
Jan 17 12:44:29 tower kernel: vfio-pci 0000:0b:00.3: enabling device (0000 -> 0002)
Jan 17 12:44:29 tower kernel: vfio_ecap_init: 0000:08:00.0 hiding ecap 0x19@0x168
Jan 17 12:44:29 tower kernel: vfio_ecap_init: 0000:08:00.0 hiding ecap 0x1e@0x190
Jan 17 12:44:29 tower kernel: vfio-pci 0000:0a:00.3: enabling device (0000 -> 0002)
Jan 17 12:44:29 tower kernel: vfio-pci 0000:43:00.3: enabling device (0000 -> 0002)

Someone else suggested it could be my PSU not providing enough power.

 

Any ideas before I go out and buy a new PSU?

Edited January 17, 2019 by kalfun

[trurl]

Not clear from your description. Is that the output you had when it crashed? The point of tailing the syslog is to get the last thing that happens.