Fatal Error Reporting

While we test our products vigorously for defects, especially fatal errors, they do still occur from time to time and can be related to specific data sets. If a fatal error occurs while using any of our tools, please send the output files from the fatal error. Submitting the fatal error to Autodesk does not do any good as we can't access the reports when sent to Autodesk. If a fatal error is confirmed to be caused by Red Transit tools, we will get the issue resolved as quickly as possible in a product update.

AutoCAD Civil 3D 2024 and Prior

Send these two files to support@redtransitconsultants.com with as detailed of an explanation of the operations leading to the fatal error as you can provide.

For further detail - you can open the 'dmpuserinfo.xml' and search for 'Current Stack'. It will show what's called a Stack Trace report with the outlined code hierarchy to where the error actually occurred. From here, you can see if it's from a specific developer's app, native Civil 3D function, or even something with a Graphics Card driver causing the issue.

Note: The screenshot below was opening in Notepad++ which is great for formatting and colorizing the text to make it easier to decipher.

AutoCAD Civil 3D 2025

Send these two files to support@redtransitconsultants.com with as detailed of an explanation of the operations leading to the fatal error as you can provide.

For further detail - you can open the 'rawdata-t1.pb' or the 'rawdata-t2.pb' and search for 'Current Stack'. It will show what's called a Stack Trace report with the outlined code hierarchy to where the error actually occurred. From here, you can see if it's from a specific developer's app, native Civil 3D function, or even something with a Graphics Card driver causing the issue.

Note: The screenshot below was opening in Notepad++ which is great for formatting and colorizing the text to make it easier to decipher.