Ansyswbu.exe Encountered A Problem. A Diagnostic File Has Been Written File

If Step 1 did not work, the "diagnostic file" mentioned in the error message contains specific error codes.

  • Look for a file named similar to ansyswbu_err.log or a text file generated at the time of the crash.
  • Open the file with Notepad.
  • Look for keywords:

    • Save this as ansys_crash_handler.py and schedule it to run after crash detection.

    import os
import subprocess
import shutil
import time
from datetime import datetime

    def archive_diagnostic(src_diag, dest_folder):
"""Copy diagnostic file with timestamp."""
if os.path.exists(src_diag):
timestamp = datetime.now().strftime("%Y%m%d_%H%M%S")
dest = os.path.join(dest_folder, f"crash_timestamp.dmp")
shutil.copy2(src_diag, dest)
print(f"Diagnostic archived to dest")
return dest
return None
    

    def attempt_clean_restart():
"""Kill hanging ANSYS processes and restart Workbench."""
subprocess.run("taskkill /f /im ansyswbu.exe", shell=True, stderr=subprocess.DEVNULL)
subprocess.run("taskkill /f /im AnsysWBU.exe", shell=True, stderr=subprocess.DEVNULL)
time.sleep(2)
# Restart Workbench
wb_path = r"C:\Program Files\ANSYS Inc\v242\Framework\bin\Win64\RunWB2.exe"
if os.path.exists(wb_path):
subprocess.Popen([wb_path])
print("Restarted ANSYS Workbench.")
else:
print("Workbench executable not found.")
    

    if name == "main":
diag_candidates = [
os.path.join(os.environ['TEMP'], f"ansys_os.environ['USERNAME']_*.dmp"),
r"C:\temp\ansys_crash.dmp"
]
# Expand wildcard manually
import glob
found_diag = None
for pattern in diag_candidates:
matches = glob.glob(pattern)
if matches:
found_diag = max(matches, key=os.path.getmtime)  # latest
break
    

    if found_diag:
    print(f"Crash detected: found_diag")
    archive_diagnostic(found_diag, r"C:\ANSYS_Crash_Reports")
    attempt_clean_restart()
else:
    print("No diagnostic file found.")

    Here are the most effective solutions, ranked from the most common fix to the most complex. If Step 1 did not work, the "diagnostic

    Since the Workbench interface is graphically intensive, driver issues are the primary suspect.

    The error "ansyswbu.exe encountered a problem. A diagnostic file has been written" is a general crash notification from ANSYS Workbench Mechanical. It indicates that the application (specifically the ansyswbu.exe executable) has failed and generated a memory dump file (.dmp) for troubleshooting. Core Causes

    This crash often stems from environmental or configuration issues rather than a single software bug:

    Graphics Drivers: Incompatible or outdated GPU drivers are a frequent culprit, especially if the crash occurs upon opening the Mechanical interface.

    Corrupted User Profile: Temporary user settings in the %APPDATA% or %TEMP% folders can become corrupted after system updates or unexpected shutdowns.

    Missing Scratch Path: The solver may crash if it cannot find or access the designated "Scratch solver files directory".

    Insufficient Resources: A lack of virtual memory or disk space can cause the ansyswbu.exe process to terminate during heavy computations. Look for a file named similar to ansyswbu_err

    Installation Issues: Missing or moved executable files, or conflicts with antivirus software, can prevent the module from launching correctly. Common Solutions

    If you are encountering this error, the following steps are widely recommended by Ansys Innovation Space and FEA Tips: Reset User Settings: Close all ANSYS applications.

    Navigate to %APPDATA% in Windows Explorer and rename the Ansys folder to Ansys_old.

    Navigate to %TEMP% and rename the .ansys folder to .ansys_old.

    Relaunch Workbench to allow it to reconstruct clean profile folders.

    Update Graphics Drivers: Ensure you are using the latest supported drivers for your workstation. For users with multiple GPUs (e.g., integrated Intel and dedicated NVIDIA), ensure the high-performance card is set as the primary for ANSYS in the NVIDIA Control Panel. Check Solver Scratch Path:

    In Mechanical, go to File > Options > Analysis Settings and Solution. Save this as ansys_crash_handler

    Under Analysis Data Management, verify that a valid local path is selected for the Scratch solver files directory. Project Maintenance:

    Try Clear Generated Data by right-clicking the Solution in the project tree.

    Move the project files from a network drive to a local drive to avoid UNC path errors.

    Did the error happen while opening Mechanical, or later during the solution phase?

    Why it happens: ANSYS Workbench can consume 8-32 GB of RAM depending on model size. When memory runs out, ansyswbu.exe crashes when trying to allocate additional space—for example, when updating a mesh or refreshing a result.

    How to identify: The diagnostic file shows std::bad_alloc or memory-related exceptions. Also, you may notice system slowdowns before the crash.

    Solutions: