Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
21401 Discussions

The Quartus Prime software quit unexpectedly!

allen18
New Contributor II
440 Views

  I frequently encounter this error during project compilation, which typically occurs during the filter process and happens after several hours of compiling. It severely wastes time and reduces work efficiency. Has anyone experienced the same issue?

 

"""

Problem Details
Error:

*** Fatal Error: Access Violation at 00007FFAB99D4EF0
Module: quartus_fit.exe
Stack Trace:
Quartus 0x104eef: RTM_COMMON_TIMING_ANALYSIS::EDGE_REQS::set_second_req + 0xf (tsm_rtm)
Quartus 0x10a2b0: std::vector<std::pair<QTL_SMALL_VECTOR<unsigned int,std::allocator<unsigned int> >,RTM_COMMON_TIMING_ANALYSIS::EDGE_REQS>,std::allocator<std::pair<QTL_SMALL_VECTOR<unsigned int,std::allocator<unsigned int> >,RTM_COMMON_TIMING_ANALYSIS::EDGE_REQS> > >::vector<std::pair<QTL_SMALL_VECTOR<unsigned int,std::allocator<unsigned int> >,RTM_COMMON_TIMING_ANALYSIS::EDGE_REQS>,std::allocator<std::pair<QTL_SMALL_VECTOR<unsigned int,std::allocator<unsigned int> >,RTM_COMMON_TIMING_ANALYSIS::EDGE_REQS> > > + 0xd0 (tsm_rtm)
Quartus 0x10ea55: RTM_COMMON_TIMING_ANALYSIS_ITERATOR::generate_tdb_clock_data_per_edge_cache + 0x115 (tsm_rtm)
Quartus 0x1814a4: RTM_RACAD_TIMING_ANALYSIS::perform_racad_timing_analysis + 0x94 (tsm_rtm)
Quartus 0x1733e5: `anonymous namespace'::MIN_REG_FINDER<0>::pre_traversal + 0x6005 (tsm_rtm)
Quartus 0x16b8fd: `anonymous namespace'::IMPLIED_RESTRICTION_FINDER::load_queue + 0x206d (tsm_rtm)
Quartus 0x71c3c: `anonymous namespace'::register_nvd_to_qhd + 0x7dac (tsm_rtm)
Quartus 0x473bc: (TSM_TDC)
Quartus 0x1114b: (TSM_TDC)
Quartus 0x30e09: (TSM_FTI)
Quartus 0x33e85: (TSM_FTI)
Quartus 0x525cf7: (fitter_vpr20kmain)
Quartus 0x501102: (fitter_vpr20kmain)
Quartus 0x5031fb: (fitter_vpr20kmain)
Quartus 0x50371a: (fitter_vpr20kmain)
Quartus 0x3e539a: (fitter_vpr20kmain)
Quartus 0x37ef44: (fitter_vpr20kmain)
Quartus 0x2bf762: (fitter_vpr20kmain)
Quartus 0x2ba52f: (fitter_vpr20kmain)
Quartus 0x320b51: (fitter_vpr20kmain)
Quartus 0x224ec9: (fitter_vpr20kmain)
Quartus 0x2246b6: (fitter_vpr20kmain)
Quartus 0x223bec: (fitter_vpr20kmain)
Quartus 0x49216a: (fitter_vpr20kmain)
Quartus 0x105204: (fitter_fdrgn)
Quartus 0x100ded: (fitter_fdrgn)
Quartus 0x26a2e: (comp_fit2)
Quartus 0x16442: (tcl86)
Quartus 0x532a: (comp_fit2)
Quartus 0x16442: (tcl86)
Quartus 0x17c4d: (tcl86)
Quartus 0xa6a8b: (tcl86)
Quartus 0xa5136: TclFSCwdIsNative + 0xffffffffffffff56 (tcl86)
Quartus 0x22200: qexe_do_tcl + 0x1cd0 (comp_qexe)
Quartus 0x20df2: qexe_do_tcl + 0x8c2 (comp_qexe)
Quartus 0x29f51: qexe_run + 0xe81 (comp_qexe)
Quartus 0x2973f: <lambda_f9491598d3e86dee3a670fcdbeed20e4>::operator() + 0x319f (comp_qcu)
Quartus 0x391de: qcu_process_implied_register_optimization_assignments + 0x151e (comp_qcu)
Quartus 0x296c9: qexe_run + 0x5f9 (comp_qexe)
Quartus 0x2aa0a: qexe_run + 0x193a (comp_qexe)
Quartus 0xbba2: <lambda_9f91090ffa5a337905f0d5d738529902>::operator()<> + 0x8c52 (quartus_fit)
Quartus 0x27b68: std::`dynamic atexit destructor for '_Fac_tidy_reg'' + 0x23e3c (CCL_MSG)
Quartus 0x28b22: std::`dynamic atexit destructor for '_Fac_tidy_reg'' + 0x24df6 (CCL_MSG)
Quartus 0x2aae3: `anonymous namespace'::mem_tcmalloc_tracker_new_hook + 0x153 (ccl_mem)
Quartus 0x25088: std::`dynamic atexit destructor for '_Fac_tidy_reg'' + 0x2135c (CCL_MSG)
Quartus 0xcd2f: __scrt_common_main_seh + 0x10b (quartus_fit)
Quartus 0x17c23: BaseThreadInitThunk + 0x13 (KERNEL32)
Quartus 0x6d720: RtlUserThreadStart + 0x20 (ntdll)

End-trace


Executable: quartus
Comment:
None

System Information
Platform: windows64
OS name: Windows 10
OS version: 10.0

Quartus Prime Information
Address bits: 64
Version: 22.3.0
Build: 104
Edition: Pro Edition

"""

