Windows更新后，Vivado无法启动GUI

嗨，
我不知道这是否会解决你的问题因为我使用的是Viv2017.2和Win7。
尝试更新您的Java版本。
我使用的是Ver8 Update 141（版本1.8.0_141-b15）。
您正在使用 -  build 1.8.0_112-b15
--------------------------------------------------
--------------------------------------------------
---- FPGA爱好者！-------------------------------------------
--------------------------------------------------
-----------



以下为原文

Hi,
 
I don't know if this will solve your problem coz I use Viv2017.2 and Win7.
 
Try updating your Java version. I am using, Ver8 Update 141 (build 1.8.0_141-b15).
You are using -  build 1.8.0_112-b15
--------------------------------------------------------------------------------------------------------
FPGA enthusiast!
--------------------------------------------------------------------------------------------------------

嗨@basaro，
作为一种快速解决方法，请尝试启动Vivado Tcl Shell，然后键入start_gui以查看是否有效。
最好的问候艾丹
--------------------------------------------------
--------------------------------------------------
--------------请将答案标记为“接受为解决方案”，如果这回答了您的问题，请给予您认为有用的帖子，并可以帮助其他用户-------
--------------------------------------------------
--------------------------------------------------
-------
--------------------------------------------------
--------------------------------------------------
--------------请将答案标记为“接受为解决方案”，如果这回答了您的问题，请给予您认为有用的帖子，并可以帮助其他用户-------
--------------------------------------------------
--------------------------------------------------
-------



以下为原文

Hi @basaro,
 
As a quick workaround try starting the Vivado Tcl Shell and then type start_gui to see if this works.
 
Best Regards
Aidan
 
 

------------------------------------------------------------------------------------------------------------------
Please mark the Answer as "Accept as solution" if this answered your question
Give Kudos to a post which you think is helpful and may help other users
------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------
Please mark the Answer as "Accept as solution" if this answered your question
Give Kudos to a post which you think is helpful and may help other users
------------------------------------------------------------------------------------------------------------------

谢谢你dpaul24。我更新了java，但vivado还有错误。
我觉得vivado 2017.2使用的是java版本的老版本。坦克你。



以下为原文

Thank you dpaul24.

I update java, but vivado has error yet.

I think so vivado 2017.2 use java version old.

Tnank you.

谢谢你hpoetzl。我想让windows new vertion有bug？当我更新windows 10 Pro Insider预览版16251时，Vivado无法启动。我返回构建版本16232，Vivado可以启动。现在，我使用windows 10 build 16232.谢谢
您。



以下为原文

Thank you hpoetzl.

I think so that windows new vertion has bug?

When I update windows 10 Pro Insider Preview build  16251,
Vivado can not start.

I return build version 16232, Vivado can start.
Now, I use windows 10 build 16232.

Thank you.

谢谢amaccre.I尝试了Vivado tcl shell，但是启动gui发生错误。（Windows build 16251）现在我返回Windows build 16232，所以Vivado可以启动。谢谢。



以下为原文

Thank you amaccre.

I tried Vivado tcl shell, but start gui happend error.(Windows build 16251)

Now I return Windows build 16232, so Vivado can start.

Thank you.

我在2017.2中遇到了同样的问题
C：赛灵思 Vivado  2017.2  BIN> vivado
****** Vivado v2017.2（64位）**** SW Build 1909853 on Thu Jun 15 18:39:09 MDT 2017 **** IP Build 1909766 on Thu Jun 15 19:58:00 MDT
2017 **版权所有1986-2017 Xilinx，Inc。保留所有权利。
start_gui ## Java运行时环境检测到致命错误：## EXCEPTION_ACCESS_VIOLATION（0xc0000005），pc = 0x00007fff02b1df88，pid = 5740，tid = 0x0000000000000c34 ## JRE版本：Java（TM）SE运行时环境（8.0_112-b15
）（build 1.8.0_112-b15）#Java VM：Java HotSpot（TM）64位服务器VM（25.112-b15混合模式windows-amd64压缩oops）＃有问题的框架：#C [ucrtbase.dll + 0x1df88] ##
无法编写核心转储。
默认情况下，在客户端版本的Windows ##上未启用Minidumps。包含更多信息的错误报告文件保存为：＃C： Xilinx  Vivado  2017.2  bin  hs_err_pid5740.log ##如果您要提交错误报告
，请访问：＃http://bugreport.java.com/bugreport/crash.jsp#崩溃发生在Java虚拟机外部的本机代码中。＃查看有问题的框架，了解在哪里报告错误。
我正在使用build 16273，但是我无法回滚到16232.这些类型的错误似乎在历史上存在。
此外，2016.4似乎确实有效。
对此有什么实际的解决方案？



以下为原文

I get the same issue with 2017.2
 
C:XilinxVivado2017.2bin>vivado
****** Vivado v2017.2 (64-bit)
**** SW Build 1909853 on Thu Jun 15 18:39:09 MDT 2017
**** IP Build 1909766 on Thu Jun 15 19:58:00 MDT 2017
** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.
start_gui
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fff02b1df88, pid=5740, tid=0x0000000000000c34
#
# JRE version: Java(TM) SE Runtime Environment (8.0_112-b15) (build 1.8.0_112-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.112-b15 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [ucrtbase.dll+0x1df88]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:XilinxVivado2017.2binhs_err_pid5740.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
 
I am using build 16273, however I can't roll back to 16232.  These type of errors seem to exist historically.  Also, 2016.4 does seem to work.  What would be an actual solution for this?

我也是，希望尽快解决。
****** Vivado v2017.2.1（64位）**** SW Build 1957588 on 8月9日16:32:24 MDT 2017 **** IP Build 1948039 on Wed Aug 9 18:19:28 MDT
2017 **版权所有1986-2017 Xilinx，Inc。保留所有权利。
Vivado％start_gui ## Java运行时环境检测到致命错误：## EXCEPTION_ACCESS_VIOLATION（0xc0000005），pc = 0x00007ffc01c4ddd8，pid = 11880，tid = 0x00000000000018ac ## JRE版本：Java（TM）SE运行时环境（8.0_112）
-b15）（build 1.8.0_112-b15）#Java VM：Java HotSpot（TM）64位服务器VM（25.112-b15混合模式windows-amd64压缩oops）＃有问题的框架：#C [ucrtbase.dll + 0x1ddd8]
##无法编写核心转储。
默认情况下，在客户端版本的Windows ##上未启用Minidumps。包含更多信息的错误报告文件保存为：#C： Users  abc  AppData  Roaming  Xilinx  Vivado  hs_err_pid11880.log ##如果您愿意
提交错误报告，请访问：＃http://bugreport.java.com/bugreport/crash.jsp#崩溃发生在Java虚拟机外部的本机代码中。＃查看有问题的框架，了解在哪里报告错误。＃



以下为原文

me too, Hope to solve as soon as possible.
 
****** Vivado v2017.2.1 (64-bit)
**** SW Build 1957588 on Wed Aug 9 16:32:24 MDT 2017
**** IP Build 1948039 on Wed Aug 9 18:19:28 MDT 2017
** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.
Vivado% start_gui
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffc01c4ddd8, pid=11880, tid=0x00000000000018ac
#
# JRE version: Java(TM) SE Runtime Environment (8.0_112-b15) (build 1.8.0_112-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.112-b15 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [ucrtbase.dll+0x1ddd8]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:UsersabcAppDataRoamingXilinxVivadohs_err_pid11880.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

当Windows 10更新到Build 16278.rs3_release.170825-1441时
运行start_gui后会弹出一个错误对话框。
运行时错误消息是：R6025 -pure虚函数调用



以下为原文

When the Windows 10 update to Build 16278.rs3_release.170825-1441
After running start_gui will be extra pop up an error dialog. The Runtime Error message is: R6025 -pure virtual function call
 

我有同样的问题......这个问题的答案呢？



以下为原文

I have the same issue... Any answer to this issue yet?

嗨，
更新Windows 10 Fall Creators Edition（1709）后，我遇到了同样的问题。
Vivado 2017.1和Vivado 2017.3.1都未能启动。
这个AR解决了我的问题：
https://www.xilinx.com/support/answers/69908.html
最好的祝福
简安德斯



以下为原文

Hi,
 
I had the same issue following an update to Windows 10 Fall Creators Edition (1709).  Both Vivado 2017.1 and Vivado 2017.3.1 failed to start.  This AR solved the problem for me:
 
 https://www.xilinx.com/support/answers/69908.html
 
Best regards
 
Jan Anders

你好，
这对我也有用



以下为原文

Hello,
This worked for me aswell

我相信我遇到了AR＃69908，但我使用的是Vivado Lab而且没有vivado.exe。
我有一个vivado_lab.exe和vvgl.exe，并为另一个重命名不起作用。
我用2017.1和2017.3尝试了这个。



以下为原文

I believe I am running into AR#69908 but I am using Vivado Lab and there is no vivado.exe.
I have a vivado_lab.exe and vvgl.exe and renaming one for the other does not work.
I have tried this with 2017.1 and 2017.3.