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, but has succesfully recovered.

    Discussion in 'Gaming (Software and Graphics Cards)' started by png910, Apr 2, 2008.

  1. png910

    png910 Notebook Enthusiast

    Reputations:
    0
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    5
    This problem has happened to me recently, and now i can't play any game whatsoever without either random polygons appearing on the screen, or the game crashing giving the same error message (Display driver nvlddmkm stopped responding, but has succesfully recovered.)

    My system is a VAIO VGN-FZ17G, with a Nvidia Geforce 8400M GT.

    This is really pissing me off, and if anyone has any solutions, I would be extremely grateful.
     
  2. usapatriot

    usapatriot Notebook Nobel Laureate

    Reputations:
    3,266
    Messages:
    7,360
    Likes Received:
    14
    Trophy Points:
    206
    Have you tried reinstalling your display drivers?

    Guide
     
  3. flipfire

    flipfire Moderately Boss

    Reputations:
    6,156
    Messages:
    11,214
    Likes Received:
    68
    Trophy Points:
    466
    A change of drivers will fix this
     
  4. Fittersman

    Fittersman Wanna trade?

    Reputations:
    225
    Messages:
    1,306
    Likes Received:
    0
    Trophy Points:
    55
    have you recently changed any drivers? (even if its not the video driver) I changed my sound driver a while back and it caused some stuttering with the sound, causing my video driver to do this. So try rolling back any recently changed drivers.
     
  5. binro01

    binro01 Notebook Consultant

    Reputations:
    7
    Messages:
    138
    Likes Received:
    0
    Trophy Points:
    30
    were you OCing the GPU when you received this message? I hope you didn't blow up the GPU
     
  6. Clairvoyant47

    Clairvoyant47 Notebook Enthusiast

    Reputations:
    20
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    15
    dude dont scare him :D
    i get the same message when i overclock or UNDERCLOCK my ATI HD2600 with AMDGPU clock tool..but for me its a 20 sec monitor shutdown, then its on and gives the message, but sometimes i can change clocks without the driver crashing..weird problem..

    to OP i get a driver crash when changing clocks manually, maybe when ur GPU changes clocks automatically it happens to you, so best advice change driver....else dunno :(
     
  7. brncao

    brncao Notebook Evangelist

    Reputations:
    541
    Messages:
    570
    Likes Received:
    5
    Trophy Points:
    31
    I guess it's pretty common. I get it too. Ah the wonders of Vista. XP was so much better...

    How do you know which video driver you should use? I don't want to end up experimenting if that's the case. Latest version doesn't always work.
     
  8. Clairvoyant47

    Clairvoyant47 Notebook Enthusiast

    Reputations:
    20
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    15
    i use official toshiba drivers for A200 Vista 32... for my HD2600, they are pretty regularly updated, about every month or so...havent had any serious problems with them except this over/under clocking issue...but its tollerable :p
     
  9. BenLeonheart

    BenLeonheart walk in see this wat do?

    Reputations:
    42
    Messages:
    1,128
    Likes Received:
    0
    Trophy Points:
    55
    Definately needs a video card driver update.
    Update to 169.28 or something 1st,
    then move up to 174.** something

    :D
    cheres!
     
  10. png910

    png910 Notebook Enthusiast

    Reputations:
    0
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    5
    okay, after updating my drivers, i no longer get this problem with the driver. However, when running an old game with low requirements that my comp can handle at maximum graphics (Neverwinter Nights), as i did before the driver messed up. now, sometimes the whole screen is fuzzy with blue, pink and many other colours. I can make out the screen and have a vague idea of what's happening, but other than that, it's unplayable. the only thing that works is lowering the graphics. might this have any connection with my recent driver problem?

    out of curiousity, why do you suggest updating in such a manner, ie not directly to 174.**?
     
  11. flipfire

    flipfire Moderately Boss

    Reputations:
    6,156
    Messages:
    11,214
    Likes Received:
    68
    Trophy Points:
    466
    Some drivers are for specific fixes, some perform better, some dont. You have to try out a couple of drivers before you can get the perfect one for you

    169.09 is the most stable so far
     
  12. Iceman0124

    Iceman0124 More news from nowhere

    Reputations:
    1,133
    Messages:
    3,548
    Likes Received:
    0
    Trophy Points:
    105
    I get that error on my desktop if I OC my GTS a little too much, lightly backing off the clocks solves that problem
     
  13. png910

    png910 Notebook Enthusiast

    Reputations:
    0
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    5
    i never/have never OC'd my graphics card.
     
  14. BenLeonheart

    BenLeonheart walk in see this wat do?

    Reputations:
    42
    Messages:
    1,128
    Likes Received:
    0
    Trophy Points:
    55
    Well, I have not overclocked yet either...
    There are many different drivers, thats why I suggest that...
    169.28 was a specific like "milestone" driver, (for me, at least).
    so yes. try.