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.

    Nvidia GPU Code 43 in device manager

    Discussion in 'Alienware 14 and M14x' started by Infin1ty, Mar 3, 2012.

  1. Infin1ty

    Infin1ty Notebook Geek

    Reputations:
    0
    Messages:
    78
    Likes Received:
    0
    Trophy Points:
    15
    Hey all, I've been having a big issue that no amount of googling or troubleshooting has fixed.

    My Nvidia GPU simply is not working. I've tried two different sets of drivers-each three times- rolling back, updating, fresh installs; but to no avail.

    In device manager the card is stopped with a code 43 "Windows has stopped this because it encountered a problem." The card is not an option for any game or application, and while I've tried opening Nvidia Control Panel, it tells me "Your display is not connected to an Nvidia GPU"

    I did recently just buy a Samsung Syncmaster and was using it right before all this happened. Could it be the monitors drivers have messed something up?
     
    Infin1ty, Mar 3, 2012
    #1
  2. Pete- 7r0jan

    Pete- 7r0jan Notebook Consultant

    Reputations:
    41
    Messages:
    189
    Likes Received:
    17
    Trophy Points:
    31
    try a sys restore??
     
    Pete- 7r0jan, Mar 3, 2012
    #2
  3. Infin1ty

    Infin1ty Notebook Geek

    Reputations:
    0
    Messages:
    78
    Likes Received:
    0
    Trophy Points:
    15
    I'm planning on it as a last resort-next to a clean install of course- but I didn't have time last night, and I'm at work right now
     
    Infin1ty, Mar 3, 2012
    #3
  4. Neil McRae

    Neil McRae Notebook Evangelist

    Reputations:
    57
    Messages:
    428
    Likes Received:
    1
    Trophy Points:
    31
    sounds like the new 555 problem, look on this forum for answer on it not being detected
     
    Neil McRae, Mar 4, 2012
    #4
  5. Infin1ty

    Infin1ty Notebook Geek

    Reputations:
    0
    Messages:
    78
    Likes Received:
    0
    Trophy Points:
    15
    I figured it out, it was the monitors drivers. So I did a restore and it's back to normal. Shame I had to return the monitor though. Thanks for all the help
     
    Infin1ty, Mar 4, 2012
    #5