BsoD on all Azure AVDs RESOURCE_NOT_OWNED

Lukas Gieske 0 Reputation points
2023-05-04T07:15:01.1866667+00:00

Hello Community,

I'm having trouble since few months on all our AVDs with sporadic Bluescreens. BlueScreens occur random on time and there are not the same users logged in on the AVD. Windows 10 are updated and are 22H2 Build 19045.2846.

Minidump is telling me following:

RESOURCE_NOT_OWNED (e3)

A thread tried to release a resource it did not own.

Arguments:

Arg1: ffff9e0b50493090, Address of resource

Arg2: ffff9e0b748d6080, Address of thread

Arg3: ffff9e0b54b1ee10, Address of owner table if there is one

Arg4: 0000000000000002

Debugging Details:


KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec

Value: 3249

Key  : Analysis.DebugAnalysisManager

Value: Create

Key  : Analysis.Elapsed.mSec

Value: 23370

Key  : Analysis.IO.Other.Mb

Value: 1

Key  : Analysis.IO.Read.Mb

Value: 0

Key  : Analysis.IO.Write.Mb

Value: 2

Key  : Analysis.Init.CPU.mSec

Value: 124

Key  : Analysis.Init.Elapsed.mSec

Value: 13179

Key  : Analysis.Memory.CommitPeak.Mb

Value: 100

Key  : Bugcheck.Code.DumpHeader

Value: 0xe3

Key  : Bugcheck.Code.Register

Value: 0xe3

Key  : WER.OS.Branch

Value: vb_release

Key  : WER.OS.Timestamp

Value: 2019-12-06T14:06:00Z

Key  : WER.OS.Version

Value: 10.0.19041.1

FILE_IN_CAB: 050323-36312-01.dmp

VIRTUAL_MACHINE: HyperV

BUGCHECK_CODE: e3

BUGCHECK_P1: ffff9e0b50493090

BUGCHECK_P2: ffff9e0b748d6080

BUGCHECK_P3: ffff9e0b54b1ee10

BUGCHECK_P4: 2

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: OneDrive.exe

STACK_TEXT:

ffffea0cebfcd5b8 fffff80221225a69 : 00000000000000e3 ffff9e0b50493090 ffff9e0b748d6080 ffff9e0b54b1ee10 : nt!KeBugCheckEx

ffffea0cebfcd5c0 fffff802210215b3 : ffff9e0b50493090 0000000000000000 ffff9e0b748d6080 0000000000000000 : nt!ExpReleaseResourceSharedForThreadLite+0x2043d9

ffffea0cebfcd680 fffff80223bda932 : ffff9e0b6f644e18 ffff9e0b6f644d78 ffff880549d0d660 ffff9e0b73825180 : nt!ExReleaseResourceLite+0xf3

ffffea0cebfcd6e0 fffff80223cf9a7d : ffff9e0b6f644d78 ffff9e0b50472180 ffff9e0b6f644e18 00000000ffffdfff : Ntfs!NtfsReleaseFcbEx+0x52

ffffea0cebfcd720 fffff80223cfe37d : ffff88056b0e8eb8 0000000000000008 ffffea0cebfcdef0 ffff9e0b6f644d78 : Ntfs!NtfsCheckpointCurrentTransaction+0x261

ffffea0cebfcd750 fffff80223cc1903 : ffff88056a0f8010 ffff880500000000 ffff880500000000 ffffea0cebfcdef0 : Ntfs!NtfsCreateNewFile+0x1fdd

ffffea0cebfcdb00 fffff80223cbbe7b : ffff9e0b797d4a20 ffffea0cebfcdef0 ffff9e0b797d4a20 0000000000000000 : Ntfs!NtfsCommonCreate+0x14b3

ffffea0cebfcdde0 fffff80221011385 : ffff9e0b50472030 ffff9e0b797d4a20 ffffea0cebfce100 ffff9e0b75002ee0 : Ntfs!NtfsFsdCreate+0x1db

ffffea0cebfce060 fffff8021d89710f : 0000000000000001 ffffea0cebfce150 ffffea0cebfce159 fffff8021d895f7a : nt!IofCallDriver+0x55

ffffea0cebfce0a0 fffff8021d8c9f54 : ffffea0cebfce150 ffff9e0b75002f38 ffff9e0b50235c20 ffff9e0b50235c20 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f

ffffea0cebfce110 fffff80221011385 : 0000000000000001 ffff9e0b4de1ac00 0000000000000060 ffff9e0b75090ce8 : FLTMGR!FltpCreate+0x324

ffffea0cebfce1c0 fffff8022100d944 : ffff9e0b748d6530 fffff8022122586f ffff9e0b748d6608 ffffea0cebfce500 : nt!IofCallDriver+0x55

ffffea0cebfce200 fffff802213ff58b : ffff9e0b4de1ac00 ffff9e0b4de1ac00 ffff9e0b75002f78 0000000000000000 : nt!IoCallDriverWithTracing+0x34

ffffea0cebfce250 fffff802213fe0d7 : ffff9e0b50235c20 fffff802210cb323 ffff9e0b6c9a8a20 0000000000100000 : nt!IopParseDevice+0x11bb

ffffea0cebfce3c0 fffff8022141501e : fffff802213fe010 ffffea0cebfce530 ffff9e0b6c9a8a20 ffff9e0b75003870 : nt!IopParseFile+0xc7

ffffea0cebfce430 fffff8022140ccea : ffff9e0b6c9a8a00 ffffea0cebfce698 ffffea0c00000240 ffff9e0b4d2f6da0 : nt!ObpLookupObjectName+0x3fe

