卡吧和暴风影音有冲突 附windbg分析

coolpeople

windbg分析。。更新后出现问题。。

1. kd> !analyze -v
   
2. *******************************************************************************
   
3. * *
   
4. * Bugcheck Analysis *
   
5. * *
   
6. *******************************************************************************
   
7. 
   
8. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
   
9. This is a very common bugcheck. Usually the exception address pinpoints
   
10. the driver/function that caused the problem. Always note this address
    
11. as well as the link date of the driver/image that contains this address.
    
12. Some common problems are exception code 0x80000003. This means a hard
    
13. coded breakpoint or assertion was hit, but this system was booted
    
14. /NODEBUG. This is not supposed to happen as developers should never have
    
15. hardcoded breakpoints in retail code, but ...
    
16. If this happens, make sure a debugger gets connected, and the
    
17. system is booted /DEBUG. This will let us see why this breakpoint is
    
18. happening.
    
19. Arguments:
    
20. Arg1: c0000005, The exception code that was not handled
    
21. Arg2: f3e9e326, The address that the exception occurred at
    
22. Arg3: f29823f0, Trap Frame
    
23. Arg4: 00000000
    
24. 
    
25. Debugging Details:
    
26. ------------------
    
27. 
    
28. 
    
29. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"
    
30. 
    
31. FAULTING_IP:
    
32. klif+e326
    
33. f3e9e326 8b4e0c mov ecx,dword ptr [esi+0Ch]
    
34. 
    
35. TRAP_FRAME: f29823f0 -- (.trap 0xfffffffff29823f0)
    
36. ErrCode = 00000000
    
37. eax=00000b50 ebx=83715870 ecx=000a0c00 edx=21080005 esi=00000083 edi=83018d7f
    
38. eip=f3e9e326 esp=f2982464 ebp=8054c7aa iopl=0 nv up ei pl nz na po nc
    
39. cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
    
40. klif+0xe326:
    
41. f3e9e326 8b4e0c mov ecx,dword ptr [esi+0Ch] ds:0023:0000008f=????????
    
42. Resetting default scope
    
43. 
    
44. CUSTOMER_CRASH_COUNT: 1
    
45. 
    
46. DEFAULT_BUCKET_ID: DRIVER_FAULT
    
47. 
    
48. BUGCHECK_STR: 0x8E
    
49. 
    
50. PROCESS_NAME: mplayerc.exe
    
51. 
    
52. LAST_CONTROL_TRANSFER: from f3e9e3a1 to f3e9e326
    
53. 
    
54. STACK_TEXT:
    
55. WARNING: Stack unwind information not available. Following frames may be wrong.
    
56. f2982474 f3e9e3a1 00000030 00000b50 f3ea4e66 klif+0xe326
    
57. f29824a8 804e4d77 8353d958 82c06208 82c06208 klif+0xe3a1
    
58. f29824b8 8056bfec 82c62c18 00000000 00000000 nt!IopfCallDriver+0x31
    
59. f29824f0 80564ff6 00c62c30 82c62c18 00000000 nt!IopDeleteFile+0x132
    
60. f298250c 804e4c55 82c62c30 00000000 0000023c nt!ObpRemoveObjectRoutine+0xdf
    
61. f2982530 80568543 82bdb330 e16c6798 82e91618 nt!ObfDereferenceObject+0x5f
    
62. f2982548 805685ac e16c6798 82c62c30 0000023c nt!ObpCloseHandleTableEntry+0x155
    
63. f2982590 805685f6 0000023c 00000000 00000000 nt!ObpCloseHandle+0x87
    
64. f29825a4 f3eaca9c 0000023c f2982638 804e006b nt!NtClose+0x1d
    
65. f29825bc 804ddea6 badb0d00 f2982634 f29825f0 klif+0x1ca9c
    
66. f29825cc 80565425 e16c6798 0000023c 82e91618 nt!ZwClose+0x11
    
67. f2982620 804ddea6 00000008 00000202 8343ee5b nt!ExMapHandleToPointerEx+0x21
    
68. f29826d8 804dea28 00000008 0000005e 00000026 nt!ZwClose+0x11
    
69. f29827cc 804e4d77 834ae770 82c52ea8 82ef5be8 nt!ZwQueryInformationProcess+0x11
    
70. f29828bc 8056486c 83565c08 00000000 832c6160 nt!IopfCallDriver+0x31
    
71. f2982944 80568c63 00000000 f2982984 00000240 nt!ObpLookupObjectName+0x56a
    
72. f2982998 80572477 00000000 00000000 ef5ae400 nt!ObOpenObjectByName+0xeb
    
73. f2982a14 80572546 82d51960 02000000 f2982bb8 nt!IopCreateFile+0x407
    
74. f2982a70 f3f69483 82d51960 02000000 f2982bb8 nt!IoCreateFile+0x8e
    
75. f2982c24 f3f702c7 82e91828 8359c2c0 f2982c58 afd!AfdBind+0x2dc
    
76. f2982c34 804e4d77 8353f530 82ef5a08 806ee070 afd!AfdDispatchDeviceControl+0x53
    
77. f2982c44 8056b9ab 82ef5ae4 82c38f90 82ef5a08 nt!IopfCallDriver+0x31
    
78. f2982c58 8057e9f7 8353f530 82ef5a08 82c38f90 nt!IopSynchronousServiceTail+0x60
    
79. f2982d00 80580bfa 0000022c 00000214 00000000 nt!IopXxxControlFile+0x611
    
80. f2982d34 804e006b 0000022c 00000214 00000000 nt!NtDeviceIoControlFile+0x2a
    
81. f2982d34 7c92eb94 0000022c 00000214 00000000 nt!KiFastCallEntry+0xf8
    
82. 0102ea50 00000000 00000000 00000000 00000000 0x7c92eb94
    
83. 
    
84. 
    
85. STACK_COMMAND: kb
    
86. 
    
87. FOLLOWUP_IP:
    
88. klif+e326
    
89. f3e9e326 8b4e0c mov ecx,dword ptr [esi+0Ch]
    
90. 
    
91. SYMBOL_STACK_INDEX: 0
    
92. 
    
93. FOLLOWUP_NAME: MachineOwner
    
94. 
    
95. MODULE_NAME: klif
    
96. 
    
97. IMAGE_NAME: klif.sys
    
98. 
    
99. DEBUG_FLR_IMAGE_TIMESTAMP: 46826975
    
100. 
     
101. SYMBOL_NAME: klif+e326
     
102. 
     
103. FAILURE_BUCKET_ID: 0x8E_klif+e326
     
104. 
     
105. BUCKET_ID: 0x8E_klif+e326
     
106. 
     
107. Followup: MachineOwner
     
108. ---------

复制代码

[ 本帖最后由 wangjay1980 于 2007-9-18 22:25 编辑 ]

gwg829

嘛意思  看不懂   

xffsfy

截图比分析更有说服力....至少是在这里

rogger

怎么会呢？我的卡巴很好啊。。。

放弃自我

不明白，完全看不明白白，暴汗中。。。。

wangjay1980

版本也不说

rcbblgy

我这用的好好的，没冲突啊

shk1106

暴风垃圾
一直用km

qingdianlgy

暴风垃圾
没错，现在还增加广告了，一直支持KM
暴风跟KM相比差远了

cshacker

这个dump分析只能说明是AVP的驱动崩溃了，在IoCallDriver里面
看不出和暴风影音有联系。