callback object and CRITICAL_STRUCTURE_CORRUPTION

Hi, I have two drivers communicating with each other through a callback object. Sometimes, a client receives a CRITICAL_STRUCTURE_CORRUPTION bugcheck pointing to my driver.

Does anyone know what a failure type dependent value of 6 means (Arg3 == 6) for callout modification (Arg4 == 18) ?

Thanks for any pointers.


CRITICAL_STRUCTURE_CORRUPTION (109)
This BugCheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:

  1. A driver has inadvertently or deliberately modified critical kernel code
    or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
  2. A developer attempted to set a normal kernel breakpoint using a kernel
    debugger that was not attached when the system was booted. Normal breakpoints,
    “bp”, can only be set if the debugger is attached at boot time. Hardware
    breakpoints, “ba”, can be set at any time.
  3. A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a3a01568310f0535, Reserved
    Arg2: b3b721ee839165f1, Reserved
    Arg3: 0000000000000006, Failure type dependent information
    Arg4: 0000000000000018, Type of corrupted region, can be
    0 : A generic data region

    18 : Kernel notification callout modification

Debugging Details:

FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: 109
BUGCHECK_P1: a3a01568310f0535
BUGCHECK_P2: b3b721ee839165f1
BUGCHECK_P3: 6
BUGCHECK_P4: 18
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: csrss.exe
STACK_TEXT:
fffff60601d5ecf8 0000000000000000 : 0000000000000109 a3a01568310f0535 b3b721ee839165f1 0000000000000006 : nt!KeBugCheckEx

SYMBOL_NAME: DriverA.sys+2d40
MODULE_NAME: DriverA
IMAGE_NAME: DriverA.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 2d40
FAILURE_BUCKET_ID: 0x109_18_6_ExCallbackObject_DriverA.sys!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7d2501a5-5f4a-f0be-575b-8d8b58f92e2e}
Followup: MachineOwner