VMware unrecoverable error: (mks) 挂起，并导致程序退出 【win 7】

出现过好几次这种状况足以让人感到愤怒！当然愤怒归愤怒，我们还是得解决问题

说起来，自开始用vmware 来，不管是在vista还是在win xp上都没有出现过vmware

挂起的问题，这真是让人郁闷，同时不得不感叹 MS$$  的大势已去。。。

 

这里是挂起后给的截图

 

分析日志文件 截取重要的部分

 

Dec 28 15:12:56.866: mks| CoreDump: including module base 0x0x02f40000 size 0x0x00018000 Dec 28 15:12:56.866: mks| checksum 0x00024ed1 timestamp 0x4a82beb9 Dec 28 15:12:56.866: mks| image file C:/Program Files/PowerWord/CBSText.dll Dec 28 15:12:56.866: mks| file version 2009.8.12.135 Dec 28 15:12:56.866: mks| CoreDump: Including thread 4992 Dec 28 15:12:56.866: mks| CoreDump: Including thread 4672 Dec 28 15:12:56.866: mks| CoreDump: Including thread 3636 Dec 28 15:12:56.866: mks| CoreDump: Including thread 6072 Dec 28 15:12:56.866: mks| CoreDump: Including thread 4184 Dec 28 15:12:56.866: mks| CoreDump: Including thread 4580 Dec 28 15:12:56.866: mks| CoreDump: Including thread 5856 Dec 28 15:12:56.866: mks| CoreDump: Including thread 6044 Dec 28 15:12:56.866: mks| CoreDump: Including thread 4980 Dec 28 15:12:56.866: mks| CoreDump: Including thread 3220 Dec 28 15:12:56.866: mks| CoreDump: Including thread 1884 Dec 28 15:12:56.866: mks| CoreDump: Including thread 5872 Dec 28 15:12:57.029: mks| ----Backtrace using dbghelp.dll---- Dec 28 15:12:57.031: mks| Module path: C:/windows/system32/kernel32.dll Dec 28 15:12:57.031: mks| backtrace[00] frame 0x0dcffd5c IP 0x75a3258a params 0 0xdcffd94 0x460e27 0x1 [C:/windows/system32/kernel32.dll base 0x759f0000 0x0001:0x0004158a] (SetPriorityClass + 0x003d) Dec 28 15:12:57.036: mks| backtrace[01] frame 0x0dcffd68 IP 0x00404938 params 0x1 0x45b08b 0x1ef 0xc8 [E:/Tools/VMware/vmware6.5/vmware-vmx.exe base 0x00400000 0x0001:0x00003938] (no symbol information): 487 Dec 28 15:12:57.036: mks| backtrace[02] frame 0x0dcffd94 IP 0x00460e27 params 0xdcffe00 0x1ef 0xc8 0x1ef [E:/Tools/VMware/vmware6.5/vmware-vmx.exe base 0x00400000 0x0001:0x0005fe27] (no symbol information): 487 Dec 28 15:12:57.039: mks| backtrace[03] frame 0x0dcffe14 IP 0x0057fd08 params 0xc8 0x201 0x1 0x1ef [E:/Tools/VMware/vmware6.5/vmware-vmx.exe base 0x00400000 0x0001:0x0017ed08] (no symbol information): 487 Dec 28 15:12:57.039: mks| backtrace[04] frame 0x0dcfff28 IP 0x759386ef params 0xdcfff3c 0x465710 0x1 0xc0682 [C:/windows/system32/USER32.dll base 0x75920000 0x0001:0x000176ef] (IsThreadDesktopComposited + 0x011f) Dec 28 15:12:57.041: mks| backtrace[05] frame 0x0dcffeb8 IP 0x75938876 params 0 0x57fb10 0xc0682 0x201 [C:/windows/system32/USER32.dll base 0x75920000 0x0001:0x00017876] (IsThreadDesktopComposited + 0x02a6) Dec 28 15:12:57.041: mks| backtrace[06] frame 0x0dcfff18 IP 0x759389b5 params 0x57fb10 0x1 0xdcfff58 0x57f77d [C:/windows/system32/USER32.dll base 0x75920000 0x0001:0x000179b5] (IsThreadDesktopComposited + 0x03e5) Dec 28 15:12:57.041: mks| backtrace[07] frame 0x0dcfff28 IP 0x75933578 params 0xdcfff3c 0x465710 0x1 0xc0682 [C:/windows/system32/USER32.dll base 0x75920000 0x0001:0x00012578] (DispatchMessageA + 0x000f) Dec 28 15:12:57.044: mks| backtrace[08] frame 0x0dcfff58 IP 0x0057f77d params 0x1 0x4a9409 0 0 [E:/Tools/VMware/vmware6.5/vmware-vmx.exe base 0x00400000 0x0001:0x0017e77d] (no symbol information): 487 Dec 28 15:12:57.044: mks| backtrace[09] frame 0x0dcfff88 IP 0x0046578c params 0x12fe88 0xdcfffd4 0x770cb3f5 0x12fe88 [E:/Tools/VMware/vmware6.5/vmware-vmx.exe base 0x00400000 0x0001:0x0006478c] (no symbol information): 487 Dec 28 15:12:57.044: mks| backtrace[10] frame 0x0dcfff94 IP 0x75a41174 params 0x12fe88 0x7a9d7c77 0 0 [C:/windows/system32/kernel32.dll base 0x759f0000 0x0001:0x00050174] (BaseThreadInitThunk + 0x0012) Dec 28 15:12:57.044: mks| backtrace[11] frame 0x0dcfffd4 IP 0x770cb3f5 params 0x4a93c0 0x12fe88 0 0 [C:/windows/SYSTEM32/ntdll.dll base 0x77070000 0x0001:0x0005a3f5] (RtlInitializeExceptionChain + 0x0063) Dec 28 15:12:57.051: mks| backtrace[12] frame 0x0dcfffec IP 0x770cb3c8 params 0x4a93c0 0x12fe88 0 0 [C:/windows/SYSTEM32/ntdll.dll base 0x77070000 0x0001:0x0005a3c8] (RtlInitializeExceptionChain + 0x0036) Dec 28 15:12:57.051: mks| ----End of backtrace---- Dec 28 15:12:57.051: mks| Msg_Post: Error Dec 28 15:12:57.051: mks| [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (mks) Dec 28 15:12:57.051: mks| Exception 0xc0000005 (access violation) has occurred. Dec 28 15:12:57.051: mks| [msg.panic.haveLog] A log file is available in "E:/Linux/jeos/vmware.log". [msg.panic.haveCore] A core file is available in "E:/Linux/jeos/vmware-vmx-4288.dmp". [msg.panic.requestSupport.withLogAndCore] Please request support and include the contents of the log file and core file. [msg.panic.requestSupport.vmSupport.windowsOrLinux] Dec 28 15:12:57.051: mks| To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly. Dec 28 15:12:57.051: mks| [msg.panic.response] We will respond on the basis of your support entitlement. Dec 28 15:12:57.051: mks| ----------------------------------------

注意开始的这行

Dec 28 15:12:56.866: mks| image file C:/Program Files/PowerWord/CBSText.dll

 

好了，你终于找到了问题的症结所在：

vmware和xdict （LJ金山词霸 ！！ ）冲突！！！

这可好像并不是我的首创，开始我还一直不信这个，怎么会出现这种状况？

现在终于证实了 网上的言论：群众的眼光是雪亮的

好了你现在知道怎么解决了吧？要么取消词霸鼠标取词（或关闭）， 要么不要同时用vmware,顺便说下我用的是谷歌金山合作版本。。