There is the MSDN document http://msdn.microsoft.com/en-us/library/windows/hardware/ff560187(v=vs.85).aspx for this.
There is also a good document in the http://social.msdn.microsoft.com/Forums/zh-TW/1295/thread/f0bf8b0c-35d6-4d70-83fb-3ff02943dc6f about the Arg1=0x62
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior t
o unloading.
Arg2: fffffadfcebce290, name of the driver having the issue.
Arg3: fffffadfcebce1f0, verifier internal structure with driver information.
Arg4: 0000000000000004, total # of (paged+nonpaged) allocations that weren't free
d.
Type !verifier 3 drivername.sys for info on the allocations
that were leaked that caused the bugcheck. Debugging Details:
------------------ *** No owner thread found for resource fffff800011dca60
*** No owner thread found for resource fffff800011dca60 BUGCHECK_STR: 0xc4_
62 IMAGE_NAME: usbser.sys DEBUG_FLR_IMAGE_TIMESTAMP: 42435eb6 MOD
ULE_NAME: usbser FAULTING_MODULE: fffffadfc66c1000 usbser VERIFIER_DRIV
ER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY fffffadfcebce1f0
+0x000 Links : _LIST_ENTRY [ 0xfffff800`011dac50 - 0xfffff800`011dac50]
+0x010 Loads : 9
+0x014 Unloads : 8
+0x018 BaseName : _UNICODE_STRING "usbser.sys"
+0x028 StartAddress : 0xfffffadf`c66c1000
+0x030 EndAddress : 0xfffffadf`c66d2000
+0x038 Flags : 1
+0x040 Signature : 0x98761940
+0x050 PoolPageHeaders : _SLIST_HEADER
+0x060 PoolTrackers : _SLIST_HEADER
+0x070 CurrentPagedPoolAllocations : 2
+0x074 CurrentNonPagedPoolAllocations : 2
+0x078 PeakPagedPoolAllocations : 9
+0x07c PeakNonPagedPoolAllocations : 0xb
+0x080 PagedBytes : 0x30
+0x088 NonPagedBytes : 0x100
+0x090 PeakPagedBytes : 0x438
+0x098 PeakNonPagedBytes : 0xe2c0
沒有留言:
張貼留言