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.

    holy ramhogs fingerprint reader!

    Discussion in 'Sager and Clevo' started by loki714, Jan 30, 2008.

  1. loki714

    loki714 Notebook Enthusiast

    Reputations:
    0
    Messages:
    27
    Likes Received:
    0
    Trophy Points:
    5
    np5792
    i've caught my fingerprint reader at 3gigs of mem usage (what the hell!?)
    why's the lil bugger of a process taking up so much mem? and 3 gigs of my 4?! really?! that's insane...

    anyhow.. is there a way for it to turn off after log in?
     
  2. Gophn

    Gophn NBR Resident Assistant

    Reputations:
    4,843
    Messages:
    15,707
    Likes Received:
    3
    Trophy Points:
    456
    there's been shown that the fingerprinter reader software has a memory leak... which causes that.

    I am not sure if there is an update for it yet, I recommend to contact your vendor about it... to see if there is an update for it.

    Other than that... I would disable it if you are not going to use it for now until you get the update software.
     
  3. rexdp10

    rexdp10 Notebook Consultant

    Reputations:
    73
    Messages:
    170
    Likes Received:
    0
    Trophy Points:
    30
    I have had the same problem. With mine it's the plqsl.exe or something like that. That program runs at startup, and if given the opportunity will leak memory. I just have that disabled as a startup service and the fingerprint reader still works. I can log into windows, and from a Locked PC. The stuff that is leaking the memory is the small application associated with the fingerprint reader and doesn't appear to be the driver itself so it doesn't have to be running.
     
  4. Duct Tape Dude

    Duct Tape Dude Duct Tape Dude

    Reputations:
    568
    Messages:
    1,822
    Likes Received:
    9
    Trophy Points:
    56
    I used to have this problem more often on Vista64, ever since swapping out to 32 bit Vista I've been doing fine.

    The process was psqltray.exe for me, and yes it is a memory leak as stated above. I just killed it via task manager and then ran the exe again to resolve it.

    If you don't want it to run on startup you can play with MSconfig (winkey+R, type "msconfig") and disable it from there. If what rexdp10 said is true about logging in without the process you should have no problems :)
     
  5. icecubez189

    icecubez189 Notebook Deity

    Reputations:
    218
    Messages:
    1,305
    Likes Received:
    0
    Trophy Points:
    55
    I had the same problem with my Protector Suite QL fingerprint reader software, but it only happened after playing Counter Strike: Source. I asked for help and a member was kind enough to provide me this link for a fix: http://files.upek.com/GetFile.asp?Ke...EII56X480D2911

    hope it works for you too, i no longer have memory leakage