ole32 崩溃!COIDTable::ThreadCleanup ...NetworkItemFactory!FDBackgroundThreadHandler

标签 crash windbg windows-7-x64

从上周开始,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

最佳答案

如果我没记错的话,它与来自德国电信的名为 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 电话,而不是软件 + 耳机。

关于ole32 崩溃!COIDTable::ThreadCleanup ...NetworkItemFactory!FDBackgroundThreadHandler,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/21579498/

相关文章:

ios - Parse.com iOS SDK 崩溃 : PFSQLiteDatabase. m 第 178 行 -[PFSQLiteDatabase _executeQueryAsync:withArgumentsInArray:cachingEnabled:]

microsoft-metro - 使用 Windbg 调试 Metro 应用程序

python - 为什么 Python 2.7 对 x64 上的 GetDC() 返回的 HDC 进行签名扩展?

c++ - 用于分析故障转储的 WinDbg 在本地 pc 上不起作用

windows - 使用 WinDbg 进一步自动化

c++ - 如何在 Windows7-64 位中为 RHEL 6 创建 C++ 应用程序

python - 使用 py2exe 从 64 位 Windows 7 机器打包用于 32 位 WIndows XP 的 python

c++ - 读取字符串时崩溃

android - Android上的loopj http库: Activity 处于后台时回调

crash - Facebook OAuth2- “Sorry, something went wrong”