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

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