Internal error during fitter for Quartus Prime 21.1

[veriguy]

I am working on an experimental design using ethernet IPs for Agilex E-tiles. During fitter, the Quartus keeps running into Internal Error. Can you please help work around it. Below is the Internal Error shown by Quartus.

Problem Details
Error:
Internal Error: Sub-system: FRPT, File: /quartus/fitter/frpt/frpt_fitter_report_utils.cpp, Line: 202
Was not able to get report file for stage plan
Stack Trace:
Quartus 0x3750: frpt_create_split_fit_message_report + 0x2630 (fitter_frpt)
Quartus 0x1339a: fit2_fit_plan + 0x1da (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 0x151f6: qexe_evaluate_tcl_script + 0x4e6 (comp_qexe)
Quartus 0x140eb: qexe_do_tcl + 0x46b (comp_qexe)
Quartus 0x1a67e: qexe_run_tcl_option + 0x5ee (comp_qexe)
Quartus 0x14b81: QCU::DETAIL::intialise_qhd_and_run_qexe + 0xa1 (comp_qcu)
Quartus 0x214a2: qcu_run_tcl_option + 0x2f2 (comp_qcu)
Quartus 0x19f6b: qexe_run + 0x3eb (comp_qexe)
Quartus 0x1b0ba: qexe_standard_main + 0x26a (comp_qexe)
Quartus 0x1fe2: qfit2_main + 0x82 (quartus_fit)
Quartus 0x194b8: msg_main_thread + 0x18 (CCL_MSG)
Quartus 0x19b81: msg_thread_wrapper + 0x71 (CCL_MSG)
Quartus 0x22dc0: mem_thread_wrapper + 0x70 (ccl_mem)
Quartus 0x1774d: msg_exe_main + 0x20d (CCL_MSG)
Quartus 0x2bd8: __scrt_common_main_seh + 0x11c (quartus_fit)
Quartus 0x17033: BaseThreadInitThunk + 0x13 (KERNEL32)
Quartus 0x52650: 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: 21.1.0
Build: 169
Edition: Pro Edition

[Kenny_Tan]

Hi,

Can you attached the design.qar for us to investigate? Let us know if you want to attach the design.qar privately, we can arrange for you.

Thanks

[veriguy]

I had to reboot my computer after which I could not reproduce the crash. So this can be considered closed.

[Kenny_Tan]

we shall close this thread. If you still need further assistance, you are welcome to post a response within 15days or open a new thread, some one will be right with you. After 15 days, this thread will be transitioned to community support. The community users will be able to help you with your follow-up questions.