nForce4 AMD Edition (6.66)

[imported_Husky55]

The 6.66 drivers contain:

1. Ethernet
2. IDE
3. Audio
4. SMBus

I wonder which component caused all the BSODs. No Nvidia audio still caused crash. Either Realtek or Creative Audigy drivers were used instead. So audio did not cause the crash.

I used Realtek drivers right now.

Nvidia IDE drivers were working for some people, CQuinn reported better speed. Are they more stable than MS IDE drivers, I am using right now? I guess there are SATA and RAID drivers involved in here which might caused the BSODs.

Nvidia Ethernet drives included the NAM. I have an old NAM which is working OK although some Port Forwarding features do not seem to work.

Finally the SMBus might be an useful upgrade.

With all the reported problems, I hesitated to pull the trigger although I did set a restore point.

May be an incremental install might be the answer here to isolate what the problem is.

 

[SilverTrine]

Edition 6.66? :evil:

 

[Aldoria]

Originally posted by: CQuinn

Originally posted by: Aldoria
Hiya CQuinn,

I did exactly what you did, but have you ever went back into add/remove programs and checked to see what you can and cannot remove with the NVidia uninstaller? For some reason, IDE Driver was not one of the option for uninstall even though I "reinstalled" it with the 6.66 drivers (just to test). I figure that some file didn't get updated when I reinstalled the IDE Driver from the newest 6.66 chipset and since I had it removed previously.

Ald

In Add/Remove Programs, I have an entry for Nvidia drivers, and one for Nvidia Nforce Drivers.
Clicking on "Nvidia Nforce Drivers" doesn't have any effect, but Nvidia drivers does list the IDE driver for me.

Previously, I just went thru Device Manager, and rolled back the drivers to the Windows defaults. You might check how
your setup looks there.

I did go into Device Manager and make sure the driver version numbers are those of the new 6.66 chipset drivers (IDE, PATA, SATA) and it looks correct. Maybe it's a registry that didn't get updated for me since I also went into Windows/System32 and made sure that the newest uninstaller got copied as well and it is.

Ald

 

[Aldoria]

Update on my add/remove program deal. I think I "fixed" the problem by just going into regedit and adding the IDE Driver key to the list of uninstalls. I of course had to copy the uninstall file to windows/system32 directory as well. For some reason, the .nvu file didn't copy so I just did it manually and it lists it correctly now, though I haven't tried to use it to uninstall yet but I have faith it will work

Ald

 

[the cobbler]

Unless you are running DriverCleaner or the Nvidia Cleaner, there is going to be crap left over that will bung up Windows and cause problems. You should never, ever install nVdia platform or FW drivers over existing drivers, just asking for trouble.
Best way to install new nvidia chipset drivers:

