Forum Discussion

IESG2000's avatar
IESG2000
Icon for New Contributor rankNew Contributor
3 years ago

Internal fatal error when I try to compile and starting analys and synthesis

Hello.

I tried to compile simple programming in VHDL for comparison at inputs using logic gates. When the compilation is working, pops up a window to inform me about an internal error, it happens when I try to do analysis & synthesis of the same programming, as well.

It started happening two days ago. Hence, the message of the window changes each time when I try to compile or do an analysis. Here's the last message that appeared to me:


*** Fatal Error: Access Violation at 0X00007FF4175CB220
Module: quartus.exe
Stack Trace:

0x45da63: QAccessible::queryAccessibleInterface + 0x33
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0x9f06: CreateStdAccessibleProxyW + 0x4e6
0x338dd: UiaReturnRawElementProvider + 0x372d
0x7bcd6: UiaRegisterProviderCallback + 0x17446
0x73597: UiaRegisterProviderCallback + 0xed07

0x1fd37: DllCanUnloadNow + 0xde57
0x1cdcc: DllCanUnloadNow + 0xaeec
0x1ca2f: DllCanUnloadNow + 0xab4f
0x1c0e8: DllCanUnloadNow + 0xa208

0x3db14: UiaReturnRawElementProvider + 0xd964
0x3d7d6: UiaReturnRawElementProvider + 0xd626
0x1e021: Ordinal2712 + 0x191
0x20bc2: SendMessageTimeoutW + 0x142
0xa0b73: KiUserCallbackDispatcher + 0x23
0x1063: NtUserPeekMessage + 0x13
0xa5c2: PeekMessageW + 0x1e2
0xa522: PeekMessageW + 0x142
0x132d77: QEventDispatcherWin32::processEvents + 0x1c7
0x83564: QApplicationPrivate::translateTouchEvent + 0x884
0x109cf0: QEventLoop::exec + 0x230
0x420e3c: QDialog::exec + 0xec
0x643a7: AFCQ_MSG_DISPLAY::prompt_display + 0x2f7
0x10828: MSG_O::prompt + 0x8
0x266ea: QUI_FRAME_WND::flow_finish_prompt + 0x91a
0x461e8: QUI_FRAME_WND::qt_static_metacall + 0xa78
0x11d699: QObject::event + 0xd9
0x6ada8: QWidget::event + 0xd18
0x3989a4: QMainWindow::event + 0x284
0x228f5: QApplicationPrivate::notify_helper + 0xf5
0x25297: QApplication::notify + 0x17f7
0x10a7c1: QCoreApplication::notifyInternal + 0x71
0x10c7cb: QCoreApplicationPrivate::sendPostedEvents + 0x29b
0x1311de: QEventDispatcherWin32::event + 0x70e
0xe857: CallWindowProcW + 0x3f7
0xe298: DispatchMessageW + 0x258
0x132f69: QEventDispatcherWin32::processEvents + 0x3b9
0x83564: QApplicationPrivate::translateTouchEvent + 0x884
0x109cf0: QEventLoop::exec + 0x230
0x10e5ff: QCoreApplication::exec + 0xdf

0x4c78: msg_exe_fini + 0x58
0x53bc: msg_exe_fini + 0x79c
0x1584: MEM_SEGMENT_INTERNAL::~MEM_SEGMENT_INTERNAL + 0x194
0x5f9f: msg_exe_main + 0x8f


0x17033: BaseThreadInitThunk + 0x13
0x52650: RtlUserThreadStart + 0x20

End-trace

Quartus II 64-Bit Version 13.0.1 Build 232 06/12/2013 SJ Web Edition


Service Pack Installed: 1

I appreciate your time!

5 Replies

    • IESG2000's avatar
      IESG2000
      Icon for New Contributor rankNew Contributor
      3 years ago

      Hello.

      I reinstalled Quartus II 3 times; it again popped up with fatal errors. I used an old FPGA; Altera DE2 board Cyclone II EP2C35F672C6; i.e. the reason I use Quartus II v13 is that it is the oldest version of the software available to download from the intel website, and it can support the mentioned board. Hence, I gonna see the direction suggested by you.

      I appreciate your attention. Blessings!

    • IESG2000's avatar
      IESG2000
      Icon for New Contributor rankNew Contributor
      3 years ago

      I saw the problem that you suggested to me, I did it and it works. Thanks so much.

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

    Galvan,


    Glad you able to resolve it.

    May I know if you able to share the qar design file or zip files for me to reproduce the issue.

    This issue will be filed as KDB.

    Appreciate you effort, thanks


  • SyafieqS's avatar
    SyafieqS
    Icon for Super Contributor rankSuper Contributor
    3 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.