Forum Discussion

ingemilo's avatar
ingemilo
Icon for New Contributor rankNew Contributor
28 days ago

Quartus Prime Pro 25.1 Crashes Randomly

I’ve been having trouble compiling projects with Quartus Prime Pro version 25.1 for several days. In an unpredictable manner, Quartus stops the compilation or freezes at a certain point—it can happen at the beginning, during synthesis, when the fitter starts, or during timing analysis. I’ve carried out extensive testing. I’ve tried reinstalling the program several times, and it’s true that right after installation, several successful compilations can be achieved; however, after around the fifth one, it usually starts failing and won’t compile anymore. The message window during compilation doesn’t provide any details about the error. I’ve also tried installing the newest version, but it behaves similarly. After a few attempts, I noticed that at the exact moment of the crash, the program generates a file called serv_req_info.txt, which I’ve attached. I’ve formatted my computer and updated to the latest version of Windows, and even replaced the internal SSD, but nothing has solved the issue. I’d appreciate any help in finding the cause of the problem.

Compilation
general

10 Replies

  • KennyT_altera's avatar
    KennyT_altera
    Icon for Super Contributor rankSuper Contributor
    20 days ago

    Thanks for the update and the detailed troubleshooting steps you’ve shared. It’s good to hear that reinstalling Quartus and reformatting your system seem to have resolved the issue for now.

    Regarding your question about why a similar problem affected both newer and older versions (like Quartus 13.1): Sometimes, underlying system changes (such as Windows updates, driver changes, or even new security software) can introduce instability in legacy applications, especially ones that haven’t been updated in years. Since Cyclone III devices are only supported by older Quartus versions, you may encounter increasing compatibility issues with newer operating systems.

    If the problem returns, you might try:

    • Running Quartus 13.1 in compatibility mode for an older version of Windows.
    • Disabling any unnecessary background software or antivirus that could interfere with Quartus.
  • ingemilo's avatar
    ingemilo
    Icon for New Contributor rankNew Contributor
    28 days ago

    Hello cblixt, thank you for your response. I’ve tried installing the patch, and it seems to have solved the issue—at least the two compilations I ran after installing it completed successfully, and no text file was generated. However, I don’t understand the origin of the problem or how it’s possible that it also affects such an old version of Quartus as 13.1, which I use for some older FPGAs. When I try to compile a project for those, a similar error appears, and the program closes.

     

    • KennyT_altera's avatar
      KennyT_altera
      Icon for Super Contributor rankSuper Contributor
      25 days ago

      Can you attached the design? Also, what device that you were using? Can you use the latest release of the Quartus Std? If no, any reason?

      • ingemilo's avatar
        ingemilo
        Icon for New Contributor rankNew Contributor
        25 days ago

        Hello, the FPGA I’m using is no longer supported (I assume) in the newer versions of Quartus—it’s an older Cyclone III. The design itself isn’t problematic, since it’s the same one I’ve been compiling for a long time, with only minor changes in each build. Moreover, the error occurs when opening the program, it doesn’t even need to reach the compilation stage. In any case, it seems that reinstalling the software and the previous system reformat have solved the issue.

    • cblixt's avatar
      cblixt
      Icon for New Contributor rankNew Contributor
      28 days ago

      This is not the same problem. That problem affected only Quartus Prime Pro versions 23.3 - 25.3.1, that's why there are only patches available for those versions.

      If you have another problem happening in Quartus 13.1 I don't expect that to have suddenly appeared on Jan 10 like the above mentioned problem did, and I would recommend posting a new question for it with an adjusted title.