<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blue Screen on</title><link>https://dawning.ca/tags/blue-screen/</link><description>Recent content in Blue Screen on</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © James Snell</copyright><lastBuildDate>Thu, 19 Dec 2019 01:21:00 +0000</lastBuildDate><atom:link href="https://dawning.ca/tags/blue-screen/index.xml" rel="self" type="application/rss+xml"/><item><title>Fix INACCESSIBLE_BOOT_DEVICE with Boot Camp Windows Systems</title><link>https://dawning.ca/posts/fix-inaccessible_boot_device-with-boot-camp-windows-systems/</link><pubDate>Thu, 19 Dec 2019 01:21:00 +0000</pubDate><guid>https://dawning.ca/posts/fix-inaccessible_boot_device-with-boot-camp-windows-systems/</guid><description>
&lt;p>Like any self-respecting computer geek, I like everything. I typically run-up Windows on my Macs by installing it via Boot Camp, and then booting it as a VM. This lets me run everything in parallel, but also go full native mode when needed.&lt;/p>
&lt;p>Recently, I found I couldn&amp;rsquo;t boot my Windows natively any more, though it would still work fine in my VMware Fusion. When booting natively, my Windows install with BSOD on an INACCESSIBLE_BOOT_DEVICE exception. After a bit of googling, I found that this was likely related to storage drivers. I ultimately managed to fix my Windows environment (without a reinstall), here are the steps:&lt;/p></description></item></channel></rss>