diff --git a/content/blog/install-virtio-drivers-from-windows-recovery.md b/content/blog/install-virtio-drivers-from-windows-recovery.md
index c25a893..0209869 100644
--- a/content/blog/install-virtio-drivers-from-windows-recovery.md
+++ b/content/blog/install-virtio-drivers-from-windows-recovery.md
@@ -11,11 +11,12 @@ all use VMware PVSCSI, but this VM was an older build still using LSI SAS.
 Now staring at the `INACCESSIBLE_BOOT_DEVICE` BSOD, your options are abort or
 press ahead. In this article, we charge forward and overcome our lack of
 preparedness!
+![Screenshot of INACCESSIBLE_BOOT_DEVICE BSOD](/images/virtio-drivers/bsod.png)
 
 # Enter Windows Recovery
 Reset the VM a few times while at the Windows loading screen and it'll dump you
 into the recovery environment. From here you can perform an advanced repair and
-summon a command prompt.
+summon a command prompt. It typically takes 2 failed boots to trigger recovery.
 
 # Mount an ISO Containing Drivers
 In this example, I've neglected to install the VirtIO SCSI driver so I'll mount
diff --git a/static/images/virtio-drivers/bsod.png b/static/images/virtio-drivers/bsod.png
new file mode 100644
index 0000000..41ba98a
Binary files /dev/null and b/static/images/virtio-drivers/bsod.png differ