Boot Loop Help Needed!

Hey there,

I know this topic has been explored to death, but I've exhausted most of the solutions I've found.

I purchased a new MB as a replacement for a failed one in my older system. It's the exact same model (ASUS P7P55D-E), but my original was branded "American Megatrends" and the new one is branded "Velocity Micro". I got it off EBAY and assume it’s been stripped from a different system.

My problem is that I'm trying to retain my existing OS install and I'm stuck in a boot loop. It stops at a few moments into the Windows animation (right at the point I usually select the user).

• The OS is Windows 7 Enterprise
• The BIOS is exactly the same as my previous one and all the settings seem the same.
• I'm trying to retain 15+ years worth of installed software, so doing a clean install would defeat the purpose

I'm guessing the OS is probably detecting it's a different motherboard, but I can't find a solution that re-calibrates it.

Here's what I've tried:

1. Trying to enter safe mode will loop in the exact same way,
2. All existing OS recovery options (on my original HD) end in the machine just rebooting.
3. Selecting the option to "not reboot on system failure" results in... a reboot.
4. I have my original Windows disc and attempted to use that as a boot disc/ recovery option. Every option reboots in the exact same way as my existing OS.
5. I created a recovery disc from another computer with a working version of Windows 7 Home (I don't have access a system with Enterprise). Using it gave me a device error connected to the DVD burner (I/O Error 0xc00000e9 -Windows encountered a problem communicating with a device connected to your computer) before it even reached the recovery option menu (it was able to reach the preliminary menu when I used F1). The drive is fine, as-it read the Windows 7 installation disc without a problem.

Any tips or intel you can give me would be very appreciated.

Cheers,
Nik

SIW2 said:

Make Windows 7 bootable after motherboard swap

Thanks! I'll give it a shot!

- - - Updated - - -

SIW2 said:

Make Windows 7 bootable after motherboard swap

When I tried to boot from the Paragon disc, I get a flashing cursor for a few seconds and then it will bypass the DVD drive and attempt to boot from the HD. I'm trying hard not to throw this computer out the window. haha

- - - Updated - - -



I also tried it as a bootable USB and it skips the removable media even though it's 1st in boot order. I forced it (via F8) to try the USB and got "An operating system wasn't found. Try disconnecting any drives that don't contain an operating system. Press Ctrl+Alt+Del to restart"

You said the motherboard failed. Are you sure that is what failed? Are you sure the new motherboard is the same or compatible with your CPU and RAM from your old motherboard?

I also had a motherboard fail recently. When I was troubleshooting the computer I took the computer apart and mounted the motherboard on its box. I then only connected what was absolutely necessary. For example, CPU, CPU cooler, RAM, and GPU. I then connected the power supply. I had some spare components so was able to confirm that either the CPU or motherboard had failed.

I have a computer with a dual-boot (Windows 7 Home/Windows 10 Pro. I changed motherboards but kept the same 3 drives. As you can see below the motherboards were completely different.

Original motherboard:
MBD: Gigabyte GA-990FXA-UD3 rev. 1.0
CPU: AMD FX-8350 (AM3+)
RAM: GSkill F3-12800CL9D-8GBXL DDR3 8GB(2x4GB)

Replacement motherboard:
MBD: ASUS Prime X370-Pro
CPU: AMD Ryzen 1700X (AM4)
RAM: Corsair Vengeance LPX DDR4 16GB(2x8GB)

Before I started I gathered the necessary drivers for the new motherboard. I put them on a flash drive.

Windows 10 booted fine with some hardware not working. Everything worked after I installed the new drivers.

When I booted Windows 7 it got to the login but neither the keyboard or mouse worked. I then realize that Windows 7 does not natively support USB 3.0. All the usual front and back panel ports were USB 3.0. I used an old keyboard with PS/2 to navigate Windows 7 until I could install the USB 3.0 drivers. In case you wonder how I copied over the drivers with no working USB ports. I did that from Windows 10. Note, I later installed a USB 2.0 bracket that connected to headers on the motherboard so that will no longer be a problem.

MisterEd said:

You said the motherboard failed. Are you sure that is what failed? Are you sure the new motherboard is the same or compatible with your CPU and RAM from your old motherboard?...

Thanks for responding! Answers to your questions:

1. You said the motherboard failed. Are you sure that is what failed?

Yup. I breadboarded the machine and it was down to the CPU or MB. I got a new CPU and it was still dead. When I swapped the board, everything functioned perfectly (from a mechanical perspective). I did a memory scan and checked the disks - they all check out fine. The old MB wasn't posting at all. Windows itself was fine.


2. Are you sure the new motherboard is the same or compatible with your CPU and RAM from your old motherboard?


Yup. It's the exact same model. It boots nicely up to the point where I usually select which user I want, but the login screen never happens. That's where it restarts! I would expect the numerous Windows repair options would work, but it's not even attempting the repairs. It feels like a permissions issue.

samuria said:

The main reason why you get these errors is bios settings ahci or legacy uefi mbr

I wish it was that easy a solution. The BIOS is old and doesn't have the option to change anything. It doesn't even boot past the logo from a USB and nothing else connected.

- - - Updated - - -

I solved the problem! In case anyone is trying to restore an old OS and finds themselves with similar symptoms, the error was caused by the way my BIOS handles ACPI.

5.0 was enabled by default, which is apparently known to cause power management instability issues with all Windows 7 media. ACPI 2.0 (compatible with W7) can be enabled in the BIOS, but disabling 5.0 causes a fatal error when booting. When I enabled them both, all W7 installations and rescue media would shut down before it reached any menus.

The solution:

1. Enable 2.0, Disable 5.0 and allow the error to happen.
2. Restart the system and enter the BIOS.
3. NOW enable ACPI 5.0 and allow the system to cycle and... boom. Works like a charm.

All W7 media wasn't working because the BIOS was configured to load 5.0 before 2.0, if they're both enabled together at the same time.
By first establishing 2.0 and then activating 5.0 on the next cycle, it allowed the OS to boot.