cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Visitor
Visitor
633 Views
Registered: ‎10-09-2017

EXCEPTION_ACCESS_VIOLATION in Vivado 2017.2

Jump to solution

Updated OS today on a window 7 to window 10 (64bit)

When Window 7 , Vivado 2017.2 is normal working

but, After update window 10 , Vivado 2017.2 is abnormal working.

I attach the file ( *.log / *.dmp .... ) 

Check the File Please

Thanks.

 

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Community Manager
Community Manager
566 Views
Registered: ‎05-08-2017

Re: EXCEPTION_ACCESS_VIOLATION in Vivado 2017.2

Jump to solution

Hi @skandra,

Is this failing during a certain job run or is this upon launching vivado in general?

A quick step to try is going into the vivado install and navigating to Xilinx\Vivado\2017.2\tps\win64 and running the xvcredist.exe and select repair. This would resolve a distributable conflict / error.

Ultimately you can also try re-installing Vivado to the new OS.

Thank you,
Devin

View solution in original post

3 Replies
Highlighted
Community Manager
Community Manager
567 Views
Registered: ‎05-08-2017

Re: EXCEPTION_ACCESS_VIOLATION in Vivado 2017.2

Jump to solution

Hi @skandra,

Is this failing during a certain job run or is this upon launching vivado in general?

A quick step to try is going into the vivado install and navigating to Xilinx\Vivado\2017.2\tps\win64 and running the xvcredist.exe and select repair. This would resolve a distributable conflict / error.

Ultimately you can also try re-installing Vivado to the new OS.

Thank you,
Devin

View solution in original post

Highlighted
Visitor
Visitor
555 Views
Registered: ‎10-09-2017

Re: EXCEPTION_ACCESS_VIOLATION in Vivado 2017.2

Jump to solution

Thanks for the reply.
Not resolved by the method offered.
So, I reinstalled the OS and solved this problem.

 

 

0 Kudos
Highlighted
Community Manager
Community Manager
538 Views
Registered: ‎05-08-2017

Re: EXCEPTION_ACCESS_VIOLATION in Vivado 2017.2

Jump to solution

Hi @skandra,

That is good to hear. The most probable cause was due to the Microsoft Visual C++ Distributable compatibility issue. With the re-install of the OS the 2015 x64 and x86 bit versions most likely needed to be picked back up by Vivado.

 

Thank you,
Devin

0 Kudos