nForce Driver 6.65 x32/x64

[garikfox]

To avoid damaging system, please do update the chipset driver to below version prior to the newer BIOS (I updated BIOS first though myself, Reason being is these drivers need nVRAID BIOS 4.84)
For WinXP 32bit system, please download and update chipset drivers V6.65
For WinXP 64bit system, please download and update chipset drivers V6.65
For Win2k/2003 32bit system, please download and update chipset drivers V6.66
For Win2003 64bit system, please download and update chipset drivers V6.66


x32 - http://dlsvr03.asus.com/pub/ASUS/misc/utils/nvidia/Chipset_WINXP32_V665.zip

x64 - http://dlsvr03.asus.com/pub/ASUS/misc/utils/nvidia/Chipset_WinXP64_V665.zip


Fresh Install (RAID) How To:
---------------------------

1. Extract the package to your favorite folder.

2. Go into the IDE/WinXP/sataraid folder.

3. Put all the contents onto a blank floppy.

4. Delete the sataraid folder.

5. Now the package is ready for the nForce driver install once windows is installed.

6. Install WinXP normally with the infamous F6 driver install etc.

7. Make sure too install BOTH drivers.

8. After WinXP is installed load up that package you made previously. And install all three options. Then restart, And now you have IDE at the same driver as RAID 5.34.

 

[FastEddie]

I noted the warning @ Asus Downloads. I don't completely understand it though. nVidia has driver package 6.66 for NF4 (for Win XP & W2K), currently available for dl. How does the Asus warning impact these nv drivers?

 

[garikfox]

Yes thats where I got the info from.

The only reason why I posted this is cuz ALOT of RAID people are haveing trouble with 6.66. BUT ASUS came too the rescue, And I explained it well I thought.

 

[FastEddie]

I'm running a raid 0 array and haven't had a lick of trouble with the nv 6.66 drivers. That's why I asked. Appearantly I shouldn't be using the nv 6.66 (according to Asus), but should be using the Asus 6.65 driver pack.

 

[garikfox]

Originally posted by: FastEddie
I'm running a raid 0 array and haven't had a lick of trouble with the nv 6.66 drivers. That's why I asked. Appearantly I shouldn't be using the nv 6.66 (according to Asus), but should be using the Asus 6.65 driver pack.

Your correct.

 

[MaxisOne]

YOU ARE A !@#@$@#$#@ GOD SEND !!! I almost pulled my Friggen Hair out Last night and his morning over the damn Raid O Issue.. and windows xp 64.
Its working ok right now but i did everything FUBAR.

I used the initial bios ver 1001
I used the initial Chipset for raid (The one on the CD)
And now when i try to update with the latest Its a whole bag of headeache (Had to system restore around three times)
I also updated the bios without to 1006 but keep in mind that i cannot update the raid since i used the old Asus Cd Driver.
Right now i have no errors but My system WONT shut down on its own.. I think a fresh reinstall is in order here.

Thanks for the Guide ill make sure to follow it to the T

 

[AgentK7]

Is the warning for the A8N-E 1006 BIOS specifically referring to RAID users?

I am not running RAID and am just using the standard Microsoft IDE driver.

 

[garikfox]

Originally posted by: MaxisOne
YOU ARE A !@#@$@#$#@ GOD SEND !!! I almost pulled my Friggen Hair out Last night and his morning over the damn Raid O Issue.. and windows xp 64.
Its working ok right now but i did everything FUBAR.

I used the initial bios ver 1001
I used the initial Chipset for raid (The one on the CD)
And now when i try to update with the latest Its a whole bag of headeache (Had to system restore around three times)
I also updated the bios without to 1006 but keep in mind that i cannot update the raid since i used the old Asus Cd Driver.
Right now i have no errors but My system WONT shut down on its own.. I think a fresh reinstall is in order here.

Thanks for the Guide ill make sure to follow it to the T

Fresh Install.

 

[garikfox]

Originally posted by: AgentK7
Is the warning for the A8N-E 1006 BIOS specifically referring to RAID users?

I am not running RAID and am just using the standard Microsoft IDE driver.

U could still load them up youll end up with just IDE at version 5.34

 

[Glocker Dude]

I'm not a RAID guy, but was going to update to 1006 anyhow. So after reading the "WARNING" to upgrade the chipset to 6.65 I did.....or at least I tried. I took all of the chipset install options even though I'm not running RAID and my system went belly up after the first reboot. Lost internet connection for 2 days. Had to play around with the ethernet drivers and bus mastering. I rolled back, installed from install CD just about everything I could do and nothing would make system run smooth. I even got it to a boot up when it was running my startup files and it hit something and I got a BSOD and it would reboot. Something was added to my WINSOCK so I reset it and got connectivity and played on the internet last night. Today on first boot up I got cursor arrow on a blank screen. I finally went into SAFE mode and was able to restore to Aug 10 and everything seems to be working smooth again as before.

