Quartus Prime Pro 25.1 fatal error during fitter: Windows "Efficiency mode" required

[dncmrc1]

Quartus 25.1 usually crashes during fitter, with a number of different crash reports. Here below are two examples:

Problem Details
Error:

*** Fatal Error: Access Violation at 000000BC2DC1E830
Module: quartus_fit.exe
Stack Trace:
Other 0xbc2dc1e82f:
Other 0xbc2dc1e6af:
Other 0x1bf404d29ff:

End-trace

Executable: quartus
Comment:
None

System Information
Platform: windows64
OS name: Windows 11
OS version: 10.0.22631

Quartus Prime Information
Address bits: 64
Version: 25.1.0
Build: 129
Edition: Pro Edition

-------------------------------

Problem Details
Error:

*** Fatal Error:
Module: quartus_fit.exe
Stack Trace:
Quartus 0x5fb4b: RaiseException + 0x6b (KERNELBASE)
Quartus 0x26ad: __ExceptionPtrRethrow + 0x15d (MSVCP140)
Quartus 0x19cfe: tbb::detail::r1::current_context + 0x277e (tbb12)
Quartus 0x19d78: tbb::detail::r1::current_context + 0x27f8 (tbb12)
Quartus 0x17695: tbb::detail::r1::current_context + 0x115 (tbb12)
Quartus 0xa2567: FDRGN_EXPERT::run_place_flow + 0xd17 (fitter_fdrgn)
Quartus 0xa0018: FDRGN_EXPERT::run_place + 0x188 (fitter_fdrgn)
Quartus 0x95135: FDRGN_EXPERT::place + 0x195 (fitter_fdrgn)
Quartus 0x2c120: fit2_fit_place_auto + 0xc0 (comp_fit2)
Quartus 0x16442: TclNRRunCallbacks + 0x62 (tcl86)
Quartus 0x4e6b: fit2_fit_place + 0x33b (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 0x230ac: qexe_evaluate_tcl_script + 0x66c (comp_qexe)
Quartus 0x21be9: qexe_do_tcl + 0x8f9 (comp_qexe)
Quartus 0x2a1ad: qexe_run_tcl_option + 0x6cd (comp_qexe)
Quartus 0x4119f: qcu_run_tcl_option + 0x6ef (comp_qcu)
Quartus 0x29969: qexe_run + 0x629 (comp_qexe)
Quartus 0x2abd6: qexe_standard_main + 0x266 (comp_qexe)
Quartus 0xbd32: qfit2_main + 0x82 (quartus_fit)
Quartus 0x28708: msg_main_thread + 0x18 (ccl_msg)
Quartus 0x29912: msg_thread_wrapper + 0x82 (ccl_msg)
Quartus 0x2b063: mem_thread_wrapper + 0x73 (ccl_mem)
Quartus 0x265df: msg_exe_main + 0x17f (ccl_msg)
Quartus 0xcfab: __scrt_common_main_seh + 0x10b (quartus_fit)
Quartus 0x1259c: BaseThreadInitThunk + 0x1c (KERNEL32)
Quartus 0x5af37: RtlUserThreadStart + 0x27 (ntdll)

End-trace

Executable: quartus
Comment:
None

System Information
Platform: windows64
OS name: Windows 11
OS version: 10.0.22631

Quartus Prime Information
Address bits: 64
Version: 25.1.0
Build: 129
Edition: Pro Edition

-----------------------------

this happens with every design and with Arria10, Stratix 10 and also Agilex 7.

The only way to avoid these Quartus crashes is to run the fitter in Windows "Efficiency Mode", but that makes fitting time more or less double.

Any hints?

[sstrell]

Have you tried reinstalling yet?  What are you computer specs?

[RichardTanSY_Altera]

There are a few things that you can troubleshoot:

1. Ensure that you are using the latest version of Quartus 25.1 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. 

8. Uninstall the software. Download and auto install the Quartus software using the new Quartus installer. Do run the installer with Administrator privileges. 

9. If possible, try to run the same Quartus project with a machine with better spec. 

Regards,

Richard

[RichardTanSY_Altera]

Any update on this? Do you able to resolve the issue?

Regards,

Richard Tan

[RichardTanSY_Altera]

We noticed that we haven't received a response from you regarding the latest previous question/reply/answer, and will now transitioning your inquiry to our community support. We apologize for any inconvenience this may cause and we appreciate your understanding.

If you have any further questions or concerns, please don't hesitate to reach out. Please login to https://supporttickets.intel.com/s/?language=en_US, view details of the desire request, and post a feed/response within the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support. The community users will be able to help you on your follow-up questions.

The community users will be able to help you on your follow-up questions.

Thank you for reaching out to us!

Best Regards,

Richard Tan

[dncmrc1]

Sorry, I didn't receive any notification about your comments to my issue. I noticed them only now.

I will ty with your action and let you know.

Thanks,

Marco