Share via

Windows BSOD because of this error

Bogdan 0 Reputation points
2026-03-12T18:10:46.2933333+00:00

Anyone has any idea how can I get more information about this?

Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000df`df41d018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80420269c61, Address of the instruction which caused the BugCheck
Arg3: fffff60adff1e290, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1031

    Key  : Analysis.Elapsed.mSec
    Value: 2060

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29507.1001

    Key  : Analysis.Version.Description
    Value: 10.2511.5.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2511.5.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x3b

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

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

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_nvlddmkm!unknown_function

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

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

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

    Key  : Failure.Hash
    Value: {7eea5677-f68d-2154-717e-887e07e55cd3}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7

    Key  : WER.System.BIOSRevision
    Value: 34.3.0.0


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80420269c61

BUGCHECK_P3: fffff60adff1e290

BUGCHECK_P4: 0

FILE_IN_CAB:  031226-7328-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff828bee69b080

CONTEXT:  fffff60adff1e290 -- (.cxr 0xfffff60adff1e290)
rax=0000000000000000 rbx=ffff828c02abcd88 rcx=ffff828c02abcd88
rdx=ffff828c02f4e6c8 rsi=ffff828c03d665b8 rdi=ffff828be6f569f8
rip=fffff80420269c61 rsp=fffff60adff1ecc0 rbp=ffff828c02f4e6c8
 r8=ffff828c03d665b8  r9=0000000000000000 r10=1fffff0084001598
r11=5405010155500000 r12=fffff60adff1ef60 r13=ffff828be6f56928
r14=ffff828be6f56928 r15=fffff60adff1edc8
iopl=0         nv up ei pl zr na po cy
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00050247
nvlddmkm+0x269c61:
fffff804`20269c61 83782001        cmp     dword ptr [rax+20h],1 ds:002b:00000000`00000020=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  nvcontainer.ex

IP_IN_PAGED_CODE: 
nvlddmkm+269c61
fffff804`20269c61 83782001        cmp     dword ptr [rax+20h],1

STACK_TEXT:  
fffff60a`dff1ecc0 00000000`00000000     : 00000000`00000000 ffff5a83`c2203861 fffff60a`dff1ef60 fffff60a`dff1ef10 : nvlddmkm+0x269c61


SYMBOL_NAME:  nvlddmkm+269c61

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .cxr 0xfffff60adff1e290 ; kb

BUCKET_ID_FUNC_OFFSET:  269c61

FAILURE_BUCKET_ID:  AV_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup:     MachineOwner
---------
Windows for home | Windows 10 | Devices and drivers
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. David-M 106.8K Reputation points Independent Advisor
    2026-03-12T18:47:52.27+00:00

    Hi. I'm David, and I'm happy to help you.


    Based on the information you shared, the crash was caused by the Nvidia driver "nvlddmkm.sys".

    Usually, performing a clean driver installation by uninstalling the current driver using the DDU tool before reinstalling it resolves the issue. However, the driver version you will need to reinstall will depend on the type of device you have.


    Please clarify the following:

    Is your computer a laptop or a desktop?

    If it's a laptop, please share a screenshot of the system information.

    • Press "Windows + R", type msinfo32 and press Enter.

    Maximize the window and use the shortcut "Windows + Shift + S" to use the screenshot tool.


    I await your reply.

    0 comments No comments

  2. Q&A Assist
    2026-03-12T18:11:02.99+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The dump shows a classic SYSTEM_SERVICE_EXCEPTION (0x3B) caused by an access violation (0xC0000005) inside the NVIDIA display driver nvlddmkm.sys while the process nvcontainer.exe was running:

    • Bugcheck: SYSTEM_SERVICE_EXCEPTION (3b)
    • Exception code (Arg1): 0xC0000005 → access violation
    • Faulting IP (Arg2): fffff80420269c61 → inside nvlddmkm.sys
    • Context record (Arg3): fffff60adff1e290
    • Faulting module: IMAGE_NAME: nvlddmkm.sys
    • Failure bucket: AV_nvlddmkm!unknown_function
    • Instruction: cmp dword ptr [rax+20h],1 with rax = 0 → NULL pointer dereference in the NVIDIA driver

    To get more information and confirm root cause using WinDbg:

    1. Use the context record from parameter 3
         .cxr 0xfffff60adff1e290
         kb
      
      This shows the full call stack around the faulting instruction and which code path in nvlddmkm.sys led to the NULL pointer dereference.
    2. Analyze the exception code
         !error 0xc0000005
      
      This will display details for STATUS_ACCESS_VIOLATION and confirm it is a memory access violation.
    3. Identify the faulting driver (already visible here)
      • The bugcheck article notes that if a driver is responsible, its name is printed and can be retrieved via KiBugCheckDriver:
             dx KiBugCheckDriver
        
      • In this dump, nvlddmkm.sys is already clearly identified as the faulting module.
    4. Use !analyze -v (already partially shown in your output)
      • This extension summarizes the bugcheck, exception, and module information and can point to patterns (e.g., access violation in a display driver).

    From a troubleshooting perspective (without source for the NVIDIA driver), the standard guidance for 0x3B applies:

    • This stop code indicates an exception occurred while executing code in a system service, often due to:
      • NULL pointer dereference
      • Access to an invalid or freed address
      • Data structure corruption
    • Since the fault is in nvlddmkm.sys, focus on the graphics stack:
      • Update or roll back the NVIDIA driver.
      • If the issue started after a driver or Windows update, test with a different NVIDIA driver version.
      • Check Device Manager and Event Viewer for related display or driver errors in the same time window.

    If multiple dumps are available, compare their stacks in WinDbg (kb after .cxr) to see if nvlddmkm.sys is consistently at the top of the stack for the 0x3B crashes.


    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.