We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 53502

Vivado - When I open Vivado on a Windows machine with Korean OS, a fatal error occurs in the JRE


When I attempt to open Vivado Design Suite, it fails and I receive the following error log:

A fatal error has been detected by the Java Runtime Environment

EXCEPTIONACCESSVIOLATION0xc0000005 at pc0x77a2f963 pid4284 tid4896

JRE version 7002b13
Java VM Java HotSpotTM Server VM220b10 mixed mode windowsx86
Problematic frame

Failed to write core dump Minidumps are not enabled by default on client versions of Windows

If you would like to submit a bug report please visit
The crash happened outside the Java Virtual Machine in native code
See problematic frame for where to report the bug

Current thread0x32008800 JavaThreadCheck for Available Updatesthreadinnative id4896 stack0x32e200000x33120000
siginfo ExceptionCode0xc0000005 writing address 0x00000014
EAX0x00000000 EBX0xfffffffc ECX0x00000000 EDX0x00000004
ESP0x3311f2a8 EBP0x3311f2f8 ESI0x71b07428 EDI0x71b0742c
EIP0x77a2f963 EFLAGS0x00010213
Top of Stacksp0x3311f2a8
0x3311f2a8 71b07428 71b0742c 2a7ed801 3311f364
0x3311f2b8 77a1d46d 01d20aff fffffffe 77a52136
0x3311f2c8 77a51fd1 2a7ed838 0000000b 0000000a
0x3311f2d8 00000000 000004cf 00000000 00000000
0x3311f2e8 00000000 00000000 8383a000 00000004
0x3311f2f8 3311f320 77a2f872 00000000 00000000
0x3311f308 2a7ed801 00000364 2a7ed838 00000004
0x3311f318 00000000 00000001 3311f35c 00e7ebc2
0x77a2f943 c2 8b d8 8b c1 f0 0f b1 1f 3b c1 0f 85 bf e0 ff
0x77a2f953 ff 33 c0 89 45 0c 89 45 08 8b 06 83 f8 ff 74 03
0x77a2f963 ff 40 14 8b 5d f4 8b 7d f0 80 3d 82 03 fe 7f 00
0x77a2f973 0f 85 52 f9 04 00 8b 45 fc 57 6a 00 83 f8 ff 0f
Register to memory mapping
EAX0x00000000 is an unknown value
EBX0xfffffffc is an unknown value
ECX0x00000000 is an unknown value
EDX0x00000004 is an unknown value
ESP0x3311f2a8 is pointing into the stack for thread 0x32008800
EBP0x3311f2f8 is pointing into the stack for thread 0x32008800
ESI0x71b07428 is an unknown value
EDI0x71b0742c is an unknown value
Stack0x32e200000x33120000 sp0x3311f2a8 free space3068k
Native framesJcompiled Java code jinterpreted VvVM code Cnative code
Cntdlldll0x2f963 iswdigit0x2a2
Cntdlldll0x2f872 iswdigit0x1b1
Clibcurldll0x1ebc2 curlgetdate0x2642
Java framesJcompiled Java code jinterpreted VvVM code
j uidataxnotifyxilinxnotifyHXNXilinxNotifyCheckUpdateJJI0
j uicFidbXV251
j uicFjaLDLjavalangObject4
j uifrmworkVrunV15
j javalangThreadrunV11
Java Threads current thread
0x32008800 JavaThreadCheck for Available Updatesthreadinnative id4896 stack0x32e200000x33120000
0x31a96c00 JavaThreadMonitor File Timestampthreadblocked id9584 stack0x31b400000x31e40000
0x302dac00 JavaThreadImage Fetcher 3 daemonthreadblocked id6104 stack0x30d400000x31040000
0x302dc400 JavaThreadImage Fetcher 2 daemonthreadblocked id8600 stack0x309400000x30c40000
0x302ddc00 JavaThreadImage Fetcher 1 daemonthreadblocked id8632 stack0x306400000x30940000
0x2f372800 JavaThreadImage Fetcher 0 daemonthreadblocked id9624 stack0x2f9900000x2fc90000
0x04573c00 JavaThreadProcess Messagesthreadblocked id9836 stack0x2ee600000x2f160000
0x04575000 JavaThreadAWTEventQueue1threadblocked id6896 stack0x2eb600000x2ee60000
0x04573000 JavaThreadThread3threadinnative id9588 stack0x031700000x04570000
0x2b3f7000 JavaThreadAWTEventQueue0threadblocked id8904 stack0x2e7600000x2ea60000
0x2c5c9000 JavaThreadAWTWindows daemonthreadinnative id7432 stack0x2cc500000x2cf50000


This issue has been seen where the computer has a corrupt or conflicting version of libcurl.dll in the C:\WINDOWS\System32 directory.

Non-system software applications should not be installing DLLs to the C:\WINDOWS\System32 directory.  

On the system that this issue was seen on, some users were not aware of what application had placed the libcurl.dll file in the system32 directory.

Deleting or renaming the libcurl.dll file in the C:\WINDOWS\System32 directory allows Vivado Design Suite to open and run correctly.

Xilinx recommends that the libcurl.dll in the C:\WINDOWS\System32 directory be renamed and then replaced with the version from the Vivado install.  

This will allow any application referencing the DLL to continue to work.

Linked Answer Records

Associated Answer Records

Answer Number Answer Title Version Found Version Resolved
57386 Vivado - "Error when launching vivado.bat: Launcher time out" N/A N/A
AR# 53502
Date Created 12/14/2012
Last Updated 05/12/2014
Status Active
Type General Article