Author: |
|
Creation Date: |
2008-11-26 |
• ArchiCAD 12 |
|
Platform: |
• Windows |
Audience: |
• power users |
Reference: |
• [tracking number] |
Analyzing Crash Reports on PC
In the vast majority of cases, only Graphisoft developers are able to analyze crash reports. Please always make sure to submit crash reports with Graphisoft Bug Reporter However, if the crash is caused by a hardware driver or a conflicting software, you may be able to find out what caused the crash by analyzing the call stack of the crash. Here are the steps:
ArchiCAD 12: Find the latest crash report file (.rpt) file in C:\Documents and Settings\USERNAME\Graphisoft\BugReporting-12 (note that each crash or incident is logged in a separate .rpt file)
ArchiCAD 11 and older: Find ArchiCAD.rpt file in C:\Documents and Settings\USERNAME\Graphisoft folder (note that all crashes are logged in the same file)
- Open the .rpt find and look for the 'Call Stack:' section (in AC 11 .rpt files logs are in a historical order - the latest crash is at the bottom of the text)
- Look for any of the following files mentioned in the Call Stack:
ig4dev32.dll |
Intel video driver |
atioglxx.dll |
ATI video driver |
nvoglnt.dll |
Nvidia video driver |
QuickTime.qtx |
|
HPW8C32.dll |
HP printer driver |
hpltdrv7.dll |
HP printer driver |
ocewpdmui.dll |
OCE printer driver |
acpdfui209.dll |
Amyuni PDF converter |
mscorwks.dll |
Microsoft library file, commonly infected by malware |
C:\Acer\Empowering Technology\eDataSecurity\x86\PSDProtect.dll |
Empowering Technology should be turned off |