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.

    9262 -- Nvlddmkm.dll BSOD on startup?

    Discussion in 'Sager and Clevo' started by BlackPanther, Jul 23, 2008.

  1. BlackPanther

    BlackPanther Notebook Consultant

    Reputations:
    34
    Messages:
    160
    Likes Received:
    0
    Trophy Points:
    30
    Just before Vista starts up, I get this nvidia display driver BSOD and then it re-boots. This happens between 3 and 5 times and then I get in Vista.

    Once Vista loads, then I have no problems. I can play games, and all performs well, no BSODs.

    I'm running Vista SP1 64bit, 8800M GTX SLi, 4GB RAM.

    Has anyone encountered this problem before?

    How can it be solved?
     

    Attached Files:

    • bsod.jpg
      bsod.jpg
      File size:
      183.5 KB
      Views:
      150
  2. gekk_gad

    gekk_gad Notebook Consultant

    Reputations:
    31
    Messages:
    281
    Likes Received:
    0
    Trophy Points:
    30
    what version of nvidia drivers you using? did you try other versions of the driver and got the same results?
     
  3. BlackPanther

    BlackPanther Notebook Consultant

    Reputations:
    34
    Messages:
    160
    Likes Received:
    0
    Trophy Points:
    30
    I got the OS and all drivers ready installed by the seller. It started doing it immediately.

    The driver I have is 167.62
     
  4. dazzyd

    dazzyd Notebook Evangelist

    Reputations:
    111
    Messages:
    498
    Likes Received:
    2
    Trophy Points:
    31
    yes i have encountered this before. remove the old drivers normally ie uninstall

    get into safe mode and use driversweeper to remove all traces of the old drivers

    then use the latest drivers from laptopvideo2go
     
  5. ashveratu

    ashveratu Notebook Evangelist

    Reputations:
    318
    Messages:
    470
    Likes Received:
    0
    Trophy Points:
    30
    To save the time and trouble of contacting the reseller or RMAing it, try downloading the latest drivers from Sager here at the Sager download page . If those do not work, then it sounds like it may be hardware related and the reseller will have to get involved.
     
  6. BlackPanther

    BlackPanther Notebook Consultant

    Reputations:
    34
    Messages:
    160
    Likes Received:
    0
    Trophy Points:
    30
    Which driver version are you using currently dazzyd?
     
  7. dazzyd

    dazzyd Notebook Evangelist

    Reputations:
    111
    Messages:
    498
    Likes Received:
    2
    Trophy Points:
    31
    175.75 at the moment. ive got 176.02. but havent installed it yet.
     
  8. BlackPanther

    BlackPanther Notebook Consultant

    Reputations:
    34
    Messages:
    160
    Likes Received:
    0
    Trophy Points:
    30
    Hmmm, what is NOD32?

    I've been doing some googling and apparently some version of it can cause this problem...

    I will try other nvidia graphics drivers as soon as I get home.
     
  9. Shyster1

    Shyster1 Notebook Nobel Laureate

    Reputations:
    6,926
    Messages:
    8,178
    Likes Received:
    0
    Trophy Points:
    205
    Just to jump on the bandwagon - this is almost certainly caused by a malfunctioning driver, or what that wasn't properly installed. The suggestion to uninstall and then use driversweeper in safe mode is a good one because it's very, very likely that the driver installation got muffed up by your reseller, so there's a good chance that some of the driver files got orphaned or otherwise put where they shouldn't be.

    Just to make sure that's all it is, though, I would first try reinstalling using the latest Sager drivers from the Sager website. If that works without giving you the BSOD, then it was merely a matter of a badly installed driver. If you still get the BSOD, then I would suggest a complete reinstallation, from the ground up, and in proper order.
     
  10. dazzyd

    dazzyd Notebook Evangelist

    Reputations:
    111
    Messages:
    498
    Likes Received:
    2
    Trophy Points:
    31
    NOD32 is a antispyware/firewall/virus scanner all in one


    absalute gem of a program and ive got it running on my system
     
  11. OV10stang

    OV10stang Notebook Consultant

    Reputations:
    6
    Messages:
    214
    Likes Received:
    2
    Trophy Points:
    31
    You wouldn't happen to be using an external monitor? Had the same problem installing the latest drivers from Sager. Found that when I do a driver install, I have to have the monitor disconnected.
     
  12. BlackPanther

    BlackPanther Notebook Consultant

    Reputations:
    34
    Messages:
    160
    Likes Received:
    0
    Trophy Points:
    30
    Nope.

    I guess it's OK using the Sager driver? Since my notebook isn't branded Sager?

    I'm very tempted not to do anything, lol I'm afraid I'd make it worse!

    Also, it doesn't do it every time I power on the notebook...
    :confused:

    The last time it did it, the culprit was nvlddmkm.sys, not dll.
     
  13. Shyster1

    Shyster1 Notebook Nobel Laureate

    Reputations:
    6,926
    Messages:
    8,178
    Likes Received:
    0
    Trophy Points:
    205
    There are actually quite a lot of posts on the web regarding this particular little file, and an article from Anandtech that seems to give something of an explanation. I don't have time to read through all of them to get to know the issue(s) in sufficient detail to say which is better than which, so I'll just give you some links to some of the articles/forum threads I found, as well as a link to the google search:

    The Anandtech article
    NVidia forum thread
    Vista_forums thread
    Eggheadcafe thread
    MS Technet thread
    Google search on "nvlddmkm.sys"
     
  14. BlackPanther

    BlackPanther Notebook Consultant

    Reputations:
    34
    Messages:
    160
    Likes Received:
    0
    Trophy Points:
    30
    I noticed, that the nvldd... error happens only when I power up the laptop on battery. Might be a coincidence? Or maybe the computer doesn't like being powered up on battery while Sli is enabled...

    I'll check it a couple of times more in the afternoon...

    I checked the administrative error/maintenance logs (or whatever they're called in Vista!) and this never happened to the seller, who appears to have powered up the notebook a lot of times in 3 days. Maybe he always powered it up on AC. (Probably since he was installing Vista, drivers, etc...)
     
  15. xizzu

    xizzu Notebook Enthusiast

    Reputations:
    47
    Messages:
    47
    Likes Received:
    0
    Trophy Points:
    15
    have you formatting the drive and install everything back?
     
  16. BlackPanther

    BlackPanther Notebook Consultant

    Reputations:
    34
    Messages:
    160
    Likes Received:
    0
    Trophy Points:
    30
    No I didn't do anything. I didn't even try a new video driver.

    I checked and re-checked and this is what I can conclude:

    The BSOD/Reboot only happens if:
    1) I power up on battery; and
    2) I have SLi enabled.

    If I power up on battery with SLi disabled I don't get a BSOD.
    If I power up on AC power (whether SLi is disabled or not) I don't get a BSOD.
    If I power up on battery with SLi enabled, I get 4 BSODs out of every 5 attempts.

    Now if only I can remember where on earth I read that the D901C must not be powered on by battery if SLi is enabled......... I'll do a quick search...
     
  17. ArmageddonAsh

    ArmageddonAsh Mangekyo Sharingan

    Reputations:
    428
    Messages:
    3,993
    Likes Received:
    0
    Trophy Points:
    105
    ive encountered a problem where one minute everything is fine then the next i get a black screen and then everything turns back to normal with a message saying the video driver failed but has recovered or something, any ideas on how to fix it or whats doing it?
     
  18. BlackPanther

    BlackPanther Notebook Consultant

    Reputations:
    34
    Messages:
    160
    Likes Received:
    0
    Trophy Points:
    30
    Hmmm, no I never got that. :confused:
     
  19. ArmageddonAsh

    ArmageddonAsh Mangekyo Sharingan

    Reputations:
    428
    Messages:
    3,993
    Likes Received:
    0
    Trophy Points:
    105
    its strange, its happens several times day.
    and though not deadly (i hope) it is annoying
     
  20. bbCan

    bbCan Notebook Guru

    Reputations:
    12
    Messages:
    65
    Likes Received:
    0
    Trophy Points:
    15
    hey, just curious, what is the current nvedio you used?
     
  21. BlackPanther

    BlackPanther Notebook Consultant

    Reputations:
    34
    Messages:
    160
    Likes Received:
    0
    Trophy Points:
    30
    Suxxxx, it started doing it again randomly, whether on battery or not, Sli enabled.
    I think I'll update to the latest driver when I get home. I'm still using 167.26 (I think) dated January 2008. I hope I solve this! :mad:
     
  22. BlackPanther

    BlackPanther Notebook Consultant

    Reputations:
    34
    Messages:
    160
    Likes Received:
    0
    Trophy Points:
    30
    I just ran 3DMark06 and got a score of 13670.

    Guess my SLi is working well.

    I didn't get any crashes (I get them only before Vista starts).

    I noticed that when the driver does load, the screen like flashes between black and very very dark green patches. I had that type of flashing also between the tests of the 3Dmark06 benchmark.

    Duh now I know before if Vista's gonna load or not - if I see the flashing (which is very subtle but weird) then Vista is going to load. If I don't see flashing, then it'd be a blue nvlddmkm.sys screen BSOD.

    I'm off to update the driver..... pray for me!

    Edit -- Driver updated to 176.02, used proper procedure with Driver Cleaner Pro...

    So far seems to be so good...
     
  23. BlackPanther

    BlackPanther Notebook Consultant

    Reputations:
    34
    Messages:
    160
    Likes Received:
    0
    Trophy Points:
    30
    After 3 days of testing I can confirm that the new 176.02 driver has definitely 'cured' the problem.

    :biggrin: