win8 doesnt install tried everything

[HawkMan]

Well the Acer Aspire's only are at version 1.10. I don't know where the 2.xx versions are at.

On the acre support/downloads site

[evieluvsrainbows]

On the acre support/downloads site

Dude I have an Acer Aspire 5333.

[Shane Nokes]

Just in case someone comes along with a similar issue, sees this and attempt it....

OS installations don't work this way. At least not as simple as that. When you install Windows, the installation process loads drivers and files for your specific hardware. It was a good suggestion, just not one that actually works.

Actually that will work in a lot of cases with Vista, 7 & 8. Just wait to activate until after you've swapped.

[nekkidtruth]

Actually that will work in a lot of cases with Vista, 7 & 8. Just wait to activate until after you've swapped.

So he could essentially install on an Intel based motherboard with an Intel CPU and then put that drive in an AMD based system and it would boot up without issue? I'm not being sarcastic either. I'm being serious. As far as I'm aware, that's not feasible.

[Brandon H Supervisor]

So he could essentially install on an Intel based motherboard with an Intel CPU and then put that drive in an AMD based system and it would boot up without issue? I'm not being sarcastic either. I'm being serious. As far as I'm aware, that's not feasible.

no, as far as I'm aware that will work AS LONG as you shutdown before the restart timer reaches 0

I'm pretty sure it doesn't install any drivers until after that initial restart (though i could be completely wrong and talking out my ass)

[HawkMan]

Dude I have an Acer Aspire 5333.

So? We're talking about the OP anyway, a for his V5 there is a 2.x uefi firmware.

[Shane Nokes]

So he could essentially install on an Intel based motherboard with an Intel CPU and then put that drive in an AMD based system and it would boot up without issue? I'm not being sarcastic either. I'm being serious. As far as I'm aware, that's not feasible.

It's feasible. :)

Moving the drive shouldn't be a problem due to how Windows works now in comparison to pre-Vista era installs. It's now image based and you can just deploy it to the drive, and then run sysprep...pull it out of machine A, and put it into machine B.

Running sysprep clears the 'unique' hardware info about the system...and then installs the correct drivers for the hardware once it's in the new machine. The HAL is nowhere near the headache that it used to be.

[Manarift]

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560129(v=vs.85).aspx a simple google search showed up with this

Cause

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

Resolution

If a kernel debugger is available, obtain a stack trace.

To resolve an error caused by a faulty device driver, system service, or BIOS

• 
  Restart your computer.
  
• 
  Press F8 at the character-based menu that displays the operating system choices.
  
• 
  Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.
  

To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool

• 
  Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
  
• 
  Try disabling memory caching of the BIOS.
  
• 
  Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
  
• 
  Make sure the latest Service Pack is installed.
  
• 
  If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
  
• 
  For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.
  

If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are compatible with the version of Windows being installed. For example, you can get information about compatibility with Windows 7 at the Windows 7 Compatibility Center.

[nekkidtruth]

It's feasible. :)

Moving the drive shouldn't be a problem due to how Windows works now in comparison to pre-Vista era installs. It's now image based and you can just deploy it to the drive, and then run sysprep...pull it out of machine A, and put it into machine B.

Running sysprep clears the 'unique' hardware info about the system...and then installs the correct drivers for the hardware once it's in the new machine. The HAL is nowhere near the headache that it used to be.

Dear god the time I could have saved! I stand corrected LOL

It's true, you really do learn something new every day ;)

[scaramonga]

Very lucky guy.