Acronis restore causes BSOD Page Fault In Nonpaged Area/Windows 10

When you restore the non-boot drive do so using the Recovery Media and when you do so disconnect the boot drive before you run the restore to the other drive.

Windows 10 can get confused in dual boot situations and multiple attached disks.  Alternatively to the above prior to booting Win 10 boot to bios and make certain that the Win 10 install is set as first boot in the boot order list.

Thanks for the quick response.  The restore file is one large file not separate files and was created with the 3 drives installed and the restore file looks like it had 3 drives backed up. The boot device is an SSD attached to the motherboard so I can't really disconnect it.

Windows 10 is set as the first boot device.

You need to backup each disk separately, the data disk should be one backup and the boot disk another backup.  When you restore the boot disk select the full disk for recovery.  Recovery of the boot disk must be performed using the Recovery Media that you must create using the Media Builder tool found in the Tools section of the GUI.  It is possible to recover the data drive from within the installed Windows application.

By restoring each OS partition individually on a single disk you are causing Win 10 to loose the location of the boot loader thus the BSOD

Thanks.

One last question.  I have this computer set to boot in legacy mode; both before and after the original Acronis backup.  Wouldn't this not require a bootloader, and if so is there a way to repair the boot process in Windows 10, is it called MBR?.  Can't get into safe mode or a command prompt.

I can get to the Windows 10 directory and files from the Windows 7 side if that helps

Robert, exactly how was / is your dual-boot system set up?

You say that the boot drive is a SSD plus there are a total of 3 drives in the computer, so out of these drives, what is used for what, and which drive failed?

My reason for asking the above is to try to understand how your system is configured here for booting from both Windows 7 and 10.

I run my own triple-boot system which has Windows 10 Insiders (was originally Vista), Windows 10 regular, and Ubuntu 16.04 where each of these OS's are using their own partitions, but both Windows OS share the same BCD store which is located on my first partition.  Ubuntu uses Grub which then launches into Windows .

Understanding how your computer is configured should help us to advice how best to recover.

Well let me see if I can answer that. I have 3 drives. A 250gb SSD, A WD 2 tb, and a Seagate 4 tb (this was the replacement). 

Windows 10 and 7

I believe they both boot off the SSD. I do get a choice when the system starts up to chose Windows 10 (1st choice) or Windows 7. If I select Windows 10 I get the BSOD and page fault, if I pick Windows 7 it boots normally and everything runs fine and can see all 3 drives. Also, when I select Windows 10 I get the "spinning dots" for about 2 rotations and then the BSOD.

Looks like both Windows 10 and Windows 7 are installed on the SSD on different partitions with the other 2 hard drives used for data and stuff.  It's possible the pagefile for Windows 10 is or was on one of those hard drives, possibly the one that was replaced as when I use a disk frag program I see the swap file for Windows 7 but not Windows 10

It appears too that when Acronis restored it placed things on the various drives where they should be and in the proper partitions.

I do think it has something to do with the boot process for Windows 10.  As I mentioned in an earlier post, a re-install of Windows 10 runs fine, so I have ruled out a hardware issue.

I appreciate your help.  Thanks

Robert, where are the OS files for both Windows 7 and 10 on your computer - are these all on the SSD and in separate partitions?  Also, do you have a separate Microsoft System Reserved or EFI partition on that SSD?

The pagefile location should not be a problem here as that file will be rebuilt when Windows is booted if not found.

If you are able to boot without problem into Windows 7, then I would recommend downloading / installing a copy of the free EasyBCD program which will allow you to look at the Windows Boot Configuration Data and try removing the entry for Windows 10, then have this re-entered again.

See the following screen shots from my computer:

This is how EasyBCD opens and shows the current boot entries and which is set as default.

The BCD Backup/Repair option lets you backup the current settings (or restore them back if needed), but it can also be used to Reset / Re-create/repair them etc (using the top options and the Perform Action button).

If you remove the Windows 10 boot entry (using the Edit Boot Menu page) then you can add it back again on this panel, selecting the Drive where it is located.

