Ask the Community
Groups
Image-based Bare Metal restore - Stop code 7B after driver injection was successful - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>After the dissimilar image-based bare metal restore process has completed, which may have involved driver injection, the system still blue screens (BSOD) with the stop code 7B.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h3 data-id="purpose">Purpose</h3> <p> Correct stop code 7B after dissimilar restore with driver injection was performed</p> <h3 data-id="applies-to">Applies To</h3> <p> Windows systems</p> <h3 data-id="symptoms-description">Symptoms / Description</h3> <p>After the dissimilar image-based bare metal restore process has completed, which may have involved driver injection, the system still blue screens (BSOD) with the stop code 7B.</p> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p></p> <h3 data-id="resolution-workaround-execution-process">Resolution / Workaround / Execution Process</h3> 1) Make sure you have injected the correct driver for the version of Windows restored to disk. For example, if you are restoring a Windows 2008 64-bit client using the BareMetal boot media, be sure you are providing the proper Windows 2008 64-bit storage controller driver.<br><img alt="User-added image" src="https://us.v-cdn.net/6032361/uploads/migrated/FO66NHHGWUWW/eid-ka03r0000015ahm-feoid-00n40000003czqx-refid-0em40000000mcaw." class="embedImage-img importedEmbed-img"></img><br>You may need to put the driver on a USB memory stick or Map Network Drive in order to access the driver. Afterward, you may Verify Compatibility and Inject the driver.<br><img alt="User-added image" src="https://us.v-cdn.net/6032361/uploads/migrated/R5NJ116PMADA/eid-ka03r0000015ahm-feoid-00n40000003czqx-refid-0em40000000mcab." class="embedImage-img importedEmbed-img"></img><br> 2) If step #1 did not resolve the issue alone, then, at the Bare Metal restore screen when booted to the Bare Metal disc, open a new command prompt and run:<br> regedit<br><img alt="User-added image" src="https://us.v-cdn.net/6032361/uploads/migrated/WE07Y67CRCPH/eid-ka03r0000015ahm-feoid-00n40000003czqx-refid-0em40000000mcag." class="embedImage-img importedEmbed-img"></img><br>In the registry editor (regedit), select HKEY_LOCAL_MACHINE\SYSTEM, then go to File->Load Hive. Navigate so that you load C:\Windows\System32\config\SYSTEM. Provide a key name of UNITRENDS. Then navigate to HKLM\UNITRENDS\ControlSet001\Services. There will be a service for your driver, such as mraid35x. Go into the key and look at the key Start. If Data is 4, set it to 0.<br><img alt="User-added image" src="https://us.v-cdn.net/6032361/uploads/migrated/VUEI41HZNR62/eid-ka03r0000015ahm-feoid-00n40000003czqx-refid-0em40000000mcal." class="embedImage-img importedEmbed-img"></img><ol><li>In the Registry Editor, select <span style="font-size: small;">HKEY_LOCAL_MACHINE.</span> </li> <li>Select <strong>File</strong> > <strong>Load Hive</strong>.</li> <li>Navigate to the drive on which Windows is installed (usually C:\).</li> <li>Open the file named SYSTEM located at Windows/system32/config.</li> <li>Name the file as P2V, when prompted.</li> <li>Navigate to <span style="font-size: small;">HKEY_LOCAL_MACHINE\P2V\ControlSet001\services\LSI_SAS.</span> </li> <li>Right-click the <strong>Start</strong> key and click <strong>Modify</strong>.</li> <li>Set the Value data to <span style="font-size: small;">REG_DWORD 0.</span> </li> <li>Close the Registry Editor.</li> <li>Restart the virtual machine.</li> </ol> Third-Party Sources<br><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Fwindows%2Fembedded%2Fms940849%28v%3Dwinembedded.5%29">https://docs.microsoft.com/en-us/previous-versions/windows/embedded/ms940849(v=winembedded.5)</a><br><br><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkb.vmware.com%2Fselfservice%2Fmicrosites%2Fsearch.do%3Flanguage%3Den_US%26cmd%3DdisplayKC%26externalId%3D2002106">VMware KB Article 200216</a><br> <h2 data-id="cause"><strong>CAUSE</strong></h2> <p> The storage controller driver is incorrect.</p> </article> </main>