Internal error"memory access violation!!

[swale74]

After an hour of updating an assembly view in drafting I dropped back into modeling to adjust one of the items in the assembly and now have a "Internal error:Memory access violation" hit ok to continue. This selecting ok seems to happen indefinitely. Is there any way to cancel this without loosing everything? These long updates and memory errors are killing our time on projects. These seem to make the geomod i-deas errors look like slight inconvinences. We're running NX 6.0.5.3 on windows xp with 3GB of ram and the 3 GB switch enabled.

 

[looslib]

3GB of physical memory and the 3GB switch won't buy you anything.
The OS takes 1.1GB of memory off the top, so you have nothing left to extend the application memory space.

It has always been recomended that the /3GB switch be run with /USERVA=2900.

When it comes to switching modules in NX, do a save before switching will save you a lot of headaches in the long term.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[JohnRBaker]

Also note that ALL 'Memory Access Violation' errors should be reported to GTAC ASAP.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

UG/NX Museum:

http://www.plmworld.org/p/cm/ld/fid=209

To an Engineer, the glass is twice as big as it needs to be.