Jan 12 2023 01:28 PM
Hi
So i have had a random 3/4 times a day BSOD on my Server 2019, this is a Hetzner Dedicated Server with AMD 3600x. Now I did analyse the dmp file but it turns out I do not have a clue what I am looking at, if someone would be so kind to assist in helping me nail down this fault I would be very grateful.
Regards
10: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000011, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80403e3530a, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1593 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 1613 Key : Analysis.IO.Other.Mb Value: 11 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 16 Key : Analysis.Init.CPU.mSec Value: 1593 Key : Analysis.Init.Elapsed.mSec Value: 12084 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : Bugcheck.Code.DumpHeader Value: 0xa Key : Bugcheck.Code.KiBugCheckData Value: 0xa Key : Bugcheck.Code.Register Value: 0xa Key : WER.OS.Branch Value: rs5_release Key : WER.OS.Timestamp Value: 2018-09-14T14:34:00Z Key : WER.OS.Version Value: 10.0.17763.1 FILE_IN_CAB: MEMORY.DMP BUGCHECK_CODE: a BUGCHECK_P1: 11 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff80403e3530a READ_ADDRESS: 0000000000000011 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXPNP: 1 (!blackboxpnp) PROCESS_NAME: System TRAP_FRAME: ffffc40dd48a77d0 -- (.trap 0xffffc40dd48a77d0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000051 rbx=0000000000000000 rcx=ffff800151fc0180 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80403e3530a rsp=ffffc40dd48a7960 rbp=ffff800151fc59a8 r8=0000000000000002 r9=ffffc40dd48a7801 r10=0000000000000000 r11=ffffc40dd48a77a0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!KiProcessExpiredTimerList+0x20a: fffff804`03e3530a 0fb64311 movzx eax,byte ptr [rbx+11h] ds:00000000`00000011=?? Resetting default scope STACK_TEXT: ffffc40d`d48a7688 fffff804`03fdd829 : 00000000`0000000a 00000000`00000011 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffc40d`d48a7690 fffff804`03fd950e : ffffc887`df97e500 fffff804`03ecee28 ffffc40d`d48a7830 00004f1e`37fe7ff1 : nt!KiBugCheckDispatch+0x69 ffffc40d`d48a77d0 fffff804`03e3530a : ffffc887`df97e670 ffff8001`51fc5a80 ffffc40d`d48a7b18 00000000`00000008 : nt!KiPageFault+0x44e ffffc40d`d48a7960 fffff804`03e36127 : 00000000`00000016 00000000`00989680 ffff8001`51fd0800 00000000`00000019 : nt!KiProcessExpiredTimerList+0x20a ffffc40d`d48a7a50 fffff804`03fce63a : ffffffff`00000000 ffff8001`51fc0180 00000000`00000000 ffff8001`51fd0800 : nt!KiRetireDpcList+0x4a7 ffffc40d`d48a7c60 00000000`00000000 : ffffc40d`d48a8000 ffffc40d`d48a2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a SYMBOL_NAME: nt!KiProcessExpiredTimerList+20a MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 20a FAILURE_BUCKET_ID: AV_nt!KiProcessExpiredTimerList OS_VERSION: 10.0.17763.1 BUILDLAB_STR: rs5_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {a74cefe1-c8f8-f6bc-a51d-bfc4da639d5f} Followup: MachineOwner --------- 10: kd> .trap 0xffffc40dd48a77d0 NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000051 rbx=0000000000000000 rcx=ffff800151fc0180 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80403e3530a rsp=ffffc40dd48a7960 rbp=ffff800151fc59a8 r8=0000000000000002 r9=ffffc40dd48a7801 r10=0000000000000000 r11=ffffc40dd48a77a0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!KiProcessExpiredTimerList+0x20a: fffff804`03e3530a 0fb64311 movzx eax,byte ptr [rbx+11h] ds:00000000`00000011=??
Jan 12 2023 03:48 PM
I'd start by checking here (and with manufacturer) about support for Server 2019
Jan 13 2023 03:03 PM
Jan 13 2023 03:07 PM - edited Jan 13 2023 03:08 PM
The link was to the windows server catalog where you can search for certified / supported hardware. Also search the hardware vendors site for supported operating systems and downloads.
Jan 13 2023 05:13 PM
Jan 13 2023 05:22 PM
If it is this one then it appears to be desktop hardware and has no support for windows server. This doesn't mean it can't work but it does mean all of the individual component vetting is left to the end user to do. In the end you'll still have an unsupportable system.
Jan 15 2023 03:12 PM
Jan 15 2023 03:22 PM
Sounds good, please don't forget to close up the thread by marking a best response.