The diagnostic file shows std::bad_alloc or memory-related exceptions. Also, you may notice system slowdowns before the crash.
To resolve this issue, try the following steps:
Ensure is checked, or manually set it to at least 1.5 times your physical RAM capacity.
If the default scratch directory is full, restricted, or on a slow network drive, the solver will fail. Open Workbench. Go to . If the default scratch directory is full, restricted,
Ansys relies heavily on dedicated hardware acceleration. Outdated, unsupported, or conflicting GPU setups will trigger immediate ansyswbu.exe failures. Switch to Discrete Graphics
If Stack Overflow or Memory Allocation appears, it indicates a .
Try these steps in order to resolve the issue quickly, as suggested by Ansys forum contributors . A. Reset User Settings (Appdata Cleanup) Ansys relies heavily on dedicated hardware acceleration
: Inside these folders, search for files bearing the .mechdb extension. This is your core Mechanical tree structure.
Move the project files from a network drive to a local drive to avoid UNC path errors.
If you are encountering this error, the following steps are widely recommended by Ansys Innovation Space and FEA Tips : : Close all ANSYS applications. Look for "Exception Code" (e.g.
Try running Workbench as an to see if the crash is related to folder write permissions. 6. Re-Registering DLLs (The Last Resort)
To help narrow down the exact cause for your system, let me know:
Suppress complex features like small fillets, text engravings, or microscopic gaps in your CAD software before importing.
Look for "Exception Code" (e.g., 0xC0000005 for Access Violation) or references to specific .dll files that might point to a corrupted installation or third-party conflict.
A large percentage of Ansys Mechanical crashes are related to graphics card driver incompatibilities, particularly with NVIDIA cards in engineering workstations.