Windows 7: Image your system with free Macrium

Sounds like another reason to avoid W8.

@SIW2

If you look at the thread I posted it explains it. After the image I rebooted and got page fault in a non paged area. I thought originally it might have been due to using a VM but as you can see I am not the only one with this.

I understood the Linux version does NOT include Win PE,
and is not amenable to incorporating requisite drivers,
you get what you get ready made for "standard" hardware.
If it fails to boot there is non work-around.

Mmm! Interesting. I have just retried it in a clean install in VBox rather than my previous install in VMPlayer and it seems to have worked this time.

If you have problems imaging Win8 with free Macrium, I suggest to use the Macrium WinPE CD/stick. In a double boot, you can also use Macrium from Windows 7 to image the Win8 partition(s).

Actually It is a later version of Macrium and 64bit in VBox as opposed to 32bit in VMPlayer so the comparison is not exact. Incidentally restoring an image works too now.

Trouble creating image

I updated to the latest edition today (4694, dated June 12, 2012) and proceeded to make my regular image to an internal SATA drive (Seagate). At the 1 min/20 sec to go mark, the program stopped responding. When I moved the mouse my Win 7/64 system threw up a BSOD ("Kernal Data Inpage Error"). First time I had ever seen this one.

I rebooted into SafeMode and ran CHKDSK on all internal/external drives. Every one came up OK. I rebooted into Windows and tried again. At the *exact* same mark (1 min/20 sec to go), Macrium again became unresponsive. This time no BSOD, but I was unable to close the program. I tried forcing a close with Task Manager, but the screen went black (the mouse pointer was still visible and able to move). Again, I rebooted into SafeMode and ran CHKDSK. Everything OK.

I tried a third time, but chose as a destination drive a different SATA internal (Seagate). This time, the image completed without a problem.

Not sure what's going on. I googled "Kernal Data Inpage Error" and came up with possible RAM issues or a possible failing hard drive. Since the error occurred at the exact same time during the image creation on just that one drive, I'm wondering if it's, in fact, the latter. I ran the short test in SeaTools DOS and came up with nothing, but I'm not sure if that was adequate.

Any ideas?

Hi bruce73. I think you would be better off starting a new thread in the Crashes and Debugging section. One of our BSOD experts will pick it up there.

Good idea, I'll do that. Although, to amend just a bit, I ended up restoring an image from a couple of weeks back as I was having others problems (unexplained 100% CPU usage). I also eliminated some files and defragged the problem disc and ran Macrium again (the previous version). This time it worked. Lots of variables here, I know, but the solid part is that it was the first restore I've done with Macrium and it performed perfectly.

That's good to know Bruce. I've never had a Macrium image fail but that doesn't mean that it won't in the future so make sure you have more than one. The problem you have with the BSOD post is that all evidence of it will have been removed by the restore. It may be better to wait until you have another so that you can follow the posting instructions to upload a crash report.