diff --git a/user/troubleshooting/vm-troubleshooting.md b/user/troubleshooting/vm-troubleshooting.md
index ece7b968..5fbbf2a4 100644
--- a/user/troubleshooting/vm-troubleshooting.md
+++ b/user/troubleshooting/vm-troubleshooting.md
@@ -1,6 +1,6 @@
 ---
 layout: doc
-title: Suspend/Resume Troubleshooting
+title: VM Troubleshooting
 permalink: /doc/vm-troubleshooting/
 redirect_from:
 - /doc/remove-vm-manually/
@@ -10,6 +10,8 @@ redirect_from:
 
 ## VM Kernel troubleshooting ##
 
+This troubleshoot applies to the non-default kernel choice described in the [Managing VM docs](https://www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm). 
+
 In case of problems, you can access the VM console using `qvm-console-dispvm VMNAME` in dom0, then access the GRUB menu.
 You need to call it just after starting the VM (until `GRUB_TIMEOUT` expires); for example, in a separate dom0 terminal window.
 
@@ -19,9 +21,9 @@ You can always set the kernel back to some dom0-provided value to fix a VM kerne
 
 ## Qubes starts, but no VMs load ##
 
-This issue may occur if a dom0 update is interrupted halfway through and/or a hard power off is done without shutting down Qubes, which results in files getting corrupted. 
-In this case, the best fix is to reinstall Qubes and restore your files from a backup. 
-Even if you have not backed up data in a while, you should be able to mount the volumes to pull data from them. 
+First, try to start a particular VM, check any failure message and direct further steps based on that.
+
+This issue has been seen to occur if a dom0 update is interrupted halfway through and/or a hard power off is done without shutting down Qubes, which results in files getting corrupted. 
 
 ## Can not uninstall a VM / “ERROR: VM installed by package manager: template-vm-name”
 
@@ -65,6 +67,7 @@ One solution is to add a dummy interface to allow the package to install correct
 
 ## "Cannot connect to qrexec agent" error ##
 
-If you face this error when starting a VM, it may be due to too little initial memory. 
-A solution is to increase the initial memory from 200MB to 400MB by navigating to VM settings » Advanced » Initial memory. 
+If you face this error when starting a VM, look into the VM logs at `/var/log/xen/console/guest-VMNAME.log`. 
+Common reasons that may be revealed are: too low memory, corrupted files or a VM crash on startup. 
 
+If the error occurs as a result of too little initial memory, increase the initial memory from 200MB to 400MB by navigating to VM settings » Advanced » Initial memory.