Init Kernel Function Info Success
驱动成功被卸载
*** Fatal System Error: 0x000000c4
(0x00000062,0x8CEC7624,0x8CE17D00,0x00000011)
Break instruction exception - code 80000003 (first chance)
Connected to Windows 7 7600 x86 compatible target at (Thu May 8 09:45:31.558 2014 (UTC + 8:00)), ptr64 FALSE
Loading Kernel Symbols
.......................................
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
........................
................................................................
...........................
Loading User Symbols
.................................
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {62, 8cec7624, 8ce17d00, 11}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
nt!RtlpBreakWithStatusInstruction:
838ad394 cc int 3
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: 8cec7624, name of the driver having the issue.
Arg3: 8ce17d00, verifier internal structure with driver information.
Arg4: 00000011, total # of (paged+nonpaged) allocations that weren't freed.
Type !verifier 3 drivername.sys for info on the allocations
that were leaked that caused the bugcheck.
Debugging Details:
------------------
BUGCHECK_STR: 0xc4_62
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAULTING_MODULE: a4f02000 SafeSystem
VERIFIER_DRIVER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY ffffffff8ce17d00
Symbol nt!_MI_VERIFIER_DRIVER_ENTRY not found.
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: services.exe
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre
LAST_CONTROL_TRANSFER: from 8391ee71 to 838ad394
STACK_TEXT:
8c2e748c 8391ee71 00000003 b7e33378 00000065 nt!RtlpBreakWithStatusInstruction
8c2e74dc 8391f96d 00000003 8ce17d00 00000011 nt!KiBugCheckDebugBreak+0x1c
8c2e78a0 8391ed10 000000c4 00000062 8cec7624 nt!KeBugCheck2+0x68b
8c2e78c0 83b76f03 000000c4 00000062 8cec7624 nt!KeBugCheckEx+0x1e
8c2e78e0 83b7b5eb 8cec7624 8ce17d00 a4f02000 nt!VerifierBugCheckIfAppropriate+0x30
8c2e78f0 8384ee8a 8cec75c8 83981ec8 83981ec8 nt!VfPoolCheckForLeaks+0x33
8c2e792c 839d369f 8cec75c8 a4f02000 40000000 nt!VfTargetDriversRemove+0x66
8c2e7940 839d3338 8398a7e0 8ce97d48 00000000 nt!VfDriverUnloadImage+0x5e
8c2e7978 839d458d 8cec75c8 ffffffff 00000000 nt!MiUnloadSystemImage+0x1c6
8c2e799c 83afd517 8cec75c8 861ff650 8ce2fb70 nt!MmUnloadSystemImage+0x36
8c2e79b4 83a636f4 8ce2fb88 8ce2fb88 8ce2fb70 nt!IopDeleteDriver+0x38
8c2e79cc 838aaf60 00000000 8c2e7ce8 8ce2fb88 nt!ObpRemoveObjectRoutine+0x59
8c2e79e0 838aaed0 8ce2fb88 83afdbe5 b7e33c98 nt!ObfDereferenceObjectWithTag+0x88
8c2e79e8 83afdbe5 b7e33c98 8c2e7b54 8c2e7bd0 nt!ObfDereferenceObject+0xd
8c2e7b3c 83afd836 00000000 8c2e7b54 8388542a nt!IopUnloadDriver+0x3a0
8c2e7b48 8388542a 8c2e7ce8 8c2e7d1c 83884741 nt!NtUnloadDriver+0xf
8c2e7b48 83884741 8c2e7ce8 8c2e7d1c 83884741 nt!KiFastCallEntry+0x12a
8c2e7bc4 83afd935 8c2e7ce8 b7e33ab8 0089f0f4 nt!ZwUnloadDriver+0x11
8c2e7d1c 83afd836 00000000 8c2e7d34 b804342a nt!IopUnloadDriver+0xf0
8c2e7d28 b804342a 0089f0f4 0089f0fc 777364f4 nt!NtUnloadDriver+0xf
WARNING: Frame IP not in any known module. Following frames may be wrong.
8c2e7d34 777364f3 badb0d00 0089f0e4 00000000 0xb804342a
8c2e7d38 badb0d00 0089f0e4 00000000 00000000 ntdll!KiFastSystemCall+0x3
8c2e7d3c 0089f0e4 00000000 00000000 00000000 0xbadb0d00
8c2e7d40 00000000 00000000 00000000 00000000 0x89f0e4
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
83885300-
[ b9 23 00 00 00:e9 fb df 7b 34 ]
[ 8b ff 55 8b ec:e9 fb df 7b 34 ]
[ 8b ff 55 8b ec:e9 fb df 7b 34 ]
[ 6a 4c 68 b8 ce 89 83:e9 23 2a 47 21 90 90 ]
22 errors : !nt (83885300-83a9185e)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_large
FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
Followup: memory_corruption
---------