On 23 Feb, 18:10, "philo" <ph...@xxxxxx> wrote:
Quote:
> <petermcmillan...@xxxxxx> wrote in message
>
> news:d8c32f6d-8258-4abc-9a7c-5832ae2aaedb@xxxxxx
> I've just built a new computer with 64bit Vista Home Premium. *The
> installation goes through its bits and then reboots itself (as it's
> supposed to). *When it comes back it does the 'completing
> installation' stage, but during this it gives me a BSOD and I can't
> get any further with the install. *It reboots itself very quickly so
> it's hard to read the message.
>
> Any ideas what happens in the 'completing installation' stage? *Does
> it have a look at the hardware? *Or does anybody know how to fix it?
> I haven't got any unusual hardware (apart from a USB memory card
> reader) in there so I wouldn't expect driver problems.
>
> At the moment I've spent £hundreds for a machine that does nothing :
> (. *Windows XP isn't really an option either because Vista was the
> whole reason for buying the computer.
>
> My hardware is:
> Asus 380W PSU
> ASUS M2A-VM HDMI Motherboard (inc sound + video)
> AMD BE-2350 Processor (dual core - 64 bit)
> Corsair XMS2 800MHz DDR2 2Gb
> LG PATA DVD writer
> Western Digital SATA 160Gb 7200rpm HD
>
> Did you install the chipset drivers?
>
> Look at the post from yesterday as that was covered
>
> see: "desperate"
I've got further now, and installed it. I tried, but I couldn't
install any drivers until after the install. I changed the memory
voltage from 'auto' to 1.9V, which I thought may have fixed it, but it
may just been luck because I keep getting a BSOD every few minutes
even when not doing much.
It looks like a hardware fault (not really the right group). I ran
the memory test from the Vista DVD and there were no errors. Does
that mean the memory should be OK or does it not stress the memory
enough? My first BSOD was at the login screen before logging in, and
it didn't crash during the performance tests either. The first two
BSODs were something about modifying internal data structures IIRC,
and the last was memory management. The only other posibility I can
think of is the processor having a hot spot if the thermal pad got
messed up (although I doubt it)?