Skip to main content

What's happening with my winloader.efi?

Thread needs solution
Beginner
Posts: 6
Comments: 8

I have windows 10 and  I make weekly full backups of my primary C , efi, and recovery  partitions .  I also have a media partition  that I do not backup.  When I Just want to wipe everything I do a diskpark clean on the drive.  I go to do a recovery with my latest backup and it will go through the recovery process as normal until it gets to the last second.  It will just hang there and eventually it will go to a black screen it says segmentation fault dump.  I reset my pc as soon as it gets to the windows boot screen  and than I see a blue page that  it's missing hardware sometimes it will also tell me missing winloader.efi. The only way I can recover is to diskpart the drive again and do a clean install of windows than load acronis recovery and install my primary partition  backup on top of it and than everything is fine. My guess is at some point my efi  partition  got corrupted and my weekly backups just kept backing the corrupted partition.  If the efi  partition is corrupted why does windows still boot up on a restart and when I just do a recovery from a backup there is no problem?

0 Users found this helpful
Legend
Posts: 109
Comments: 27965

Jeremy, segmentation faults can be caused by memory issues during the recovery process but there was also a known issue which was fixed in ATI 2017.  See forum topic: Bootable media - seg fault when clicking restore disks - where this was reported nearly 4 years ago.

I would recommend ensuring that you have the final ATI 2017 build #8058 version installed and are using rescue media created for the same.

Beginner
Posts: 6
Comments: 8

Steve Smith wrote:

Jeremy, segmentation faults can be caused by memory issues during the recovery process but there was also a known issue which was fixed in ATI 2017.  See forum topic: Bootable media - seg fault when clicking restore disks - where this was reported nearly 4 years ago.

I would recommend ensuring that you have the final ATI 2017 build #8058 version installed and are using rescue media created for the same.

 

I am using 8058 

Legend
Posts: 109
Comments: 27965

Jeremy, which type of rescue media are you using here?

Is this the Linux based media which is the default for all versions of ATI prior to 2018, and used also for ASRM (F11 prompt on boot) and the ISO download from user accounts?

If so, I would recommend trying the Windows PE version of the media instead.  Given that you are still on ATI 2017, I would recommend using the MVP Custom PE Builder tool from the link in my signature as this can create the WinPE media using your Windows 10 Recovery Environment files (without the need to install 5GB of Windows ADK files!).

Beginner
Posts: 6
Comments: 8

Steve Smith wrote:

Jeremy, which type of rescue media are you using here?

Is this the Linux based media which is the default for all versions of ATI prior to 2018, and used also for ASRM (F11 prompt on boot) and the ISO download from user accounts?

If so, I would recommend trying the Windows PE version of the media instead.  Given that you are still on ATI 2017, I would recommend using the MVP Custom PE Builder tool from the link in my signature as this can create the WinPE media using your Windows 10 Recovery Environment files (without the need to install 5GB of Windows ADK files!).

 

I am using winpe for my rescue media.  Last night I tried the process again first with an older image and I got the same result as before with the blue screen. I also did the process with an image I just created and it recovered fine. I do think it's a problem on my end.  I was using a disk cleanup utility and I believe  that is what corrupted my efi partition .

Thanks for your help  Steve