The OS files are both on the SSD and in separate partitions.  The Microsoft System Reserved is showing on the 2tb drive and is 100mb in size. So it is NOT on the SSD. Could that be the issue??

I will give EasyBCD a try and let you know.

Thanks again!

See also webpage: Repair Dual-boot (Multi-boot) Configuration: Guide for Windows XP, Vista, 7, 8, 10 from the same people who provide EasyBCD but which also has manual instructions for doing this type of repair for a variety of different OS scenarios.

I downloaded that and burned it to both a USB and CD and made it bootable.  But everytime I ran it I just got a very fast scrolling lines of test and not the GUI interface

Robert, EasyBCD is a Windows program and needs to be installed on your working Windows OS, i.e. Win 7 and then run from there.  It is not a bootable application.

Working on EASYBCD as we speak

I was referring to the other program you mentioned by neosoft Recovery Essentials. But I couldn't get it to run

I got EasyBCD running but so far no luck

Does the Microsoft System Reserved partition need to be on the boot drive? Looks like mine is not.

Also, in EasyBCD, while in windows 7 and running EasyBCD, the WIndows 10 settings shows a BCD ID: {default}

Is this normal?

The answer depends on how Windows was installed in the beginning?

If the MSR partition has always been on a different drive, then chances are that it is a left-over from a different installation.

When Windows is installed on an empty drive then the MSR is created before the Windows OS partition and holds the Boot configuration folder.  If Windows is installed on an already formatted drive, then no MSR is created and the Boot data is in a hidden folder on the OS partition.

Doing an Acronis restore will not cause the MSR to be moved to a different disk.

OK thanks. Still no luck with EasyBCD. Was able to save remove and reenter but still get BSOD

Robert wrote: "The OS files are both on the SSD and in separate partitions."

When you did the restore, did you restore the whole SSD drive with all of its partitions?

Sorry for the delay....had trouble logging in.

Both Windows 10 and Windows 7 are on the SSD and on separate partitions 

So far I have not had any luck.  Windows 7 boots fine but Windows 10 gets a BSD with the page fault in non paged area.

Here's a pic of what the drives look like.

Robert, thanks for the screen shot of your disk layout etc.

My main concern looking at this is that you have drive letters allocated to hidden/system partitions that should not be there! 

Disk 0 drive letter J: looks to be left over from when perhaps that drive was the main OS boot drive, before migrating to the SSD drive?

Disk 1 unallocated 1678.02GB space would suggest this drive was formatted on a system which didn't support 4TB drives and only permitted half of this to be partitioned?

Disk 2 drive letter D: should be the System Reserved partition for the SSD drive, with no allocated drive letter.  As such, this should probably also be shown as the Boot partition instead of this being shown on your C: partition.

Sorry to repeat my question but: When you did the restore, did you restore the whole SSD drive with all of its partitions?

Having the Boot indicator shown on the C: partition need not be a major issue, but if this is correct then you shouldn't have the 500MB (System Reserved) partition.  This is part of the reason for repeating my question above, to try to understand if what you are showing us now is what the drive was looking like when the full backup of the SSD was created, and again, did you put back everything that was in the backup image of the SSD?

The backup was created while running Windows 10.  The snapshot of the drives I posted is how it looks under Windows 7.  So I suspect it is going to look different when (if) I can boot to Windows 10.

Disk 0 drive letter J: looks to be left over from when perhaps that drive was the main OS boot drive, before migrating to the SSD drive? This PC came with Windows 10 installed, I believe on the SSD. I installed Windows 7 later.

Disk 1 unallocated 1678.02GB space would suggest this drive was formatted on a system which didn't support 4TB drives and only permitted half of this to be partitioned? This disk is the replacement for the failed 3gb hardrive.  The BIOS is running in legacy mode (not UEFI) and MBR. Hence, I think that is why it is not using the whole drive. Is this an issue?

Disk 2 drive letter D: should be the System Reserved partition for the SSD drive, with no allocated drive letter.  As such, this should probably also be shown as the Boot partition instead of this being shown on your C: partition.

