RC1: MEMORY_MANAGEMENT BSOD during "Expanding Files"

[Mark D. VandenBerg]

There are a few other posts scattered around that speak of BSOD's
immediately following the loading of the SATA controller drivers. Is this a
bug?

 

[Colin Barnhorst]

Correction: That was, could NOT find the hard drive. Sorry.

 

[Colin Barnhorst]

Don't be too sure. I just set up a new Core 2 Duo box with XP SP2
preinstalled on one drive. I purchased additional ram and installed it.
When I tried to install XP Pro x64 on the second drive the computer blue
screened. Yet x86 ran fine with the additional ram. When I removed the
additional ram, x64 installed just fine. Go figure.

 

[Colin Barnhorst]

Sorry.

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]

Well still no luck. I tryed upplugging my SATA drive and just running off the
ATA133 drive... ive tryed loading drivers for the ATA and SATA drives with no
change. I even unplugged my CD drives, no change. Now this is what I find
sooooo wierd. If I use the DVD on boot and try to do a clean install that
way... it passes "Copying Windows Files" right up.... it immediatly goes to
"Expanding Files" BUT if I try a clean install under Win XP It copys files
and expands them... it restarts and once it hits either 26% or 29% the BSOD
pops up saying "MEMORY_MANAGMENT"

 

[Guest]

Well, I managed to get it installed! Turned out to be a "faulty" stick of
RAM. I say "Faulty" because it seems to run fine in XP

Anyhow, I ran the Windows Memory Diagnostic Tool that Vista installs into
the dual boot menu (I think it's also available separately). This detected a
vague "hardware problem". I tried with each of my sticks of RAM individually
and only one of them got the error. So I just put the good one in and lo and
behold, Vista installed.

 

[Colin Barnhorst]

The same thing would have happened to you if you had installed XP Pro x64.
I just went through that last week. I had to pull two sticks. I suspect it
had passed testing under 32bits but not been tested against 64bit.

 

[Guest]

I had the BSOD message after the installation and entering Vista. I have to
say that the installation didn't go well either but finaly managed to get it
done. I have a Asus K8N-E deluxe moterhboard with a 300 GB SATA disk. Ik
installed without loading other Nforce drivers and it finished finaly.

I will seperatly post about how my installation went (and went wrong)

 

[Guest]

I ran a memory Diagnostic tool and found 1 stick had an error on Test 3. So I
pulled the memory and pre-rc1 installed... Once installed my expectations
were trampled on. With Beta 2 on my system it had constant Hangs and freezes.
Well guess what. pre-rc1 is EXACTLY THE SAME WAY!!!! What the hell. I had
thought that through all the builds from 5384 to 5536 they would have fixed
whatever is causing my constant hangs. I sure as hope that RC-1 is fixed. But
I seriously doubt it. What is causing this and why. OH and they still do NOT
have a driver for my on board sound card. Its a Realtek ALC655 nor my Belkin
Wireless PCI card. However the XP driver works just fine for the wireless
card. Any input on all this would be great....
Here are my specs...

ECS Elitegroup RC410L/800-M V.2
P-4 2.8 with H/T
512MB DDR2
nVIDIA GeForce 6600 PCI-E
80GB Samsung ATA133 HDD -Vista
80GB Seagate SATA - XP-PRO
NEC DVD-RW
TSST- CD-RW
Microsoft wireless Keyboard and mouse combo