Problem is now I'm not sure what drivers I have where? Hopefully it resotred installation CD drivers, although I didn't think a RESTORE could do that. I can't imagine what I have that is different that would cause problems with the CHIPSET 6.65 update. ANY IDEAS OUT THERE ????

Here is what I have....started with clean drive formatted and fresh install of Prof XP
1. Antec Sonata case with 24 pin power adapter cable (380W True power supply)
2. X600 ATI AIW Express graphics card
3. Hitachi SATA II 160G drive with drive unlocked for SATA II
4. Venice 3000 CPU
5. 1 meg Kingston memory (2X512)
6. XP Professional (clean install)
Can't think of anything else that might affect system drivers.

I haven't read of anyone else with Nforce4 chipset upgrade problems so I'm not sure what I going on with my setup.

 

[MaxisOne]

Ok Ive Got the Sata Raid Working perfectly and to my liking ... Then I decided to add a liitle spice to the mix... My Old 120 GIG Ide Hard Drive and my OLDER 40 gig Hard drive .. Whats even more interesting is the Fact that the 120 gig has regular windows xp on it WITH the OS pagefile on the 40 Gig. (Dear lord Help me!!) .. Sos i slept on it and decided to take the plunge and add it to my Current Sata Raid system running Windows XP 64 and see if i can have everybody happy in one PC case .

So
Configured Sata 1 and 2 as Raid (windows xp 64 running smooth as glass) Set this to boot Second
Configured the IDE 120 GIG (Running regluar windows xp with nforce 3 chipset already installed... eeek !!) Set this to boot First and pray
Configured the IDE 40 GIG Containing windows xp Pagefile for the 120gig above as IDE Primary Slave
Configured the IDE DVD Rom and CDRW as Secondary Master and Slave accordingly

Booted .. Problems ... Windows Detected everything and was swapping out accordingly but it was starting to ask for CDs for drivers...
Solution ... Ignore Windows .. Proceed directly to Uninstall Nvidia Chipset drivers for Nforce 3 (Drive was connected to my NEO 2 Platinum before wihch is Nforce 3)
In the mean time .. Went and obtained Nforce 4 6.66 drivers on CD for windows xp for when I boot again and it asks for drivers
Booted again .. Started detecing everything and the usual asking for CD ... Press cancel on everything and installed Nforce 6.66 Drivers
Rebooted .. It found Everything and "more" I had 3 Raid devices for my sata raid .. something had to go.. I deleted the one that had the red X on it and rebooted
It then Detected and installed the Individual Drives for the raid and said I needed to reboot again.
After Doing this .. viola !!! My Raid Drive is showing up on "My Computer" ... but there was still another problem... Another pesky raid device driver showed up in the Device manager with the Yellow icon on it... So I decided to .. Disable it (To see if anything would go wrong.. After verifying that everything was still operational and that it would not autodetect anything else I uninstalled it) It went away without even asking for a reboot which probably means it wasnt associated with anything . I rebooted again 2 times for good measure and everything is fine and dandy !!!
I think I just sucessfully passed through the most complicated/Scary Hardware/Software upgrade to date for me and ive been doing this over 13 years since 286 days

So I managed to get the Windows xp to work fine ... I would asssume that when i set the raid as first boot and the Windows xp 64 boots up It should not have any problems detecting the 120Gig and the 40 gig hopefully

Cheers


Update .. Set Raid as Primary Boot drive ....Loaded up Win xp 64 Autodected the Drives and the CD rom Drives ... Good to Go .. !!!
So

Raid 0 Holding Windows xp64 Installed and optimal
IDE Primary Master Holding Windows XP Installed and optimal

I couldnt ask for a better Upgrading Weekend.. Thanks for the Help with the Raid install Garick

 

[garikfox]

Glad you got it working correctly, Took me Probably about 6 mos. to figuire this all out, Also whats funny is im still seeing people post about the RAID probs they have etc. Too bad they cant read, LoL

 

[ss284]

Updating to the 1.013 bios was hell for me. It wouldnt let me computer boot off my drive at all. I was using 6.66 at the time. Im guessing asus fvcked up yet again with their board design and had to release some buggy bios mixed with some buggy drivers. I really really love my a8n-sli deluxe.

-Steve

 

[sandeep108]

Sorry intended to post in the A8NE thread.

 

[garikfox]

Bump...

This Post is "Very" Serious Most people have disregarded the importance of this..

But in Fact. It's the Truth.

Sticky Please...

 

