Steve_S Posted February 9, 2005 Share Posted February 9, 2005 Please refer to my previous post: posted 12-30-2004 10:25 PM Topic: Vectorworks 11 & 11.0.1 crash shortly after loading -------------------------------------------------- System & application info: Application: Vectorworks 11 (First complete version) Application Versions: 11 & 11.0.1(Update) Licensed Products: Vectorworks & Renderworks Operating System: Windows XP Professional -Service Pack 2 Computer: Gateway ATXAEG LX2 700XL Manufacture Date: 07/12/02 RAM: 2 GB File System: NTFS Hard Drive Size: 120 GB (disk - 26 % full) Graphic Board: NVIDIA GeForce4 Ti 4600 (Updated to latest display driver - 11/09/04) Memory: 128 MB Bios Information: Version 4.25.0027 Security software: Norton Internet Security 2005 (enabled) Mouse: Logitech MX1000 Laser Cordless (latest driver / software installed) Monitor: Wacom Cintiq 18SX Interactive Display Although I fixed the problem with Vectorworks crashing (related to the installation of SP2), ever since I updated my (NVIDIA GeForce4 Ti 4600) driver to the latest version (at least I think that may be the cause), the same behavior seems to be occurring. Every time I open a file and begin working on it, an application error message appears and upon clicking "OK" the program abruptly terminates. The application error message reads as follows: Vectorworks.exe - Application error The instruction at "0x6966355eb" referenced memory at "0x00000020". The memory could not be read. Click on OK to terminate the program. Click on CANCEL to debug the program. What do I need to do to correct this problem? Quote Link to comment
Guest Posted February 10, 2005 Share Posted February 10, 2005 That's an OS memory related message. You may have a problem with a bad memory chip or something like that. I suggest you go through Microsofts KB or call them regarding this. I know this is a common message after updating to SP2 also. Quote Link to comment
Steve_S Posted February 10, 2005 Author Share Posted February 10, 2005 Thank you for your initial assessment. I should also note that I have several memory intensive graphics programs that I use regularly, none of which produce this error message. At this point, I don't think it makes sense to take such a broad approach to the problem until similar error messages appear within other applications that put similar demands on my system. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.