ffffea0cebfce600 fffff802213fd0ac : ffff9e0b00000000 ffffea0cebfcec00 0000000000000000 0000000000000000 : nt!ObOpenObjectByNameEx+0x1fa

ffffea0cebfce730 fffff802213fa8fd : ffffea0cebfceb98 0000000000100180 ffffea0cebfcec00 ffffea0cebfcec30 : nt!IopCreateFile+0x132c

ffffea0cebfce7f0 fffff8021d8cb7d3 : 0000000000000000 ffffea0cebfce949 ffff9e0b75090ce8 0000000000000000 : nt!IoCreateFileEx+0x11d

ffffea0cebfce890 fffff8021d8cba37 : 0000000000000000 ffffea0cebfcebd8 ffffea0cebfcec00 fffff802273320a9 : FLTMGR!FltpCreateFile+0x16f

ffffea0cebfce980 fffff8022731d660 : ffff9e0b52d04a20 ffffea0cebfced50 ffffea0cebfceb98 ffffea0cebfceb30 : FLTMGR!FltCreateFileEx2+0xe7

ffffea0cebfceab0 fffff8022731ca32 : 0000000000e18943 ffffea0cebfced50 ffff9e0b52e3f2d0 0000000000000000 : cldflt!HsmpOpCreatePlaceholders+0x9f4

ffffea0cebfced00 fffff80227323cb5 : ffff9e0b00000001 0000000000000000 ffff9e0b00000001 ffffea0c00e18943 : cldflt!HsmFltProcessCreatePlaceholders+0x202

ffffea0cebfced90 fffff80227352be4 : ffffea0cebfcef01 ffff880500000098 ffff9e0b6627f118 ffff880572d48270 : cldflt!HsmFltProcessHSMControl+0x275

ffffea0cebfceec0 fffff8021d8964cc : 0000000000000000 ffff9e0b6627f010 ffffea0cebfcefd0 ffff9e0b52e64d40 : cldflt!HsmFltPreFILE_SYSTEM_CONTROL+0x6a4

ffffea0cebfcef60 fffff8021d895f7a : ffffea0cebfcf100 ffff9e0b0000000d ffff9e0b75004500 0000000000000000 : FLTMGR!FltpPerformPreCallbacksWorker+0x36c

ffffea0cebfcf080 fffff8021d895021 : ffffea0cebfd0000 ffffea0cebfc9000 ffff9e0b62494630 ffffea0cebfcf190 : FLTMGR!FltpPassThroughInternal+0xca

ffffea0cebfcf0d0 fffff8021d8cae2f : ffff9e0b4cc05d80 0000000000000000 00000000000000c8 fffff80221411b31 : FLTMGR!FltpPassThrough+0x541

ffffea0cebfcf160 fffff80221011385 : ffff9e0b748d6608 0000000000000002 ffff9e0b750045a0 0000000000000098 : FLTMGR!FltpFsControl+0xbf

ffffea0cebfcf1c0 fffff80221410b1c : 0000000000000001 ffff9e0b624949d0 ffff9e0b750045a0 ffff9e0b6b1220c0 : nt!IofCallDriver+0x55

ffffea0cebfcf200 fffff80221410771 : ffff9e0b624949d0 ffffea0cebfcf540 0000000000010005 ffff9e0b624949d0 : nt!IopSynchronousServiceTail+0x34c

ffffea0cebfcf2a0 fffff802214ba2e6 : 0000000000000000 0000000000000df4 0000000000000000 0000001b88dfd9c0 : nt!IopXxxControlFile+0xc71

ffffea0cebfcf3e0 fffff8022120f3f5 : ffff9e0b748d6080 0000001b88dfd908 ffffea0cebfcf468 0000000000000001 : nt!NtFsControlFile+0x56

ffffea0cebfcf450 00007ffdde12d784 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25

0000001b88dfd8b8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffd`de12d784

SYMBOL_NAME: nt!ExpReleaseResourceSharedForThreadLite+2043d9

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.2846

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 2043d9

FAILURE_BUCKET_ID: 0xE3_nt!ExpReleaseResourceSharedForThreadLite

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {321aa310-6654-009f-ad13-07c9b7115742}

Followup: MachineOwner

Anyone who may can help?

Regards

Lukas

Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,446 questions
FSLogix
FSLogix
A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
474 questions
{count} votes

1 answer

Sort by: Most helpful
  1. vipullag-MSFT 25,861 Reputation points
    2023-05-10T04:41:16.4166667+00:00

    Hello Lukas Gieske

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    It seems like you are experiencing RESOURCE_NOT_OWNED (e3) error on all your AVDs. This error occurs when a thread tries to release a resource it does not own. The arguments in the minidump suggest that the thread tried to release a resource at ffff9e0b50493090, which it did not own.

    This error can be caused by a number of factors, including outdated drivers, hardware issues, or software conflicts. Since you mentioned that your Windows 10 is updated and is 22H2 Build 19045.2846, it is less likely to be a software issue.

    I would suggest you to check if there are any outdated drivers or hardware issues. You can also try to run a memory diagnostic test to check if there are any issues with your RAM.

    If you are still experiencing the issue after checking the above, as suggested in my previous response I would recommend you to contact Microsoft Support for further assistance.

    Hope this helps.

    If the suggested response helped you resolve your issue, please 'Accept as answer', so that it can help others in the community looking for help on similar topics.

    0 comments No comments