• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

New NF4 Standalone Drivers 6.53

Man, I wish this was good news but my machine started to give me "insert system disk errors) and sometimes it would get to the Win XP screen and then crap out on a blank screen. I had to reset my CMOS to boot up again. I will try uninstalling the IDE driver and see if that fixes it.
 
I gave 'em a try last night, but ended up re-installing the old drivers. After installing the new set, if I opened up a web page as soon as Windows was up, the home page would start to load, but that's about it. No BSOD's, but it appeared NAM was blocking everything. It took several attempts to get the old drivers installed again, but finally got them back in Safe Mode.

Might have to give it another go today.
 
Originally posted by: Trente
Anyone here attempted running these with a K8NF-9?
Click to expand...

I did install them on my computer, all the set except the audio drivers and thay gimme not problems at all. The IDE works good for me and I'll use it, as I did with all of the other.


Could not try the LAN drivers as I'm still on dial-up.
 
On my Gigabyte KA-K8NXP-SLI board the IDE driver on these new Nforce4 drivers cause a BSOD when I run Prime95 on my machine. The BSOD specifically mentions nvatabus.sys. This happened with the previous nforce4 standalone drivers as well as with these new ones. However, after I install the 6.31 IDE driver from Gigabyte here...

http://www.giga-byte.com/Motherboard/Support/Driver/Driver_GA-K8NXP-SLI.htm

Prime95 runs without any issues.

After I installed the new drivers I also got an immediate BSOD and reboot just before Windowx XP Pro got to the desktop. After a resetting the box it seems to have come up ok. I have a feeling that NAM is the culprit. However the last time I tried to uninstall it, it kept BSODing when it booted into Windows.
 
Just the latest and greatest. If you aren't having any problems, there is really no need to install just for the sake of installing. 😉
 
These drivers still have the bug in them where the the PC will become unresponsive when doing a lot of HD work with a RAID 0 setup on the NV controller. The interrupt process which is an invisible process under System Idle Process will hog the CPU totally at random. I really regret setting up a RAID 0 on this board.

Simon
 
Originally posted by: T3mplar
These drivers still have the bug in them where the the PC will become unresponsive when doing a lot of HD work with a RAID 0 setup on the NV controller. The interrupt process which is an invisible process under System Idle Process will hog the CPU totally at random. I really regret setting up a RAID 0 on this board.

Simon
Click to expand...

stange. i have yet to see this one.
i'm using RAID0 on the nv controller...
 
Make sure you roll back the pata nv sw ide controllers to the native ms one after the install of the standalone pk. 😉
 
Originally posted by: FastEddie
Send this up for the daily ingestion.

sxr7171 Did the uninstall of the sw ide fix your problem?
Click to expand...

I don't know. I got a little overzealous and used Driver Cleaner Pro to take out the IDE driver + the Video Driver and my Computer would not boot into Windows at all (even safe mode). So I did a reinstall. I installed the entire driver set including the IDE driver onto the new install and it seems to be working fine so far.

I can't say with certainty that it was the IDE driver that messed things up. I am running stock right now and things might change with an O/C. It seemed to me that it was the IDE before though since all my symptoms were related to the HD.
 

Driver cleaner is alot different than just rolling back a driver set. Looks like you hosed the MBR with that utility.
 
I'm using these drivers (plus GART 4.4.0) on my NF3-250Gb and they are working very well. No crashes and I've had them installed for almost 2 days now.

I just don't understand why NVidia is offering these drivers for "only" NF4 boards... 😕
 
I uninstalled 6.39 and ran driver cleaner pro. I rebooted and reinstalled 6.53 drivers without any problems. I am not sure how one would "hose" the MBR using a file removal utility. Driver Clean Pro is just a handy removal tool and does not perform any low level disk functions.
 
I agree with SilkySmooth. To the best of my knowledge DC doesn't touch the MBR. It deletes driver files, cleans out the cab files, and removes old registry entries pertaining to the uninstalled drivers.

I personally use DC every time I update my drivers. I uninstall all NVidia chipset drivers in windows, reboot into safe mode, run driver cleaner and cab cleaner, and reboot once again into windows and install my new drivers. Never once have I caused an MBR problem using that tool.
 
All this being as they are. When the user ran Drive Cleaner, and was unable to reboot afterward--what would you formally call that? OOPS doesn't count. 😉
 
This also happens to users who do not use Driver Cleaner. There could be any number of reasons why this might happen. One user at DFI-Streets is running a RAID array and uninstalled his nForce drivers prior updating, he also was unable to reboot. He did not use Drive Cleaner. I think the only consensus among users is that it is a driver issue. Probably WinXP not rolling back to default MS drivers after uninstalling nForce drivers. When diagnosing driver issues in WinXP, it could be so many things, it would be premature, if not unfair, to point the finger at Driver Cleaner.
 
When installing a raid array on the nv sata ports, you must be mindfull of not having any ide channels incorporated when enabling Raid Enable, (which allows for the spanning of arrays across pata&sata. Removing an ide channel afterward will hose the ability to boot to the array.

I'm not pointing my finget at driver cleaner as the 100% culprit in hosing the boot sector, (probrably the "between the keyboard and chair error"). But that is like shooting a fly with a twelve gage shotgun. All you have to do is roll back the controllers to the native ms XP ones, instead of combing your system for every registry entry for the nv sw controllers.

Driver Cleaner is a decent program---but so are proper uninstallation procedures for drivers, making Driver Cleaner unneccessary most of the time. It was a good program for uninstalling DirectX, and some nVidia beta driver packages---but my point is that it's not really needed everytime you uninstall a device. 😉
 
Did anybody else start getting a longer shutdown time after installing these? I'm using a DFI Lanparty UT NF4 Ultra-D with the latest BIOS.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top