DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000c, Invalid IOSB in IRP at APC IopCompleteRequest (appears to be on
stack that was unwound)
Arg2: 8791b464, IOSB address
Arg3: 8f40cf68, IRP address
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0xc9_c
DRIVER_VERIFIER_IO_VIOLATION_TYPE: c
IOSB_ADDRESS: ffffffff8791b464
IRP_ADDRESS: 0040cf68
DEVICE_OBJECT: 8e20a0e0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 1
LOCK_ADDRESS: 82984f60 -- (!locks 82984f60)
Resource @ nt!PiEngineLock (0x82984f60) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0x82984f60
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from 82b4e9f1 to 828fbd10
STACK_TEXT:
8791b4c0 82b4e9f1 000000c9 0000000c 8791b464 nt!KeBugCheckEx+0x1e
8791b4e0 828c116d a11ff2ed 84fded48 8f40cfa8 nt!IovpCompleteRequest+0x3c
8791b524 828c6fb9 0040cfa8 8791b550 8791b55c nt!IopCompleteRequest+0x4a
8791b574 8284892e 00000000 00000000 00000000 nt!KiDeliverApc+0x111
8791b58c 8290497e 8544c8b8 84e5a260 8544e4b8 nt!KiCheckForKernelApcDelivery+0x24
8791b5ac 82b4f1f4 00000000 00000000 8544c8b8 nt!MiTrimAllSystemPagableMemory+0x354
8791b5cc 82b58e32 8791b638 00000500 00000000 nt!MmVerifierTrimMemory+0xdd
8791b5e4 82b59387 00000002 8544c8b8 8791b638 nt!ViKeRaiseIrqlSanityChecks+0xb8
8791b600 85424ddd 8b361218 8b35a000 00000000 nt!VerifierKfAcquireSpinLock+0x50
8791b61c 8cb7b0cf 00000050 00000000 00000000 ndis!NdisMRegisterMiniportDriver+0x511
WARNING: Stack unwind information not available. Following frames may be wrong.
8791b688 829c2740 8b361218 8b35a000 c000035f Rt86win7+0x410cf
8791b86c 829c9fff 00000000 00000000 8791b894 nt!IopLoadDriver+0x7ed
8791b918 82a0eea4 8c45f848 00000001 8c45f834 nt!PipCallDriverAddDeviceQueryRoutine+0x34b
8791b950 82a170f8 00000001 8791ba1c c0000034 nt!RtlpCallQueryRegistryRoutine+0x2cd
8791b9bc 829c7120 40000000 80000118 8791ba38 nt!RtlQueryRegistryValues+0x31d
8791ba98 829c688e 87be4880 8791bcc8 00000000 nt!PipCallDriverAddDevice+0x383
8791bc94 829aaa42 84fe8628 84f6e8a0 8791bcc8 nt!PipProcessDevNodeTree+0x15d
8791bcd4 82832f9c 84f6e8a0 82982e80 84fded48 nt!PiProcessStartSystemDevices+0x6d
8791bd00 8288cf3b 00000000 00000000 84fded48 nt!PnpDeviceActionWorker+0x241
8791bd50 82a2d6d3 00000001 a11ffa59 00000000 nt!ExpWorkerThread+0x10d
8791bd90 828df0f9 8288ce2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
Rt86win7+410cf
8cb7b0cf ?? ???
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: Rt86win7+410cf
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Rt86win7
IMAGE_NAME: Rt86win7.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c21cf7f
FAILURE_BUCKET_ID: 0xc9_c_VRF_Rt86win7+410cf
BUCKET_ID: 0xc9_c_VRF_Rt86win7+410cf
Followup: MachineOwner