w10. Working fine. Weekly images with AOMEI Backupper. Suddenly would not boot. Used rescue dvd disc to restore image from external HD . Done this successfully 4 times in last 3 years, no issues. This time, no. Tried 4 times.

Used w10 dvd to install fresh, then installed Backupper, and tried to restore image again. Failed. Restored images are on external usb HD.

Attempted to boot from rescue disc again but cannot. Computer goes into continual boot loop. Starts up, runs a few seconds, shuts down and restarts, over, and over, and... never gets to boot screen.

i2500k stock,, sandisk 240gb ssd 4g ram, p67a mobo, good cooling, ANTEC 550W PSU.

The new W10 i Had installed was running fine, but didn't have all my stuff on it, hence the need for the backup.

Any ideas. Thanks.

I would suspect the RAM. I don't have time to find a bootable memory test disk at the moment, but they are available.

https://www.memtest86.com/

Quote:

Suddenly would not boot

What did it do?

Quote:

Restored images are on external usb HD

AOMEI have an image test type utility?

After installing fresh version of w10, and installing fresh version of Aomei Backupper, I used Aomei to check validity of restored image and it checked out OK.

When I got the initial message that it could not boot after the original restore attempt, it said, your computer ran into a problem and needs to restart. This repeated over and over again.

Cannot run memtest since stuck in boot loop. Can't get to anything on screen . Using 2 2GB ram sticks. Just pulled them and subb 2 other identical sticks. No change, which makes me doubt it's the ram.

Follow up. I figured the problem might be the mobo. I took the boot drive, which is an ssd, and put it into a 6 year old Gateway W7 comp, with the plan of installing w10 there. I really didn't think my backups would then work there, since it was dissimilar hardware.

I didn't even have the chance to find out. It booted up right into my regular w10 version with all my data on it. Don't know how, since it's a different machine. Device Manager is clean. Everything works> Apparently, all the backups took, but the computer was bricked and couldn't boot them.

Check to see if it's activated I'm betting that triggered activation.

Good catch. It did. I noticed that and fixed it. The Gateway at 2.9G seems just about as fast as my borked comp which before it farted, was running at 4.1.

How did you fix it? Phone call or did the online way work?