Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
9 years ago

java crash when opening Qsys on windows 10

Hello there,

Im fairly new to quartus and im having an issue with Qsys. When i try to open Qsys from quartus, im getting a "java (tm) platform se binary has stopped working". Note that i have Quartus 16.1 with update 2 installed on a windows 10 system. Could this be an issue with compatibility with windows? I have also tried to run the Qsys in windows 7 compatible mode and it still did not work. Also, i saw on a old post that it might be because of any current JRE installed in the computer, but i dont seem to have any java related software installed on my computer besides quartus itself.

Anyone might have a clue on the issue?

Thanks

Renato

17 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    I have the same issue. I upgraded from 16.0 to 16.1.2 yesterday (2/7/17) and encountered the problem. De-installed separate Java installation and 16.1.2 and now 16.0 won't run either. De-installed 16.0 and clean installed 16.1.2. No joy. Now I'm dead in the water. If I come across a solution, I'll post to this thread.

    Ken
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    I will open a ticket with altera today after work to see if they can figure out something

    thanks for the replies.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    Unless Altera has seen this before and has a solution, I think we're in for a battle. For starters, I don't think many users that the issue (a guess from Google searches). Next, I don't think it has anything to do with the basic file sets in question:

    C:\altera\<ver>\quartus\sopc_builder\bin for the "qsys-edit.exe" executable, and,

    C:\altera\<ver>\quartus\bin64\jre64 for the Java SE Runtime.

    I have performed the following:

    1) Compared the jre64 files from a 16.0 installation to a 15.1 installation on another computer and they verify byte-for-byte.

    2) Copied the sopc_builder files from the 16.0 installation to a working 15.1 installation and it works fine.

    3) Run 16.0 from a new user environment (logged into the workstation as someone else) and it fails, so we should be able to eliminate C:\Users\<username>\* files as culprits.

    4) Went through the C:\ProgramData folder and removed anything suspicious.

    5) Run CCleaner on the registry to clean any dangling links and also removed questionable QSys and Java references using RegEdit.

    6) Deinstalled/reinstalled 16.0 between different types of cleanings. It still always crashes Java on one machine and runs on the other.

    Please let me know if you've learned anything.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    Hi Renato,

    This morning, I've temporarily replaced the JRE that Altera uses (1.8.0_05-b13) with the current one you can get from Oracle (1.8.0_121-b13) with no difference. I've also tried to connect JProfiler to the JVM in the short interval before it crashes without success.

    Can you please share the number of your Altera Service Request? I'd like to open another SR and reference yours, at the very least to indicate to them that more than one of us has an issue. Also, if you want to contact me directly, kcrocker<at symbol>kcconsulting<period>com works for me.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    hi there,

    sure no problem. here is the request number "11292306". Thanks for the research. This will help push altera to fix the bug.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    Hi guys!

    I've been struggling with this all day, and just now found a solution. I finally narrowed it down to one thing changing since Qsys last started, which was me updating my nvidia drivers. I then found a recently updated log file in C:\ProgramData\NVIDIA Corporation\nvstapisvr which apparently is related to nvidia 3D Vision, something I didn't even know I had installed. After removing it, Qsys is working again. So, if you're also running nvidia cards, check if the 3D Vision drivers are installed.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    Nice, i will give a try.

    So to debug this issue, you check the state of your pc when the Qsys was working and the state of the pc when it was crashing and the difference was the nvidia 3d vision drivers? this was a nice debugging you did :D

    Thanks for all the research you guys did :)
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    Brilliant! NVidia 3D Vision drivers were installed on my machine on Jan 24th. I must not have started QSys since then. When I upgraded Quartus a few days ago, it forced me to upgrade IP associated with the project, which led to the issue discovery. Removed the drivers (3D Vision Controller driver and 3D Vision driver) and QSys started up!!! I'm thrilled and overjoyed! Thank you 'storste'!!