Geeks With Blogs
Brian Biales because blogging is just the easiest way to remember things
Whenever an individual asks me about the best way to backup their personal computer, I point them to the Macrium Reflect product.  It has a free version, making it very easy to try out, and the free version is actually very full featured, probably enough for most people.  Of course, they can always pay for a license, giving them support and some additional useful features, if they like it. 

I used it to backup my daughter's laptop before she went away for school several years ago.  Now she is going away again, and I upgraded it to the latest version.  She has a large external USB drive, and the full backup was created easily.  For protection from a catastrophic disk failure, you need to create a bootable USB or CD, so you can restore the entire disk image should the hard drive fail completely and need to be replaced.  The software has an excellent tool to help you do that.  So I created a CD, based on Windows PE, and tried to boot with it.  It started out looking good, started up the Reflect program, but then loaded a driver that caused a BSOD frown face screen from Microsoft, saying that a driver caused the stack to be over ridden.  It didn't even say which driver!   

Rather than describe the whole ugly process I went through trying to figure this out, I'll just cut to the chase and tell you why the problem occurred and an easy way to fix it.  

I had created a rescue CD several years ago when the computer was running Windows 7.  The software does a great job of hiding all the gory details of creating a Windows PE image and then creating a CD image with it, including the Reflect software you can run from it.  But by hiding the details, when it doesn't work, it is not obvious what went wrong or how to fix it.  I am not sure if this is even a "standard" place to put such things - but Reflect takes Network, Disk, and USB drivers that it detects are necessary for your hardware to include in the Windows PE boot disk, and places them in a hidden folder - C:\boot\macrium\drivers.  These are then pulled in when making the image.  

Because these drivers were already there from several years ago when I first created a Rescue CD image, Reflect assumed they were correct, and did not attempt to copy existing drivers this time.  However, last time I built a rescue CD, it was running Windows 7.  The computer was upgraded to Windows 10.  These older drivers were causing the BSOD.  

The solution once found was so very simple.  I simply removed the folder c:\boot\macrium.  Then I created the rescue CD again from within the Reflect program.  This time, it showed that the network drivers and USB drivers would be copied from the machine when making the Windows PE image.  I completed the process.  I then looked in the new C:\boot\macrium\drivers folder that Reflact had created during the process, and the drivers there now were different names and newer.  I burned the new image to a CD to test it out, and it boots just fine.   Mystery solved. 

So next time your Reflect Rescue image fails to boot, check out the contents of the C:\boot\macrium folder.  Don't necessarily delete it, but see what's there, maybe move it to a different location, let Macrium create it again, and see if it is different like I did.  Perhaps you need to add additional drivers.  Whatever the cause, this is a good place to start looking.
Posted on Wednesday, August 31, 2016 6:26 PM Windows 10 , Macrium Reflect , Windows PE | Back to top

Comments on this post: Macrium Reflect Windows PE Rescue Disk Mysterious BSOD resolved

# re: Macrium Reflect Windows PE Rescue Disk Mysterious BSOD resolved
Requesting Gravatar...
Thanks for the data, will try it out soon
Left by Renu on Jan 02, 2017 11:53 AM

# re: Macrium Reflect Windows PE Rescue Disk Mysterious BSOD resolved
Requesting Gravatar...
This is great.

Download -
Left by Dean on Feb 02, 2017 4:00 PM

Your comment:
 (will show your gravatar)

Copyright © Brian Biales | Powered by: