Using a new installation of 4.0.4 for a week now, fully updated, after a crash and self-restart left the system unbootable. The same crash and self-restart has occured three times since, fortunately without damage to the OS and I have been able to recover the openoffice documents, which were open at the time of the crash. No idea if the cause is hardware or software related. There may be a log file somewhere to offer some clues, but that’s beyond my level of knowledge. The most recent restart occured yesterday. Fortunately the system restarted back to square one and I just needed to restore the open office documents, which were open at time of crash.
When the crashes/restarts have happened, I have had a number of VMs running - typically let’s say three open office documents, Thunderbird, Firefox (dedicated to ProtonMail), two Firefoxes (one in untrusted VM and one in personal VM), a Keepass VM, and a Mullvad VM. In one of the firefox instances I have sometimes had two or three youtube videos stacked, watching one and the other one or two tabbed and waiting to be watched. So I’m not sure if I’m placing too much demand on the Qubes installation memorywise, if there is an update-related problem or if this is hardware related.
I always update my VMs the same day, that I see available updates. All VMs are debian based except for the as-installed dom0 and the various Sys VMs. The desktop system has 16GB ram, Intel i5-9600k cpu, Asus Prime B365M-A mobo, a Samsung 970 EVOPlus ssd plus 2TB drive and the usb keyboard and mouse are connected through a Tripp-Lite PS/2 to usb connector to the mobo, so I’m using the stock disposable sys-usb VM. I think, that the hardware should be sufficient to handle the load I’m putting on it, but cannot say for sure. Any ideas on how I can proceed to sort this out? Many thanks