Windows 10: BSOD Caused by nvlddmkm.sys

Discus and support BSOD Caused by nvlddmkm.sys in Windows 10 BSOD Crashes and Debugging to solve the problem; I'm not sure where to put this, since most of my issues are non-BSOD issues, but I feel like they are related. I just recently built a new computer,... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by silentreaper, Mar 21, 2019.

  1. BSOD Caused by nvlddmkm.sys


    I'm not sure where to put this, since most of my issues are non-BSOD issues, but I feel like they are related.

    I just recently built a new computer, and besides a monitor I had to send for repairs, it was working fine until I upgraded the PSU, added a second graphics card with NVLink SLI, and added a Samsung 970 Pro. The issues started off with Windows thinking there was something wrong with the graphics drivers. Upon booting into Linux, it would state the NVLink was unlinked and only one graphics card would show up (the second one I put in). The issue continues to happen until I power off the computer completely, turn off and on the switch on the PSU, and restart the computer.

    After having that issue a few times, I upgraded the BIOS and drivers on Windows, and while it was idling earlier today, I got a BSOD, namely SYSTEM_THREAD_EXCEPTION_NOT_HANDLED caused by nvlddmkm.sys. The computer hit 100% on collecting info and froze, forcing me to hit the reset button. I later tried checking for RAM issues via a test Windows provides, and that too froze. I reset the computer, checked BIOS settings, and upon saving and exiting, another freeze. I shut down the computer and did the same thing I did to "fix" the NVLink issue from before. Computer is working fine so far, but I'm certain I will continue to have issues.

    Basically, I'm wondering what the likely cuplrit(s) are.

    I ran the Beta log collector just in case you need it: HOME-(2019-03-20_22-44-48).zip

    :)
     
    silentreaper, Mar 21, 2019
    #1

  2. wdf01000.sys and ntoskrnl.exe BSOD

    I'm on Windows 10, 64bit

    Basically, whenever I try to update my LPC controller through Device Manager, BSOD with WDF_VIOLATION occurs (culprit being wdf01000.sys)

    So I try to use the driver verifier to see which driver is causing the BSOD, but then it causes BSOD (cultprit being ntoskrnl.exe)

    Have no idea which driver is causing them

    Please help!

    Here are my list of drivers and system info: Documents
     
    interestingkid005140, Mar 21, 2019
    #2
  3. axe0 Win User
    System_Thread_Exception_Not_Handled dxgmms2.sys


    Hi Asellia,

    Welcome to the 10forums.


    What driver versions have you tried currently for your graphics?
    If it is the newest version, 361.43, try rolling back the drivers.
    Driver Rollback | NVIDIA
    Code:
    Code:
    Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+3a )  7: kd> lmvm nvlddmkmstart             end                 module name fffff800`cf870000 fffff800`d048b000   nvlddmkm   (deferred)                  Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys     Image name: nvlddmkm.sys     Timestamp:        Wed Dec 16 15:03:30 2015 (56716F32)     CheckSum:         00BE13AE     ImageSize:        00C1B000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
    Please remove Daemon Tools and run the SPTD pass through remover.

    1. Uninstall Daemon Tools
    2. Download the SPTD standalone installer and follow these steps:
      • Double click the executable to open it
      • Click on the button shown below

    BSOD Caused by nvlddmkm.sys [​IMG]

    If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window
     
  4. BSOD Caused by nvlddmkm.sys

    BSOD - driver_irql_not_less_or_equal (l1c63x64.sys)

    Hi Seung,

    Sorry for the inconvenience caused by BSOD - driver_irql_not_less_or_equal (l1c63x64.sys).

    Please let us know the make/model of your computer.

    The L1C63x64.sys is the Atheros LAN driver and I would suggest to uninstall and reinstall the Atheros LAN driver but install the latest Atheros LAN driver by visiting the manufacture's website and avoid using any LAN driver available though Windows Update.

    However the problem could also be with any VPN software and other software so make sure you have the latest version of each of these software.

    If the errors continue uninstall the VPN software and check if the issue persist.

    Hope this helps. Get back to us for further queries for BSOD - driver_irql_not_less_or_equal (l1c63x64.sys). We are happy to help!
     
    Joy Kemprai, Mar 21, 2019
    #4
