Vista - blue screen when installing vista

Hi,
I just built a computer and I just started the installation of Vista Home
Premium and get this blue screen,

fltmgr.sys
PAGE_FAULT_IN_NONPAGED_AREA

STOP: 0X00000050 (0XD7856850,0X00000001, 0X857D156A, 0X00000002)
FLTMGR.SYS -address 857d156a base at 857cf000 datestamp 4549acc2

I've got the installation to start before but every time I get a different
blue screen and it stops. Its stopped at 1%, 13%, and 17%.
I'm guessing it is a driver problem and I've got a driver for the
motherbored but I don't know where to install it, if that's the problem.

Here are the specs:
Motherbored: MSI K8T890M-V/K8M890M-V
Processor: AMD Athlon 64 X2 2GHz OEM
Hardrive: Seagate SATA 250GB OEM
RAM: 2GB DDR 400Mhz PC3200 SDRAM (2 1Gb sticks)

Hi Blair,

You're guessing correctly, as it is definitely a driver issue. Make sure
that the motherboard is set to timing defaults, and that boot time
protection is disabled. Also, disconnecting unnecessary peripherals can
help. If the HDD needs a driver file, make sure to load the most current one
that MSI offers for their motherboard during setup.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"Blair" <Blair@xxxxxx> wrote in message
news:62707631-8FF6-499C-BCD1-A5AE45B1BB82@xxxxxx

Thanks for the response, I've gotten a new blue screen that said
MEMORY_MANAGMENT with no error code. I ran the Windows Memory Diagnostic Tool
and it said the memory is OK. I've got a CD with the drivers for the
motherbored on it but I don't know if that's the problem, but if it is how
would I install it?
I almost got the installation it get to 60% expanding files before I got the
first blue screen. On the MSI website, it said that the motherbored is
designed for XP so is that the problem?
"Rick Rogers" wrote:

Hi,

It could be that the board simply will not run Vista, but MSI is usually
pretty good about keeping up the specs. The new BSOD is likely an indicator
of a problem with the virtual memory manager, not the ram itself. This could
be caused by a number of things, but most likely a problem accessing the
drive controller and not being able to write to or retrieve from the hard
drive pages.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"Blair" <Blair@xxxxxx> wrote in message
news:50886B7D-C9B7-4B4B-83D4-E0EEB54D431E@xxxxxx