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.

    nvlddmkm.sys error

    Discussion in 'Alienware M15x' started by PenguinForce, Aug 30, 2011.

  1. PenguinForce

    PenguinForce Notebook Enthusiast

    Reputations:
    5
    Messages:
    37
    Likes Received:
    0
    Trophy Points:
    15
    Hi all, I'm not sure if this is the right forum to post this on. Apologies if it is.

    Recently I've started playing Guild Wars again after almost a year. During my play through of the game I often get a BSOD with the STOP: 0x00000116 and nvlddmkm.sys error. This sometimes happens 15 minutes into the game or sometimes I will be playing for 3 to 4 hours without any problems.

    My specs:

    Alienware M15x
    Windows 7 Home Premium 64bit
    4GB 1333MHz Dual Channel DDR3 SDRAM
    1GB NVIDIA® GeForce GTX260M
    Intel Core i7 Processor 720QM (1.60Ghz, 6MB L3 cache)

    Graphic driver version: 280.26 WHQL

    Anyway to solve this?

    Thank you.
     
    PenguinForce, Aug 30, 2011
    #1
  2. inap

    inap .........................

    Reputations:
    4,417
    Messages:
    7,827
    Likes Received:
    19
    Trophy Points:
    206
    looks like the nvidia driver is causing the bsod, try another driver to see if it helps.
     
    inap, Aug 30, 2011
    #2
  3. noelho

    noelho Notebook Consultant

    Reputations:
    9
    Messages:
    118
    Likes Received:
    0
    Trophy Points:
    30
    noelho, Aug 31, 2011
    #3
  4. PenguinForce

    PenguinForce Notebook Enthusiast

    Reputations:
    5
    Messages:
    37
    Likes Received:
    0
    Trophy Points:
    15
    Thanks for the replies. I uninstalled my driver and downloaded and installed an older version and the problem is gone.

    I might try some of the solution in the link if it happens again with the new drivers.
     
    PenguinForce, Sep 1, 2011
    #4