Numerous attempts to install Win7 64

Adrian, thanks for jumping in!

I have done that! I made sure that ANY drivers that i personally installed were done from the C drive and "run as administrator". The exact same thing happens...

what is curious tho is that if i watch the chipset installer package for ASUS 64bit for the board (and yes i made tripply sure that i downloaded the correct file) I see the process with a *32 beside it... not sure what this means exactly in a 64 bit OS but one might assume that this means its a 32 bit installer or application.

So as stated when running the ASUS 64 chipset dirver installer, there is no "progress" as one would expect to see and as one sees when doing other ASUS driver packages - it just goes from the start button directly to the Success splash which leads to the win prompt.

It would almost say this is irrelevant to my problems tho because i get the same flakky issues even if i dont intsall the vendor DL driver set vs. the win7 selected dirvers.

Keg mentiones that Asus is being a problem child with win7x64. how solid is this thought?

Adrian said:

Enoch, some questions if I may?

1. Are you installing directly from the dvd?
2. Is your flat panel connected via dvi? Or HDMI?
3. You have prior issues installing the chipset updates from Assus?
4. Is your hard drive connected via SATA?
5. Does your bios read the hard drive as SATA?

Your issue suggests problems with your video card.
Check these points out and let us know.

Adrian

I posted before seeing this latest post from ya so we may get ahead of ourselves...

Answers:
1. installing directly from DVD
2. flat pannel is connected by DVI-D
3. no prior issues with ASUS drivers. Other than an intel board, I wont use anything else but ASUS given my good history with them.
4&5. HD is physically connected as SATA, but i have the bios set up for RAID to support 2 other drives i have in a mirrored array. These other 2 are not plugged in durring the install process tho to ensure their integrity.

I agree that several of my crashes would point toward video card, but some of the crashes start out as "win Explorer stopped working" that fails the system and in my novice perspective i dont think this is a video issue.

Adrian said:

Enoch, what Intel Socket is used for your Mother Board?

Mobo is Asus P5Q turbo

• LGA775 socket for Intel Core 2 Extreme/Core 2 Quad/Core 2 Duo.....
• Chipset is P45/ICH10R with intel FMA

Adrian, your a god if this works!

I have to ask tho because im a bit of a noob at RAID/AHCI...

I will change the board to AHCI, but will this allow me to plug in the 2 ADDITIONAL drives in a mirrored format?

They are not plugged in because I currently have home/personal data on them and my only experience is with RAID setups.

Adrian said:

enochthered said:

I will change the board to AHCI, but will this allow me to plug in the 2 ADDITIONAL drives in a mirrored format?

They are not plugged in because I currently have home/personal data on them and my only experience is with RAID setups.

Enoch, change bios setting for AHCI for right now. Do not plug any additional hardware in for the moment. We can go back and review once we get a stable system running.
I'm curious as to when you performed the chipset update, you said you attempted to install a 32 bit update?
If you can give me your intel socket I will direct you to the correct update.

i am doing an install under AHCI as requested as i type this... and the additonal drives are not plugged in.

I did not try to install a 32 bit driver, rather, i went to the ASUS site the other day, selected the win7x64 when prompted and was lead to a page with the following chipset package "Intel(R) Chipset Software Installation Utility V9.1.1.1019 for Windows 32/64bit XP & 32/64bit Vista & 32/64bit Windows 7.(WHQL)" which i D/L and tried to install.. Win then says it "MAY" have not installed properly, so when i selected "reinstall with the recomended cofiguration" option the process seems to hand and task manager shows the process with a *32 beside it.

I too thought that perhaps i had the wrong installer so i have D/Ld the package 3 times in my journey with win7 and always the same situation.