What does this mean??

[DBay]

Problem Details

Error:

*** Fatal Error: Access Violation at 0X000007FEB5A007F5

Module: quartus_cdb.exe

Stack Trace:

0x307f4: HDB_SECTIONS_COL::find_sections + 0x14 (DB_HDB)

0x19f57: HDB_SECTION::find_section + 0x27 (DB_HDB)

0x38d69: HDB_NAME_MGR::open_cap_inst + 0x85 (DB_HDB)

0x3b57f: HDB_NAMESPACE::close_pdb_and_clear_cache + 0xc3 (DB_HDB)

0xa2b2d: QTK_QIC_EXPORT_IMPL::close_cap + 0x4d (db_qtk)

0xa3f47: QTK_QIC_EXPORT_IMPL::work + 0x177 (db_qtk)

0x1fb98: qatm_qic_export_project + 0x168 (quartus_cdb)

0x160a5: QATM_FRAMEWORK::execute + 0xff5 (quartus_cdb)

0x112bc: qexe_do_normal + 0x1ec (comp_qexe)

0x16142: qexe_run + 0x432 (comp_qexe)

0x16e51: qexe_standard_main + 0xc1 (comp_qexe)

0x1f352: qatm_main + 0x92 (quartus_cdb)

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)

0x447f2: __tmainCRTStartup + 0x10e (quartus_cdb)

0x159cc: BaseThreadInitThunk + 0xc (kernel32)

0x5385c: RtlUserThreadStart + 0x1c (ntdll)

End-trace

Executable: quartus_cdb

Comment:

None

System Information

Platform: windows64

OS name: Windows 7

OS version: 6.1

Quartus Prime Information

Address bits: 64

Version: 18.0.0

Build: 614

Edition: Standard Edition

[DBay]

Besides the meaning that the software is BROKEN, how do I make it not CRASH??

[Tricky]

it means quartus has crashed.

The usual first attempt to fix would be to delete the /db and /incremental_db folders.

If that doesnt help, then you will have to raise a support ticket to try and discover why it is crashing.

[DBay]

Yes, that would be nice, but since I'm not a $100M+ customer, they don't do support tickets anymore.

Already done the obvious., now I'm back to the hunt and peck method of design.... Add a feature one at a time until it crashes. Been doing this for months for other parts of the design. Now, it crashes when I add the first feature. The good news is I'm down to the last 30% of conversion.

This is an old multi chip design from 13.1 that has already been debugged and I'm just updating it to a new board, single chip. Funny how it is easier and quicker for me to port this whole design to Xilinx than it is to move up a few families in Altera. Their software didn't crash. I just had to overcome well enunciated errors.