download DriverCleanerPro
turn off modem or disconnect
RESET GPU OVERCLOCK TO DEFAULT. THIS IS MUUUUY IMPORTANTE!!! (you do not have to bring your CPU back to default, but it can't hurt)
turn off firewall and A/V

1. add/remove programs: first, turn off NAM and uninstall - reboot. Then uninstall all nVidia drivers, including display and audio. also uninstall Realtek audio under separate Realtek entry if you're using Realtek.
2. reboot into safe mode
3. run DriverCleaner Pro's CAB cleaner on driver.cab but NOT SP2.cab
4. run DriverCleaner Pro's Nvidia Driver Cleaner. Use multiple filters for nVidia Chipset, nVidia(display), nVidia audio, Realtek audio. DO NOT clean IDE or RAID drivers or you will hose your installation and have to reinstall Windows.
5. empty recycle bin and reboot normally
6. when Windows prompts you to install new hardware it found, hit cancel in each popup
7. run the nVidia 6.66 installer. you may choose not to install both nVidia audio drivers and nVidia IDE SW drivers. reboot when prompted
8. if you didn't install nVidia audio in (7), install Realtek drivers instead. reboot.
9. run the nVidia installer for the ForceWare drivers of your choice. reboot.
10. set up your display options again, bring your overclock gradually back up and you're done.

use DC Pro according to its instruction and you will never have headaches from nVidia drivers gooping up the place.

I just want to try these out to see if the NAM has been fixed. I loved it, especially the Active Armor TCP/IP accelerator function, until it started randomly producing BSOD's yesterday after two weeks of use. bleh.

 

[NokiaDude]

Just unistalled 6.53 drivers and installed 6.66 on an Asus A8N-SLI Deluxe. I didn't get any BSOD's and the update was painless. I'll report back on how 6.66 improved or made things worse.

 

[Capt Caveman]

Cobbler, thanks for the useful information. I tried following your instructions and was half-successful.

Uninstalling and cleaning the drivers was a frustrating task. A number of BSODs. And my ATI video card drivers were some how removed.

I was finally able to install the 6.66 drivers. Installed my ATI video drivers. But everytime I booted-up I would get the BSOD, until I figured it was the Nvidia Firewall. I have always left it at Anti-hacking mode but when I turned if off completely, my system is running again.

Any ideas on why this is happening?

 

[n7]

I m surprised they didn't skip the 6.66

 

[MadScientist]

Originally posted by: the cobbler
I just want to try these out to see if the NAM has been fixed. I loved it, especially the Active Armor TCP/IP accelerator function, until it started randomly producing BSOD's yesterday after two weeks of use. bleh.

Using your method of installation, where you able to get all of v6.66, including NAM, installed and running stable, no BSODs?

 

[MadScientist]

Originally posted by: wetcoastguy
I had a look at the Nvidia page yesterday. I could swear that they recommend uninstalling first before installing the new drivers.

Why wouldn't someone take their advice?

Did it, done it, still BSODs.

Nvidia link

 

[Mucker]

6.66

* Audio driver 4.62 (WHQL)
* Audio utilities 4.51
* Ethernet driver 4.82 (WHQL)
* Network management tools version 4.88
* SMBus driver 4.45 (WHQL)
* NVIDIA PATA RAID driver 5.34
* NVIDIA SATA RAID driver 5.34 (WHQL)
* NVIDIA SATA IDE driver 5.34 (WHQL)
* NVIDIA RAID Application 4.82
* Installer 4.78

6.53

* Audio driver 4.60 (WHQL)
* Audio utilities 4.51
* Ethernet driver 4.75 (WHQL)
* SMBus driver 4.45 (WHQL)
* Installer 4.60
* IDE NVIDIA driver 5.18 (WHQL)

For me, I don't use raid, or audio, so I didn't install them. Also, the SMB driver versions are the same between 6.66 and 6.53 so no need to update. So, that left me with updating only the IDE and Ethernet drivers which I did with zero problems. I uninstalled the ide first and installed the new driver and then did the same for the ethernet. Versions are reading correctly. It looks like my ide benchmark went up a tad. No problems here...

m

 

[imported_Husky55]

Well, I just wasted the better part of today, Sunday, messing with Nvidia 6.66 and 6.53 drivers.

I have to say I am really disappointed with Nvidia and their drivers uninstall and install programs.

I have uninstalled all the drivers, used DriverCleaner Pro2, installed in whole and/or in part of various parts of the drivers and my results:

1. NAM is now totally not working, independent of versions, 6.37, 6.53 and 6.66. It was working pecfectly well before at 6.37, except port forwarding. Now I cannot even open the application. Why? I don't know. Seemed to install fine.

2. Ethernet and NAM created BSODs. I lost my Ethernet connection during various iterations of installs.

3. IDE drivers also created BSODs. Yes, old drivers were uninstalled. Nvidia IDE drivers are what they are reputed to be, bad, buggy and just not working.

4. Windows System Restore saved Windows but could not saved NAM.

Since Nvidia at the moment owns AMD 64 processors including the X2 series, I really have to think twice about building another system with Nvidia chipset.

My Epox is only a couple weeks old from the egg, but it is a revision 1.xx. Don't know if this is a problem.

Anyway I owe the good people of this thread who posted and shared their experiences.

 

[MadScientist]

Husky55,
I was just about to try installing v6.66 again without NAM using the same method you tried. Glad I checked back here first. I also have an Epox 9NPA+ Ultra board. After I did a system restore after my first attempt I uninstalled what was left of the nvidia drivers and then did a fresh install of v6.37. Everything is working again, including NAM.

 

[Regulator07]

tried installing the drivers right over the 6.53 drivers, got that 1156 dialog box at the end, then i restared and then bsod everytime i got into windows. i installed the 6.53 drivers over the 6.66 before the computer bsod and everything is good right now. i find it rediculous that nvidia doesnt catch this sh!t before they release the driver.

 

[GadgetBuilder]

Some things never change -- the 6.66 release is like the prior releases, where the majority of users will have no difficulty and about 2% of owners will have very serious problems. It is not predictable which systems will encounter problems, it seems to be random. When problems are encountered the most effective thing to do is a clean install of XP followed immediately by the nVidia mobo drivers.

I've been harping on this for a while, more details here:
http://forums.anandtech.com/messageview.aspx?catid=29&threadid=1633257
http://forums.anandtech.com/messageview.aspx?catid=29&threadid=1634087

Some things are predictable, though:

1) Someone who successfully installed the drivers will be along shortly with the answers to all the problems others are having installing the drivers.