Thema:

BSOD Caused by nvlddmkm.sys

Loading...
  1. BSOD Caused by nvlddmkm.sys - Similar Threads - BSOD Caused nvlddmkm

  2. Crash caused by nvlddmkm

    in Windows 10 Gaming
    Crash caused by nvlddmkm: Hello, for the past few weeks, my laptop has been crashing every so often. I have no idea what causes the crash and when it happens. Sometimes it happens a few times in a day, sometimes it can go an entire week without occurring.I tried analyzing the crash dumps generated by...
  3. Crash caused by nvlddmkm

    in Windows 10 Software and Apps
    Crash caused by nvlddmkm: Hello, for the past few weeks, my laptop has been crashing every so often. I have no idea what causes the crash and when it happens. Sometimes it happens a few times in a day, sometimes it can go an entire week without occurring.I tried analyzing the crash dumps generated by...
  4. nvlddmkm BSOD

    in Windows 10 Gaming
    nvlddmkm BSOD: Microsoft R Windows Debugger Version 10.0.25200.1003 AMD64Copyright c Microsoft Corporation. All rights reserved.Mini Kernel Dump File: Only registers and stack trace are available************* Path validation summary **************Response Time ms...
  5. nvlddmkm BSOD

    in Windows 10 Software and Apps
    nvlddmkm BSOD: Microsoft R Windows Debugger Version 10.0.25200.1003 AMD64Copyright c Microsoft Corporation. All rights reserved.Mini Kernel Dump File: Only registers and stack trace are available************* Path validation summary **************Response Time ms...
  6. BSOD caused by dxgmms2.sys and watchdog.sys

    in Windows 10 Software and Apps
    BSOD caused by dxgmms2.sys and watchdog.sys: I've tried reverting graphics drivers, windows updates, updating BIOS, resetting windows and other recommended methods such as chkdsk and DISM. I would like some confirmation on my issue being potentially video card related. Another pair of eyes/insight is the goal of this...
  7. BSOD caused by netwtw10.sys

    in Windows 10 Drivers and Hardware
    BSOD caused by netwtw10.sys: From a couple of days ago my machine has been frequently BSOD and showing the error to be caused by netwtw10.sys. I have attempted to reinstall network drivers, reset machine with content, reset to factory and the issue has persisted through all the changes I made. In...
  8. QCAMAIN1.SYS CAUSING BSOD

    in Windows 10 BSOD Crashes and Debugging
    QCAMAIN1.SYS CAUSING BSOD: This was probably caused by the following module: qcamain1.sys Qcamain10x64+0x108678 Bugcheck code: 0x1D3 0x333, 0x0, 0x0, 0x0 Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for...
  9. BSOD caused by Dot4.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by Dot4.sys: I have a BSOD problem caused by Dot4.sys very often but I have no idea what is causing it. SYSTEM_SERVICE_EXCEPTION Dot4.sys+e23f IEEE-1284.4-1999 Driver Windows (R) Win 7 DDK driver Windows (R) Win 7 DDK provider 6.1.7600.16385 built by: WinDDK x64 ntoskrnl.exe+1aab90
  10. BSOD caused by QCamain10x64.sys and IntelHaxm.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by QCamain10x64.sys and IntelHaxm.sys: My laptop crashed with STOP code DEVICE_IRQL_NOT_LESS_OR_EQUAL, stating that QCamain10x64.sys had failed, which according to Google, is the driver of my laptop's wireless adapter. Just to make sure before attempting to reinstall the driver via device manager, I saw this wiki...
Tags: