Share via

BUGCHECK_CODE: 3b on multiple Windows 2022 VMs

Anonymous
2023-10-26T11:02:10+00:00

Hello,

I have a problem with BSOD on Windows 2022 VMs.

The VMs are running on a ESXi 8 environment and all is upgraded with latest versions.

However many VMs are failing with BSOD.

According to VMware they believe this to be an OS issue. I'm unable to find anything in the dump that points to a driver for that matter. 

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8002ff0e389

BUGCHECK_P3: ffffdc8ebe3a96c0

BUGCHECK_P4: 0

FILE_IN_CAB:  MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

CONTEXT:  ffffdc8ebe3a96c0 -- (.cxr 0xffffdc8ebe3a96c0)
rax=0000000000000002 rbx=00000198f1dc1004 rcx=0000000000000002
rdx=0000000000000003 rsi=ffff9281e03a1000 rdi=0000000000000000
rip=fffff8002ff0e389 rsp=ffffdc8ebe3aa0e0 rbp=ffffdc8ebe3aa1f1
 r8=00000000ffffffff  r9=7fff9281e03a1050 r10=7ffffffffffffffc
r11=0000000000000000 r12=ffff9281e03a108c r13=0000000000000000
r14=ffff9281e9f568a0 r15=00000198f1dc1004
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!CmpUpdateKeyNodeAccessBits+0x45:
fffff800`2ff0e389 08430c          or      byte ptr [rbx+0Ch],al ds:002b:00000198`f1dc1010=??
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  Registry

STACK_TEXT:  
ffffdc8e`be3aa0e0 fffff800`2feaed3d     : 00000000`00000000 00000000`00000000 ffff9281`e03a1000 ffff9281`e03a1000 : nt!CmpUpdateKeyNodeAccessBits+0x45
ffffdc8e`be3aa110 fffff800`2feaf213     : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmEnumerateKey+0x31d
ffffdc8e`be3aa240 fffff800`2fc34685     : 00000000`00000000 00000000`00000000 00000000`00020019 000000f8`d8ffed90 : nt!NtEnumerateKey+0x3e3
ffffdc8e`be3aa430 00007ffc`cca20814     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000f8`d8ffe7c8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`cca20814

SYMBOL_NAME:  nt!CmpUpdateKeyNodeAccessBits+45

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .cxr 0xffffdc8ebe3a96c0 ; kb

BUCKET_ID_FUNC_OFFSET:  45

FAILURE_BUCKET_ID:  AV_nt!CmpUpdateKeyNodeAccessBits

OS_VERSION:  10.0.20348.859

BUILDLAB_STR:  fe_release_svc_prod2

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {80329bcd-3295-f74e-7819-ca0df7eca8c6}

Followup:     MachineOwner

Is there anyone on this forum that would like to take a look at the crash dump and see if they can spot something?
Windows for business Windows Server Performance System performance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-10-27T02:13:14+00:00

    Hello

    Thank you for posting in Microsoft Community forum.

    It appears that you’re dealing with a Bug Check 3B: SYSTEM_SERVICE_EXCEPTION. This check is usually caused by an exception that occurs during the execution of a routine that transitions from non-privileged code to privileged code.

    Here are some details from the dump you provided:

    Exception Code: c0000005 (Access violation)

    Faulting IP: fffff8002ff0e389 (nt!CmpUpdateKeyNodeAccessBits+0x45)

    Process Name: Registry

    The error occurred in the nt!CmpUpdateKeyNodeAccessBits+0x45 function of the ntkrnlmp.exe module. This function is part of the Windows NT Kernel & System.

    The access violation occurred while trying to write to memory location 00000198f1dc1010, which seems to be causing the system service exception.

    You might want to investigate further into what’s causing this access violation. It could be due to faulty hardware, a driver issue, or even a software problem. If you recently installed new hardware or software, consider rolling back or uninstalling to see if the problem persists.

    Please note that this is a general analysis based on the provided dump and might not pinpoint the exact cause of your issue.

    For the dump files, it is better to open start and search for feedback and open the Feedback Hub app and file a bug report and attach dump files there:

    Send feedback to Microsoft with the Feedback Hub app - Microsoft Support

    Or contact Microsoft online support engineers for help:

    Global Customer Service phone numbers - Microsoft Support

    Best Regards,

    Wesley Li

    0 comments