Azure Local BugCheck 3b when validating network in Azure Portal

Question

Twice now, my Azure Local 23H2 2411 has BugChecked 3B while validating the cluster in the Azure Portal. Hooking the memory dump to ntsd, and running !analyze -v gives the following output:

Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64

Loading Dump File [Q:\systemp\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

************* Path validation summary **************

Response Time (ms) Location

Deferred cache*D:\Symbols

Deferred srv*https://msdl.microsoft.com/download/symbols

Symbol search path is: cacheD:\Symbols;srvhttps://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 25398 MP (80 procs) Free x64

Product: Server, suite: TerminalServer SingleUserTS

Edition build lab: 25398.1.amd64fre.zn_release.230610-1204

Machine Name:

Kernel base = 0xfffff8005fa00000 PsLoadedModuleList = 0xfffff80060813a10

Debug session time: Sun Dec 15 01:34:32.128 2024 (UTC + 1:00)

System Uptime: 0 days 0:39:59.886

Loading Kernel Symbols

...............................................................

................................................................

...............................................

Loading User Symbols

PEB is paged out (Peb.Ldr = 000000bb`2a1ee018). Type ".hh dbgerr001" for details

Loading unloaded module list

.......

For analysis of this file, run !analyze -v

2: kd> !reload

Loading Kernel Symbols

...............................................................

................................................................

...............................................

Loading User Symbols

PEB is paged out (Peb.Ldr = 000000bb`2a1ee018). Type ".hh dbgerr001" for details

Loading unloaded module list

.......

2: kd> !analyze -v

                   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: fffff8007c325971, Address of the instruction which caused the BugCheck

Arg3: fffff985e8d7f660, Address of the context record for the exception that caused the BugCheck

Arg4: 0000000000000000, zero.

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec

Value: 3702

Key  : Analysis.DebugAnalysisManager

Value: Create

Key  : Analysis.Elapsed.mSec

Value: 15469

Key  : Analysis.Init.CPU.mSec

Value: 890

Key  : Analysis.Init.Elapsed.mSec

Value: 32843

Key  : Analysis.Memory.CommitPeak.Mb

Value: 142

Key  : WER.OS.Branch

Value: zn_release

Key  : WER.OS.Timestamp

Value: 2023-06-10T12:04:00Z

Key  : WER.OS.Version

Value: 10.0.25398.1

FILE_IN_CAB: MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x800

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8007c325971

BUGCHECK_P3: fffff985e8d7f660

BUGCHECK_P4: 0

CONTEXT: fffff985e8d7f660 -- (.cxr 0xfffff985e8d7f660)

rax=0000000000000000 rbx=0000000000000000 rcx=fffff8007c3bf9b8

rdx=0000000000000000 rsi=ffffe602ad257000 rdi=ffffe60291a56770

rip=fffff8007c325971 rsp=fffff985e8d80080 rbp=fffff985e8d800f8

r8=0000000000000000 r9=ffffe60291fcf1c0 r10=0000000000000000

r11=fffff985e8d80070 r12=0000000000000001 r13=ffffe602ad258640

r14=0000000000000001 r15=fffff20662a1c000

iopl=0 nv up ei pl zr na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246

vmswitch!VmsVmqPvtAllocateVmq+0xcc5:

fffff8007c325971 3882b50f0000 cmp byte ptr [rdx+0FB5h],al ds:002b:0000000000000fb5=??

Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: vmms.exe

STACK_TEXT:

fffff985e8d80080 fffff8007c326323 : fffff20662b0f000 ffffe6029211a000 fffff8007c3f3200 fffff8006051f001 : vmswitch!VmsVmqPvtAllocateVmq+0xcc5

fffff985e8d80140 fffff8007c3264a4 : fffff20662a1c000 fffff8007c00ff00 fffff20662b0f000 0000000000000000 : vmswitch!VmsVmqPvtAllocateVmqAndPropagateChanges+0x113

fffff985e8d801a0 fffff8007c2a6773 : ffffe602ad257000 ffffe602ad257000 0000000000000001 fffff20662b0f000 : vmswitch!VmsVmqPvtAllocateVmqForNic+0xf8

fffff985e8d80200 fffff8007c25c75a : fffff8007c3f32f8 fffff985e8d80540 ffffe602ad257000 ffffe602ad257000 : vmswitch!VmsVmqDoVmqOperation+0x1eb

fffff985e8d80270 fffff8007c283c5e : fffff985e8d804e8 0000000000000000 0000000000000000 000000000000ff02 : vmswitch!VmsOmNicConnect+0x1cee

fffff985e8d80440 fffff8007c29d9b8 : 0022341402481007 fffff206601e9d01 ffffe60292b1cb70 0000000000223401 : vmswitch!VmsCdpNicConnect+0x65a

fffff985e8d805a0 fffff8006540136d : fffff206601e9d10 0022341402481003 000000059675f309 0000000000000328 : vmswitch!VmsCdpDeviceControl+0x388

fffff985e8d80630 fffff8005fcfcfb5 : fffff206601e9d10 0000000000000069 fffff985e8d80721 0000000000000002 : VmsProxy!VmsProxyDeviceControl+0xad

fffff985e8d80680 fffff8006017b88d : ffffe60291e05cb0 fffff985e8d80721 0000000000000000 ffffe60292b1cb70 : nt!IofCallDriver+0x55

fffff985e8d806c0 fffff8006017c35b : 0000000000000005 ffffe60292b1cb70 fffff985e8d80b60 0000000000000000 : nt!IopSynchronousServiceTail+0x1dd

fffff985e8d80770 fffff8006017bc06 : fffff30148f03ea8 0000000000000000 0000000000000000 0000000000000000 : nt!IopXxxControlFile+0x73b

fffff985e8d80a00 fffff8005fe80c45 : 0000025c654cffd0 000000bb2aa7e640 0000025c649b1620 0000025c61bce0c8 : nt!NtDeviceIoControlFile+0x56

fffff985e8d80a70 00007ffa51d23424 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25

000000bb2aa7d928 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`51d23424

SYMBOL_NAME: vmswitch!VmsVmqPvtAllocateVmq+cc5

MODULE_NAME: vmswitch

IMAGE_NAME: vmswitch.sys

STACK_COMMAND: .cxr 0xfffff985e8d7f660 ; kb

BUCKET_ID_FUNC_OFFSET: cc5

FAILURE_BUCKET_ID: AV_vmswitch!VmsVmqPvtAllocateVmq

OS_VERSION: 10.0.25398.1

BUILDLAB_STR: zn_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a9738849-c8fc-67c5-4d90-738f3466c062}

Followup: MachineOwner

2: kd>

Answer

Hi pwehland,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
https://zcusa.951200.xyz/en-us/windows-hardware/drivers/debugger/bug-check-0x3b--system-service-exception

Arg1: 00000000c0000005 - This indicates an access violation occurred.

Arg2: fffff8007c325971 - This is the address of the instruction that caused the BugCheck.

Failure Bucket ID: AV_vmswitch!VmsVmqPvtAllocateVmq

The stack trace indicates that the failure occurred in the vmswitch module, specifically in the function VmsVmqPvtAllocateVmq

Recommendations:

If new device drivers or system services have been added recently, try removing or updating them.The vmswitch.sys driver may be corrupted or outdated. Ensure that your drivers for virtual switches and network interfaces are updated.
If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.
VMQ can sometimes cause issues, especially if the hardware doesn’t fully support it or is improperly configured. Try disabling it: Get-NetAdapterVmq | Disable-NetAdapterVmq Re-run your cluster validation in the Azure Portal and observe if the crash reoccurs.
If you have any further queries, do let us know.

Share via

Azure Local BugCheck 3b when validating network in Azure Portal

1 answer

Your answer