Asus A8V problem with windows install

[monkelyoy]

After the unexpected death of my old MB, I have upgraded to an Athlon 64 3000+ (939) and an Asus A8V deluxe MB. I attempted to use my old Windows XP installation but, not suprisingly, received a "blue screen" error. I attempted to reinstall Windows XP but the installation would hang up during the "inspecting your drive configuration" window (early in the process). I thought this was a Bios issue but upgrading to version 1008 did not help. I disabled every other controller I was not using (RAID/ATA,etc) and attempted the install on two seperate IDE hard drives but it keeps hanging. I only have my video card (Radeon 9800 pro) and a keyboard installed.

Any information would be helpful. I read a few posts about similar problems with the Promise controller but these hard discs are plain vanilla IDE drives.

 

[Ryland]

I will throw my "normal" response of "Try the 1009.002 bios from ftp.asuscom.de" before turning it into a frisbee. What information is on the blue screen? Which DLL is dying?

 

[monkelyoy]

I'm at work so I can't tell you exactly what was on the blue screen. In essence it said that "if this is the first time seeing this message and new hardware was installed, reinstall windows", which I did. I will post a better description when I get home. Thanks for your reply.

 

[jamesbond007]

I have found that this is common if you are using a harddisk that is hooked up to a controller (ie: SATA or a RAID controller) that Windows does not have default drivers for. Basically what is happening is Windows freaks out when it can't find a harddisk, even though it may be hooked up to a controller, but Windows can't talk to this controller because it doesn't have the drivers for it installed. Upon Windows setup, press the F2 key and a menu will come up after Windows has loaded its files. Here, you will have the option to install drivers for your controller. (A floppy disk should have shipped with the motherboard with the drivers on it) Insert the floppy and press enter. Windows should search the disk for the proper drivers so it can talk with the controller card and find your harddisk successfully.

This is a common problem if your drive isn't on the primary/secondary motherboard IDE controller.

 

[mechBgon]

Full specs of the system would be helpful. I'll take an initial guess: you have one or more Western Digital hard drives, and the WD is on its own IDE cable but is not properly jumpered as Single Drive.

Aside from that, if you have PC3200, then raise your memory voltage to a proper level. Since you don't say what your exact RAM is, I'll throw out 2.7 volts as a blanket recommendation.

 

[monkelyoy]

Thanks for the info. I updated my profile to include some of my system specs.

Regarding my hard drives, I do have 2 WD drives connected to the same IDE cable. They are not connected to a RAID or ATA controller. They are jumpered correctly and are in the same configuration as they were in my last system which worked correctly for 18 months. I also have the same memory as my old system (geil 3200) which also worked without a hitch. In fact, the only new components are the motherboard and CPU.

 

[DAPUNISHER]

Download and run memtest86+, I suspect your ram isn't playing nice in the new board right now. BTW, is it in dual channel?

 

[Ryland]

I have the Geil 3200 running on my A8V Deluxe without a problem.

 

[monkelyoy]

Just a single stick of DDR Ram. I kept it simple for now. Can this program be run from the command prompt?- I've never used it.

 

[monkelyoy]

I don't think it's the memory, either. I has to be something with the IDE interface or the motherboard. It locks up whenever the Windows Setup utility "examines my hardware" or "examines my disc configuration". I may consider adding an SATA drive, loading windows, then trying to recover my data. any other suggestions? I'll try the beta bios tonight.

 

[DAPUNISHER]

If you see that BSOD again write it down and post it please

 

[monkelyoy]

The BSOD says:

A problem has been dectected and windows has been shut down to prevent damage to your computer.

Check for viruses, hard drive configuration, yadda, yadda.

Technical information:

*** STOP: 0x0000007B (0xF894D640, OxC0000034, 0x0000000, 0x00000000)

Wadda ya think?

 

[mechBgon]

Did you raise your memory voltage yet? 2.7 volts, STAT!

 

[monkelyoy]

Yes, I raised the memory voltage without help.

 

[mechBgon]

two seperate IDE hard drives but it keeps hanging

If you used one WD by itself, which I'm not positive you did, then you'd want to jumper them for Single Drive. They are pretty predictable about causing trouble if they're solo on their cable and still jumpered as Master or Slave.

 

[DAPUNISHER]

Give FDISK a go

 

[kogase]

That "Single Drive" would be CS, or "Cable Select".

 

[Skoop]

Unplug the second drive. FDISK the remaining one.

 

[mechBgon]

Originally posted by: kogase
That "Single Drive" would be CS, or "Cable Select".

On WD's recent drives, Single Drive is taking the jumper off the pins entirely.