Blog/hull-au
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added a screenshot for the BSOD

Browse Source
This commit is contained in:
brayden 2024-04-25 00:26:07 +08:00
parent 55de50bac7
commit 8645a647c7
Signed by: brayden
GPG Key ID: D73DC8941D3B65BC
2 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
content/blog/install-virtio-drivers-from-windows-recovery.md
View File

@ -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 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 press ahead. In this article, we charge forward and overcome our lack of
preparedness! preparedness!
![Screenshot of INACCESSIBLE_BOOT_DEVICE BSOD](/images/virtio-drivers/bsod.png)
# Enter Windows Recovery # Enter Windows Recovery
Reset the VM a few times while at the Windows loading screen and it'll dump you 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 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 # Mount an ISO Containing Drivers
In this example, I've neglected to install the VirtIO SCSI driver so I'll mount In this example, I've neglected to install the VirtIO SCSI driver so I'll mount

BIN
static/images/virtio-drivers/bsod.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 29 KiB