07-15-2019 07:25 PM
I ge the following error in Vivado 2018.3
Abnormal program termination (EXCEPTION_ACCESS_VIOLATION)
Please check 'C:/..../hs_err_pid4612.log' for details
# An unexpected error has occurred (EXCEPTION_ACCESS_VIOLATION)
no stack trace available, please use hs_err_<pid>.dmp instead.
07-15-2019 07:36 PM
Hi @dmzehnder ,
It is actually Vivado getting crashed. Please chec the below link of an AR# for more infomation:
Also can you please let us know in which phase it is getting crashed?
Please if possible can you please try the latest Vivado 2019.1 version and check whether the crash is still persisting?
07-15-2019 11:50 PM
Any update on this thread? If the above shared information was not helpful then please share the vivado.log, crash log files and xifno.txt file.
Run below command from Vivado TCL console and share generated xinfo.txt file.
report_environment -file xinfo.txt
09-05-2019 03:55 AM
are there any update on this thread?
We have the same Problem with Vivado 2018.3 and Windows 10. We implemented the design with 2019.1 and it was passed thru.
The problem is, at the moment we cannot switch to Vivado 2019.1 because the project is at an advanced stage and
we don't want to add other problems with the switch.
So, are there other solutions for Vivado 2018.3?
09-10-2019 02:17 AM
Can you share the vivado.log, crash log file and xinfo.txt mentioned in my previous post above.
01-24-2021 11:17 AM
no, unfortunately there is nothing new....
We have switched to a new version (2019.1/2020.2) of Vivado, where the problem no longer occurs.