Windows Server is supported at Microsoft Q&A. You should post your question there.
https://learn.microsoft.com/en-us/answers/
Don
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
I've been getting this message for a week while running a Jenkins build:
12.04.2023 09:15:39 - INFO : Sprawdzam kodowanie dla modułu Base.Web Cannot contact Agent-Worker: hudson.remoting.RequestAbortedException: java.nio.channels.ClosedChannelException
I copied the Memory dump file from Windows Server 2016 to a Windows 10 laptop and here it analyzes the error. I am writing this so that no one is confused as to why there is a Windows 10 version in the MemoryDump log.
It turned out that the Jenkins build is interrupted by a blue screen. I found the Memmory dump file and analyzed it and got errors like this
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [...\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 srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (16 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Edition build lab: 14393.5850.amd64fre.rs1_release.230329-2152
Machine Name:
Kernel base = 0xfffff803`93c02000 PsLoadedModuleList = 0xfffff803`93f07cd0
Debug session time: Fri Apr 14 11:32:17.692 2023 (UTC + 2:00)
System Uptime: 0 days 0:13:20.120
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`0107f018). Type ".hh dbgerr001" for details
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`93d5f1c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9600`2528ba00=0000000000000050
10: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffff81086f718003, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff8061b7b8dfc, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Page 8700 not present in the dump file. Type ".hh dbgerr004" for details
Page 8700 not present in the dump file. Type ".hh dbgerr004" for details
Page 8700 not present in the dump file. Type ".hh dbgerr004" for details
KEY_VALUES_STRING: 1
Key : AV.Type
Value: Read
Key : Analysis.CPU.mSec
Value: 2061
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 10266
Key : Analysis.IO.Other.Mb
Value: 1
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 1
Key : Analysis.Init.CPU.mSec
Value: 1671
Key : Analysis.Init.Elapsed.mSec
Value: 287884
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : Bugcheck.Code.DumpHeader
Value: 0x50
Key : Bugcheck.Code.KiBugCheckData
Value: 0x50
Key : Bugcheck.Code.Register
Value: 0x50
Key : WER.OS.Branch
Value: rs1_release
Key : WER.OS.Timestamp
Value: 2023-03-29T21:52:00Z
Key : WER.OS.Version
Value: 10.0.14393.5850
FILE_IN_CAB: MEMORY.DMP
VIRTUAL_MACHINE: HyperV
BUGCHECK_CODE: 50
BUGCHECK_P1: ffff81086f718003
BUGCHECK_P2: 0
BUGCHECK_P3: fffff8061b7b8dfc
BUGCHECK_P4: 0
READ_ADDRESS: ffff81086f718003 Paged pool
MM_INTERNAL_CODE: 0
IMAGE_NAME: WdFilter.sys
MODULE_NAME: WdFilter
FAULTING_MODULE: fffff8061b750000 WdFilter
PROCESS_NAME: sencha.exe
TRAP_FRAME: ffff96002528bcf0 -- (.trap 0xffff96002528bcf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000105 rbx=0000000000000000 rcx=ffff81086f717de6
rdx=00000000000001fe rsi=0000000000000000 rdi=0000000000000000
rip=fffff8061b7b8dfc rsp=ffff96002528be80 rbp=ffff96002528c248
r8=000000000000020c r9=0000000000000016 r10=ffffdf8104aece10
r11=ffff81086f717dd8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
WdFilter!MpQueryLoopbackEa+0x3f0:
fffff806`1b7b8dfc 66837c41135c cmp word ptr [rcx+rax*2+13h],5Ch ds:ffff8108`6f718003=????
Resetting default scope
STACK_TEXT:
ffff9600`2528b9f8 fffff803`93cae7e4 : 00000000`00000050 ffff8108`6f718003 00000000`00000000 ffff9600`2528bcf0 : nt!KeBugCheckEx
ffff9600`2528ba00 fffff803`93cbdda4 : 00000000`00000000 ffffc17f`ffffffff 00000000`00000000 ffff8108`6f718003 : nt!MiSystemFault+0xfb4
ffff9600`2528baf0 fffff803`93d6dfdb : 00000000`0000008b fffff803`93cd24ea ffffdf81`085cfe18 ffffdf81`085cfe00 : nt!MmAccessFault+0x254
ffff9600`2528bcf0 fffff806`1b7b8dfc : ffffdf81`04aec010 00000000`0000022b 00000000`00000004 ffffdf81`085cfed8 : nt!KiPageFault+0x31b
ffff9600`2528be80 fffff806`1b7b80e8 : 0000006f`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WdFilter!MpQueryLoopbackEa+0x3f0
ffff9600`2528c030 fffff806`1b77fccb : 00000000`00000000 00000000`00000001 ffffdf81`0b53bd68 ffff9600`2528c248 : WdFilter!MpQueryLoopbackLocalPathByFileObject+0x5c
ffff9600`2528c0b0 fffff806`1b77e320 : ffffdf81`0b53bd00 ffffdf81`0b53bd68 ffff8108`5ce19600 fffff806`1b769000 : WdFilter!MpDlpPostCreate+0x27f
ffff9600`2528c160 fffff806`1bd014b7 : ffffdf81`0b53bc90 ffff9600`2528c269 00000000`00000000 ffffdf81`0b53bd68 : WdFilter!MpPostCreate+0x430
ffff9600`2528c1f0 fffff806`1bcf3646 : ffffdf81`0b53bc00 ffff9600`2528d000 ffff9600`25287000 00000000`00000000 : FLTMGR!FltpPerformPostCallbacksWorker+0x2fb
ffff9600`2528c2d0 fffff806`1bcf41b9 : ffffdf81`0b53bca8 ffffdf81`0b53bc90 ffffdf81`0a3d7580 ffffdf81`0a3d7728 : FLTMGR!FltpPassThroughCompletionWorker+0x76
ffff9600`2528c310 fffff806`1bd24325 : fffff806`1bd14060 00000000`00000250 00000000`00000000 ffff8108`6f707b70 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x239
ffff9600`2528c3a0 fffff803`940f1e0f : 00000000`00000000 00000000`00000085 ffffdf81`0978abe0 ffffdf81`00000000 : FLTMGR!FltpCreate+0x2f5
ffff9600`2528c450 fffff803`9411e72f : fffff803`940f06e0 fffff803`940f06e0 ffff9600`2528c740 ffffdf81`04d3d880 : nt!IopParseDevice+0x172f
ffff9600`2528c640 fffff803`94113b4d : ffffdf81`0a252b01 ffff9600`2528c8a0 00000000`00000040 ffffdf81`04409b00 : nt!ObpLookupObjectName+0x8af
ffff9600`2528c810 fffff803`940bed90 : 00000000`00000001 00000000`00000000 00000000`00ff9cf0 00000000`00ff9d50 : nt!ObOpenObjectByNameEx+0x1dd
ffff9600`2528c950 fffff803`940be519 : ffffdf81`0b03a800 00000000`80100080 00000000`00ff9d50 00000000`00ff9c78 : nt!IopCreateFile+0x860
ffff9600`2528ca00 fffff803`93d70d03 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateFile+0x79
ffff9600`2528ca90 00007ff8`80ec6734 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00ff9c58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`80ec6734
SYMBOL_NAME: WdFilter!MpQueryLoopbackEa+3f0
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 3f0
FAILURE_BUCKET_ID: AV_R_(null)_WdFilter!MpQueryLoopbackEa
OS_VERSION: 10.0.14393.5850
BUILDLAB_STR: rs1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e5d50d66-5dda-22ed-9499-508b0d466acd}
Followup: MachineOwner
---------
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.
Answer accepted by question author
Windows Server is supported at Microsoft Q&A. You should post your question there.
https://learn.microsoft.com/en-us/answers/
Don