Ask a new question

NVIDIA crash - Related to nvlddmkm process

Hi all,

For the past week or so I've had some BSODs. The issue points to the nvlddmkm process. So far, I've:

  • Reinstalled the NVIDIA driver

  • manually uninstalled the NVIDIA driver, restarted, then installed an older NVIDIA driver from Dec 2021

  • run RAM checker (no issues)

  • verified the windows image (no issues)

The issue continues and occurs at random moments. I'm half expecting it to fail right now. Here's the crash report. I'd be grateful for any advice. 

Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\090922-10468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`7b600000 PsLoadedModuleList = 0xfffff801`7c22a250
Debug session time: Fri Sep  9 17:11:49.129 2022 (UTC - 4:00)
System Uptime: 0 days 4:26:17.756
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`7b9f88c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff801`7960d480=0000000000000133
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
	DISPATCH_LEVEL or above. The offending component can usually be
	identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8017c2fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3796

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7183

    Key  : Analysis.Init.CPU.mSec
    Value: 343

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2200

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 85

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  090922-10468-01.dmp

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8017c2fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8017960d7f0 -- (.trap 0xfffff8017960d7f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa50d8c0cf7e0 rbx=0000000000000000 rcx=ffffa50d86c17000
rdx=ffffa50d8c0cf7e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8031c4a4150 rsp=fffff8017960d988 rbp=0000000000000000
 r8=0000000000000018  r9=fffff8017960db20 r10=0000000000000003
r11=000000000000000c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x14150:
fffff803`1c4a4150 b801000000      mov     eax,1
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  steam.exe

STACK_TEXT:  
fffff801`7960d478 fffff801`7ba2a998     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`7c2fb320 : nt!KeBugCheckEx
fffff801`7960d480 fffff801`7b850fed     : 000003ab`650231f8 fffff801`77df7180 00000000`00200246 00000000`000f9a70 : nt!KeAccumulateTicks+0x1dcbc8
fffff801`7960d4e0 fffff801`7b851591     : 00000000`00000003 00000000`00094cdf fffff801`77df7180 00000000`00001001 : nt!KiUpdateRunTime+0x5d
fffff801`7960d530 fffff801`7b84b403     : fffff801`77df7180 00000000`00000000 fffff801`7c231818 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff801`7960d670 fffff801`7b853e02     : fffff801`7960d7f0 fffff801`7960d870 fffff801`7960d800 00000000`00000005 : nt!KeClockInterruptNotify+0x2e3
fffff801`7960d720 fffff801`7b8d9405     : 00000025`33d1bad4 fffff801`7c2f3a20 fffff801`7c2f3ad0 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
fffff801`7960d750 fffff801`7b9fa36a     : fffff801`7960d870 fffff801`7c2f3a20 fffff801`7960db20 fffff803`1c532bf5 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`7960d7a0 fffff801`7b9fa8d7     : 00000000`00b81010 fffff803`1c518763 00000000`00611c30 fffff803`1c5b076b : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff801`7960d7f0 fffff803`1c4a4150     : fffff803`1c84b6a0 ffffa50d`86c17000 fffff803`1c51971f fffff801`7960db20 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`7960d988 fffff803`1c84b6a0     : ffffa50d`86c17000 fffff803`1c51971f fffff801`7960db20 fffff803`1c8289c0 : nvlddmkm+0x14150
fffff801`7960d990 ffffa50d`86c17000     : fffff803`1c51971f fffff801`7960db20 fffff803`1c8289c0 fffff801`7960db20 : nvlddmkm+0x3bb6a0
fffff801`7960d998 fffff803`1c51971f     : fffff801`7960db20 fffff803`1c8289c0 fffff801`7960db20 fffff803`1c52d170 : 0xffffa50d`86c17000
fffff801`7960d9a0 fffff801`7960db20     : fffff803`1c8289c0 fffff801`7960db20 fffff803`1c52d170 ffffa50d`86c17000 : nvlddmkm+0x8971f
fffff801`7960d9a8 fffff803`1c8289c0     : fffff801`7960db20 fffff803`1c52d170 ffffa50d`86c17000 ffffa50d`8be52010 : 0xfffff801`7960db20
fffff801`7960d9b0 fffff801`7960db20     : fffff803`1c52d170 ffffa50d`86c17000 ffffa50d`8be52010 ffffa50d`8be52010 : nvlddmkm+0x3989c0
fffff801`7960d9b8 fffff803`1c52d170     : ffffa50d`86c17000 ffffa50d`8be52010 ffffa50d`8be52010 ffffa50d`8ba4b000 : 0xfffff801`7960db20
fffff801`7960d9c0 ffffa50d`86c17000     : ffffa50d`8be52010 ffffa50d`8be52010 ffffa50d`8ba4b000 fffff801`7960db20 : nvlddmkm+0x9d170
fffff801`7960d9c8 ffffa50d`8be52010     : ffffa50d`8be52010 ffffa50d`8ba4b000 fffff801`7960db20 fffff801`7960dae3 : 0xffffa50d`86c17000
fffff801`7960d9d0 ffffa50d`8be52010     : ffffa50d`8ba4b000 fffff801`7960db20 fffff801`7960dae3 ffffa50d`8c0cf7e0 : 0xffffa50d`8be52010
fffff801`7960d9d8 ffffa50d`8ba4b000     : fffff801`7960db20 fffff801`7960dae3 ffffa50d`8c0cf7e0 ffffa50d`8b06f060 : 0xffffa50d`8be52010
fffff801`7960d9e0 fffff801`7960db20     : fffff801`7960dae3 ffffa50d`8c0cf7e0 ffffa50d`8b06f060 000003ab`65005100 : 0xffffa50d`8ba4b000
fffff801`7960d9e8 fffff801`7960dae3     : ffffa50d`8c0cf7e0 ffffa50d`8b06f060 000003ab`65005100 ffffa50d`86c17000 : 0xfffff801`7960db20
fffff801`7960d9f0 ffffa50d`8c0cf7e0     : ffffa50d`8b06f060 000003ab`65005100 ffffa50d`86c17000 ffffa50d`8be52010 : 0xfffff801`7960dae3
fffff801`7960d9f8 ffffa50d`8b06f060     : 000003ab`65005100 ffffa50d`86c17000 ffffa50d`8be52010 fffff801`7960db20 : 0xffffa50d`8c0cf7e0
fffff801`7960da00 000003ab`65005100     : ffffa50d`86c17000 ffffa50d`8be52010 fffff801`7960db20 00000000`00000050 : 0xffffa50d`8b06f060
fffff801`7960da08 ffffa50d`86c17000     : ffffa50d`8be52010 fffff801`7960db20 00000000`00000050 fffff803`1c5162b2 : 0x000003ab`65005100
fffff801`7960da10 ffffa50d`8be52010     : fffff801`7960db20 00000000`00000050 fffff803`1c5162b2 fffff801`7960db20 : 0xffffa50d`86c17000
fffff801`7960da18 fffff801`7960db20     : 00000000`00000050 fffff803`1c5162b2 fffff801`7960db20 ffffa50d`8c0cf7e0 : 0xffffa50d`8be52010
fffff801`7960da20 00000000`00000050     : fffff803`1c5162b2 fffff801`7960db20 ffffa50d`8c0cf7e0 00000000`00000000 : 0xfffff801`7960db20
fffff801`7960da28 fffff803`1c5162b2     : fffff801`7960db20 ffffa50d`8c0cf7e0 00000000`00000000 fffff801`7960db20 : 0x50
fffff801`7960da30 fffff801`7960db20     : ffffa50d`8c0cf7e0 00000000`00000000 fffff801`7960db20 00000000`00000000 : nvlddmkm+0x862b2
fffff801`7960da38 ffffa50d`8c0cf7e0     : 00000000`00000000 fffff801`7960db20 00000000`00000000 00000000`00000000 : 0xfffff801`7960db20
fffff801`7960da40 00000000`00000000     : fffff801`7960db20 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffa50d`8c0cf7e0


SYMBOL_NAME:  nvlddmkm+14150

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  14150

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner
---------

0: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff803`1c490000 fffff803`1e90b000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_db8d3f1ff9f89487\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Dec  6 18:30:13 2021 (61AE9D05)
    CheckSum:         023D47E2
    ImageSize:        0247B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
Hi and thanks for reaching out. My name is Bernard a Windows fan like you. I'll be happy to help you out today.

I understand the issue you have, nothing to worry I am here to help.

First, before reinstalling Nvidia Driver I suggest doing a clean installation of Nvidia driver first, by referring to this link: https://nvidia.custhelp.com/app/answers/detail/...

If none will work from the above solution, I suggest doing an in-place upgrade wherein it will upgrade the device to the latest version and repair all issues without deleting any files.

Note: before doing this make sure to create a restore point: https://support.microsoft.com/en-hk/help/402753...

1. go to this link: https://www.microsoft.com/en-us/software-downlo...

2. Select Download tool, and select Run. You need to be an administrator to run this tool.

3. On the License terms page, if you accept the license terms, select Accept.

4. On the What do you want to do? page, select Upgrade this PC now, and then select Next.

5. After downloading and installing, it should fix the issue.

Reference: https://www.microsoft.com/en-us/software-downlo...


Let me know how it goes and I hope that helps.

Bernard
Independent Advisor

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

So I tried both a clean installation and a in-place upgrade as described above. Still no luck. Did the upgrade yesterday evening and used my computer this evening. Just had a crash after only a few hours of running. 

Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\091222-10500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`3c400000 PsLoadedModuleList = 0xfffff802`3d02a250
Debug session time: Mon Sep 12 23:34:03.017 2022 (UTC - 4:00)
System Uptime: 1 days 7:58:53.644
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`3c7f88c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff802`393ade20=0000000000000133
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8023d0fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding this single DPC timeout

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2984

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 10656

    Key  : Analysis.Init.CPU.mSec
    Value: 468

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2251

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 93

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  091222-10500-01.dmp

BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8023d0fb320

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff802393a62c0 -- (.trap 0xfffff802393a62c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa0067ceeea40 rbx=0000000000000000 rcx=ffffa0067ceee000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8025c644753 rsp=fffff802393a6450 rbp=0000000000bb0084
 r8=0000000000000000  r9=0000000000bb0084 r10=ffffa0067cef0380
r11=0000000000000005 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nvlddmkm+0x184753:
fffff802`5c644753 4c397020        cmp     qword ptr [rax+20h],r14 ds:ffffa006`7ceeea60=ffffa0067ce78df0
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  steam.exe

STACK_TEXT:  
fffff802`393ade18 fffff802`3c82a914     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff802`393ade20 fffff802`3c64b573     : 00004c31`e845c5af fffff802`37b1b180 00000000`00000000 fffff802`37b1b180 : nt!KeAccumulateTicks+0x1dcb44
fffff802`393ade80 fffff802`3c64b05a     : fffff802`3d0f3900 fffff802`393a6340 00000000`00000000 fffff802`393adf20 : nt!KeClockInterruptNotify+0x453
fffff802`393adf30 fffff802`3c6d9405     : fffff802`3d0f3900 fffff802`3c7f9f80 ffffc380`14b6a788 ffffc380`14b6a780 : nt!HalpTimerClockIpiRoutine+0x1a
fffff802`393adf60 fffff802`3c7fa36a     : fffff802`393a6340 fffff802`3d0f3900 00000000`00000000 00000000`00bb0084 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`393adfb0 fffff802`3c7fa8d7     : ffffa006`7ceeea40 ffffa006`7ceee000 00000000`00000000 00001f80`00000200 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff802`393a62c0 fffff802`5c644753     : ffffa006`7ceee000 00000000`00000020 00000000`01000010 00000000`00000246 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`393a6450 ffffa006`7ceee000     : 00000000`00000020 00000000`01000010 00000000`00000246 fffff802`393a6480 : nvlddmkm+0x184753
fffff802`393a6458 00000000`00000020     : 00000000`01000010 00000000`00000246 fffff802`393a6480 00000000`00000000 : 0xffffa006`7ceee000
fffff802`393a6460 00000000`01000010     : 00000000`00000246 fffff802`393a6480 00000000`00000000 00000000`00000000 : 0x20
fffff802`393a6468 00000000`00000246     : fffff802`393a6480 00000000`00000000 00000000`00000000 ffffa006`7ceeea40 : 0x1000010
fffff802`393a6470 fffff802`393a6480     : 00000000`00000000 00000000`00000000 ffffa006`7ceeea40 ffffa006`7cfaa000 : 0x246
fffff802`393a6478 00000000`00000000     : 00000000`00000000 ffffa006`7ceeea40 ffffa006`7cfaa000 00000000`00000000 : 0xfffff802`393a6480


SYMBOL_NAME:  nvlddmkm+184753

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  184753

FAILURE_BUCKET_ID:  0x133_DPC_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {15c3af0e-5564-7a80-2e26-65b5115ecc4d}

Followup:     MachineOwner

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Just an update, got a new GPU. Issue still occurs. Pretty much the same as this person's experience:

BSOD's, random restarts, and nvlddmkm.sys stops responding and - Microsoft Community

I'm still looking for a resolution. Let me know if anyone has any ideas.

8 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi,

This may help: forums.tomshardware.com/threads/nvlddmkm-crashes-and-bluescreens.3716097/post-22413792

And this: reddit.com/r/techsupport/comments/dnm7pt/comment/fnnm9p7

[edit] And this: linustechtips.com/topic/1389625-nvlddmkm-nvidia-driver-crashing-repeatedly/#comment-15156272

My system did this for the first time today while in the Modern Warfare II pre-game screen. After a spot of research (verifying Steam game files not having worked) I decided to uninstall my RTX 3070 from Device Manager, ticking the box to delete the driver software. (After a few minutes I found it had reinstalled itself - Windows, trying to be helpful yet at the most unhelpful moment possible, had restored the Nvidia driver from Windows Update.) I'd already dowloaded the latest Nvidia driver .exe package, so I disabled my network adapter to stop WU reinstalling the driver, and tried the removal again - success.

I then cleaned up with Wise Program Uninstaller to safely uninstall any remnants of Nvidia installed apps (e.g. GeForce Experience, Control Panel, Physx) and had to fall back on the 'force uninstall' option for any stubborn bits. Then further tidy up with Wise Registry Cleaner, cleaning all discovered issues, then running the included system tuneup util. (I am a power user and IMO this util is excellent - it corrects a large number of bad Windows settings in one fell swoop (e.g. Fast Startup - a travesty! Removing the sanitising action of a regular full Windows restart is a horrible idea - it causes various software problems to accumulate in Windows, and introduces kernel instability. Nobody should leave this turned on - particularly in the age of SSDs.)

Anyway, new Nvidia driver installed (avoiding 'express install') and choosing the 'clean install' option in Advanced, then a final reboot. You may or may not need GeForce Experience (most people don't, unless they're streaming or otherwise need to capture video from games/other applications. If you don't need it, choose driver only.

Also worth noting I had MSI Afterburner running with hardware monitoring enabled - as you'll see from some of the comments in those threads, any software which is querying your CPU/GPU hardware (e.g. for monitoring purposes) particularly at the low level, could result in this kind of instability. I've turned off Afterburner for now. If you have any such software running, try disabling it.

It's early days but my system has been stable since doing the above. Will be doing some extended stress testing in the coming days...

I hope the above fixes the issue for you. If not, at least you'll be enjoying a garbage-free registry and squeaky clean GPU driver, which are always good things. :)

James

8 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hunting the same issue with MW2/WZ2.

Some information I have collected on my research:
Potential solutions/ additional information relating the issue:

  1. Crashing due to nvlddmkm failing to respond:

https://www.nvidia.com/en-us/geforce/forums/discover/54045/the-nvlddmkm-error-what-is-it-an-fyi-for-those-seeing-this-issue/

https://www.reddit.com/r/battlefield_4/comments/1xzzn4/tdrdelay_10_fixed_my_crashes_since_last_patch/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

2) NVIDIA Acknowledgment of 3060 Ti not detected after upgrade to 526.98

https://nvidia.custhelp.com/app/answers/detail/a_id/5412/~/game-ready-driver-526.98-installation-failure-on-geforce-rtx-3060-ti

Still have the issue. I am currently trying to undervolt (I have a Zotac OC). My goal is to see if reverting the clock speeds back to NVIDIA stock will help. I will report in a little bit.

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Nub here also trying to figure this out. Hope someone figures our a fix or nvidia drops a patch

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info

Last updated April 25, 2024 Views 24,948 Applies to: