Macrium recovery media gives error on boot v7.2.4971 AMD computer


  1. Posts : 11,211
    Windows / Linux : Arch Linux
       #1

    Macrium recovery media gives error on boot v7.2.4971 AMD computer


    Hi there

    Trying to restore (using stand alone recovery) and build v7.2.4971 -- I get the Windows BSOD -- OOPS something went wrong and interrupt code of all zeros

    This only happens on an AMD machine with older opeteron X4321 processor -- no prob on another system with INTEL celeron or a laptop with Intel I5.

    Linux live distros all boot OK so I know the computer isn't broken. Fortunately I've got a spare HDD with Windows on it which I can temporarily put back and use the Windows version of Macrium to restore the image to the main Windows HDD.

    First time I've ever run into a snag with the stand alone recovery media.

    I made the media from Macrium itself -- direct to USB -- it suggested MBR/UEFI multi-boot.
    I could try booting the machine in MBR mode (it can be changed at start up and seeing if that makes a difference, and then trying UEFI with CSM enabled -- although I shouldn't need to go through that nonsense.

    Normally this machine boots in UEFI with CSM disabled - Is it only me or do others have more than their fair share of problems with AMD based computers !!!

    Anyway I'll investigate further before messing around and swapping HDD's.

    Cheers
    jimbo
      My Computer


  2. Posts : 25,692
    Windows 11 Pro 22621.169
       #2

    When I try to restore using MR in the start menu or rescue media all I get is a black Screen. It never did this before..
      My Computer


  3. Posts : 5,209
    21H1 64 Bit Home
       #3

    I no longer use Macruim Reflect. That's just because I prefer an alternative.

    I only ever had Macrium fail once. Something screwed up MBR and restore failed every attempt.

    Solution was to boot into PE from USB and use a partition tool to fix drive letters then still in PE use the same partiton tool to wipe windows partition. That allowed me to restore backup of windows partition using Macrium Reflect USB.
      My Computer


  4. Posts : 25,692
    Windows 11 Pro 22621.169
       #4

    Callender said:
    I no longer use Macruim Reflect. That's just because I prefer an alternative.

    I only ever had Macrium fail once. Something screwed up MBR and restore failed every attempt.

    Solution was to boot into PE from USB and use a partition tool to fix drive letters then still in PE use the same partiton tool to wipe windows partition. That allowed me to restore backup of windows partition using Macrium Reflect USB.
    Thanks I will try that
      My Computer


  5. Posts : 5,209
    21H1 64 Bit Home
       #5

    Josey Wales said:
    When I try to restore using MR in the start menu or rescue media all I get is a black Screen. It never did this before..
    Hey, don't wipe your windows partition unless you can verify an image by mounting it in Macrium Reflect.
      My Computer


  6. Posts : 25,692
    Windows 11 Pro 22621.169
       #6

    Callender said:
    Hey, don't wipe your windows partition unless you can verify an image by mounting it in Macrium Reflect.
    I do not intend to.
      My Computer


  7. Posts : 5,209
    21H1 64 Bit Home
       #7

    I suppose that the thing to try is uninstall Macrium, reboot, then reinstall it. Rebuild rescue media then see if it works.
      My Computer


  8. Posts : 11,211
    Windows / Linux : Arch Linux
    Thread Starter
       #8

    Hi folks

    I think I've found the problem with Macrium stand alone media not booting on some computers from USB device
    Can't get anything to work if partition > 8GB for starters although you can use larger USB devices. Ensure partition for bootable restore <= 8GB.

    I managed to make it work on an 8GB USB stick (Cruser edge 8GB) where I forced the partition to be FAT32 and used an older 1903 version of Windows to create the bootable media.

    This booted OK -- so I then booted up a Linux Live distro and copied the USB device to another (bigger one --16GB) as a test using the DD command - DD if=/dev/usbdev1 of=/dev/usb2 bs=16M status=progress.

    This worked as well

    So IMO there's either something in the latest Winre that has changed the boot program or something in windows that has changed EFI boot.

    Latest versions of RUFUS if you use that to create stand alone bootable media don't give FAT32 any more when formatting the device -- older machines can't use NTFS for boot loader. (NTFS partitions are of course OK once the boot loader has actually loaded properly).

    Hopefully Macrium will get on the case -- meanwhile if you can force the file system to FAT32 it works -- Earlier versions of Rufus also give FAT32 as an option when creating bootable EFI media.

    Note that if you use MBR with option to boot on either MBR or UEFI (requires CSM) then I've found on MBR you get the Windows logo and then it after a while just goes back to the Bios boot screen.

    Something's hosed up seriously here -- candidates : possibly WINRE (Old WINPE probably OK), Windows boot, RUFUS and MACRIUM.

    Cheers
    jimbo
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 13:38.
Find Us




Windows 10 Forums