nVidia driver(nvnrm.sys) causes BSOD

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

After installing the latest nVidia "ForceWare" package (ver 4.82 network
driver &
build 4.88 NAM), any attempt to alter my NIC configuation from the default
settings
results in a BSOD naming "nvnrm.sys"(nVidia Network Resource Manager) as the
culprit. This driver version is supposedly on the WHQL for XP, so why the
BSOD?
Any way to determine what the "real" cause of this conflict is? Have tried
the "uninstall/reinstall" routine and receive no errors/warnings of any kind
anywhere until I attempt to alter my NIC config, either in the NAM interface
or in the
windows device manager, then I get the BSOD--same one every time. Everything
else works perfectly, including the much maligned nVidia Firewall(NAM). How
do I
get windows to accept this driver so I can alter my NIC configuaration?
 
Depending upon which M/B you have, the latest released driver is 5.10, from
Sept. 2004.

--

Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
Thanks for responding. I have an AMD Athlon and I d/l and installed the
package
from nVidia (nForce4_amd_6.66_winxp2k_international.exe) on 10/3 which
contains
the ethernet drivers (including nvnrm.sys) with a version of 1.0.0.482, dated
4/6/2005. The NAM-Network Access Manager- in this package is version
2.2.0.488,
dated 4/26/2005. All are WHQL certified for WinXP and are listed as such
("signed")
in the Device Manager. nvnrm.sys in particular is listed as a "signed"
driver under
the "NVIDIA Network Bus Enumerator" in the Device Manager. I recieved no
errors
or warnings regarding "unsigned drivers" when installing the package.

I suspect that the "older" version you are referring to is what is offered
by the
"windowsupdate" site? I rarely install non-microsoft software from microsoft.
Besides, isn't the whole point of the WHQL certification to have a reasonable
expectation that software so certified will be compatable with windows? It
would
appear that my system is not recognizing this certification for one reason
or another
when this driver is called--I only receive the BSOD when attempting to
change any
setting in my NIC configuration, ie "throughput optimization", etc. There
should be
a way to fix this so windows will accept these changes?

If you need more details to help me, let me know.

Thank you
 
Update:
nVidia has released an updated version as of 10/26/2005
(nforce_nf4_winxp32_amd_6.70) which is supposed to contain "General
compatibility fixes for nForce4 AMD Edition motherboards." The version and
build #'s for the ethernet drivers is the same, so we'll see. Will let you
know if the problem is solved.

Thank you
 
Back
Top