BSOD Resource not owned on windows server 2016

Shumail Usmani 1 Reputation point
2021-09-16T16:08:42.573+00:00

My both nodes are rebooted with BSOD. Please find below windbg bug analysis

Bug check analysis

6: kd> !analyze -v


  • *
  • Bugcheck Analysis *
  • *

RESOURCE_NOT_OWNED (e3)
A thread tried to release a resource it did not own.
Arguments:
Arg1: ffffb10144059a08, Address of resource
Arg2: ffffb90be1ee4540, Address of thread
Arg3: ffffb10159c78010, Address of owner table if there is one
Arg4: 0000000000000003

Debugging Details:


KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 2093

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 2093

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

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

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

Key  : WER.OS.Branch
Value: rs1_release

Key  : WER.OS.Timestamp
Value: 2021-07-30T18:50:00Z

Key  : WER.OS.Version
Value: 10.0.14393.4583

BUGCHECK_CODE: e3

BUGCHECK_P1: ffffb10144059a08

BUGCHECK_P2: ffffb90be1ee4540

BUGCHECK_P3: ffffb10159c78010

BUGCHECK_P4: 3

PROCESS_NAME: oracle.exe

STACK_TEXT:
ffff9d020724ba18 fffff8034761e4b5 : 00000000000000e3 ffffb10144059a08 ffffb90be1ee4540 ffffb10159c78010 : nt!KeBugCheckEx
ffff9d020724ba20 fffff80c097287f2 : 0000000000000000 ffff9d01ffd93560 ffff9d01ffd93560 ffffdc84aa2486b0 : nt!ExpReleaseResourceForThreadLite+0xfbce5
ffff9d020724bb00 fffff80c097355c9 : ffffb1017b7ea3c8 ffffb10179bb9550 ffff9d01ffd934f0 ffffb90be1ee4540 : NTFS+0xf87f2
ffff9d020724bf50 fffff803475f99b7 : ffff9d01ffd934f0 0000000000000000 ffff9d020724c000 ffffb1016113b5c0 : NTFS+0x1055c9
ffff9d020724bf80 fffff803475f997d : 0000000000006000 ffffb10141825230 0000000000000012 fffff80347542041 : nt!KxSwitchKernelStackCallout+0x27
ffff9d01ffd93350 fffff80347542041 : ffff9d0100000012 0000000000006000 ffffb1017ad6d6f0 ffff9d0100000006 : nt!KiSwitchKernelStackContinue
ffff9d01ffd93370 fffff80347541ca6 : ffff9d01ffd93400 0000000000006000 0000000000000008 0000000000000009 : nt!KiExpandKernelStackAndCalloutOnStackSegment+0x241
ffff9d01ffd93400 fffff80347541b6f : 0000000000000001 ffff9d01ffd934f0 ffff9d01ffd93520 0000000000000000 : nt!KiExpandKernelStackAndCalloutSwitchStack+0xa6
ffff9d01ffd93460 fffff80c097195e8 : 0000000000000000 ffffb1017ad6d6f0 ffff9d01ffd93560 0000000000000000 : nt!KeExpandKernelStackAndCalloutInternal+0x2f
ffff9d01ffd934b0 fffff80c08204146 : ffffb1017bab6010 fffff80c082030c6 ffffb1017ad6d6f0 ffffb1017ad6da48 : NTFS+0xe95e8
ffff9d01ffd937e0 fffff80c08202e86 : fffffffffffe7960 ffffb1014487c400 0000000000000001 ffffb1014487c400 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a6
ffff9d01ffd93870 fffff803478a4c50 : ffffb1015e98fca0 ffffb1014487c400 0000000000000000 000000a1b79f4701 : FLTMGR!FltpDispatch+0xb6
ffff9d01ffd938d0 fffff803478be1a5 : ffffb1015e98fc70 0000000000000000 ffffb1015e98fc70 ffffb1015e98fc80 : nt!IopCloseFile+0x150
ffff9d01ffd93960 fffff803478fb11b : 0000000000000000 0000000000000000 ffffb90be1ee4540 fffff803478b13db : nt!ObCloseHandleTableEntry+0x245
ffff9d01ffd93aa0 fffff80347606103 : ffffb90be1ee4540 000000000000001e 0000000000000000 0000000000000002 : nt!NtClose+0xcb
ffff9d01ffd93b00 00007ff9d9ee5e54 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13
000000a1b79f4918 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff9`d9ee5e54

SYMBOL_NAME: nt!ExpReleaseResourceForThreadLite+fbce5

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: fbce5

FAILURE_BUCKET_ID: 0xE3_nt!ExpReleaseResourceForThreadLite

OS_VERSION: 10.0.14393.4583

BUILDLAB_STR: rs1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {64cb0cd3-7a98-a650-01cf-9e8fada5a7e1}

Followup: MachineOwner


Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,429 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 39,506 Reputation points
    2021-09-17T10:58:19.31+00:00

    Hello,

    Thank you for reaching out.

    I would suggest below troubleshooting steps for this issue.

    1. Please disable any Antivirus program for temporary purposes.
    2. Please check other Windows event logs right before and after this reboot.
    3. Please check are there any Hardware logs from this server’s iiDRAC or ILO related RAM, Diks, CPU.
    4. Please try to un install last patches applied to these servers.
    5. If the BOOT volume is connected to SAN Storage it I would also check health of Storage or any network or Disks related issues.

    Hope this helps,

    Regards

    0 comments No comments