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.

    Display Driver nvlddmkm Stopped Responding and Has Recovered

    Discussion in 'Asus' started by lukos004, Nov 26, 2009.

  1. lukos004

    lukos004 Notebook Enthusiast

    Reputations:
    0
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    5
    Just barely got this laptop 2 months ago and it was working great, now every chance I play my game it the screen goes black and aftewards a pop shows saying "Display Driver nvlddmkm Stopped Responding and Has Recovered" can anyone tell me whats going on? Is it my graphics card or vista?

    I have a G51VX-X2A
     
    lukos004, Nov 26, 2009
    #1
  2. TevashSzat

    TevashSzat Notebook Deity

    Reputations:
    334
    Messages:
    1,438
    Likes Received:
    0
    Trophy Points:
    55
    That implies a drivers problem which implies either you are overclocking too much or your GPU is overheating to a degree. What temps have you been getting?
     
    TevashSzat, Nov 27, 2009
    #2
  3. lukos004

    lukos004 Notebook Enthusiast

    Reputations:
    0
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    5
    I'm pretty sure I haven't touched the overclocking thing on my gpu and I dont know if its overheating, is there a prograb I can download to see what temps I'm getting?
     
    lukos004, Nov 29, 2009
    #3
  4. Abula

    Abula Puro Chapin

    Reputations:
    1,115
    Messages:
    3,252
    Likes Received:
    13
    Trophy Points:
    106
    EVGA Precision 1.8.1 for in game temp display (you have enable it in the options) and HWmonitor 1.15 (dl 1.15setup and run it) just open it before you play, go game and it will record the highest temp you had while gaming.
     
    Abula, Nov 29, 2009
    #4
  5. ASUS Customer Care

    ASUS Customer Care Company Representative

    Reputations:
    105
    Messages:
    90
    Likes Received:
    0
    Trophy Points:
    15
    Please verify what version of VGA drivers you are currently using, I'm afraid you might need to update it.

    There are tons of community modded drivers here or you can also try the beta drivers from Asus. If you need further assistance in obtaining drivers please do not hesitate to PM us.
     
    ASUS Customer Care, Dec 1, 2009
    #5
  6. be77solo

    be77solo pc's and planes

    Reputations:
    1,460
    Messages:
    2,631
    Likes Received:
    306
    Trophy Points:
    101
    I had this problem with my first G51 from Best Buy.... I troubleshooted for days, multiple reinstalls, driver updates, stock clocks, overclock, temps were always fine... but when ever I'd game, it would randomly do exactly what yours is doing, giving me that same message after a pause and blank screen.

    Unfortunately, it was a hardware problem, and I had to swap it for a new machine, which has worked flawlessly so far with multiple drivers and overclocks.

    Sounds like you might have a bad GPU.

    Here's what I was getting just as you described:

    [​IMG]
     
    be77solo, Dec 2, 2009
    #6
  7. martinique90

    martinique90 Notebook Enthusiast

    Reputations:
    0
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    5
    i have exactly the same problem and i have tried all the drivers there is and consulted with an expert and it seems its a hardware problem, most likely a bad contact in gpu.
     
    martinique90, Dec 3, 2009
    #7
  8. FuniGTR

    FuniGTR Notebook Guru

    Reputations:
    18
    Messages:
    56
    Likes Received:
    0
    Trophy Points:
    15
    I've been getting that message every so often when I play 1080p videos and PES2010, really hope its not a hardware issue! :(
     
    FuniGTR, Dec 3, 2009
    #8