Hi,
During a debugging / tesing session of a file system
minifilter I got the following error from Driver
Verifier, but the WinDbg documentations offer
no information about code 0x12.
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 00000012, Code that specifies the violation
Arg2: 8e9892d0
Arg3: 00000000
Arg4: 00000002
Debugging Details:
BUGCHECK_STR: 0xc9_12
DRIVER_VERIFIER_IO_VIOLATION_TYPE: 12
FAULTING_IP:
+ffffffff8e9892d0
8e9892d0 8b542408 mov edx,dword ptr [esp+8]
FOLLOWUP_IP:
nt!VfBugCheckNoStackUsage+23
8186d110 cc int 3
PREVIOUS_IRQL: 0
CURRENT_IRQL: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 8186d110 to 818d85c9
STACK_TEXT:
849a8b64 8186d110 000000c9 00000012 8e9892d0 nt!KeBugCheckEx+0x1e
849a8b7c 81ad5ebf 8dfa2e28 849a8ba8 81ace68e nt!VfBugCheckNoStackUsage+0x23
849a8b88 81ace68e 8fe3b89c 00000000 8ff11020 nt!VfAfterCallDriver+0x5e
849a8ba8 81827e86 820b3a5c 8dfa2e28 8ff11020 nt!IovCallDriver+0x25f
849a8bbc 820b3a5c 8fe20338 8dfa2e28 00000000 nt!IofCallDriver+0x1b
849a8be0 820b3c18 849a8c00 8fe20338 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x22a
849a8c18 81ace681 8fe20338 8dfa2e28 8dfa2e38 fltmgr!FltpDispatch+0xc2
849a8c3c 81827e86 819950bd 8e81a9c0 8fe20338 nt!IovCallDriver+0x252
849a8c50 819950bd 00000000 8e81a998 00000000 nt!IofCallDriver+0x1b
849a8c94 819ed5b5 8e81a9c0 81ba7078 8e81a9a8 nt!IopDeleteFile+0x178
849a8cb0 818476d0 8e81a9c0 00000000 8e821d48 nt!ObpRemoveObjectRoutine+0x100
849a8cd8 819d37ed 00000000 00000000 8e821d48 nt!ObfDereferenceObject+0xa1
849a8d04 81811907 8e821d48 00000000 00000000 nt!MiSegmentDelete+0xd2
849a8d58 818114f7 83df5a10 00000000 81912140 nt!MiProcessDereferenceList+0x32
849a8d7c 81a254a8 00000000 849a3680 00000000 nt!MiDereferenceSegmentThread+0xaa
849a8dc0 8189145e 8181144b 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
Does anybody knows what does 0x12 mean? Or
where could I search for more info about?
thank you very much,
Sandor LUKACS
Virus Analyst, SOFTWIN
This seems to be a new bugcheck subtype for Vista:
0x12 : IRQL not equal across call to driver dispatch routine
2 - Driver dispatch routine address.
3 - IRQL before calling driver dispatch routine.
4 - Current IRQL.
–
This posting is provided “AS IS” with no warranties, and confers no
rights.
slukacs wrote:
During a debugging / tesing session of a file system
minifilter I got the following error from Driver
Verifier, but the WinDbg documentations offer
no information about code 0x12.
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 00000012, Code that specifies the violation
Arg2: 8e9892d0
Arg3: 00000000
Arg4: 00000002
Debugging Details:
BUGCHECK_STR: 0xc9_12
DRIVER_VERIFIER_IO_VIOLATION_TYPE: 12
FAULTING_IP:
+ffffffff8e9892d0
8e9892d0 8b542408 mov edx,dword ptr [esp+8]
FOLLOWUP_IP:
nt!VfBugCheckNoStackUsage+23
8186d110 cc int 3
PREVIOUS_IRQL: 0
CURRENT_IRQL: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 8186d110 to 818d85c9
STACK_TEXT:
849a8b64 8186d110 000000c9 00000012 8e9892d0 nt!KeBugCheckEx+0x1e
849a8b7c 81ad5ebf 8dfa2e28 849a8ba8 81ace68e
nt!VfBugCheckNoStackUsage+0x23
849a8b88 81ace68e 8fe3b89c 00000000 8ff11020 nt!VfAfterCallDriver+0x5e
849a8ba8 81827e86 820b3a5c 8dfa2e28 8ff11020 nt!IovCallDriver+0x25f
849a8bbc 820b3a5c 8fe20338 8dfa2e28 00000000 nt!IofCallDriver+0x1b
849a8be0 820b3c18 849a8c00 8fe20338 00000000
fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x22a
849a8c18 81ace681 8fe20338 8dfa2e28 8dfa2e38 fltmgr!FltpDispatch+0xc2
849a8c3c 81827e86 819950bd 8e81a9c0 8fe20338 nt!IovCallDriver+0x252
849a8c50 819950bd 00000000 8e81a998 00000000 nt!IofCallDriver+0x1b
849a8c94 819ed5b5 8e81a9c0 81ba7078 8e81a9a8 nt!IopDeleteFile+0x178
849a8cb0 818476d0 8e81a9c0 00000000 8e821d48
nt!ObpRemoveObjectRoutine+0x100
849a8cd8 819d37ed 00000000 00000000 8e821d48 nt!ObfDereferenceObject+0xa1
849a8d04 81811907 8e821d48 00000000 00000000 nt!MiSegmentDelete+0xd2
849a8d58 818114f7 83df5a10 00000000 81912140
nt!MiProcessDereferenceList+0x32
849a8d7c 81a254a8 00000000 849a3680 00000000
nt!MiDereferenceSegmentThread+0xaa
849a8dc0 8189145e 8181144b 00000000 00000000
nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
Does anybody knows what does 0x12 mean? Or
where could I search for more info about?