在ole32中崩溃！COIDTable :: ThreadCleanup … NetworkItemFactory！FDBackgroundThreadHandler

2019年8月4日 296次阅读

从上周开始,即使在非常简单的文档上,Word和Excel也经常崩溃.刚才,Firefox也崩溃了.我该怎么做才能修复它或找到真正的根本原因？

我已经使用安装程序修复了Office安装.应安装所有定期更新.笔记本电脑每天都会重启.

我已经将WinDbg配置为附加,这就是我得到的.我也有转储,所以如果你需要更多信息,我仍然可以得到它.这是我第一次转载Word时的信息：

0:020> .exr -1
ExceptionAddress: 11fdf91c
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000008
   Parameter[1]: 11fdf91c
Attempt to execute non-executable address 11fdf91c


0:020> kb
ChildEBP RetAddr  Args to Child              
WARNING: Frame IP not in any known module. Following frames may be wrong.
11fdf91c 75d05d3f 00000008 0dc0bbe8 fffffffe 0x11fdf91c
11fdfacc 75d38f82 bf3079e6 0dc0bbe8 00000000 ole32!COIDTable::ThreadCleanup+0xcb [d:\w7rtm\com\ole32\com\dcomrem\idobj.cxx @ 1760]
11fdfb10 75d38ec3 00000000 11fdfb60 75e37724 ole32!FinishShutdown+0x9d [d:\w7rtm\com\ole32\com\class\compobj.cxx @ 1035]
11fdfb30 75d2bac3 00000000 75d309ad 0dc0bbe8 ole32!ApartmentUninitialize+0x96 [d:\w7rtm\com\ole32\com\class\compobj.cxx @ 1291]
11fdfb48 75d388e8 11fdfb60 00000000 00000000 ole32!wCoUninitialize+0x153 [d:\w7rtm\com\ole32\com\class\compobj.cxx @ 2766]
11fdfb64 6e77314a 11fdfbf4 75f043c0 0b179b08 ole32!CoUninitialize+0x72 [d:\w7rtm\com\ole32\com\class\compobj.cxx @ 2620]
11fdfb6c 75f043c0 0b179b08 00000000 00000000 NetworkItemFactory!FDBackgroundThreadHandler+0x21
11fdfbf4 75bf336a 0da0f624 11fdfc40 773a9f72 SHLWAPI!WrapperThreadProc+0x1b5
11fdfc00 773a9f72 0da0f624 66709c63 00000000 kernel32!BaseThreadInitThunk+0xe
11fdfc40 773a9f45 75f042ed 0da0f624 ffffffff ntdll!__RtlUserThreadStart+0x70
11fdfc58 00000000 75f042ed 0da0f624 00000000 ntdll!_RtlUserThreadStart+0x1b


0:020> vertarget
Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
kernel32.dll version: 6.1.7601.18229 (win7sp1_gdr.130801-1533)
Machine Name:
Debug session time: Wed Feb  5 14:55:55.241 2014 (UTC + 1:00)
System Uptime: 0 days 3:46:03.386
Process Uptime: 0 days 0:05:08.582
  Kernel time: 0 days 0:00:03.822
  User time: 0 days 0:00:11.528

最佳答案 如果我没记错的话,它与来自Deutsche Telekom的名为Netphone Client的VOIP软件有关,它通过COM对象将自己包含在其他应用程序中.

因此,这与评论中的Hans Passant完全一致：

You are buried inside the COM plumbing with a clear hint that its internal state is corrupted. This is an environmental problem, some kind of DLL that gets injected into the process and screws things up. Long before the crash occurs so you’ll have very little hope of diagnosing it with a debugger. Find the common source of the problem from the modules list. Suspect any shell extension, anti-malware, any utility similar to Dropbox. Use SysInternals’ AutoRuns to disable them.

我不记得我究竟是怎么找到罪魁祸首的,但我终于使用了物理VOIP手机而不是软件耳机.

点赞