2) Someone else will acknowledge that a very small minority of systems encounter problems but opine that it is not economically rational for nVidia to address these problems because so few units are effected.

3) nVidia will not acknowledge a problem with their drivers (nor do they have a contact mechanism which would allow a user to complain about the drivers). Party line: "We make chips, see your mobo manufacturer if you encounter problems with your system".

4) Mobo manufacturers don't write the drivers so they will not or cannot address the problem so they too will not acknowledge a problem with nVidia's hardware or software.

5) NF4 systems will be known as the best performing mobo's available -- and the driver complaints will continue.

As long as 98% of driver installs go well, I doubt things will change...

If you're part of the 2% where things don't go well, try a clean install -- it is the best hope you have.

 

[SupraTran]

I installed over the 6.53 drivers and everything seems the same but my audio drivers got messed up, my sound doesnt play anymore.....this problem always occurs though when I install new drivers :-(

 

[Jaxidian]

Originally posted by: GadgetBuilder
<<snip>>
If you're part of the 2% where things don't go well, try a clean install -- it is the best hope you have.

true dat, unfortunately...

 

[Nocturnal]

I wasn't able to upgrade as I formatted my system anyway. I installed the 6.66 drivers. I first left out the IDE drivers just to be on the safe side. I just came back from rebooting as I installed the SATA/IDE drivers seperately. So far so good, I will report back if anything happens.

 

[homercles337]

Originally posted by: the cobbler
Unless you are running DriverCleaner or the Nvidia Cleaner, there is going to be crap left over that will bung up Windows and cause problems. You should never, ever install nVdia platform or FW drivers over existing drivers, just asking for trouble.
Best way to install new nvidia chipset drivers:

download DriverCleanerPro
turn off modem or disconnect
RESET GPU OVERCLOCK TO DEFAULT. THIS IS MUUUUY IMPORTANTE!!! (you do not have to bring your CPU back to default, but it can't hurt)
turn off firewall and A/V

1. add/remove programs: first, turn off NAM and uninstall - reboot. Then uninstall all nVidia drivers, including display and audio. also uninstall Realtek audio under separate Realtek entry if you're using Realtek.
2. reboot into safe mode
3. run DriverCleaner Pro's CAB cleaner on driver.cab but NOT SP2.cab
4. run DriverCleaner Pro's Nvidia Driver Cleaner. Use multiple filters for nVidia Chipset, nVidia(display), nVidia audio, Realtek audio. DO NOT clean IDE or RAID drivers or you will hose your installation and have to reinstall Windows.
5. empty recycle bin and reboot normally
6. when Windows prompts you to install new hardware it found, hit cancel in each popup
7. run the nVidia 6.66 installer. you may choose not to install both nVidia audio drivers and nVidia IDE SW drivers. reboot when prompted
8. if you didn't install nVidia audio in (7), install Realtek drivers instead. reboot.
9. run the nVidia installer for the ForceWare drivers of your choice. reboot.
10. set up your display options again, bring your overclock gradually back up and you're done.

use DC Pro according to its instruction and you will never have headaches from nVidia drivers gooping up the place.

I just want to try these out to see if the NAM has been fixed. I loved it, especially the Active Armor TCP/IP accelerator function, until it started randomly producing BSOD's yesterday after two weeks of use. bleh.

You cant be serious. You really think nVidia would release drivers that require this kind of effort?

 

[imported_Husky55]

Originally posted by: MadScientist
Husky55,
I was just about to try installing v6.66 again without NAM using the same method you tried. Glad I checked back here first. I also have an Epox 9NPA+ Ultra board. After I did a system restore after my first attempt I uninstalled what was left of the nvidia drivers and then did a fresh install of v6.37. Everything is working again, including NAM.

I have NEVER had any problem with updating drivers, be they BIOS, graphics, chipset (Intel) or myriads of upgrades.

I am happy for you MadScientist, at least you are back to where you were. I had to uninstall NAM because I could not make it work.

This is almost beyond belief. I cannot believe this is happening to me. I have built about 12 systems in the last 5 years alone and I always fixed any problem I have had.

But this is insane. When did you ever heard about Intel chipset drivers problems? IDE problem? Ethernet problem?

:disgust:

 

[imported_Husky55]

Originally posted by: Jaxidian

Originally posted by: GadgetBuilder
<<snip>>
If you're part of the 2% where things don't go well, try a clean install -- it is the best hope you have.

true dat, unfortunately...

My system is a couple of weeks old. Windows was activated with SP2 and all the latest updates.

Why do I have the problem?

So I am in the 2% now which have the problem?I would say that Nvidia released a very buggy driver.

:disgust:

 

[bob661]

I followed the cobbler's instructions and the install was flawless. I have to admit that the system seems a bit peppier. Boot up time was quite a bit quicker. Maybe I'll even try updating my bios. Thanks much dude.

 

[SupraTran]

My Sound WOnt Work now..............Danm Drivers

 

[Capt Caveman]

Alrighty, playing around I've been able to isolate the issue to enabling Active Armor. I reinstalled the NAM and when you turn-on the firewall to anything, it also enables Active Armor. So, after I changed the Firewall to Anti-Hacking, I then disabled Active Armor and now my system is running fine.

Is anyone able to run Active Armor?

 

[Aldoria]

Originally posted by: Capt Caveman
Alrighty, playing around I've been able to isolate the issue to enabling Active Armor. I reinstalled the NAM and when you turn-on the firewall to anything, it also enables Active Armor. So, after I changed the Firewall to Anti-Hacking, I then disabled Active Armor and now my system is running fine.

Is anyone able to run Active Armor?

This might turn on a lightbulb in your quest to find the problem. I've been running wireless internet the whole time in my house, but then I went to a LAN party. The whole time at my house, I was running with all Active Armor settings with no problem whatsoever. But the instant I plugged in a lined ethernet cable, yay BSOD. I mean... I can produce BSOD on the fly, it was quite amazing! lol Simply just plug in the ethernet cable and there it goes. So I just uninstalled all of the Network Management Driver set and everything was just fine. Oh and of course I had to give the ethernet interface back to Window's Firewall instead of Active Armor

Ald