allen18_0-1742351222659.png

 

Labels (1)
0 Kudos
6 Replies
RichardTanSY_Intel
382 Views

For fatal error, this is most likely caused by the user system.


There are a few things that you can troubleshoot:

1. Ensure that you are using the latest version of Quartus 24.3 Pro as there are a few bug fixed. 

2. Try restarting Quartus and your computer. This can help clear any temporary issues that may be causing the error.

3. Check your system resources, including memory, CPU usage, and disk space. Make sure you have enough available resources to run Quartus.

4. Try disabling any antivirus or firewall software temporarily, as they may be interfering with Quartus.

5. Run Quartus as administrator. 

6. Install currprocess https://www.nirsoft.net/utils/cprocess.html and disable all the software running behind in the background. 

7. Check your OS history update, e.g. to check if the issue happen after some specific Window update. 


If the issue still persists, kindly share your design by archiving the project (Project > Archive Project) so I can duplicate the issue.


Regards,

Richard Tan


0 Kudos
RichardTanSY_Intel
341 Views

Dropping a note to ask if my last reply was helpful to you.

Do you able to resolve the issue? 


Regards,

Richard Tan


0 Kudos
allen18
New Contributor II
330 Views

  This issue tends to occur probabilistically during the filter process when CPU and memory usage becomes excessively high. I attempted to mitigate it by limiting the number of CPU cores allocated for compilation, but the problem still recurred several times afterward. I have not yet upgraded to the latest Quartus version because a significant number of IP cores would require simultaneous upgrades, which complicates the process.

  

allen18_0-1742787006801.png

 

0 Kudos
RichardTanSY_Intel
328 Views

Could you share your design by archiving the project (Project > Archive Project) so that I can test it from myself?


Regards,

Richard Tan


0 Kudos
allen18
New Contributor II
298 Views

  I cannot upload the QAR file as an attachment because the file is encrypted on my computer. I suspect this issue might relate to the computer's performance, as my current 8-core processor consistently reaches 100% CPU usage during the filter phase. I cannot confirm whether the latest version of Quartus has the same problem yet and will continue monitoring. Perhaps this issue can be closed for now‌.

0 Kudos
RichardTanSY_Intel
295 Views

Noted @allen18,  I will transitioning this thread to community support.

At the same time, you can try isolating a specific part of the design to determine if a particular section is causing the issue.


Regards,

Richard Tan



0 Kudos
Reply