RC1: MEMORY_MANAGEMENT BSOD during "Expanding Files"

[Guest]

I'm trying to do a clean install of RC1, but get a BSOD with a
MEMORY_MANAGEMENT issue while it is expanding files. I have tried both boot
from DVD and installing from a different partition.

Technical Details:
STOP: 0x0000001A (0x00008887,0x0000AD97,0x00000000,0x00000000)

The machine is fairly recent (Athlon XP 2400+, nForce2, 1GB RAM, ATI Radeon
x1600PRO)

Any clues?

 

[rogerlebo]

Hi!

I got the same STOP: 0x0000001A with Build 5536 during the step "Expanding
files" around 20%. (Clean install or upgrade)
So, I was not able to install Build 5536.
I bought my new machine in last July (Motherboard ASUS P5N32-SLI Deluxe,
Intel Extreme Edition Dual Core, 4GB RAM, ASUS 7900GTX 512 MB).
But, I was able to install Build 5384 with success. I run with it now.

I hope I will not get the same issue with RC1.

Have a nice week-end! Roger

 

[rogerlebo]

Just curious:

at what % did you get BSOD during the step "Expanding files" ?

Thanks!

 

[Guest]

Yay, im not the only one. I was trying to install pre-rc1 and get the same
crap. Tryed installing clean, tryed upgrading beta 2, tryed installing
through XP, tryed installing through a virtual drive... Everytime I get that
Blue screen with the same messege. Most the time it did it at 26% of
expanding files, there were a couple times it did it at random times. But
then the damn thing just automatically uninstalls and returns the system back
to where I started. One time I got all the way to Finalizing setup then it
gave me the BSOD. MEMORY_MANAGMENT What the hell does that mean. Only thing I
could think was it was a bad download but hey there are others... so I dunno.

 

[Mark D. VandenBerg]

Yay, im not the only one. I was trying to install pre-rc1 and get the same
crap. Tryed installing clean, tryed upgrading beta 2, tryed installing
through XP, tryed installing through a virtual drive... Everytime I get
that
Blue screen with the same messege. Most the time it did it at 26% of
expanding files, there were a couple times it did it at random times. But
then the damn thing just automatically uninstalls and returns the system
back
to where I started. One time I got all the way to Finalizing setup then it
gave me the BSOD. MEMORY_MANAGMENT What the hell does that mean. Only
thing I
could think was it was a bad download but hey there are others... so I
dunno.

Not sure about this build, but with 5384, the error at 26% was always
indicative of SATA controller drivers not being loaded when installing. Do
you have SATA hard drives?

 

[John Barnes]

Are you trying to install the 64-bit or 32-bit version?

 

[Guest]

It varies for me. When I booted from the DVD, I got it around 4% twice in a
row. When trying to install from XP (to a clean partition) I think it got to
around 27%.

 

[Guest]

I thought bad download too, but my brother was able to install successfully
with the same DVD. I may run the memory diagnostic to see if that turns up
anything, bad memory might cause the random timing like that. However, I
don't have any issues running XP.

 

[Guest]

No SATA drives, just IDE.

Although, I am trying to install to a second hard drive (F. I have even
installed Beta 2 successfully to that partition before.

 

[Mark D. VandenBerg]

No SATA drives, just IDE.

Although, I am trying to install to a second hard drive (F. I have even
installed Beta 2 successfully to that partition before.

Ah, it was worth a shot. It does seem like there is some sort of hardware
conflict going on. Have you tried installing with all peripherals (except
mouse and keyboard) disconnected?

 

[Colin Barnhorst]

That is the first reboot point. It sounds like Setup could find the hard
drive. Do you need to provide a hard disk controller driver during the
initial phase of Setup?

 

[Colin Barnhorst]

Touchy ram? Module not firmly seated somewhere? It definitely is hardware
at that point.

 

[Colin Barnhorst]

A bad download gives a different error code (and not a stop error) when
Setup tries to find the image file.

 

[Colin Barnhorst]

Given where the error is occuring his machine is capable of running the
version he is installing. However, the 64-bit versions of Windows are
quicker to spot bad ram.

 

[Guest]

First off, sorry for the double-post. I first posted through the web
interface which showed an error stating that the post didn't go through, so I
went back and reposted through OE. But then it turns out the web interface
is working (despite what it says! Anyways...

It's the x86 (32-bit) version.

 

[Guest]

No, I didn't need to. It is a standard IDE controller on a nForce2 mobo. I
have installed Vista Beta 2 successfully on the same partition before.

 

[Guest]

There is not much hardware to remove, since I need the video card and DVD
drive and everything else (sound, ethernet, etc) is integrated in the mobo.

It could be touchy ram although that doesn't explain why XP runs fine and I
have been able to install Vista successfully before (Beta 2). I'll play
around later and see what happens.

 

[Mark D. VandenBerg]

No, I didn't need to. It is a standard IDE controller on a nForce2 mobo.
I
have installed Vista Beta 2 successfully on the same partition before.

Another hair-brained, longshot:

Some people had a hard time installing previous Vista builds to a
drive/partition that had been formatted with Acronis. Something to do with
Vista using a slightly different NTFS than XP. Is this a possibility?

 

[Guest]

Hmm, nope I had never even heard of that tool. I formatted using either the
option in the Vista install (boot from DVD) or from XP.

Keep the ideas coming

 

[Mark D. VandenBerg]

Keep the ideas coming

Punt?