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.

    Veriface on Lenovo G550

    Discussion in 'Lenovo' started by billaboard, May 16, 2011.

  1. billaboard

    billaboard Notebook Consultant

    Reputations:
    10
    Messages:
    182
    Likes Received:
    0
    Trophy Points:
    30
    Today I've started getting consistent BSOD's on login when I allow the machine to go past the password screen and onto the Veriface login method. It's fine if I'm quick enough to login manually.

    This has worked well since I've had the machine, and the only thing that I know has changed overnight was that I allowed a bunch of Microsoft updates for the Windows 7 32-bit OS.

    I know that most people will stick with a normal login and despise things like Veriface on security grounds, but it has been very useful here.

    Has anyone else found this, or do I need to start looking further into this?
     
    billaboard, May 16, 2011
    #1
  2. AboutThreeFitty

    AboutThreeFitty ~350

    Reputations:
    814
    Messages:
    1,705
    Likes Received:
    0
    Trophy Points:
    55
    I would uninstall Veriface and make sure that is what's causing the BSOD's. Then I would get the latest version of Veriface and see if the BSOD's return.
     
    AboutThreeFitty, May 16, 2011
    #2
  3. billaboard

    billaboard Notebook Consultant

    Reputations:
    10
    Messages:
    182
    Likes Received:
    0
    Trophy Points:
    30
    I think I've solved this. I remembered that I'd reverted to an older display driver about 6 months ago because the machine has a display problem.
    I changed to the current Intel display driver and I haven't had a blue screen since. It looks as though an MS update has clashed with the older driver.
    The display problem is still there though. Try to install drivers when you have a screen-filling display and the whole thing loses lock and gradually fades to blank. I'm plucking up courage to take it to bits to check out the motherboard to screen cable.
     
    billaboard, May 16, 2011
    #3