NX 7.5 memory access violation error.

[SkyRat]

Hi Guys,

I don't know if anyone else has had this problem before, but one of my users is telling me that whenever he opens either a model or drawing from Teamcenter (We are using TC 8.3 + NX 7.5) he consistently gets a memory access violation error (see attached picture).

He also states, that if he gets this error while he is busy working with a model, then he is unable to save any progress he has made since his last succesful save and therfore loses all his changes.

His computer is a:

- HP Z400 Workstation
- Windows XP 64 bit
- 6 Gig. RAM
- 3 GHz Xeon Quad core CPU
- nVidia Quadro FX 1800 GPU

I am currently downloading the 7.5.4 MP & MR patch which i hope will sort this problem out, but i could be wrong. Any thoughts?

Thanks in advance!

 

[uwam2ie]

contact the GTAC,
occurs this problem after the last NX 7.5.4 update?
regards

 

[Arkance/PhoeNX]

Try deleting the dialogmemory file in the users profile directory. Use the NX log file to show you where the profile directory is. I've seen a number of errors a fixed by deleting this file. Since it sounds lke you have a number of users and I would guess theybare all similar systems, it's logical to me that the problem could be related to the user profile. Try this before applying the MR & MP.

Anthony Galante
Senior Support Engineer

NX4.0.4MP10, NX5.0.0->5.0.6, NX6.0.0->NX6.0.5, NX7.0.0->NX7.0.1 & NX7.5.0.32-> NX7.5.4.4, Beta NX8.0.0.23

 

[looslib]

Also be sure you have installed the 64bit version of NX.


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

Ben Loosli

 

[SkyRat]

Great, let me give this a try, thanks for all your input.

Yes, x64 version of NX is installed.

 

[SkyRat]

namdaci45, are you talking about this file:

C:\Documents and Settings\ryjoost\Local Settings\Application Data\Unigraphics Solutions\NX75\DialogMemory.dlx


If so, what is this file, what is it's function?


Thanks!

 

[JohnRBaker]

'Dialog Memory' remembers the settings for individual dialogs so that the next time that dialog is accessed the values and settings which you used the last time is was used will be the current 'default' values and settings.

Note that this feature can be disabled so that these settings are NOT remembered from session to session, that is, they're reset once you close your current NX session and your next session will revert the Customer Default settings. However, the out-of-the-box default is to retain these settings from session to session, thus the creation and use of the 'DialogMemory.dlx' file.

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

http://www.siemens.com/plm

http://www.plmworld.com/museum/

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

 

[SkyRat]

John, Could this be the root cause of my error? If so, how do I disable this feature?

 

[phillpd]

It's quite a common 'issue' for CAM users.

I've just deleted a 52MB dialog memory file.

NX 6.0.5.3 (NX 8 Beta)
Windows XP32 (Windows 7 64)

 

[Arkance/PhoeNX]

That is the file.

Anthony Galante
Senior Support Engineer

NX4.0.4MP10, NX5.0.0->5.0.6, NX6.0.0->NX6.0.5, NX7.0.0->NX7.0.1 & NX7.5.0.32-> NX7.5.4.4, Beta NX8.0.0.23

 

[SkyRat]

How do I disable this feature? Or do I just need to get my user to delete this file once a day?

 

[JohnRBaker]

It generally takes months to get a dialog memory file up to a size like that. Besides, I'm not convinced that there's really any direct correlation between the size of your .dlx file and these memory errors unless you're running a very minimally configured system. I would suggest that ANY case of a memory access violation, that this gets immediately reported to GTAC so that they can track down what's really causing the problem.

Case in point, I just checked my dialog memory file for NX 8.0. I installed my first copy of an early development phase back in September, 2010, 11 months ago, and the first time you launch a new system this .dlx file is one of the first files created by the system and unless you explicitly delete it, it will continue to be reused and even as I de-installed old versions of NX 8.0 and installed new ones, this file, as well as the other files in the ...\appdata\local\unigraphics solutions\NX80 folder are not replaced, but simply accessed and are continued to be used. Anyway, in 11 months, my NX 8.0 .dlx file isn't even up to 5MB yet. Now granted, I'm not running NX 8.0 in a production environment, but it has been 11 MONTHS and I've done a lot of testing and many many demos, and it's only up to close to 5MB.

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

http://www.siemens.com/plm

http://www.plmworld.com/museum/

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

 

[Arkance/PhoeNX]

I would argue that it's not the size, but the file somehow becomes corrupted. For example one of techs rang to me test if a routing function was broken in NX7.5.4 as he'd just installed and was getting an error. I tested and found it was OK. From experience we thought the user profile folder might be the cause so he deleted one file at a time. As soon as the dlx file was gone the error went away. Put the file back and the error reappeared.

Also seen where NX will not start at all. Delete the dlx and it can start again. As I said this has been seen on a number of different systems.

Anthony Galante
Senior Support Engineer

NX4.0.4MP10, NX5.0.0->5.0.6, NX6.0.0->NX6.0.5, NX7.0.0->NX7.0.1 & NX7.5.0.32-> NX7.5.4.4, Beta NX8.0.0.23

 

[phillpd]

John,

That file can get quite big, quite quickly, for CAM users. It can then cause a multitude of issues.

The response from GTAC for our CAM users in Brazil was to switch to a 64bit OS. Deleting the dialog memory file cured the problem.

NX 6.0.5.3 (NX 8 Beta)
Windows XP32 (Windows 7 64)

 

[SkyRat]

To delete it is fine and all, but it just gets gets recreated, so is this a case where you delete it when you get an error or is there someway I can disable this feature so that the settings are NOT remembered from session to session?

 

[phillpd]

File->Utilities->Customer Defaults->Gateway->User Interface

Toggle off Save Dialog Box Settings between Sessions

This should keep the file size in check.

NX 6.0.5.3 (NX 8 Beta)
Windows XP32 (Windows 7 64)

 

[JohnRBaker]

Yes, but this sort of defeats the whole purpose of even having this feature, Dialog Memory, in the first place. That's why I'm advocating that ALL memory access issues need to be immediately reported to GTAC. They ONLY occur when there's a problem somewhere with the software itself or your hardware configuration.

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

http://www.siemens.com/plm

http://www.plmworld.com/museum/

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

 

[phillpd]

We did call it in, GTAC's advice was to upgrade to a 64bit OS

NX 6.0.5.3 (NX 8 Beta)
Windows XP32 (Windows 7 64)