The quartus prime software quit unexpectedly

[ShirleyZ]

Hi

I got Quartus prime Problem report during compilation - I got pop up message and then the Quartus stuck

The problem details are :

Problem Details
Error:
Internal Error: Sub-system: FDRGN, File: /quartus/fitter/fdrgn/fdrgn_expert.cpp, Line: 5351
Final postfit netlist check failed
Stack Trace:
Quartus 0x93ce8: FDRGN_EXPERT::check_and_report + 0x568 (fitter_fdrgn)
Quartus 0x20ea5: fit2_write_fitter_report + 0x1b5 (comp_fit2)
Quartus 0x16442: TclNRRunCallbacks + 0x62 (tcl86)
Quartus 0x17c4d: TclEvalEx + 0x9ed (tcl86)
Quartus 0xa6a8b: Tcl_FSEvalFileEx + 0x22b (tcl86)
Quartus 0xa5136: Tcl_EvalFile + 0x36 (tcl86)
Quartus 0x22260: qexe_evaluate_tcl_script + 0x640 (comp_qexe)
Quartus 0x20e0f: qexe_do_tcl + 0x8df (comp_qexe)
Quartus 0x29d91: qexe_run_tcl_option + 0x701 (comp_qexe)
Quartus 0x28d0f: QCU::DETAIL::intialise_qhd_and_run_qexe + 0x10f (comp_qcu)
Quartus 0x3804e: qcu_run_tcl_option + 0x76e (comp_qcu)
Quartus 0x2951c: qexe_run + 0x48c (comp_qexe)
Quartus 0x2a84a: qexe_standard_main + 0x26a (comp_qexe)
Quartus 0xbba2: qfit2_main + 0x82 (quartus_fit)
Quartus 0x1db28: msg_main_thread + 0x18 (CCL_MSG)
Quartus 0x1e312: msg_thread_wrapper + 0x82 (CCL_MSG)
Quartus 0x2a313: mem_thread_wrapper + 0x73 (ccl_mem)
Quartus 0x1b048: msg_exe_main + 0x178 (CCL_MSG)
Quartus 0xcd1f: __scrt_common_main_seh + 0x10b (quartus_fit)
Quartus 0x17613: BaseThreadInitThunk + 0x13 (KERNEL32)
Quartus 0x526f0: RtlUserThreadStart + 0x20 (ntdll)

End-trace

Executable: qpro
Comment:
None

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

Quartus Prime Information
Address bits: 64
Version: 22.1.0
Build: 174
Edition: Pro Edition

Do someone know how can I solve it ?

ShirleyZ

[ShengN_Intel]

Hi,

Check these two KDBs below:

https://www.intel.com/content/www/us/en/support/programmable/articles/000095629.html

https://www.intel.com/content/www/us/en/support/programmable/articles/000094100.html

Check the personal email sent to you as well about the workaround.

Can try to run the design in latest version (22.4 / 23.1) as well see whether the problem still exist?

Seems like the problem had been fixed in newer release based on internal engineering team.

Thanks,

Best Regards,

Sheng

p/s: If any answer from the community or Intel Support are helpful, please feel free to give best answer or rate 4/5 survey.

[ShengN_Intel]

Hi,

Any further update? Does the problem being resolved?

Thanks,

Best Regards,

Sheng