blue screen code in windbg

Question

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

   -- 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.047 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


Loading Dump File [C:\Windows\Minidump\092223-12421-01.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 22000 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff802`14200000 PsLoadedModuleList = 0xfffff802`14e29840
Debug session time: Fri Sep 22 13:22:29.172 2023 (UTC + 8:00)
System Uptime: 0 days 0:54:40.914
Loading 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 Symbols

Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`1461d4b0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff802`1b0b0740=000000000000000a
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8022ea41b54, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2468

    Key  : Analysis.Elapsed.mSec
    Value: 11584

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: IP_MISALIGNED_nvlddmkm.sys

    Key  : Failure.Hash
    Value: {7ddd7c93-3080-7b78-b4a9-835ce9348670}


BUGCHECK_CODE:  d1

BUGCHECK_P1: 0

BUGCHECK_P2: 9

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8022ea41b54

FILE_IN_CAB:  092223-12421-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

READ_ADDRESS: fffff80214f05450: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 0000000000000000 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8021b0b0880 -- (.trap 0xfffff8021b0b0880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffff8c82abe86000
rdx=0000000000000009 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8022ea41b54 rsp=fffff8021b0b0a18 rbp=fffff8021b0b0b20
 r8=0000000000001001  r9=0000000000001001 r10=0000000000000000
r11=fffff8021b0b07c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nvlddmkm+0xb1b54:
fffff802`2ea41b54 8b3b            mov     edi,dword ptr [rbx] ds:00000000`00000000=????????
Resetting default scope

MISALIGNED_IP: 
nvlddmkm+b1b54
fffff802`2ea41b54 8b3b            mov     edi,dword ptr [rbx]

STACK_TEXT:  
fffff802`1b0b0738 fffff802`14632769     : 00000000`0000000a 00000000`00000000 00000000`00000009 00000000`00000000 : nt!KeBugCheckEx
fffff802`1b0b0740 fffff802`1462df4c     : 00000000`00000003 fffff802`2ea27d79 ffff8c82`abe86000 fffff802`1b0b0908 : nt!KiBugCheckDispatch+0x69
fffff802`1b0b0880 fffff802`2ea41b54     : fffff802`2ea2d052 00000000`000000a7 fffff802`1b0b0b20 ffff8c82`abf77000 : nt!KiPageFault+0x44c
fffff802`1b0b0a18 fffff802`2ea2d052     : 00000000`000000a7 fffff802`1b0b0b20 ffff8c82`abf77000 fffff802`1b0b0a58 : nvlddmkm+0xb1b54
fffff802`1b0b0a20 00000000`000000a7     : fffff802`1b0b0b20 ffff8c82`abf77000 fffff802`1b0b0a58 fffff802`1b0b0b50 : nvlddmkm+0x9d052
fffff802`1b0b0a28 fffff802`1b0b0b20     : ffff8c82`abf77000 fffff802`1b0b0a58 fffff802`1b0b0b50 fffff802`2e9f00a7 : 0xa7
fffff802`1b0b0a30 ffff8c82`abf77000     : fffff802`1b0b0a58 fffff802`1b0b0b50 fffff802`2e9f00a7 ffff8c00`00000001 : 0xfffff802`1b0b0b20
fffff802`1b0b0a38 fffff802`1b0b0a58     : fffff802`1b0b0b50 fffff802`2e9f00a7 ffff8c00`00000001 fffff802`00000000 : 0xffff8c82`abf77000
fffff802`1b0b0a40 fffff802`1b0b0b50     : fffff802`2e9f00a7 ffff8c00`00000001 fffff802`00000000 ffff8c82`abf1c320 : 0xfffff802`1b0b0a58
fffff802`1b0b0a48 fffff802`2e9f00a7     : ffff8c00`00000001 fffff802`00000000 ffff8c82`abf1c320 ffff8c82`ae82c030 : 0xfffff802`1b0b0b50
fffff802`1b0b0a50 ffff8c00`00000001     : fffff802`00000000 ffff8c82`abf1c320 ffff8c82`ae82c030 ffff8c82`abe81050 : nvlddmkm+0x600a7
fffff802`1b0b0a58 fffff802`00000000     : ffff8c82`abf1c320 ffff8c82`ae82c030 ffff8c82`abe81050 fffff802`1b0b0b80 : 0xffff8c00`00000001
fffff802`1b0b0a60 ffff8c82`abf1c320     : ffff8c82`ae82c030 ffff8c82`abe81050 fffff802`1b0b0b80 00000000`00000004 : 0xfffff802`00000000
fffff802`1b0b0a68 ffff8c82`ae82c030     : ffff8c82`abe81050 fffff802`1b0b0b80 00000000`00000004 00000000`00000000 : 0xffff8c82`abf1c320
fffff802`1b0b0a70 ffff8c82`abe81050     : fffff802`1b0b0b80 00000000`00000004 00000000`00000000 00000000`00000000 : 0xffff8c82`ae82c030
fffff802`1b0b0a78 fffff802`1b0b0b80     : 00000000`00000004 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff8c82`abe81050
fffff802`1b0b0a80 00000000`00000004     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff802`14f35bc0 : 0xfffff802`1b0b0b80
fffff802`1b0b0a88 00000000`00000000     : 00000000`00000000 00000000`00000000 fffff802`14f35bc0 00000000`005d72e6 : 0x4


SYMBOL_NAME:  nvlddmkm+b1b54

MODULE_NAME: hardware

IMAGE_NAME:  hardware

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  IP_MISALIGNED_nvlddmkm.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7ddd7c93-3080-7b78-b4a9-835ce9348670}

Followup:     MachineOwner

Accepted Answer

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

Make sure that share links are available without sign in.

.

--please don't forget to upvote and Accept as answer if the reply is helpful--

.

Share via

blue screen code in windbg

0 additional answers

Your answer