Sign in
Microsoft.com
 
Windows Client TechCenter
 
 
 
Windows Client TechCenter > Windows 7 Forums > Windows 7 Networking > Win7 with nForce Driver 15.35 - Bugs!
Ask a questionAsk a question
Search Forums:
 

General DiscussionWin7 with nForce Driver 15.35 - Bugs!

  • Thursday, May 14, 2009 9:33 AMLuCkY2k9 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    NVIDIA certainly is busy offering good Windows 7 support. Here you can find the latest Windows 7 WHQL nForce platform drivers.

    Windows 7 64-bit Driver Versions:

    • Ethernet Driver (v73.06) WHQL
    • Network Management Tools (v73.05) "Sedona"
    • SATAIDE Driver (v11.1.0.23) WHQL
    • SATARAID Driver (v11.1.0.23) WHQL
    • RAIDTOOL Application (v11.1.0.23)
    • SMU Driver (v1.67) WHQL
    • Installer (v7.01)
      •

    Compatible with:

    • nForce 790i Ultra SLI
    • nForce 790i SLI
    • nForce 780i SLI
    • nForce 750i SLI
    • nForce 740a SLI
    • nForce 710a SI
    • nForce 680i SLI
    • nForce 680i LT SLI
    • nForce 680a SLI
    • nForce 650i SLI
    • nForce 650i Ultra
    • nForce 590 SLI AMD
    • nForce 570 SLI AMD
    • nForce 570 Ultra AMD
    • nForce 550
      •
      After installing these drivers, i have multiple problems with DNS Acess, and my Network Connection to my Router get lost every few hours.

      The Event Log dont gimme any information about what happened to the hardware at that time, only the following Errors were shown:
    - System
    - Provider
    [ Name ] Microsoft-Windows-DNS-Client
    [ Guid ] {1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}
    EventID 1014
    Version 0
    Level 3
    Task 0
    Opcode 0
    Keywords 0x4000000000000000
    - TimeCreated
    [ SystemTime ] 2009-05-14T09:16:41.232200000Z
    EventRecordID 6919
    Correlation
    - Execution
    [ ProcessID ] 1156
    [ ThreadID ] 864
    Channel System
    Computer LuCKY-PCwin7
    - Security
    [ UserID ] S-1-5-20
    - EventData
    QueryName messenger.hotmail.com
    AddressLength 16
    Address 02000035C0A802010000000000000000

      In my opinion, this is just a result of the Connection Lost with the new Drivers.
      I have multiple entrys with that, it pops up a few seconds after the connection get lost.

      When the connection is gone, i can reset it with the Troubleshooting option, and it repaires the Gateway, that was "not available"

      Log Name:      System
      Source:        Microsoft-Windows-Diagnostics-Networking
      Date:          14.05.2009 11:16:49
      Event ID:      5000
      Task Category: Validation Success
      Level:         Information
      Keywords:      (70368744177664),Core Events
      User:          LOCAL SERVICE
      Computer:      LuCKY-PCwin7
      Description:
      The Network Diagnostics Framework has completed the repair phase of operation. The following repair option or work-around was executed:

      Helper Class Name: AddressAcquisition

      Repair option: Reset the "Local Area Connection 2" adapter
      This can sometimes resolve an intermittent problem.

      RepairGuid: {07d37f7b-fa5e-4443-bda7-ab107b29afb9}

      The repair option appears to have successfully fixed the diagnosed problem.
      Event Xml:
      <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
        <System>
          <Provider Name="Microsoft-Windows-Diagnostics-Networking" Guid="{36C23E18-0E66-11D9-BBEB-505054503030}" />
          <EventID>5000</EventID>
          <Version>1</Version>
          <Level>4</Level>
          <Task>6</Task>
          <Opcode>0</Opcode>
          <Keywords>0x4000400000000001</Keywords>
          <TimeCreated SystemTime="2009-05-14T09:16:49.440200000Z" />
          <EventRecordID>6922</EventRecordID>
          <Correlation ActivityID="{4853BCC1-E81F-4276-89AE-2D4E9FD4515D}" />
          <Execution ProcessID="752" ThreadID="4476" />
          <Channel>System</Channel>
          <Computer>LuCKY-PCwin7</Computer>
          <Security UserID="S-1-5-19" />
        </System>
        <EventData>
          <Data Name="RootCause">The default gateway is not available
      The default gateway is a device that connects a local network or computer to the Internet. A broadband modem or router is usually the default gateway.</Data>
          <Data Name="RootCauseGUID">{AA537141-C1AF-4BF0-B8A3-FCF94C877AEF}</Data>
          <Data Name="RepairOption">Reset the "Local Area Connection 2" adapter
      This can sometimes resolve an intermittent problem.</Data>
          <Data Name="RepairGUID">{07D37F7B-FA5E-4443-BDA7-AB107B29AFB9}</Data>
          <Data Name="SecondsRequired">70</Data>
          <Data Name="SIDTypeRequired">80</Data>
          <Data Name="HelperClassName">AddressAcquisition</Data>
          <Data Name="InterfaceDesc">Local Area Connection 2</Data>
          <Data Name="InterfaceGUID">{0FCD9DDC-A232-4EF8-9AD4-CEE4932AAA9A}</Data>
        </EventData>
      </Event>

      Mainboard

      Asus P5N64 WS Pro , nForce 790i ultra


      Discuss !
    15min after clean install : exploner.exe Trojan Horse on Win7
     

