• 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.

nVidia chipset drivers crippling my comp!!!

Okasa

Member
ok so ive been trying to sovle this problem for prob a month now. this is the third reformat and so i tested for the error after every installation. so i found that once i installed my mobo's chipset drivers, i got the error.

its a Delayed Write Failed Error. i tried to uninstall all the components and then install one at a time to see whats causing it, but i guess i didnt install it all or didnt fix what it f'ed up on my system because im still getting it.....and there isnt a new chipset version out, i have the newest....what should i do? any ideas?
 
I doubt that it's the chipset drivers that are causing this message to appear. Every time that I've encountered this error it's usually a faulty cable, a drive that is fixing to puke, or an unstable pc. Can you pass Memtest, SuperPi or Prime95?

It happens on USB drives as well, and of course there are other things that can trigger the message as well. In some cases an unstable machine will cause this error as well.

You receive a "Delayed Write Failed" error message in Windows XP Service Pack 2
 
brand new build, passes memtest and prime95, replaced mobo, drives, cables, psu, did a complete reformat.

after the complete reformat i tested for the error and it did not occur(TESTED BEFORE INSTALLING CHIPSET DRIVERS)
installed chipset drivers
tested again and the error occurs.
 
do you install the IDE drivers with the rest of the Nforce Drivers?

try leaving that driver out when you reinstall the drivers..the NV IDE drivers are a stinking pile of crap and should never be used.
 
Originally posted by: Stumps
do you install the IDE drivers with the rest of the Nforce Drivers?

try leaving that driver out when you reinstall the drivers..the NV IDE drivers are a stinking pile of crap and should never be used.

I agree that the NVIDIA SW IDE can cause issues on some systems, and it's possible that is the OP's problem with the delayed write failed messages. However they are not a pile of crap and I've installed them on hundreds of systems without a hitch.
 
Originally posted by: John
Originally posted by: Stumps
do you install the IDE drivers with the rest of the Nforce Drivers?

try leaving that driver out when you reinstall the drivers..the NV IDE drivers are a stinking pile of crap and should never be used.

I agree that the NVIDIA SW IDE can cause issues on some systems, and it's possible that is the OP's problem with the delayed write failed messages. However they are not a pile of crap and I've installed them on hundreds of systems without a hitch.

I can get them to work flawless on my NF420/NF2 systems, but as soon as I try to get them working on my NF3/NF4 system I have massive problems..usually when I try to access any of the optical drive I get BSOD's...so I figure that they aren't worth the hassle on later A64 systems and I just leave them out...I don't think there is any real performance difference anyway.
 
They are indeed a pile of crap. Just kidding. But really, they have caused me lots of instability and frustration. I would not install them at least to begin with. We need to rule things out here, and certainly the MS ATAPI drivers are more stable than these NVIDIA ones (at least from my experience). The PATA emulation mode seems rock solid and I haven't had a problem ever since I stopped installing them. If NVIDIA's fixed the problems since, more power to them, but I don't see any advantage to using them besides NCQ (<1% performance increase) and that annoying "safely remove device" icon. Only install NVIDIA graphics/SMBus/ethernet and also don't install the NVIDIA firewall stuff.
 
i only installed the smbus and ethernet drivers from it and nothing else. thought that py problem was solved, but now i got it again. so i actually changed the systempages entry to "ffffffff"(max) to try to combat it, but im worried its a dumb way to do it. hard for me to decide, because im not 100% on what systempages is in the registry. i have 2gb of ram if thats important.
 
well no im not certian i suppose, i mean this was my testing process

install xp
copy huge amounts of files(testing)
intall one nvidia chipset driver(ethernet)
copy huge amounts of files(testing)
install other chipset driver(smbus)
copy huge amounts of files(testing)
error occured several hours later when not transferring large files
 
this thingy usually fixes it:

Finally found the solution. I had to change the LargeSystemCache setting in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management back to zero. One of my users programs is changing this value, haven't figured out which one yet.
--------------------
actually, change all large system cache reg entries to "0" - off
loading vidcard drivers sometimes changes cache entries

The ultimate write failed thread - if you can read more than one sentence before falling asleep. like so many here that want a ten word answer
http://www.hardwareanalysis.com/content/topic/22061/

 
I'm on my seventh NForce motherboard right now and chipset drivers, including SW IDE, have never caused me any instability. Except the 2.41 back in the days when NF2 was brand new.
 
Back
Top