The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Current wireless driver has a memory leak problem ...

    Discussion in 'Dell XPS and Studio XPS' started by kuram, Sep 14, 2008.

  1. kuram

    kuram Notebook Consultant

    Reputations:
    0
    Messages:
    168
    Likes Received:
    0
    Trophy Points:
    30
    The current wireless driver I have for the "Dell Wireless 1505 Draft 802.11n WLAN Mini-Card" is this one : "R174291" or also named this by the install exe: "Dell_multi-device_A17_R174291.exe". I've discovered that it has a memory leak problem, and its been eating my memory for the past few weeks, eventually maxing out my pagefile at 6.8gb preventing me from doing anything (i have 3gb ram).

    I run my system on XP32, and its the model xps 1530. I was wondering if somebody could help me find a better, or at least more functioning wireless driver? Thanks alot in advance!
     
    kuram, Sep 14, 2008
    #1
  2. BatBoy

    BatBoy Notebook Nobel Laureate

    Reputations:
    7,395
    Messages:
    7,964
    Likes Received:
    25
    Trophy Points:
    206
    Try this one...

    R189136

     
    BatBoy, Sep 14, 2008
    #2
  3. kuram

    kuram Notebook Consultant

    Reputations:
    0
    Messages:
    168
    Likes Received:
    0
    Trophy Points:
    30
    The problem isn't so much with the drivers, it's just that one process (bcmwltry.exe) that has the memory leak. It does on both the driver i had, and the one you gave me as well.

    From what i gathered it's not a required process for the wireless card to work, cause my system still detected my wireless card after i cancel the process. Would there be a way to simply block it from starting up? It isn't in the msconfig startup list, so maybe a registry value?
     
    kuram, Sep 14, 2008
    #3