Format the 32 bit installation partition using disk management from your 64 bit install.
Your CPU should have nothing to do with the problem. Set your BIOS to default settings and try again. Take note of the settings in your BIOS as they are now. ( Write it down if you have to. )
Try install again after following AddRAM's suggestion to reset BIOS to defaults, delete and format the target partition.
This time enter Device Manager during install if necessary to uninstall any devices in error (likely display driver) to see if install will complete, then update device drivers from desktop. Device Manager - Access During Windows 7 Installation
Where did you get the Win7 installer? Did you burn the DVD yourself?
What do you mean by default settings ?
My bios-setup, as purchased, was: 1. [EFI device], 2. [Hard disk WDC WD20E....], 3. [CD&DVD: ATAPI DVD.....], 4. [Removable device], 5. [LAN]. I just swapped 1 and 2.
For the install, I just hit F12 on bootup, then got a menu where I selected to boot from the DVD device (= with my Windows DVD inserted). What's wrong with that ? Of course, I have no control of the device Windows boots from when it does its several restarts...
Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS
is how to reset the BIOS which can solve the issues in some cases.
It takes special steps to install Win7 on an EFI mobo: UEFI (Unified Extensible Firmware Interface) - Install Windows 7 with - Windows 7 Forums.
I'd enter BIOS setup to see if EFI is enabled, follow the steps given above.
Gregrocker's tutorial on how to access the device manager during windows installation has really helped me a big step forward. At least, I know what's wrong, but I cannot (yet) put it right. The instance of Win 7 (32-bit) which I have
installed is actually fairly completely installed, but all it does on startup is displaying me its problem window. So I did F8 on booting, selected safe mode and eventually shift-F10, etc and I got the Device Manager, showing me the devices that are not working: 1. "SM bus controller" (what is that ?), 2. "Ethernet controller", 3. "PCI controller for simplified communications" (what is that ?). Looking at these devices more closely, I noticed that they don't have a driver for them. I thought, I could start with the Ethernet controller by looking in the device manager of my other instance of Windows 7, the 64-bit one, and downloading the 32-bit version from the supplier (Intel Gigabit 82579V). This way, I got a file from Intel that is described to provide all the drivers required for all the Windows 7 versions, including mine. But this file (which I downloaded) is an "exe" file, and I cannot run an exe file under an operating system that does not work. Any advice on how I could get the right drivers out of that .EXE file into the different directories of my unable instance of windows 7 ?
I don't think these chipset drivers would stall installation by their absence, or if they are it is a rare case. The deal killer at this stage is normally the Display driver. What does it show and in what state?
You'll need to get to the desktop to run the .exe then browse into the extracted files from missing Device to Update Driver. Or you can simply run the chipset although Win7 may have provided drivers it prefers for other chipset elements.
I think the first thing you need to address if if you have an EFI BIOS (as it would seem from the boot order listings) and if so follow the steps given here to install: UEFI (Unified Extensible Firmware Interface) - Install Windows 7 with - Windows 7 Forums
The missing chipset drivers are the only ones with a yellow exclamation mark. For the display, it reports a "generic VGA", no problem symbol, obviously the default windows VGA display driver. The machine has a NVIDIA GeForce GX550Ti graphic card which works well in the 64-bit instance but which I don't intend to activate in the 32-bit instance of win 7.(on another machine, I have a similar setup with xp: the graphics card died after 4 years, so the "primary" instance of my dual boot became unusable (black screen), but I could still access all my data with the secondary instance which had been left under the VGA of the windows VGA controller). By the way, could you confirm whether the 32-bit win 7 has a compatibility mode with 16-bit apps ? I still have some good ones which get rejected by the 64-bit win 7, so I would expect this at least from the 32-bit version.
The only way I could run the .EXE drivers file at this point would be under the 64-bit win 7 instance. If I do execute it that way, what will happen ? will it just unload all the files it contains onto an unzip-directory or will it outright install and interfere with my installed 64-bit drivers ? Regarding the EFI bios, as I said, I have moved the hard disk option into the first place and the EFI second and I found no change to the bootup speed which comes near to a "kickstart" - at least compared with good old win 2000 I have on another machine. But, as I already said, for the install, I use F12 and the CD&DVD menu-option, so this should logically not be involved with EFI ? My machine is actually sold as a "gamer" and there is no 32-bit version on the market, so I am not sure there are all the 32-bit drivers possibly needed. So, this exercise could become pretty difficult.
If you have an EFI BIOS on the machine you need to use the special install steps. I'll ask you again to go into BIOS setup to look for what EFI settings are there and how they are set. These are not boot order settings, but the most fundamental BIOS settings.
You cannot insert any element of the chipset into the Win7 installer except SATA controller which is only needed if the HD or partitions do not show up on drive selection screen.
You'll need a Vista or WIn7 driver for Display to replace VGA if you want better resolution or Sleep/Hibernate.
This isn't entirly true if the driver is in the inf form. I know my intel chipset drivers can be downloaded as a zip and when extracted they are just inf files.You cannot insert any element of the chipset into the Windows 7 installer except SATA controller which is only needed if the HD or partitions do not show up on drive selection screen.
Add Device Drivers During Windows Setup
I also know you can put a folder called $WinPEDriver$ on the root of the Win 7 DVD or USB drive if installing from a USB drive and place your drivers in there, subfolders are ok, and the drivers will be loaded. Not sure if it'll work placing the folder on a USB drive that is not the installation media.By adding device drivers during the windowsPE or offlineServicing configuration passes, you can add out-of-box device drivers to the Windows image before the computer starts. This method can also be used to add boot-critical device drivers to a Windows image.
If you need boot-critical drivers for Windows PE, use the windowsPE configuration pass to reflect the drivers before the Windows PE image is booted. The difference between adding boot-critical drivers during the WindowsPE configuration and the OfflineServicing configuration pass is that, during the WindowsPE configuration pass, boot-critical drivers are reflected for use by Windows PE and other drivers are staged to the Windows PE driver store. Then, during the offlineServicing configuration pass, the drivers in the Windows PE driver store are staged to the driver store on the Windows image.
Then there's the offline option.
The thing is when non boot-critical drivers are installed, I don't think this happens till Windows boots for the first time.
Here's a couple of other links for more info
Understanding Device Drivers and Deployment
Add and Remove Drivers Offline
I forgot to mention if the EFI stuff which I know nothing about doesn't work you can always check the setup log, even though that's not always helpful.
Quote