storport.sys bugcheck with IRQL_NOT_LESS_OR_EQUAL on Windows Server 2019 VM

Question

Hi,

We are installing Windows Server 2019 on a Linux QEMU/KVM hypervisor. The VM uses Redhat Virtio SCSI controller. We are frequently seeing BSOD due to storport.sys bugchecking. Can you please help us to diagnose given the below analysis?

From Winver: Windows Server 2019 Version 1809 (OS Build 17763.2686)

Thank you!

---

• *
• 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: fffffffffffc0001, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, 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: fffff8002d2c8f04, address which referenced memory

Debugging Details:

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec

Value: 6749

Key  : Analysis.DebugAnalysisManager

Value: Create

Key  : Analysis.Elapsed.mSec

Value: 6870

Key  : Analysis.Init.CPU.mSec

Value: 11249

Key  : Analysis.Init.Elapsed.mSec

Value: 113740

Key  : Analysis.Memory.CommitPeak.Mb

Value: 80

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

BUGCHECK_CODE: a

BUGCHECK_P1: fffffffffffc0001

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8002d2c8f04

WRITE_ADDRESS: fffffffffffc0001

BLACKBOXBSD: 1 (!blackboxbsd)

PROCESS_NAME: System

TRAP_FRAME: fffff8002fa98040 -- (.trap 0xfffff8002fa98040)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=fffff8002fa98268

rdx=fffffffffffc0001 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8002d2c8f04 rsp=fffff8002fa981d0 rbp=ffffa90bd63e8520

r8=0000000189d1ae2c r9=0000000001d8650d r10=fffff80074b92550

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nt!KxWaitForLockOwnerShipWithIrql+0x14:

fffff8002d2c8f04 48890a mov qword ptr [rdx],rcx ds:fffffffffffc0001=????????????????

Resetting default scope

STACK_TEXT:

fffff8002fa97ef8 fffff8002d482be9 : 000000000000000a fffffffffffc0001 0000000000000002 0000000000000001 : nt!KeBugCheckEx

fffff8002fa97f00 fffff8002d47efd4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000064 : nt!KiBugCheckDispatch+0x69

fffff8002fa98040 fffff8002d2c8f04 : 0000000000000000 fffff8002d2fb464 ffffa90bdade2080 ffffa90bdae760c0 : nt!KiPageFault+0x454

fffff8002fa981d0 fffff8002d2c8edd : fffff8002fa98268 00000003ffffff00 0000000000000001 0000000000000000 : nt!KxWaitForLockOwnerShipWithIrql+0x14

fffff8002fa98200 fffff80074b92a95 : fffff80074bf04c0 0000000000000000 fffff8002c17ae80 ffffa90bd5d24050 : nt!KeAcquireInStackQueuedSpinLock+0x7d

fffff8002fa98230 fffff80074b925f0 : 00000000000000f4 fffff8002c170040 ffffa90bd63e8520 fffff80074bf04c0 : storport!StorpLogStatistics+0x8d

fffff8002fa982e0 fffff8002d2e7dd9 : 0000000000000002 fffff8002d815800 fffff80074bf04c0 0000000000000002 : storport!StorpTraceLoggingTelemetryTimerDpcRoutine+0xa0

fffff8002fa98320 fffff8002d2e8ca7 : 000000000000000c 0000000000989680 fffff8002d815840 0000000000000019 : nt!KiProcessExpiredTimerList+0x159

fffff8002fa98410 fffff8002d474d4a : 0000000000000000 fffff8002c175180 0000000000000000 fffff8002d815840 : nt!KiRetireDpcList+0x4a7

fffff8002fa98620 0000000000000000 : fffff8002fa99000 fffff8002fa92000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x5a

SYMBOL_NAME: storport!StorpLogStatistics+8d

MODULE_NAME: storport

IMAGE_NAME: storport.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 8d

FAILURE_BUCKET_ID: AV_storport!StorpLogStatistics

OS_VERSION: 10.0.17763.1

BUILDLAB_STR: rs5_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {39ac8913-ccdb-3681-c6e7-030f89784846}

Followup: MachineOwner

---

Answer 1

We're having the same exact issue, except with Windows Server 2022 installing off the DVD on a server. BSOD before we even get to the menu to choose where we're installing to.