Forum Discussion

Mitsuo3314's avatar
Mitsuo3314
Icon for New Contributor rankNew Contributor
4 years ago

Fatal Error: Access Violation at 0X00007FFCA1DCA69C

Hello,

When I installed and used Quartus Prime ver18.1, it occurred in "Analysis & Synthesis".
Please tell me how to resolve this error.

I am using 18.1 to match the environment with the existing project.

The contents of the error file are as follows.

Problem Details
Error:

*** Fatal Error: Access Violation at 0X00007FFCA1DCA69C

Module: quartus_map.exe

Stack Trace:

0x1a69b: HDB_SOURCE_FILE::get_library + 0x3 (DB_HDB)

0x6744c: SGN_QIC_UTILS::create_new_hierarchy_info + 0xe8c (synth_sgn)

0xb75ae: SGN_EXTRACTOR::recursive_extraction + 0x28e (synth_sgn)

0xb6e6f: SGN_EXTRACTOR::recurse_into_newly_extracted_netlist + 0x36f (synth_sgn)

0xb757b: SGN_EXTRACTOR::recursive_extraction + 0x25b (synth_sgn)

0xb6e6f: SGN_EXTRACTOR::recurse_into_newly_extracted_netlist + 0x36f (synth_sgn)

0xb757b: SGN_EXTRACTOR::recursive_extraction + 0x25b (synth_sgn)

0xb08c3: SGN_EXTRACTOR::extract + 0x1d3 (synth_sgn)

0x1324e: sgn_qic_full + 0x19e (synth_sgn)

0x4351: qsyn_execute_sgn + 0x131 (quartus_map)

0x13f9c: QSYN_FRAMEWORK::execute_core + 0x12c (quartus_map)

0x13aa6: QSYN_FRAMEWORK::execute + 0x496 (quartus_map)

0x112bc: qexe_do_normal + 0x1ec (comp_qexe)

0x16142: qexe_run + 0x432 (comp_qexe)

0x16e51: qexe_standard_main + 0xc1 (comp_qexe)

0x1b08b: qsyn_main + 0x51b (quartus_map)

0x12e98: msg_main_thread + 0x18 (CCL_MSG)

0x1467e: msg_thread_wrapper + 0x6e (CCL_MSG)

0x16660: mem_thread_wrapper + 0x70 (ccl_mem)

0x12761: msg_exe_main + 0xa1 (CCL_MSG)

0x29872: __tmainCRTStartup + 0x10e (quartus_map)

0x17033: BaseThreadInitThunk + 0x13 (KERNEL32)

0x52650: RtlUserThreadStart + 0x20 (ntdll)

End-trace



Executable: quartus_map
Comment:
None

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

Quartus Prime Information
Address bits: 64

Best Regards,

4 Replies

  • SyafieqS's avatar
    SyafieqS
    Icon for Super Contributor rankSuper Contributor
    4 years ago

    Hi Mitsuo,


    Can you attach a small test design here .qar for me to replicate the issue.

    This might be a valid bug.


  • Mitsuo3314's avatar
    Mitsuo3314
    Icon for New Contributor rankNew Contributor
    4 years ago

    Hi SyafieqS.

    Thank you for your reply.

    I attached .qar file.

    This qar file is similar to the hdmi sample.

    Add one piece of information.
    I moved it on another PC, and this Fatal did not occur.
    Next, I moved it to another folder and checked it, and this Fatal did not occur.


    Therefore, it is considered that the problem depends on the corresponding folder,

    and I think this problem is solved.

    Best Regards,

    Mitsuo

  • SyafieqS's avatar
    SyafieqS
    Icon for Super Contributor rankSuper Contributor
    4 years ago

    Mitsuo,


    Thank you for the file..

    Let me know if the workaround not feasible for you as by changing the folder or machine as you mentioned.




  • SyafieqS's avatar
    SyafieqS
    Icon for Super Contributor rankSuper Contributor
    4 years ago

    I’m glad that your question has been addressed, I now transition this thread to community support. If you have a new question, feel free to open a new thread to get the support from Intel experts. Otherwise, the community users will continue to help you on this thread. Thank you.


    p/s: If any answer from community or Intel support are helpful, please feel free to mark as solution and give Kudos.