blue screen bsod

Question

blue screen bsod

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

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


Loading Dump File [C:\Users\admin\Desktop\010626-8171-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff804`40000000 PsLoadedModuleList = 0xfffff804`40c2a420
Debug session time: Tue Jan  6 21:50:24.398 2026 (UTC + 3:00)
System Uptime: 0 days 4:43:54.102
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols

Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`403fd5c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff818f`3c01f740=0000000000000113
5: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols

Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_DXGKRNL_FATAL_ERROR (113)
The dxgkrnl has detected that a violation has occurred. This resulted
in a condition that dxgkrnl can no longer progress.  By crashing, dxgkrnl
is attempting to get enough information into the minidump such that somebody
can pinpoint the crash cause. Any other values after parameter 1 must be
individually examined according to the subtype.
Arguments:
Arg1: 0000000000000019, The subtype of the BugCheck:
Arg2: 0000000000000002
Arg3: 00000000000010de
Arg4: 0000000000001f11

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2046

    Key  : Analysis.Elapsed.mSec
    Value: 15640

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29482.1003

    Key  : Analysis.Version.Description
    Value: 10.2509.29.03 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2509.29.3

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x113

    Key  : Bugcheck.Code.TargetModel
    Value: 0x113

    Key  : DirectX.FatalError.Code
    Value: 0x19

    Key  : DirectX.FatalError.Desc
    Value: UNEXPECTED_DEFERRED_DESTRUCTION

    Key  : Failure.Bucket
    Value: 0x113_19_nvlddmkm!unknown_function

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff80471d172a3

    Key  : Failure.Exception.IP.Module
    Value: nvlddmkm

    Key  : Failure.Exception.IP.Offset
    Value: 0xd372a3

    Key  : Failure.Hash
    Value: {fb504da1-90a7-64ec-e7aa-d0c04338976f}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.System.BIOSRevision
    Value: 7.2.0.0


BUGCHECK_CODE:  113

BUGCHECK_P1: 19

BUGCHECK_P2: 2

BUGCHECK_P3: 10de

BUGCHECK_P4: 1f11

FILE_IN_CAB:  010626-8171-01.dmp

FAULTING_THREAD:  ffffd287fdcde040

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

IP_IN_PAGED_CODE: 
nvlddmkm+d372a3
fffff804`71d172a3 448bc3          mov     r8d,ebx

STACK_TEXT:  
ffff818f`3c01f738 fffff804`57583ad0     : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx
ffff818f`3c01f740 fffff804`573c8064     : ffffd288`01c7b180 ffffd288`0fe37010 ffffd288`01c7b180 ffffd288`01c7b180 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff818f`3c01f780 fffff804`57346c31     : ffff818f`3c01f800 00000000`00000000 ffffd288`00000000 ffffd288`0fe37200 : dxgkrnl!DpiFdoHandleDevicePower+0x80b94
ffff818f`3c01f820 fffff804`57348161     : ffffd288`0fe37010 ffffd288`01c7b180 ffffd288`01c7b030 ffffd288`01c7b030 : dxgkrnl!DpiFdoDispatchPower+0x21
ffff818f`3c01f850 fffff804`71d172a3     : 00000000`00000001 00000000`00000000 00000000`00000000 ffffd288`0cfad000 : dxgkrnl!DpiDispatchPower+0xe1
ffff818f`3c01f970 00000000`00000001     : 00000000`00000000 00000000`00000000 ffffd288`0cfad000 ffff818f`3c01fa1c : nvlddmkm+0xd372a3
ffff818f`3c01f978 00000000`00000000     : 00000000`00000000 ffffd288`0cfad000 ffff818f`3c01fa1c ffffd287`00000004 : 0x1


SYMBOL_NAME:  nvlddmkm+d372a3

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffffd287fdc9a140; .thread 0xffffd287fdcde040 ; kb

BUCKET_ID_FUNC_OFFSET:  d372a3

FAILURE_BUCKET_ID:  0x113_19_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fb504da1-90a7-64ec-e7aa-d0c04338976f}

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

5: kd> .thread /r /p ffffd287fdcde040
Implicit thread is now ffffd287`fdcde040
Implicit process is now ffffd287`fdc9a140
Loading User Symbols


************* Symbol Loading Error Summary **************
Module name            Error
nvlddmkm               The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
5: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff804`70fe0000 fffff804`77725000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nvcvi.inf_amd64_d45d8d77dcc0fc1f\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Tue Dec 30 17:49:47 2025 (6953E68B)
    CheckSum:         0647471A
    ImageSize:        06745000
    Mapping Form:     Loaded
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
5: kd> .process /r /p 0xffffd287fdc9a140; .thread 0xffffd287fdcde040 ; kb
Implicit process is now ffffd287`fdc9a140
Loading User Symbols


************* Symbol Loading Error Summary **************
Module name            Error
nvlddmkm               The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
Implicit thread is now ffffd287`fdcde040
  *** Stack trace for last set context - .thread/.cxr resets it
 # RetAddr               : Args to Child                                                           : Call Site
00 fffff804`57583ad0     : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx
01 fffff804`573c8064     : ffffd288`01c7b180 ffffd288`0fe37010 ffffd288`01c7b180 ffffd288`01c7b180 : watchdog!WdLogEvent5_WdCriticalError+0xe0
02 fffff804`57346c31     : ffff818f`3c01f800 00000000`00000000 ffffd288`00000000 ffffd288`0fe37200 : dxgkrnl!DpiFdoHandleDevicePower+0x80b94
03 fffff804`57348161     : ffffd288`0fe37010 ffffd288`01c7b180 ffffd288`01c7b030 ffffd288`01c7b030 : dxgkrnl!DpiFdoDispatchPower+0x21
04 fffff804`71d172a3     : 00000000`00000001 00000000`00000000 00000000`00000000 ffffd288`0cfad000 : dxgkrnl!DpiDispatchPower+0xe1
05 00000000`00000001     : 00000000`00000000 00000000`00000000 ffffd288`0cfad000 ffff818f`3c01fa1c : nvlddmkm+0xd372a3
06 00000000`00000000     : 00000000`00000000 ffffd288`0cfad000 ffff818f`3c01fa1c ffffd287`00000004 : 0x1

3 answers

Your answer

Answer 1

Jonathan Deives 63,465 Independent Advisor

The minidump log indicates that the cause of the BSOD is "nvlddmkm.sys" which is an NVIDIA driver.

Uninstall the current graphics card driver using DDU tool, go to the nvidia website and search for the driver before the last one released, download and install it.

https://www.nvidia.com/en-us/drivers/

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

вадим толоконников 0 Reputation points

2026-01-09T09:13:34.6166667+00:00

I removed the driver using ddu and installed a new one, but it didn't help

Answer 2

вадим толоконников 0

I removed the driver using ddu and installed a new one, but it didn't help

Answer 3

Hi вадим толоконников,
Welcome to Microsoft Q&A forum. I'm happy to help.

The latest driver version is not always the best. Please try various versions if possible.

In addition, your GPU may not be stable with current frequency. Please navigate to its manufactural website to download the tool to underclock GPU core and GPU memory to see if the issue is gone.

You may also want to run GPU stress test with applications like FurMark, GPU Caps Viewer, OCCT.

Disclaimer: Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party linked sites or any support related to technology.

In case your GPU fails stress test even after underclocked, then you probably have hardware issue.

I hope that above information is helpful to you.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Lucus-V 3,995 Reputation points Microsoft External Staff Moderator

2026-01-12T22:43:55.7366667+00:00

Hi вадим толоконников,
I hope everything is going well on your end. Just wanted to check in and see how things are going for you lately, anything you'd like to share or discuss?

Share via

blue screen bsod

3 answers

Your answer