All Replies

  • Friday, May 15, 2009 10:05 AMLuCkY2k9 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Bump

    After deleting 15.35WHQL, the problem is fixed.
    15min after clean install : exploner.exe Trojan Horse on Win7
     
  • Friday, May 29, 2009 2:28 PMeatfrog Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    There is obviously a problem with rc and later builds of win7 and the nvidia nforce network controller. up to 7077 it worked like a charm, then it started randomly dying.

    ive tried the original drivers and nvidias drivers, but nothing helps. i've tried the dhcp broadcastflag, but it didnt help. otoh why should it since im using a static ip.

    this is quite an odd bug, since it dies so randomly without anything helpful being stated in the event logs. if i am downloading something it seems to die pretty much instantly though.

    i hope microsoft and/or nvidia wakes up to this problem, this is affecting alot of people since the nforce-mobos were quite popular a few years back.
     
  • Friday, May 29, 2009 9:47 PMbZZfZZ Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Same problem here. Running W7x64 RC on nForce 680i LT. No problems with Microsoft driver (1.0.1.211), but if I install those v15.35 drivers my local network is dropping all the time.

    Fix: Just uninstall the drivers, reboot the computer and let Windows install their own drivers.
     
  • Friday, May 29, 2009 10:04 PMeatfrog Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Although I said it in my previous post:
    I've tried that, and it didn't help.
     
  • Sunday, May 31, 2009 3:22 AMBLA8291 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Uninstall nVIDIA Forceware Network Access Manager and restart (maybe twice) and I'm pretty sure you won't have the problem anymore.
     
  • Sunday, May 31, 2009 12:07 PMeatfrog Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I don't have it installed.
     
  • Sunday, May 31, 2009 8:34 PMHellfyre Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I don't have it installed.
    I don't have it installed either, i never install their network manager. Also i was experiencing the issue not only on NVidia based chipsets, but on 3rd party wireless cards. There's an issue with Microsoft's TCP/IP stack, not with the nforce drivers themselves. Either an incompatability when nvidia's drivers are installed, or an issue when doing the latest updates, but clearly the issue is on microsoft's side. this is a SERIOUS bug that transfered from Pre-Beta (Alpha), to Closed Beta, to Public Beta, to RC1 for me, and i don't see it being fixed at ALL. please review, revise, and check on MULTIPLE systems using multiple wireless devices and multiple wireless cards, and post your entire network setup here (what cards you use, what chipsets, what version of drivers you're using, and who makes the devices. Maybe we can find a common issue rather than arguing about who's solution works or not.

    Also, could it be an issue with Routes?

    I'll start:

    Device Description    Type
    D-Link DWA-552 XtremeN Wireless Network Adapter    PCI
    nVIDIA nForce 780i SLI (MCP55PXE) - Gigabit LAN Controller (PHY: Marvell 88E1116)    PCI
    nVIDIA nForce 780i SLI (MCP55PXE) - Gigabit LAN Controller (PHY: Marvell 88E1116)    PCI

    Field    Value
    Network Adapter Properties   
    Network Adapter    NVIDIA nForce 10/100/1000 Mbps Ethernet
    Interface Type    Gigabit Ethernet
    Hardware Address    **-**-**-**-**-**
    Connection Name    LAN1
    Connection Speed    100 Mbps
    MTU    1500 bytes
    DHCP Lease Obtained    5/31/2009 1:13:22 PM
    DHCP Lease Expires    6/30/2009 1:13:22 PM
    Bytes Received    56486969 (53.9 MB) - 66 bytes/s
    Bytes Sent    178281886 (170.0 MB) - 64 bytes/s
       
    Network Adapter Addresses   
    IP / Subnet Mask    10.20.0.18 / 255.255.255.0
    Gateway    10.20.0.1
    DHCP    10.20.0.1
    DNS    10.20.0.1
       

    Type      Net Destination     Netmask                Gateway   Metric  Interface
    Active    0.0.0.0                 0.0.0.0                  10.20.0.1    20       10.20.0.18 (NVIDIA nForce 10/100/1000 Mbps Ethernet)
    Active    10.20.0.0              255.255.255.0       10.20.0.18    276    10.20.0.18 (NVIDIA nForce 10/100/1000 Mbps Ethernet)
    Active    10.20.0.18            255.255.255.255    10.20.0.18    276    10.20.0.18 (NVIDIA nForce 10/100/1000 Mbps Ethernet)
    Active    10.20.0.255          255.255.255.255    10.20.0.18    276    10.20.0.18 (NVIDIA nForce 10/100/1000 Mbps Ethernet)
    Active    127.0.0.0              255.0.0.0              127.0.0.1    306     127.0.0.1 (Software Loopback Interface 1)
    Active    127.0.0.1              255.255.255.255    127.0.0.1    306     127.0.0.1 (Software Loopback Interface 1)
    Active    127.255.255.255    255.255.255.255    127.0.0.1    306    127.0.0.1 (Software Loopback Interface 1)
    Active    169.254.0.0           255.255.0.0           10.20.0.18    30    10.20.0.18 (NVIDIA nForce 10/100/1000 Mbps Ethernet)
    Active    169.254.255.255    255.255.255.255    10.20.0.18    276   10.20.0.18 (NVIDIA nForce 10/100/1000 Mbps Ethernet)
    Active    224.0.0.0              240.0.0.0               127.0.0.1    306    127.0.0.1 (Software Loopback Interface 1)
    Active    224.0.0.0              240.0.0.0              10.20.0.18    276    10.20.0.18 (NVIDIA nForce 10/100/1000 Mbps Ethernet)
    Active    255.255.255.255    255.255.255.255    127.0.0.1    306    127.0.0.1 (Software Loopback Interface 1)
    Active    255.255.255.255    255.255.255.255    10.20.0.18    276    10.20.0.18 (NVIDIA nForce 10/100/1000 Mbps Ethernet)


     
  • Thursday, July 16, 2009 3:42 PMTheTimster Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I removed only the network drivers and rolled back to the built in 7 drivers and i have no isses. IT seems the only bugs present in the 15.35 WHQL drivers are found in the ethernet drivers. Although everything could be plenty snappier on a 780i board with 6gigs of ram with newer drivers. Just go into device manager and right click each NIC and manually update the drivers from those on your computer. Then select the microsoft drivers. Restart and you're all set to go.
     
  • Wednesday, November 04, 2009 12:59 AMmcpwiz Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Thanks, worked for me too.  Using MS drivers for nvidia NIC instead of the new 15.35 Nvidia WHQL drivers fixed it!

    Many thanks!
    Justin Nichols MCSE