SLDWORKS error messages
Joel
below) it seems to be moving quiet nicely at the moment, but even
before receiving this computer I have been having problems with
solidworks crashing out on me.
I have the latest spin installed ( Solidworks 2001 SP9 ) and some of
the issues which I have had problems with in the past are still
occurring, graphics related ( eg. solid entities are show as see
through in drawings, with hidden line removal active )
I have Windows NT (4.0)
The following are errors which I have recorded from June 2001. In each
case solidworks was shut down.
In most cases the errors occured when trying to save an assembly, part
etc. or while a reasonably large assembly was being rebuilt.
6/6/01
sldworks.exe
Exception : Access Violation : (0xc0000005) Address: 0x5f80263a
21/6/01
Application Error. sldworks.exe
17/8/01
sldworks.exe
Exception : Access Violation : (0xc0000005) Address: 0x10089c59
24/8/01
sldworks.exe
Exception : Access Violation : (0xc0000005) Address: 0x07315edb
24/8/01
sldworks.exe
Exception : Access Violation : (0xc0000005) Address: 0x06ec5edb
--------------------------------------------------------------------------------
Installation of new computer.
AMD 1.4 Mhz Athlon Thunderbird CPU
Gigabyte GA-7ZXR Motherboard
On-Board promise PDC-20265 ATA100 IDE Raid controller
For Raid 0 & Raid 1
512 MB PC-133 SDRAM
1x Quantum 60GB Fireball AS 7200 rpm ATA100 Hard Drive
Oxygen VX-1 Video Card
On-board Creative Sound
1.44 floppy
50x CD-Rom
--------------------------------------------------------------------------------
20/9/01
solidworks
"0x0a404f9d" referenced memory at " 0x00000008" The memory could not
be read.
21/9/01
sldworks.exe
Exception : Access Violation : (0xc0000005) Address: 0x40273b1e
02/10/01
sldworks.exe
Exception : Access Violation : (0xc0000005) Address: 0x0afabe70
03/10/01
sldworks.exe
Exception : Access Violation : (0xc0000005) Address: 0x406314eb
While the computer i am using is networked, all drawing files are
stored locally.
I hope the above is helpful in determining why this is happening.
While all drawings are regularly saved it is becoming a frustrating
problem.
Regards
Joel Dixon
Enviromist Industries Pty Ltd
Design Dept
des...@enviromist.com.au
Kman
can't help you there. There have been multiple threads in this newsgroup on
the subject of Oxygen VX1 card.
Some considerations:
01. Go to Tools: Options: Performance: Use Software OpenGL. This uses SW's
software driver inplace of Oxygen VX1 hardware. Note: Cannot have any
documents open when performing the sequence of tasks. Else the check box for
"Use Software OpenGL" will be grayed out.
02. Go to Display Properties: Set colors < 32 bit
03. Go to Display Properties: Effects: Uncheck "use transition effects for
menus and tooltips"
04. Go to Display Properties: Effects: Uncheck "show window contents while
dragging"
05. Go to Display Properties: Advanced Settings: Configuration Profiles:
check "SolidWorks" not "Default" (got this information from SW website).
Setting to use depends on the driver presently installed.
06. Go to Display Properties: Advanced Settings: Hardware Acceleration and
move pointer one-two notches to the left from the "Full" position
07. Download latest drivers for the Oxygen VX1. Make sure you uninstall
previous drivers first and set display to VGA mode before installing new
drivers.
08. If you have the knowledge, go into Windows registry and purge all old
driver data. This step is risky and should be avoided unless you are
familiar with the registry.
09. Verify your graphic card is functioning properly. Install card in a
different machine if possible and run SW from there.
There are probably other good suggestions that have been posted. Can't
remember them all.
Ken Redman
"Joel" <des...@enviromist.com.au> wrote in message
news:d4d75dd7.01101...@posting.google.com...
Jerry Steiger
> below) it seems to be moving quiet nicely at the moment, but even
> before receiving this computer I have been having problems with
> solidworks crashing out on me.
Joel,
I'm afraid I don't have any answers for you, other than to tell you that the
error messages are basically useless for figuring out what is going wrong. I
also hate to say it, but 9 crashes in the last 4 months doesn't seem too
extreme. I think I'm doing better than that (on a GVX1), but I suspect that
my partner in crime (basically identical machines) is doing about that
badly.
On the SW website, go to
http://www.solidworks.com/swdocs/support/html/videoissues/videoreport.cfm
It says that the 2.16-0388 driver works for the VX1 on NT. If that's not the
one you are using, try getting hold of it. If that's the one you are using,
then try Ken's suggestions. Since the Oxygen cards have a very good
reputation in the group, and since your number of crashes doesn't seem that
high, I suspect you won't improve things much.
Jerry Steiger
At Work Computers
Per O. Hoel
You should have mentioned which Service Pack you are using with Windows NT 4.0
Make sure that it is 5 or higher (6a being the latest...)
Per O. Hoel
_______________________________________________________________________________
"Jerry Steiger" <jer...@AtWorkCom.com> wrote in message news:<9qivf8$oglu3$1...@ID-110347.news.dfncis.de>...
kellnerp
fun to model in, but comes in handy for troubleshooting.