Windows 10: nvlddkm.sys errors

When playing games on my windows 10 x64 laptop with my nvidia graphics card geforce 920m i get frequent BSoDs like Video TDR Failure or VIDEO_MEMORY_MANAGEMENT_INTERNAL and the error is always in some component called "nvlddkm.sys"


Here is a recent minidump of a BSoD if it helps:



Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20201225-1730.dmp]Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: srv*

Executable search path is: Windows 10 Kernel Version 19041 MP 4 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalMachine Name:Kernel base = 0xfffff802`58800000 PsLoadedModuleList = 0xfffff802`5942a2b0Debug session time: Fri Dec 25 17:30:14.045 2020 UTC + 5:30System Uptime: 0 days 2:47:03.240Loading Kernel Symbols..Press ctrl-c cdb, kd, ntsd or ctrl-break windbg to abort symbol loads that take too long.Run !sym noisy before .reload to track down problems loading symbols.


.............................................................

.........................................................................................................................................Loading User SymbolsMini Kernel Dump does not contain unloaded driver listFor analysis of this file, run !analyze -vwatchdog!WdpDbgCaptureTriageDump+0x64a:fffff802`65205e1a 488b4328 mov rax,qword ptr [rbx+28h] ds:002b:ffff9904`fe5a9d38=????????????????


2: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************VIDEO_ENGINE_TIMEOUT_DETECTED 141One of the the display engines failed to respond in timely fashion.This code can never be used for a real bugcheck.Arguments:Arg1: ffff9904fdf9a460, Optional pointer to internal TDR recovery context TDR_RECOVERY_CONTEXT.Arg2: fffff802697de9f0, The pointer into responsible device driver module e.g owner tag.Arg3: 0000000000000000, The secondary driver specific bucketing key.Arg4: 00000000000022f0, Optional internal context dependent data.Debugging Details:------------------Unable to load image nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 10468 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on AYAAN Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 18905 Key : Analysis.Memory.CommitPeak.Mb Value: 85 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1OS_BUILD_LAYERS: 1DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated DumpBUGCHECK_CODE: 141BUGCHECK_P1: ffff9904fdf9a460BUGCHECK_P2: fffff802697de9f0BUGCHECK_P3: 0BUGCHECK_P4: 22f0TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202bPROCESS_NAME: SystemSTACK_TEXT: ffffdd0e`217475d0 fffff802`65210ea0 : ffff9904`fdf9a460 ffffdd0e`21747840 ffff9904`fdf9a460 ffff9904`fe5a9d10 : watchdog!WdpDbgCaptureTriageDump+0x64affffdd0e`21747680 fffff802`650b0f19 : 00000000`0000000b ffff9904`f3942000 ffff9904`f39658f0 ffff9904`f7b4f000 : watchdog!WdDbgReportRecreate+0xd0ffffdd0e`217476e0 fffff802`67b312e9 : ffff9904`00000000 ffff9904`fe497070 ffff9904`fdf9a460 ffff9904`f7b4f000 : dxgkrnl!TdrUpdateDbgReport+0x119ffffdd0e`21747740 fffff802`67bd1db5 : ffff9904`f7b4f000 00000000`00000000 ffff9904`f3942000 ffff9904`f7b4f001 : dxgmms2!VidSchiResetEngine+0x709ffffdd0e`217478f0 fffff802`67ba591b : ffff9904`f3942000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xb1ffffdd0e`21747940 fffff802`67b7d6b2 : ffffdd0e`21747a01 00000000`0009c8f9 00000000`00989680 00000000`00000001 : dxgmms2!VidSchiCheckHwProgress+0x2823bffffdd0e`217479b0 fffff802`67b0b9ca : 00000000`00000000 ffff9904`f3942000 ffffdd0e`21747ad9 ffff9904`f3942000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x372ffffdd0e`21747a80 fffff802`67b8b1a5 : ffff9904`defe8200 ffff9904`f3942000 ffff9904`defe8260 ffff9905`0694f010 : dxgmms2!VidSchiScheduleCommandToRun+0x2caffffdd0e`21747b40 fffff802`67b8b15a : ffff9904`f3942400 fffff802`67b8b090 ffff9904`f3942000 fffff802`5598c100 : dxgmms2!VidSchiRun_PriorityTable+0x35ffffdd0e`21747b90 fffff802`58b17e25 : ffff9904`f3954280 fffff802`00000001 ffff9904`f3942000 000fa427`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xcaffffdd0e`21747bd0 fffff802`58bfcdd8 : fffff802`5598c180 ffff9904`f3954280 fffff802`58b17dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55ffffdd0e`21747c20 00000000`00000000 : ffffdd0e`21748000 ffffdd0e`21741000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: nvlddmkm+19e9f0MODULE_NAME: nvlddmkmIMAGE_NAME: nvlddmkm.sysSTACK_COMMAND: .thread ; .cxr ; kbFAILURE_BUCKET_ID: LKD_0x141_IMAGE_nvlddmkm.sysOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc}Followup: MachineOwner---------

:)

 

BSOD while using the internet. error (L1C63x64.sys)


Hi trainman81,

Welcome to the 10forums.

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

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


AVG is trying to request data from the internet, which is why the network driver is marked as the cause.
Code:

Code:

*** WARNING: Unable to verify timestamp for L1C63x64.sys *** ERROR: Module load completed but symbols could not be loaded for L1C63x64.sys 0: kd> lmvm L1C63x64 start             end                 module name fffff801`89700000 fffff801`89722000   L1C63x64 T (no symbols)                Loaded symbol image file: L1C63x64.sys     Image path: \SystemRoot\System32\drivers\L1C63x64.sys     Image name: L1C63x64.sys     Timestamp:        Mon Apr 01 05:15:17 2013 (5158FBC5)     CheckSum:         000245C4     ImageSize:        00022000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

AVG drivers that have been flagged
Code:

Code:

*** WARNING: Unable to verify timestamp for avgwfpa.sys *** ERROR: Module load completed but symbols could not be loaded for avgwfpa.sys *** WARNING: Unable to verify timestamp for avgfwd6a.sys *** ERROR: Module load completed but symbols could not be loaded for avgfwd6a.sys

Please uninstall AVG and see if it helps
Uninstall AVG | AVG
It is further recommended to check your Qualcomm network driver for updates, its driver is not supported for Windows 10.
Driver Reference Table - L1C63x64.sys

 

dxgmms2.sys error

Hi Ed,

The dxgmms2.sys error may arise due to faulty hardware, outdated drivers, and software conflicts. For us to properly determine what's causing this and provide you with the solution to rectify the concern, supply more information by
answering these questions:

• How and when did the issue start?
• May we know what exactly happens when you encounter this error?
  
• Have you recently installed any updates?
• Have you made any significant changes to your device prior to this happening?
• Are there any 3rd party applications or antivirus software installed on your computer?
• What troubleshooting steps have you done so far?

We will be waiting for your reply so we can move forward to resolving your issue.

 

Blue Screen because of cm11264.sys

Hi,

This blue screen error due to cm11264.sys error could have happened due to the corrupted Windows component. To resolve your issue, we suggest that you follow the steps provided in this

article.

Let us know if there is anything else we can do to assist.