Nvlddmkm.sys on startup

OS - windows 7 home edition 64bit - updated to SP1 the other day
MOBO - ASUS P5B DLX/WIFI-AP Pentium 4/Celeron/Pentium D/PentiumEE/65nm dual-core/Core2Duo/Core2EE
PSU - Hiper 580W Type-R Modular PSU SLI/CrossFire Certified
GPU - MSI Nvidia GTX460/OC 1GB PCI-EX
HD - Western Digital WD2500KS Caviar SE 250GB 7200RPM SATAII/300 16MB Cache
RAM - Corsair TWIN2X 6400C4 DDR2, 2048MB CL4 Kit w/two 1GB Dimm's, E.P.P Technology (two of these 4Gb in total)         
CPU - Intel Core 2 Duo E6600 (2.4ghz) Socket 775 FSB1066 4MB Cache Retail Boxed Processor
CPU cooler - Arctic Cooling (AC-FRZ-7P) Freezer 7 Pro Socket 775 CPU Cooler
DVD - NEC AD-5170A-0B 18xDVD±RW DL Black - Bare Drive
floppy drive - Sony OEM 3.5 Floppy Drive Black
Hi all,
After my MSI 8800GTX broke, i have now bought a MSI 560 GTX.
https://forum-en.msi.com/index.php?topic=146292.0
Im very pleased with it, but was very dissapointed to see an old problem reoccurring. I used to get nvlddmkm.sys errors during certain games (IL2 1946 was the main culprit) where the game would freeze, black out, and i would have to end task to get back to the desktop. When I got back to the desktop there would be an error saying 'a driver had stopped' and then something about nvlddmkm.sys. I started on Vista 64bit, then upgraded to windows 7. I had the problem on both, but more so on Vista.
Now I have tried every remedy under the sun for this, if you google it you will see what I mean, noone seems to have a clear idea of what causes it, and there are plenty of remedies(none worked for me). Nvidia blame windows, windows blame nvidia, some blame ram, some PSU, some the GPU, some the mobo.
Some claim updating drivers fixes it, some that you have to use the driver cleaner, or rolling back drivers, or looking for nvlddmkm.sys in your registry (multiple copies were rpesent, driver cleaner wasnt deleting them) or numerous other things.
The issue I am having is not quite the same, it hasn't happened in-game yet, but I have got a BSOD on startup a few times and the error message is the nvlddmkm.sys one.
I really hope this forum can help, Ithis is the 2nd MSI card I have bought i would like to enjoy this one.

Quote from: conorc on 31-March-11, 17:57:21
but if it calls for 31, and i have 30, thas close enough.
You have a bungeecord that stretches to 140 meters, the jump is 139 meters, close enough, but would you jump??
Close enough doesnt work in the computer/electricsworld
Dont go skimping on the psu, its your lifeblood for your system, if it goes it often takes other parts with it to the eternal electronicafields.
Get a Corsair, PC an Powercooling, Seasonic, Thermaltake or so, those are good quality psu's.
Read here for good reviews about psu's:
http://www.jonnyguru.com/index.php

