Windows 7 installation resets computer on "Starting Windows" message

essenbe · 23 Dec 2014

If I may interject something here, a stop 7E is usually a storage problem. That was great advise from Greg to check the hard drive for errors.

Anak · 23 Dec 2014

And Greg's mention of removing the video card, a stop 0x50 could involve video memory on the 650 ti.

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

TreeFlight · 23 Dec 2014

I've been slowly going through this list(and I had to buy some new blanks), so far:
1)DVD install to compare - the same results

2)Vista/any other installation disk boot - I've had an unpleasant surprise that my old OEM disk(perfectly working last time I've used it) for some reason isn't seen by computer at all;
(Could/Should I perhaps shrink a partition to create a new one for Win7? To be more cautious?)
Vista64 I've placed on a USB stick with Rufus - it gives msrpc.sys 0x0000007E BSOD at the same place

3)Partition Wizard - boots and shows no errors
I didn't try quick wipe

4)Another PC - I'll be able to try it later today

5)I did reset my BIOS to defaults before setting SATA controller to AHCI - choices are default_sata1, Power2, USB3;
Changing enhanced to compatible still gives BSOD
I don't see any UEFI settings

6)Sadly I only have external disks left, but I thinks I will try disconnecting it later

7)I have 2 DVD drives in total, Floppy drive, my video card is new(some months) because I have substituted another one that was giving me BSODs and artifacts - I can't test it. I hope I'm not forgetting anything

Additionally: Today my antivirus license was about to end, so I was forced to delete it or else I'd have to use up a new code.
(I was hoping to start a new license on a new Win7)
With IDE now I see a 0x000000D1 ACPI.sys BSOD Driver_irql_not_less_or_equal

Anak · 23 Dec 2014

Stop 0xD1 ACPI, shows a problem with the ACPI driver:

Symptoms

Assume that you have a computer that is running Windows 7 or Windows Server 2008 R2. The Advanced Configuration and Power Interface (ACPI) BIOS on this computer contains a namespace object that is not a PCI device. However, Windows assumes that the device is a PCI device incorrectly. Therefore, if Windows tries to access the PCI configuration space for the device, you receive a "STOP 0x000000D1"” error message.

Notes

The parameters in this error message vary, depending on the computer's configuration.
Not all "0x000000D1" Stop errors are caused by this problem.

Cause

This issue occurs because of an error in the Acpi.sys system driver. The Acpi.sys system driver returns an incorrect flag that causes the device to be regarded as a PCI device instead of a child of the PCI bus. Therefore, the device may not function correctly when the operating system tries to access it by using a special function. Sometimes, you may receive a stop error message that is mentioned in the "Symptoms" section.

Source: "STOP 0x000000D1" error message when you try to access a device that is not a PCI device in Windows 7 or in Windows Server 2008 R2

Since it included ACPI.sys I would think you can assume it is related to ACPI.

gregrocker · 23 Dec 2014

Make sure you first try everything to Troubleshoot Windows 7 Installation Failures - Windows 7 Help Forums. Since wiping the HD is the most common solution to installation failures if you haven't done that yet then you haven't yet tried everything to troubleshoot this failure.

Yes, you can try shrinking Vista to do a test install of Win7. If you can't get it to boot to install then you can even run the Setup file from Sources folder to install Win7 from Vista. You can save a backup image of Vista so you can perform the drive wipe first.

When running Setup File from Sources folder (only) then it may allow WIn7 to boot as C instead of another letter as it normally does when installed from another OS.