[photoguy99]

This nor anything else works for the TYAN K8SE (2992).

It will simply not run RAID 1.

Tyan has verified the problem and said sorry we'll have to contact engineers in Taiwan.

This is so much fun. I might try posting at PlanetAMD64 since I'm not sure if it's x64 related.


Windows Server 2003 64-bit
Dual Opteron 246
4GB RAM
4.8 TB RAID 5 (3Ware)
160 GB RAID 1 (NVRaid) Hopefully

 

[benlperkins]

Why do you list

4. Delete the sataraid folder.

as a critical step in your HOWTO? Does it actually make a difference in your install if you don't delete it?

The reason I ask is that I'm using an A8N-E motherboard and having shutdown/startup hangs under WinXP (32 bit) regardless of whether I use 6.66 from Nvidia or 6.65 from ASUS. Oddly, these problems happen only if I'm in non-RAID mode. If I set up my Maxstor MaxLine III drives in Raid0, Raid1, or JBOD mode, I'm able to install XP, install the chipset drivers, and get all the way through the XP patch sets from Microsoft without problems.

If I turn off RAID and try the install using bare SATA, somewhere in the process I start getting the hangs on shutdown.

Also, in one of your posts you seem to indicate that the 5.34 drivers are the critical piece of the puzzle. Regardless of whether I install with 6.66 from Nvidia or 6.65 from ASUS, both my Raid Controller Driver version and my SATA driver version report as being 5.10.2600.534. Were you expecting that from 6.66 I should see a higher version? Or are you suggesting that ASUS somehow changed the driver but left the version number the same?

Thanks for any suggestions.

 

[garikfox]

Updated to Top! To help me quit scanning motherboard furum for my post, That continiously is helping people.

 

[Doctorweir]

I also got several issues since going to 1013 paired with 6.66/6.65.
In the mood for a fresh install yesterday I did that and no changes: The system freezes randomly after some time (could be one hour, could be up to four), even if just sitting there and doing nothing...not while working hard...
Damn...I really consider back to 1011 & 6.58 :frown:
Oh...x32...haven't tested my x64 yet how long it's stable...

 

[sloblox]

Text I'm not a RAID guy, but was going to update to 1006 anyhow. So after reading the "WARNING" to upgrade the chipset to 6.65 I did.....or at least I tried. I took all of the chipset install options even though I'm not running RAID and my system went belly up after the first reboot. Lost internet connection for 2 days. Had to play around with the ethernet drivers and bus mastering. I rolled back, installed from install CD just about everything I could do and nothing would make system run smooth. I even got it to a boot up when it was running my startup files and it hit something and I got a BSOD and it would reboot. Something was added to my WINSOCK so I reset it and got connectivity and played on the internet last night. Today on first boot up I got cursor arrow on a blank screen. I finally went into SAFE mode and was able to restore to Aug 10 and everything seems to be working smooth again as before.

6.65 driver listed on the ASUS site for the A8N-E is NOT for the A8N-E at all, it's actually for the A8N-SLI.

 

[jchampion]

Hi,
I'm having similar problems with an A8N-E motherboard. I've been able to configure the raid ok for two SATA 200GB drives, and XP pro works fine with it. The problem is that I tried to add a backup drive (300GB SATA) as non-raid. The BIOS has trouble finding the drive in this mixed environment. Sometimes it works, then the next time I boot, the problem returns with no known change to the system. I've tried moving the drives to different ports, I've tried 6.65 and 6.66 drivers, I've tried BIOS 1001, 1006, and 1008, and nothing fixes the problem. I even thought it could be a problem with the new drive, so I exchanged it for another one and still had the same problem.

The first evidence of the problem is that the BIOS takes a long time discovering the drives (and when you look in the BIOS setup, the 300GB drive is not there). When it's working ok, the discovery process goes very quickly. Is anyone else having similar problems?

Note: if it makes any difference, I also have two IDE hard drives plugged into PATA, plus two DVD drives.

John

 

[Steve1077]

I'm still using bios 1005 with my A8N sli premium, I used the raid drivers on the Asus CD to install windows xp as the latest version blue screened as soon as windows booted the first time, I used both 6.65 and 6.66, if you look at 6.65 they are the same version and date as 6.66 with the audio drivers and applications removed, anyway when I try to update the raid drivers in windows it wont update, is this normal? It starts to install the new ones and stops saying it cant get access to the device or something like that, but the ide and sata drivers are the latest version, everything works fine as far as I can see but I find it odd the raid drivers wont update, is anyone using 534 raid drivers with bios 1005? At the moment I?m using 521 and cant update

 

[Steve1077]

It seems I needed bios 1006 to update to the latest raid driver