memory access violation after upgrade to 5.0.4

[speedster29]

I just upgraded my NX 5.0.0.2 to 5.0.4. Now I get frequent "memory access violation" errors when using the software. GTAC has been notified but does not have a solution yet. Anyone else experience this?

 

[speedster29]

Well, it turned out to caused by having the cursor crosshairs turned on! Once I turned them off, no more errors. GTAC has created a PR for this. That's my second PR this week!

 

[JohnRBaker]

Can you recall what it that you were doing when you go the error(s)?

I'm running NX 5.0.5.3 and I just went in and turned on the full-screen cursor and so far no problems. I don't usually use this option, but I'll leave it on for awhile and see if I can get it to err-out. If it doesn't then perhaps it has already been fixed and you will be getting it in about a month or so.

John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

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

 

[speedster29]

Yes, I moved the cursor.

 

[JohnRBaker]

Well, I've been working for 7 or 8 minutes and so far so good. Perhaps this has been fixed in NX 5.0.5.3.

John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

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

 

[JohnRBaker]

BTW, I've now been working with the full-screen cursor for over an hour and have encountered no problems whatsoever. So perhaps this indicates that the problem has already been addressed and will be working in the latest MR, NX 5.0.5.3.

John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

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

 

[rossob]

Hi guys, just my 2cents worth. I generally seem to get this problem when working with drawings, also with the cursor cross-hairs turned on. The problem I am having, is that this error occurs at least 90% of the time when I go to save the drawing. The only work-around I have found so far, is to switch to the master-model and save it first, before i save the drawing. There are also 2 other peope in the office having the same problems, all with different drawings.

Ross

NX5.0.4.1 WinXP SP2
SolidWorks 2007

 

[speedster29]

Hi, I just received a response from GTAC with a PR resolution (PR 5977492.) Here is the recommended work-around:

"You can try setting an environment variable to use deprecated crosshair/rubberband rendering logic instead of the default logic to see if it allows you to avoid the NVIDIA error.

UGII_USE_LEGACY_CROSSHAIRS=TRUE"

This cleared up the problem for me.