Sorry to repeat my question but: When you did the restore, did you restore the whole SSD drive with all of its partitions? As far as I know yes.  

Having the Boot indicator shown on the C: partition need not be a major issue, but if this is correct then you shouldn't have the 500MB (System Reserved) partition.  This is part of the reason for repeating my question above, to try to understand if what you are showing us now is what the drive was looking like when the full backup of the SSD was created, and again, did you put back everything that was in the backup image of the SSD? Backup was done under Windows 10, but the picture depicts layout under Windows 7.

When I did the backup, I did it as "backup entire pc". So it created one large backup (.tib) file, I assume each drive and their respective partitions.  

Again, I appreciate your help.  It does seem like things are not being put in the right place, at least for Windows 10.  Windows 7 runs ok.  

Robert, the only advice that I can offer here would be to re do the recovery again, and doing this as a full disk recovery for the SSD drive only, doing this using the Acronis Rescue Media to boot the computer.

Please see the attached PDF document showing the steps you should take for the above recovery.  This was written for ATIH 2017 but the steps remain the same for 2018 as there is very little difference when using the rescue media.

One key difference in your case is that your 'Entire PC' backup .tib file will contain your 3 separate disk drives, so you need to just select your Disk 2 - 250GB SSD drive from the drives shown in the ATI application, where this may be shown as Disk 3 given the way Acronis numbers drives (starting from 1).

I'll give it a try....thanks Steve!

Thanks for the help Steve. One last question.

I did as you suggested and restored just the SSD. It didn't solve the problem but I did notice that when I went into Windows 7 and looked at the hard drive layout, it had changed somewhat. There is now a 128mb unallocated piece on the SSD. The other partitions on the SSD are the same.  

So I decided to restore each drive separately.  While for now, I still cannot boot into Windows 10, when I look at the drive layout in Windows 7, the drive letters assigned to the 2 other hard drive (not the SSD) have changed.

Could this be the issue with Windows 10? Perhaps the drive letters are not being assigned like they were originally when I created the backup and Windows 10 can't find something it needs. 

I enclosed a picture of the current layout to compare against the previous one above.

Thoughts?

Thanks

Bob

I am going to guess here and say that your Win 10 install is on Disk 2 labeled OS (H:).  If not than it should be partition C: on Disk 2.  The first thing I would try is to boot to your Windows 7 install, open an admin command prompt and type the following:

Bcdboot X:\Windows   where X is the partition of your Win 10 install. 

Once you have done this reboot the machine and see if you can boot Windows 10.  If not then I would try what appears below:

Looking at your screenshots my thoughts are that when you performed the first restore attempt and selected to restore the Windows 10 partition of the backup file this caused the restore to leave out the boot partition needed for Windows 10 to boot.

It now appears that the boot of Windows 10 could be set to the first partition of Disk 0 as it is marked as the Active partition.  It also appears that partition C: on Disk 2 is marked as the boot partition.

Since you cannot get Windows 10 to boot I would try to backup the first partition of Disk 0 (100MB Drive G) then restore that partition to the 128MB unallocated space (partition 2) on Disk 2. Once you have that done see if Windows 10 will boot or offer to repair startup. 

Thanks for the reply Enchantech.

The Windows 10 install is in fact on H: drive as shown via Windows 7

I tried the first suggestion but got "failure when attempting to copy boot files"

I will try your second suggestion and report back

Thanks

Bob

One last question. Is 100mb the right size for the System Reserved partition for Windows 10?

Yes, should be fine. 

Well have a minor issue. All the drives are MBR. Hence, I'm limited to 4 partitions on the SSD Drive.

In order to move the System Reserved partition from Disk 0 to Disk 2 Don't I have to create a partition in the 128mb unallocated space on drive 2?

The SSD already has 4 partitions.

You have 4 primary partitions on the disk which includes counting the 128MB unallocated space.  The remaining partitions at the end of the disk are extended partitions.