08-28-2017 09:18 AM
I am now getting a error message upon the startup of the gui for Vivado in Win 10. I get a Run Time error: R6025 - pure virtual function call, for Vivado.exe.
I have tried reinstalling Vivado and the run time lib. I am using Win 10 release 16275.
08-28-2017 09:21 AM
08-28-2017 11:49 AM
Please check if this helps:
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
08-30-2017 08:55 AM
The only solution I have at the moment is using a separate PC workstation loaded with a older revision of windows and I have disconnected it from the network to keep it from updating. The problem with ANY windows 10 platform, is eventually Microsoft will force you to update if connected to the internet. This is why I highly recommend Xilinx address this error before it shows up in mass in a few weeks when the new Win 10 release is pushed to all other users and many Vivado installations become bricks.
09-02-2017 01:10 PM
09-02-2017 01:45 PM
Does Xilinx have any updates on this? The fall update form Win 10 will be released soon (expected in a few weeks) and this will be happening to many Win 10 users and most will not have a choice to not updates, thanks to Microsoft's update system.
09-07-2017 08:59 AM
I'm also in the Windows 10 preview program and having the same exact error trying to launch Vivado. This is a major issue if Xilinx isn't going to bother to fix anything until the update hits stable release.
09-17-2017 11:19 AM
Did anybody found its solution?? I am facing the same problem. Few weeks ago all was working well and now suddenly Vivado wont start. If I try to open vvgl.exe it gives the error "Missing Loader Argument" and if I try to open vivado.exe then it gives the error "The application was unable to start correctly (0xc000007b)". When I try to run vivado.exe with admin rights it gives error about missing some .dll files.
09-25-2017 07:45 PM
I have encountered the same problem when I upgraded the version of Win10 with the Windows Insider Program. I fixed the problem with getting back the version. Xilinx should fix the problem soon, by the fall update of the Windows...
09-29-2017 10:10 AM
My issue is that I can't roll back this version, as there has been various updates since this first started. The fall update should be in just a few days and this will confront many non-insider program members. Xilinx really need to get on this problem, like now, before they have a mass of bug reports where people walk in and fine their computer automatically updated and Vivado will not load any more. To me this should be an fairly easy fix as it appears to be related to the version of MS VC redist being used.
10-25-2017 02:08 PM
I just got the windows update last night and my Vivado 2017.2 gets the "Runtime Error!" and then a minute later I get another pop up with Error launching vivado.bat.
Sounds like this has been a well known issue for a while.
Vivado HLS runs fine.
Just installed 2017.3 and it fails similarly
10-25-2017 02:23 PM
11-06-2017 06:45 AM
11-06-2017 07:00 AM
Please note that Windows 10 Fall Creators update (version 1709) isn't currently unsupported by Xilinx tools, and that is the reason why we haven't tested Vivado tools on this Windows 10 version 1709. We only perform tests on the supported OSs. List of the supported OSs can be found here: https://www.xilinx.com/support/documentation/sw_manuals/xilinx2017_3/ug973-vivado-release-notes-install-license.pdf
As you can see, Windows 10 Professional Creators Update (64-bit) is the only supported OS from WIn 10 OSs.
However, please note that form Vivado 2017.4 release you should not see this problem and neither would need to use this workaround, as this issue is resolved then.
11-18-2017 02:54 PM
I had this exact same problem. I updated windows 10 on 11_17_2017 and this update completely broke Vivado. It would not launch and I received the same error message. Xilinx needs to fix this in the next patch or faster since having a completely broken tool chain after updating is ridiculous.
With that said, the above work around seemed too work. I've launched vivado 2017.3 now and have opened a project. The only issue from here on out for me is that this work around may damage the reliability of the tools.
11-20-2017 04:25 AM
Please note that the only difference between the “old” .exe file (that is causing this Vivado launch error on Win 10 1709 OS) and new ones that you are using after applying this workaround, is the use of Smartheap, where the memory corruption does not happen without Smartheap.
Therefore, this work around will/should not damage the reliability of the tools. If you notice any issues with this, please report these to us, as we haven't seen yet any other problems with Vivado on Windows 10CF (due to this workaround applied).
Thanks in advance and have a nice day.
02-21-2018 10:57 PM
I am trying to compile a design for the Amazon F1 FPGA, but seem to be running into a heap corruption bug that causes Vivado to crash and is preventing me from making further progress.
I've tried to investigate the problem and recently ran Vivado with a manually compiled GitHub version of TCMalloc's debug library libtcmalloc_debug.so.4. After an overnight run, I ran into and icare data recovery tool what I suspect is a Vivado bug (see below for more details). The last line below is an error reported by TCMalloc:
memory stomping bug: a word after object at 0x1a79daaa0 has been corrupted
04-21-2018 02:55 AM
I am trying to compile a design for the Amazon F1 FPGA, Free May 2018 Calendar but seem to be running into a heap corruption bug that causes Vivado to crash and is preventing me from making further progress.
10-09-2018 11:47 PM
Hi, Here is the .bat file that i created to solve the Error R6025.
Method of used is easy just download and double click to run. If there was still a problem occur. The location of the software in your computer might be different. try to move this bat file into the directory which parallel with the Vivado 2017.2 and execute the .bat file. Hopefully It Work for you guys.