Win7 install error - too much memory?

[Diggs]

Did I miss the memo on this.......?

Tried installing (Nuke-n-Pave) Win7 on an Acer Aspire with 8 GB of RAM (4 x 2GB) this morning. Kept getting a "Windows cannot install required files - error 0x80070570". A quick Google and the consensus was to pull out some memory. I yanked banks 3 & 4 and Win7 installed gracefully. Really?????

 

[GTP]

From the "weird and wonderful" department?

 

[MichaelEC]

That's strange. Never saw that before.

 

[mr m]

I've never heard of this either.

I wonder if that mobo's Northbridge chipset can handle 8 GB's?

 

[MichaelEC]

??? Not enough info in the OP, but I would think that if it was running on it before the reload it would accept the reload.

 

[carrcomp]

That's going to be a read error - either bad media and you got lucky the second time, or there's something wrong with the RAM you removed.

 

[nlinecomputers]

I've heard of this before. I assume that the basic drivers in Windows PE aren't able properly see it. Loading chipset drivers during the Installation might also work.

 

[GTP]

I agree with @carrcomp I would suspect the ram. I've had this happen to me on occasion and simply removing and reseating the RAM worked.

 

[Altster]

Not enough info here-

Was all of the ram exactly alike?
Were the speeds and configuration(s) alike?
32-bit or 64-bit installation?
Did you do any research on the Internet pertaining to exactly what type of RAM to use with this machine?

I agree, could be the Chipset causing some issues. But information is needed for you to fully understand what is going on.

Some computers have a total ram limit (including type/speed/etc.) that the main/motherboard will accept.

 

[Diggs]

A final observation. After the full install, updates and programs I added back the 2 sticks of 2GB each to bring the system back to 8GB. Shortly after I started getting BSODs. I yanked backed out the memory (and trashed it) as it is fine for the user at 4GB. Funny thing is, when Win7 installs it gives an option for memory test which I did several times both during install and prior through a Linux boot. All seemed fine until Win7 wouldn't install. It detected something and maybe just gave the wrong (or obscure) error message is my guess(???).

 

[MichaelEC]

I've done Lenovos with up to 16 GB with nothing strange like that happening. Maybe a bad ram slot or...???

 

[cypress]

Did you make sure the memory is the same exact one as the one in the system? Same Memory clock and such. I had the same issue with a Dell Lattitude I wanted to upgrade to 8GB from 4GB. Computer would BSOD and then reboot right after. I even took that memory and threw it on my field laptop and it worked no issues. Further inspection of the original memory and it only uses that particular speed so I just left it at 4GB as that type of speed was $120+ online lol.

 

[gn2]

Memory can do some awful stuff during an install.

 

[ComputerRepairTech]

he said he yanked banks 3&4 that means he disabled dual channel, you disable dual channel you release some of the stress on the ram. Don't ask me why its just a real thing based on my experience. Ram may be fine running outside of dual channel but soon as you put it in dual channel boom problems are revealed.

Edit: Well...based on my experiences about 11 years ago, I don't exactly deal with a lot of hardware issues these days.

 

[GTP]

Ram may be fine running outside of dual channel but soon as you put it in dual channel boom problems are revealed.

Mixed and matched ram doesn't work terribly well in some motherboards, let alone in dual channel mode.
So many different types of (cheap and cheerful) ram and motherboards make it very hard to predict what will happen in any given configuration.
I've found that the more expensive ram/mobo combo's seem to have less issues and are more tolerant of different ram brands/speeds when mixed and matched in dual channel!
Clients sometimes insist on using their old ram sticks to save a few bucks (against my advice!) and invariably end up with issues because of it.