nTopology has crashed.
The only known cause of nTopology crashing and unexpectedly closing out is when the computer's memory (RAM) runs out of space. When the size of the mesh and/or simulation data approaches the computer's total RAM, nTopology may crash. You can observe the current memory used by nTopology using the Windows Task Manager.
Crashes can be prevented by:
- Increasing the Pagefile (by using the computer's disk as virtual memory) To increase the Pagefile, we recommend following this article. Note, that this article isn't written by nTopology and this link will take you to a different website.
- Increasing the RAM
- Reducing the mesh element count
- Removing memory-intensive blocks, such as Topology Optimization and Simulation blocks, from your notebook
- Making sure other memory intense programs aren't running at the same time
Locating crash dump logs
The system generates a crash log when nTopology exits unexpectedly.
Find the crash dump file here (copy and paste the location into File Explorer):
The crash dump is in the format: ntop.exe.N.dmp
Where N is a system-generated value.
If you are looking up the location manually and can't see Hidden Folders:
- Go to Windows Explorer.
- Open the C: drive.
- Click the ^ in the upper right-hand corner to expand the options
- Select the View tab.
- Check 'Show hidden items'
- Go to: This PC > Local Disc > Users > YOURNAME > AppData > Local > CrashDumps
Submitting a crash dump log
Sending one or more crash dump log to technical support helps our developers diagnose and solve the problem. To submit crash logs, click 'Contact Support' at the upper right corner of this support site, and attach the file(s). Please also include a description of what you observed, and if possible, the nTop file used during the crash.