2010年项目崩溃

本文介绍了2010年项目崩溃的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

您好

我的公司在Windows 7 Enterprise x64上使用Project Pro SP1。我们的一个用户在使用各种项目文件时遇到了frequest崩溃，无论是大型还是小型，都存储在本地和网络共享上。

到目前为止，我已尝试重新安装Project并重新安装在其计算机上创建用户配置文件以解决问题。在这两种情况下，项目一天都很好，然后问题再次发生。任何解决这些崩溃的帮助都将大大降价！

谢谢

Alex

请参阅以下有关崩溃的详情：

于2013年6月26日

问题签名： 问题事件名称：AppHangXProcB1 应用程序名称：WINPROJ.EXE 应用程序版本：14.0.6023.1000 申请时间戳：4d7a60be Hang Signature ：5391 挂牌类型：128 等待应用程序名称：splwow64.exe 等待应用程序版本：0.0.0.0 操作系统版本：6.1.7601.2.1.0.256.4 区域设置ID：2057

其他吊签名1：53915fd6d3c9615fd265c22ab87f95b7 其他吊牌2：59fd 其他Hang Signature 3：59fdebdafbe00535efc88d474a4c9c08 其他Hang Signature 4：5391 其他Hang Signature 5：53915fd6d3c9615fd265c22ab87f95b7 其他Hang Signature 6：59fd 其他Hang Signature 7：59fdebdafbe00535efc88d474a4c9c08

b

问题签名：

问题事件名称：BEX

应用程序名称：WINPROJ.EXE

应用程序版本：14.0.6023.1000

应用程序时间戳：4d7a60be

故障模块名称： MSVCR90.dll

故障模块版本：9.0.30729.6161

故障模块时间戳：4dace5b9

例外抵消：000320f0

例外代码：c0000417

异常数据：00000000

操作系统版本：6.1.7601.2.1.0.256.4

区域设置ID：2057

附加信息1：9355

附加信息2：9355c752bfbcfcaf957c0b424c6bd347

附加信息3：5951

附加信息4：5951441ecb5f285224e92d918aac4a57

解决方案

Alex，

不幸的是，故障数据转储对我们没有帮助。我们是志愿者，不为微软工作，因此我们中的一个人可以从失败数据中挖掘有用信息的机会是零。

但是，我们可以提出一些建议。您说SP1已安装，您已经尝试了新的用户配置文件，甚至重新安装了Project。所有有用的信息。文件是链接结构的一部分（即主/子项目或资源池/共享者，或两者）？该文件是否具有项目间链接（即外部前置/后继）？该文件是否包含任何VBA宏？

文件可能已损坏。尝试保存为XML，然后在Project中重新打开。注意：您将丢失任何自定义格式，如果此文件是链接结构的一部分，则需要执行更多步骤。

John

Hi

My company uses Project Pro SP1 on Windows 7 Enterprise x64. One of our users is experiencing frequest crashes while using various project filesboth large and small, stored both locally and on network shares.

So far I have tried re-installing Project and re-creating their user profile on their machine to resolve the issue. On both occasions Project was fine for a day or so and then the problem re-occurs. Any assistance in resolving these crashes would be greatly appreciated!

Thanks

Alex

Please see below details from crashes:

on 26/06/13

Problem signature: Problem Event Name: AppHangXProcB1 Application Name: WINPROJ.EXE Application Version: 14.0.6023.1000 Application Timestamp: 4d7a60be Hang Signature: 5391 Hang Type: 128 Waiting on Application Name: splwow64.exe Waiting on Application Version: 0.0.0.0 OS Version: 6.1.7601.2.1.0.256.4 Locale ID: 2057

Additional Hang Signature 1: 53915fd6d3c9615fd265c22ab87f95b7 Additional Hang Signature 2: 59fd Additional Hang Signature 3: 59fdebdafbe00535efc88d474a4c9c08 Additional Hang Signature 4: 5391 Additional Hang Signature 5: 53915fd6d3c9615fd265c22ab87f95b7 Additional Hang Signature 6: 59fd Additional Hang Signature 7: 59fdebdafbe00535efc88d474a4c9c08

on 03/07/13

Problem signature:

Problem Event Name: BEX

Application Name: WINPROJ.EXE

Application Version: 14.0.6023.1000

Application Timestamp: 4d7a60be

Fault Module Name: MSVCR90.dll

Fault Module Version: 9.0.30729.6161

Fault Module Timestamp: 4dace5b9

Exception Offset: 000320f0

Exception Code: c0000417

Exception Data: 00000000

OS Version: 6.1.7601.2.1.0.256.4

Locale ID: 2057

Additional Information 1: 9355

Additional Information 2: 9355c752bfbcfcaf957c0b424c6bd347

Additional Information 3: 5951

Additional Information 4: 5951441ecb5f285224e92d918aac4a57

解决方案

Alex,

Unfortunately the failure data dump doesn't help us. We are volunteers and do not work for Microsoft so the chance that one of us can dig useful information from the failure data is nil.

However, there are some things we can suggest. You said SP1 is installed and you already tried a new user profile and even re-installing Project. All useful information. Is the file part of a linked structure (i.e. master/subproject or resource pool/sharer, or both)? Does the file have inter-project links (i.e. external predecessors/successors)? Does the file contain any VBA macros?

It's possible the file is corrupt. Try saving as XML and then re-opening in Project. Note: you will lose any custom formatting and if this file is part of a linked structure, more steps will be required.

John