Similar Messages

  • T410 NVIDIA BSOD caused by nvlddmkm.sys

    Hi all,
    I have lot of BSOD (1/week at least) caused by nvlddmkm.sys
    I have the latest driver according to lenovo update.
    I'm on Win7 x64.
    This is not caused by overheating I'm not running any game or 3d application,
    GPU idles ~60C.
    Could someone help me what to do?
    (Some time ago I tried the driver from NVIDIA page, but had the same experience, now I'm back on the Lenovo "official" driver.)

    hey nuri,
    could you try the following ?
    - uninstall the current driver you have installed
    - -restart your system and let Win7 install its generic driver
    - check if it happens again
    WW Social Media
    Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
    Follow @LenovoForums on Twitter!
    Have you checked out the Community Knowledgebase yet?!
    How to send a private message? --> Check out this article.

  • My Pavillion G6 - 1a52nr gets error code (ks.sys) upon startup

    My computor keeps restarting because of error code (ks.sys), it then restarts auto and I can not do anything. Any suggestions.  And I am not able to troubleshoot since I can not keep it on long enough. thx

    Hi @SeaDog90 ,
    Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your HP Pavilion g6-1a52nr Notebook and issues with error code (ks.sys) upon startup. This error is linked to either software that you have just installed or new Hardware that is connected. Try performing a hard reset.
    When performing a hard reset please note remove any and all USB devices. Disconnect all non-essential devices.
    Here is a link to computer won't start for Windows 8.
    If you installed new hardware try to remove it from the Notebook to see if this helps.
    Can get to safe mode with command prompt?
     F11 upon startup choose safe mode with Networking.
    Then you can do a system restore. System restore will help if something automatically updated and did not go well on the Notebook. I recommend doing this for at least 2 weeks prior to this happening.
    I hope this helps.
    Thanks.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

  • 0X00000116 nvlddmkm.sys - with Nvidia GTX280 OC

    Hello lads,
    Ive started getting a Stop Error with "0X00000116 nvlddmkm.sys" when trying to play games.
    I have 2 GTX280 OC's from MSI and tried them both on their own and still get the error.
    Ive reinstalled the latest drivers thinking its corrupt drivers, but it still happens.
    Any help or advice would be great.
    CPU: Quad Core Q6600 @ 3Ghz
    Motherboard: Asus Striker 2 Extreme
    Memory: OCZ Platinum Edition DDR3 1333mhz 2x 2GB
    Video card: MSI GTX280 OC x 2
    Hard drive: 2x Seagate Baracuda 750GB
    Operating system: Vista 64bit SP1
    Power Supply: Cooler Master Real Power 1000watt
    Mathew

    if i followed bas's advice i would be on 32 bit xp and thrown away my 2 280gtxocs for a ati 4870 (it's better apparently) vista 64 is a little wobbly, especially with overclocked quads, using overclocked grx cards with the latest drivers gives me the same error, either downclock card to standard or use an older driver, i use 142 from msi site and have both cards @700 which gives me better performance than standard clocks with latest driver, you have to experiment when you find the set up that works, back your system up on it for when you try nvidias next attempt at satisfying the masses. use a driver cleraner or good registry cleaner if you're not happy with manually removing the left overs after standard add/ remove.
    mines a different system and with quad sli you need 64 bit, experiment most set ups work fine, a few bsod, check through vista logs to make sure it's nvidia driver and nothing else.
    good luck.

  • BSOD after installing NVIDIA driver (nvlddmkm.sys error)

    Hi, I hope I'm posting this in the right place.
    A few days ago I purchased an MSI GS60 044 (970m) laptop with Windows 8 preinstalled on it. I have an intense hatred for Windows 8 so I decided to do a clean install of Windows 7 using a disk I own. Everything was going well until I installed the NVIDIA graphics driver. The computer would run sluggishly and then Blue Screen with an error regarding "nvlddmkm.sys."
    I got the drivers from MSI's website and followed the installation order on that page. I even tried downloading the latest driver from NVIDIA's website, but I got the same results.
    Is anyone familiar with this issue? Is there anything I can do?
    Thanks!
    - Daniel

    I really appreciate the help! I ended up reinstalling windows again and this time before installing the NVIDIA driver I installed the BIOS update that's provided under the "BIOS" tab on the GS60's support page. It's been installed for about 2 hours now with no crashes, so I hope that means it's fixed. I could just be getting lucky though, I'll post again tomorrow with results.
    Unfortunately, now my LAN and WLAN drivers have stopped working. When I troubleshoot, windows says that there aren't any drivers detected. I have tried uninstalling and reinstalling both the bigfoot and intel drivers but neither are working. I just can't catch a break with this thing. >_<
    In the event that I do have to send it to MSI, wouldn't the computer not be covered in their service anymore since I installed a different OS/formatted the original drives? I'm really hoping there isn't a hardware issue since I ordered the laptop brand new off of ebay.
    Thanks again for all of the help!

  • Nvlddmkm.sys

    Hello all this is my first posting:
    I have a HP m8200n computer using Windows Vista, recently i tried to upgrade to the Microsofts SP2 update, then a power outtage happened, now the computer won't reboot entirely.
    I am getting a message for nvlddmkm.sys after a crash dump it restarts and i can never get back into the login screen for my username.
    Can someone please help me with this issue.
    I also cannot use safemode it just keeps restarting, can i modify the bios or something?
    any help is greatly appreciated.

       Unfortunately yes, you does your motherboard have a integrated graphics card if so you may be able to remove your graphics card and plug into the integrated. That may be able to get you to the OS aso that you can see what is causing the issue. If that works then you may be able to get a new graphis card and it may work.
    Brandon
    Best Buy Associate | Geek Squad Agent
    Forum Guidelines | Terms & Conditions | Community Guidelines | Blogging Guidelines
    *Remember to mark your questions solved and click the star under the user's name to show your thanks!

  • GT70 OND-219US + nvlddmkm.sys + BSOD

    Before I dive into the issue, I'll throw out there that I have an RMA to have warranty work done that is related to the issue. I'm posting this in case anyone has ran into the issue and knows of any way to remedy the issue without having to resort to an RMA.
    This rig has run flawlessly for nearly two years, and has been amazing at playing every game I've tossed at it on max settings.
    About 8 weeks ago, it started doing random BSOD, paired with nvlddmkm.sys in the error. The fan kicks into a heightened state and sticks as this happens. The settings are factory, with no modifications and no overclocking (laptop was too expensive for me to risk that). I suspect that it was the result of an Nvidia driver, but can't be 100% certain.
    I have removed all video drivers using DDU, and performed reinstalls with the factory OEM drivers. None of these have proven useful.
    I am able to test games using the Intel GPU, and there are no crashes using this method (I suspected as much, since the file at the center of the BSOD, nvlddmkm.sys, is an Nvidia file).
    I have reinstalled Windows 7 home premium three times. I also own Windows 7 Pro, and Windows 8.1 Pro. I have installed these each two times. The issue still occurs.
    I'm reasonably confident that the RMA is the best step for this. I have further read on Nvidia's official forums that there have been driver issues with the 675m that cause the issue, and Nvidia has yet to remedy this. None of the 680m cards have these issues. It is only the 675m.
    I don't think MSI would do this, but following the revelation that the 675m has some pretty big issues with Nvidia's drivers (not pointing fingers at MSI at all. Nvidia gets all the blame for this), I'm wondering if MSI would be open to swapping my 4GB 675m for a 2GB 680m, or even a comparable AMD GPU? Seeing as my warranty is expiring at the end of August, I'd like to make sure the issue is resolved, and I'm not stuck with another 675m that will have the same issues at some point after the warranty expires.
    For me, this is more about peace of mind, being able to get work and play done without any downtime. I'd love it if I didn't have to live under the threat of the same card having the same issue after the warranty has expired. :D
    Selling my ASUS gaming laptop and getting this laptop was the best decision I've made (next to getting divorced, of course).

    This exact same thing happened to me, the month after my warranty expired. 
    BSOD with the same nvidia file.  After that, the device is always stopped by Windows (error 43) in Device Manager.  I can get it "Working properly" if I disable and re-enable it, but it's still useless since for any software (Nidia Contol Panel, games, etc) to recognize it's existence it needs to be enabled on reboot.  (OR it's not really enabled and CP is lying to me). 
    Does anyone know if there will every be a fix for this?  It's starting to seem like the card itself is damaged, since no driver works (even the one on the MSI Install CD).   
    Please say it ain't so. It'll be another ten years before I can buy a lappy like this one :(
    MSI G70 0ND, GTX 675MX 4GB with Windows 8.1

  • GT70-0ND nvlddmkm.sys BSOD error

    Hello Everyone.
    the last months or so i started getting random BSOD all pointing to nvlddmkm.sys
    i got in touch with nvidia to help me solve the problem.
    the things i tried:
    1) changing registry: add TdrDelay and TdrLevel (per nvidia tech department)
    2) clean install of several different versions of nvidia graphics drivers (note i also used Driver-Fusion to clean up registry after each uninstall)
    3) Full-system scan for Malware, Virus etc - using several programs, such as: AVG, MalwareByte.... - all returned clean reports.
    lastly i tried running "Windows Memory Diagnostic Tool" and Memtest86+.
    now both discovered errors!!
    Memtest86 was able to complete a full pass with no crashes
    but Windows tool crashed twice, once just as i started testing and once just at the beginning of the second pass.
    Pictures of the Errors:
    Memtest86 after 1 pass:
    Windows Memory Diagnostic Tool - Stuck.
    now i wanna test out which RAM module is at fault, by removing them all and inserting them one by one for testing.
    the problem im currently having is as follows:
    as u open up the laptop cover from the bottom, u can immediately see 2 RAM modules sitting near the CPU & GPU.
    but my system has 4 RAM sticks. the other 2 i cannot locate.
    if u guys know, could you please tell me where can i locate them and how to remove them?
    i rather not disassemble the entire thing.
    just in case you wonder, i checked youtube and google for instructions on how exactly to do this.
    but all the guides i found only mention the 2 RAM modules i already know about and not the other 2.
    Thanks in Advance.
    Edit:
    forgot to add system specs:
    CPU: i7-3630QM
    GPU Geforce GTX 675MX 4GB
    Memory: 16GB DDR3 1600Mhz (4x4GB)
    SSD: 120GB Patriot Pyro SE
    HDD: 750GB WesternDigital 7200rpm
    OS: Windows 7-64bit
    side-note: system came pre-installed with windows 8 + appropriate UEFI Bios.
    as soon as i got the system i formatted it and installed Windows 7-64bit. - switched Bios to LEGACY mode.

    i also dont live in the USA, luckily mine is still within the 1 year global warranty.
    i actually got this laptop as an RMA replacement because of MSI :censored:up.
    i had the GT783R, the graphics card went bad just 1 month after the 1 year global warranty expired. had to send all the way to the USA to fix it (still a better option than buying a new laptop or a replacement graphics card - which almost none sell it.)
    well, they replaced my GTX 580M 2GB with a GTX 670M 3GB, calling the 670M "better" than the 580M. if you know your graphics card, a little check up on google can tell u that no! its not better. the 670M is almost equal in performance to the 570M.
    anyways after several calls to their tech support and speaking with a manager they agreed to take back my GT783R with them covering shipping expenses and giving me a new laptop, the GT70, in its stead.
    luckily for me, Laptop warranty goes according to laptop serial number, meaning my GT70 is still under the 1 year global warranty.
    so i can fix it in my own country.
    why am i telling you all this?
    because prior to sending my GT783R to the USA, i spent almost 2 months troubleshooting the problem and trying to solve it. so im trying to save u some time and headache.
    i even tried contacting nvidia tech support to help me solve the problem
    eventually the problem wouldnt go away and i had wasted 2 months without a laptop for nothing.
    so basically if you run the following tests and everything is fine it most likely the graphics card and it needs to be replaced.
    first you can make sure your laptop isnt full of dust inside and the vents arent clogged.  then try these:
    1) running memtest (several passes) with no errors
    2) formatting the laptop to rule out software issues
    3) testing several nvidia drivers (the ones the came with the laptop and the latest Stable nvidia release)
    4) (nvidia tech rep suggestion) Open NVIDIA Control Panel --> Manage 3D settings.
        Go to Program Settings tab.
        In the setting window, change the ‘Power Management Mode’ to ‘Prefer Maximum Performance’.
    5) (nvidia tech rep suggestion)  Please try this registry fix and observe the computer performance.
         a) Go to the Registry Editor (Press Windows Logo + R and type "regedit" in the Run window and click ok)
         b) Navigate to HKEY_LOCAL_MACHINE - > System -> CurrentControlSet -> Control -> GraphicsDrivers (make sure Graphics Drivers is highlighted).
         c) Right click -> New -> DWORD (32-bit) value -> Name it: TdrDelay -> double click it -> Set it to A (hexadecimal) or 10 (decimal).
         If that doesn't work, try disabling it, by adding the following DWORD: TdrLevel and setting the value to 0, then rebooting.
    6) updating BIOS to latest version.
    ****obviously im not responsible for anything that happens to your laptop and you are trying the stuff i mentioned at your own risk.*****
    btw, if your laptop suddenly doesnt even recognize your Graphics card i think its toast.
    no point wasting time, send it RMA if u can.
    Good Luck.

  • Fix For nvlddmkm.sys Black Screen Of Death

    I think I finally found a fix for the Black Screen of Death from the bug with nviddmkm.sys and all the latest Nvidia Drivers.  This works on my IQ816 with NVIDIA 9600GS, it should work for most TouchSmarts that are having the random black screens.
    There is a free utility called RivaTuner that works with Nvidia cards.  You can get it here:
    http://downloads.guru3d.com/download.php?det=163#download
    Do the following:
    Install Rivatuner.
    Click okay when it gives you the box about not being a supported card or whatever.
    On the screen that comes up, click the tiny icon next to Customize, it's under Driver Settings in the middle of the screen.  Then click on the icon for the card.  It looks like a videocard and should be the first icon on the left.
    At the core clock screen, click the checkbox at the top to enable.  Click Detect Now when it asks for it.  Set the dropdown on the right to 3D.  Then set the core clock slider to 550 or as close as you can get to it.  I had 551.
    You can either check off start with Windows or wait and see if it's okay and then come back to this screen and check Start with Windows.  That will make sure the setting will stay all the time.  Otherwise it just reverts back to the original settings.
    Click okay.  And that should be it.
    If you need help, watch the video tutorial on it here:
    http://www.youtube.com/watch?v=NU8_EMjSUf4
    So far, since I did this, no random black screens of death.  So this may be it.
    This question was solved.
    View Solution.

    gilandme wrote:
    I might have the same issue, the problem is that my HP IQ804 desktop screen is in total darkness, no image, what can I do?
    Did you try the steps posted above? if so in what order.

  • 2013 Dev Sys slow startup?

    Just upgraded my laptop with  a solid state drive, Win7 Enterprise, and have installed Labview 2013 Academic Site license for 1st time. Also have RT and FPGA modules installed. Activated using serial number given to me by sys admins so I don't have to maintain a connection to the license server as I move through various department sites or take work home. Machine has 4GB ram installed, 2ghz Core Duo CPU.
    The development system is taking what seems like a lifetime to load. 20-30 secs just to display the splash, then another 2 min to finish initializing. Total 2:40 to get to the point where i can do something.
    Is something screwed up, or is this the new normal??

    If your IT is as bad as mine, I would consider this normal.  Virus scans, especially, tend to not like the NI folders.  Mostly likely due to it being a compiler.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • When I open FF or other browsers this message appears "Display driver stopped responding and has recovered" & PC Restart & BSoD:VIDEO_TDR_FAILURE(nvlddmkm.sys)

    It also happens at other times, but much less
    my system is :
    - Operating System:
    Microsoft Windows 8 Pro 32-bit
    - CPU:
    Intel Pentium 4 630
    Prescott 90nm Technology
    - RAM:
    2.00GB Dual-Channel DDR2 @ 200MHz (3-3-3-9)
    - Motherboard:
    Gigabyte Technology Co., Ltd. 8I945PL-G (Socket 775) 33 °C
    - Graphics:
    SyncMaster (1280x1024@85Hz)
    - 1024MB GeForce 210 (driver update version 332.21) 52 °C
    - Hard Drives:
    149GB MAXTOR STM3160215AS ATA Device (SATA) 38 °C
    - Optical Drives:
    PIONEER DVD-RW DVR-110D ATA Device
    - ELBY CLONEDRIVE SCSI CdRom Device
    - Audio:
    Realtek High Definition Audio

    It is a video related crash of your Operating System. Try Microsoft or Windows related Fora.
    Updating, or conversely rolling back your Video Drivers, if a recent update corresponds with this problem starting, may help.
    * [[Upgrade your graphics drivers to use hardware acceleration and WebGL]]

  • MOVED: BSOD caused by nvlddmkm.sys in Vista Ultimate x64

    This topic has been moved to Vista problems.
    https://forum-en.msi.com/index.php?topic=121723.0

    hey nuri,
    could you try the following ?
    - uninstall the current driver you have installed
    - -restart your system and let Win7 install its generic driver
    - check if it happens again
    WW Social Media
    Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
    Follow @LenovoForums on Twitter!
    Have you checked out the Community Knowledgebase yet?!
    How to send a private message? --> Check out this article.

  • Win 8.1 un-repsonsive after login, random restarts during startup

    SPECS:
    CPU: I7 4770K @stock
    MOBO: MSI Z87 GD65
    RAM: 8GB Corsair Platinum @1600MHz
    SSD: 120GB Samsung 840 evo
    HDD: 1TB WD Black
    GPU: MSI GTX 970
    PSU: 850W EVGA Supernova G2
    WIN 8.1 Enteroprise (EVALUATION) (I need to save a little more for a full version, got 30days left ^.^)
    Hi all, I have tried my best to fix this issue alone but I am really struggling now. I have had my new rig for a while, I have a had a few minor issues which have all seemingly been fixed now. The main one was my old win7 install; before I grabbed
    my new GPU if I were to game using integrated GFX I would occasionally crash; my board would refuse to boot with both sticks of my memory and I would need to try them one by one to get them to boot. All of a sudden they like each other again and will boot
    together; may have been due to them being clocked wrong as I forgot to enable X.M.P in the BIOS. Anyway, on to today's issue. I have my SSD for ~2months now, I grabbed Windows 8.1 straight away and installed it; all is going well and I love it. Only issue
    is, after a windows update my system will occasionally go through POST ok, when it comes to the phase where the OS should load and take over, it re-boots. It would do this 2, maybe 3 times and sometimes would boot into the login screen all ok; others it would
    go into start-up repair where I can click cancel and end up in my OS all fine. This in itself is strange, but then I have another problem.
    When I eventually get into my OS (even when it doesn't want to keep re-booting) I will login, the OS will load me into my desktop and it will jsut hang there and do nothing; simply crash. When I move my mouse over certain icons it will highlight
    them; but I can not do anything and must reset my system from my motherboard's internal reset button as the front panel buttons are un-responsive.
    I re-installed win 8.1 today, after having enough and once all my drivers are installed and I reboot; the re-boot loop happens again. I load into safe mode and try to 'refresh' my PC. This works ok and I install all my drivers but one called MSI
    fast boot, which seemingly allows me to use win 8's fast boot mode. Now the re-boot loops seem to be gone, but I still occasionally get the hanging at desktop; it is worth noting CTRL+ALT+DEL works; but if I press anything it simply hangs and does
    nothing.
    Now, if this is a software issue I am not bothered; this can be fixed. But I need to rule out any hardware. This can't be my motherboard can it? As it POST's fine? My CPU wouldn't pick and choose a time and date to work would it? If it were faulty
    it would simply not work at all correct? As for RAM; I'll be running memtest tomorrow for a good 6+ hours. And now for storage; is there a possibility this is my SSD? 
    Has anyone heard of anything like this? Is there any logs I can look at? 

    Sicarius
    The BSOD was related to your video driver (nVidia).  There is a known problem wit the new nVidia drivers on some systems.  As a workaround I would try rolling back to a driver at least 6 months old.
    The event viewer logonly contains a day or two of events (suspect you cleared it).
    It does give us a bit of information.  Three things need looking at.
    Intel, Orbiter, and driver installation failures.  I would re-install Intel (or not use it), remove orbiter, and check device manager to see if any drivers need re-installation
    If none of the above fix the issue we can diagnose it more by running a windows performance recorder trace
    In order to diagnose your problem we need to run Windows performance toolkit the instructions for which can be found in this
    wiki
    If you have any questions feel free to ask
    Please run the trace when you are experiencing the problem
    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\012415-8265-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred srv*E:\symbols
    Deferred *http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*E:\symbols;*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
    Machine Name:
    Kernel base = 0xfffff800`5e478000 PsLoadedModuleList = 0xfffff800`5e7422d0
    Debug session time: Sat Jan 24 11:46:44.942 2015 (UTC - 5:00)
    System Uptime: 0 days 0:00:06.595
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff801e026c37e, ffffd001174cdb50, 0}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+76e37e )
    Followup: MachineOwner
    6: kd> !analyze -v
    * Bugcheck Analysis *
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff801e026c37e, Address of the instruction which caused the bugcheck
    Arg3: ffffd001174cdb50, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    Debugging Details:
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
    FAULTING_IP:
    nvlddmkm+76e37e
    fffff801`e026c37e 83490802 or dword ptr [rcx+8],2
    CONTEXT: ffffd001174cdb50 -- (.cxr 0xffffd001174cdb50;r)
    rax=fffff801e0174ca0 rbx=ffffe0003b114000 rcx=ffffffffffffffff
    rdx=0000000000000008 rsi=ffffe0003af72868 rdi=00000000c00000bb
    rip=fffff801e026c37e rsp=ffffd001174ce580 rbp=ffffd001174ce700
    r8=ffffe0003af72868 r9=0000000000000000 r10=0000000000000001
    r11=000000000000000f r12=ffffe0003af72b00 r13=0000000000000000
    r14=ffffe0003af72190 r15=0000000000000008
    iopl=0 nv up ei ng nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    nvlddmkm+0x76e37e:
    fffff801`e026c37e 83490802 or dword ptr [rcx+8],2 ds:002b:00000000`00000007=????????
    Last set context:
    rax=fffff801e0174ca0 rbx=ffffe0003b114000 rcx=ffffffffffffffff
    rdx=0000000000000008 rsi=ffffe0003af72868 rdi=00000000c00000bb
    rip=fffff801e026c37e rsp=ffffd001174ce580 rbp=ffffd001174ce700
    r8=ffffe0003af72868 r9=0000000000000000 r10=0000000000000001
    r11=000000000000000f r12=ffffe0003af72b00 r13=0000000000000000
    r14=ffffe0003af72190 r15=0000000000000008
    iopl=0 nv up ei ng nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    nvlddmkm+0x76e37e:
    fffff801`e026c37e 83490802 or dword ptr [rcx+8],2 ds:002b:00000000`00000007=????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x3B
    PROCESS_NAME: csrss.exe
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    LAST_CONTROL_TRANSFER: from 0000000000000010 to fffff801e026c37e
    STACK_TEXT:
    ffffd001`174ce580 00000000`00000010 : 00000000`00010286 ffffd001`174ce5a8 00000000`00000018 00000000`c00000bb : nvlddmkm+0x76e37e
    ffffd001`174ce588 00000000`00010286 : ffffd001`174ce5a8 00000000`00000018 00000000`c00000bb fffff801`dfb60afe : 0x10
    ffffd001`174ce590 ffffd001`174ce5a8 : 00000000`00000018 00000000`c00000bb fffff801`dfb60afe ffffe000`3b114000 : 0x10286
    ffffd001`174ce598 00000000`00000018 : 00000000`c00000bb fffff801`dfb60afe ffffe000`3b114000 ffffd001`174ce700 : 0xffffd001`174ce5a8
    ffffd001`174ce5a0 00000000`c00000bb : fffff801`dfb60afe ffffe000`3b114000 ffffd001`174ce700 ffffe000`3af72868 : 0x18
    ffffd001`174ce5a8 fffff801`dfb60afe : ffffe000`3b114000 ffffd001`174ce700 ffffe000`3af72868 00000000`c00000bb : 0xc00000bb
    ffffd001`174ce5b0 ffffe000`3b114000 : ffffd001`174ce700 ffffe000`3af72868 00000000`c00000bb fffff801`dfb60a60 : nvlddmkm+0x62afe
    ffffd001`174ce5b8 ffffd001`174ce700 : ffffe000`3af72868 00000000`c00000bb fffff801`dfb60a60 ffffe000`3b114000 : 0xffffe000`3b114000
    ffffd001`174ce5c0 ffffe000`3af72868 : 00000000`c00000bb fffff801`dfb60a60 ffffe000`3b114000 00000000`00000000 : 0xffffd001`174ce700
    ffffd001`174ce5c8 00000000`c00000bb : fffff801`dfb60a60 ffffe000`3b114000 00000000`00000000 00000000`00000000 : 0xffffe000`3af72868
    ffffd001`174ce5d0 fffff801`dfb60a60 : ffffe000`3b114000 00000000`00000000 00000000`00000000 00000000`0013347d : 0xc00000bb
    ffffd001`174ce5d8 ffffe000`3b114000 : 00000000`00000000 00000000`00000000 00000000`0013347d 00000000`00000000 : nvlddmkm+0x62a60
    ffffd001`174ce5e0 00000000`00000000 : 00000000`00000000 00000000`0013347d 00000000`00000000 00000000`00000008 : 0xffffe000`3b114000
    FOLLOWUP_IP:
    nvlddmkm+76e37e
    fffff801`e026c37e 83490802 or dword ptr [rcx+8],2
    SYMBOL_STACK_INDEX: 0
    SYMBOL_NAME: nvlddmkm+76e37e
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nvlddmkm
    IMAGE_NAME: nvlddmkm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 54b0548e
    STACK_COMMAND: .cxr 0xffffd001174cdb50 ; kb
    FAILURE_BUCKET_ID: 0x3B_nvlddmkm+76e37e
    BUCKET_ID: 0x3B_nvlddmkm+76e37e
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x3b_nvlddmkm+76e37e
    FAILURE_ID_HASH: {f567d75e-9039-f40c-e30a-b65dc4bbd018}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • Windows latency issues 2-3 days after reboot. Sound/mouse/PC very Choppy - tcpip.sys ndis.sys NETIO.SYS

    Alright, so I've tried what feels like everything. First off, I am troubleshooting for WINDOWS 7.
    After I reboot, the computer functions relatively fine. Great latency, no choppyness, no matter what I do. About two to three days later, it gets incredibly bad. Specifically when browsing the internet using any browser. The audio becomes terribly choppy
    as the mouse lags across the screen. Running LatencyMon, I see tcpip.sys is always at the top. This issue only seems to happen the most when internet activity usage is high. Also, ndis.sys is always up there too, as well as NETIO.SYS
    Any help would be so greatly appreciated!! I run a small web server from this PC, so this is quite critical for me. It never used to happen until I recently began getting Pool_corruption blue screens, later to be discovered they were caused by my GIGABYTE
    motherboards utility driver files, which I took care of.
    I haven't really made any changes to my PC, besides several driver updates in attempt to resolve this. I have since updated my BIOS to the latest version. I even tried using Auslogics Boost Speed to improve the TCP settings based on on my 50mbps internet
    speed. Nothing clears the lag, but a reboot, which is temporary. I used to run this PC for up to two weeks before I rebooted, no issues.
    Driver Execution Time Screenshot:
    http://gyazo.com/7adc868ee2b76dee4ef5c19ad19ce088
    LatencyMon log below:
    CONCLUSION
    Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing
    for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS
    setup. Check for BIOS updates. 
    LatencyMon has been analyzing your system for  0:16:52  (h:mm:ss) on all processors.
    SYSTEM INFORMATION
    Computer name:                                        ThisIsAComputerName
    OS version:                                           Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
    Hardware:                                             Z87X-UD4H, Gigabyte Technology Co., Ltd., Z87X-UD4H-CF
    CPU:                                                  GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
    Logical processors:                                   8
    Processor groups:                                     1
    RAM:                                                  16324 MB total
    CPU SPEED
    Reported CPU speed:                                   3491.0 MHz
    Measured CPU speed:                                   3868.0 MHz (approx.)
    Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.
    MEASURED INTERRUPT TO USER PROCESS LATENCIES
    The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the
    signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.
    Highest measured interrupt to process latency (µs):   81947.411914
    Average measured interrupt to process latency (µs):   8.685069
    Highest measured interrupt to DPC latency (µs):       71439.589036
    Average measured interrupt to DPC latency (µs):       3.104919
     REPORTED ISRs
    Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
    Highest ISR routine execution time (µs):              147.623890
    Driver with highest ISR routine execution time:       USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation
    Highest reported total ISR routine time (%):          0.100862
    Driver with highest ISR total time:                   dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
    Total time spent in ISRs (%)                          0.146654
    ISR count (execution time <250 µs):                   2354800
    ISR count (execution time 250-500 µs):                0
    ISR count (execution time 500-999 µs):                0
    ISR count (execution time 1000-1999 µs):              0
    ISR count (execution time 2000-3999 µs):              0
    ISR count (execution time >=4000 µs):                 0
    REPORTED DPCs
    DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
    Highest DPC routine execution time (µs):              4384.048124
    Driver with highest DPC routine execution time:       ndis.sys - NDIS 6.20 driver, Microsoft Corporation
    Highest reported total DPC routine time (%):          0.031341
    Driver with highest DPC total execution time:         nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 347.52 , NVIDIA Corporation
    Total time spent in DPCs (%)                          0.201231
    DPC count (execution time <250 µs):                   7333801
    DPC count (execution time 250-500 µs):                0
    DPC count (execution time 500-999 µs):                423
    DPC count (execution time 1000-1999 µs):              433
    DPC count (execution time 2000-3999 µs):              7
    DPC count (execution time >=4000 µs):                 0
     REPORTED HARD PAGEFAULTS
    Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted
    and blocked from execution.
    NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
    Process with highest pagefault count:                 avastsvc.exe
    Total number of hard pagefaults                       1535
    Hard pagefault count of hardest hit process:          344
    Highest hard pagefault resolution time (µs):          77184.982813
    Total time spent in hard pagefaults (%):              0.063944
    Number of processes hit:                              21
     PER CPU DATA
    CPU 0 Interrupt cycle time (s):                       45.681687
    CPU 0 ISR highest execution time (µs):                147.623890
    CPU 0 ISR total execution time (s):                   11.875990
    CPU 0 ISR count:                                      2354800
    CPU 0 DPC highest execution time (µs):                4384.048124
    CPU 0 DPC total execution time (s):                   13.495186
    CPU 0 DPC count:                                      6501345
    CPU 1 Interrupt cycle time (s):                       16.680073
    CPU 1 ISR highest execution time (µs):                0.0
    CPU 1 ISR total execution time (s):                   0.0
    CPU 1 ISR count:                                      0
    CPU 1 DPC highest execution time (µs):                3350.307935
    CPU 1 DPC total execution time (s):                   0.426748
    CPU 1 DPC count:                                      107359
    CPU 2 Interrupt cycle time (s):                       17.093312
    CPU 2 ISR highest execution time (µs):                0.0
    CPU 2 ISR total execution time (s):                   0.0
    CPU 2 ISR count:                                      0
    CPU 2 DPC highest execution time (µs):                1974.991693
    CPU 2 DPC total execution time (s):                   0.441413
    CPU 2 DPC count:                                      122078
    CPU 3 Interrupt cycle time (s):                       17.086010
    CPU 3 ISR highest execution time (µs):                0.0
    CPU 3 ISR total execution time (s):                   0.0
    CPU 3 ISR count:                                      0
    CPU 3 DPC highest execution time (µs):                2766.876540
    CPU 3 DPC total execution time (s):                   0.269897
    CPU 3 DPC count:                                      65999
    CPU 4 Interrupt cycle time (s):                       8.237525
    CPU 4 ISR highest execution time (µs):                0.0
    CPU 4 ISR total execution time (s):                   0.0
    CPU 4 ISR count:                                      0
    CPU 4 DPC highest execution time (µs):                1918.52220
    CPU 4 DPC total execution time (s):                   0.618606
    CPU 4 DPC count:                                      220533
    CPU 5 Interrupt cycle time (s):                       8.578453
    CPU 5 ISR highest execution time (µs):                0.0
    CPU 5 ISR total execution time (s):                   0.0
    CPU 5 ISR count:                                      0
    CPU 5 DPC highest execution time (µs):                1899.919794
    CPU 5 DPC total execution time (s):                   0.206159
    CPU 5 DPC count:                                      56896
    CPU 6 Interrupt cycle time (s):                       11.541397
    CPU 6 ISR highest execution time (µs):                0.0
    CPU 6 ISR total execution time (s):                   0.0
    CPU 6 ISR count:                                      0
    CPU 6 DPC highest execution time (µs):                1861.963334
    CPU 6 DPC total execution time (s):                   0.358036
    CPU 6 DPC count:                                      108505
    CPU 7 Interrupt cycle time (s):                       12.079986
    CPU 7 ISR highest execution time (µs):                0.0
    CPU 7 ISR total execution time (s):                   0.0
    CPU 7 ISR count:                                      0
    CPU 7 DPC highest execution time (µs):                1797.655113
    CPU 7 DPC total execution time (s):                   0.479542
    CPU 7 DPC count:                                      151950

    Hello and thank you for the reply!
    While I am waiting for the issue to start up again, I'd just like to cover some things you mentioned in your post. :)
    I only updated the bios because I was originally experiencing these issues. It was a method to hopefully resolve them, which did not work. I was very careful, and the process was a success. I updated to the most recent recommended driver for my motherboard
    from the manufacturers.
    As for Auslogics Boost Speed, it is not running on my computer, as it is a piece of software I only have used to clean junk files (cache/temp) for a very long time now with no issue. I have also tried updating all of my drivers with success, however that
    did not solve the issue either. I even rolled back my network card driver just in case with no luck.
    I have not thought of disabling my audio driver yet, being how it effects far more than just my audio when it happens. My mouse is jittery/laggy as well when no sound is playing. But other tests have shown that it may be a network issue. Next time it happens
    I'll temporary disable my network drivers to see if that causes the issue to clear up.
    I will be sure to mark answers which help appropriately. Thanks again! I should return with the information requested from Zigzag's wiki within 2 days of on-time, when this happens again. 

  • Problem with nvidia graphic card, nvlddmkm.s​ys

    I have a HP m9000 , originally it had Vista, it started to fail and display the error nvlddmkm.sys (on a blue screen od death), i intalled Windows 8 in hope the problem get resolve. but the problem still persist. At the beginning on W8 it looks like working fine, but suddenly it started to display "controller not responding", and then it is displayin "Something goes wrong with your graphic card".
    I found on internet a fix; expanding the nvlddmkm.sy_ and replace the file in system32. i made it but right now after the windows logon screen the monitor starts to blink between black screen and off screen.
    The grapghic card is a NVIDIA 8500 GT. I tested the graphic card in other computer, and at the begining it worked fine, but after the dirver installation it started to fail in the same way.
    Ad far i could read on intetrnet it is a failure with NVIDIA.
    Is there any solution for this problem? Or i should change the graphic video card? (Maybe for an ATI)

    Hi,
    I have used many different NVIDIA cards (including a 8600) on different PCs and never had your issue.
    As for drivers, you can always use the original drivers that came with your PC and then do an update if necessary.
    HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
    HP Photosmart Premium C309G, HP Photosmart 6520
    HP Touchpad, HP Chromebook 11
    Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
    Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
    Windows 7/8 UEFI/Legacy mode, MBR/GPT

Maybe you are looking for