Forum Discussion

Hung2's avatar
Hung2
Icon for New Contributor rankNew Contributor
1 year ago

QUARTUS II INTERNAL ERROR

Everytime I run Quartus II, I get this error. I try installing 2 version of Quartus web 13.1(lastest) and previous version 13.0sp1 BUT in both version, the Fatal Error: Access Violation still occurs.


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

0x45da63: QAccessible::queryAccessibleInterface + 0x33
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0xa4c0: CreateStdAccessibleProxyW + 0x1e0


0x5360e: UiaReturnRawElementProvider + 0x1f3e
0xefff0: UiaHasServerSideProvider + 0xa7e0
0x14ed0c: WindowPattern_WaitForInputIdle + 0x24b6c
0x53114: UiaReturnRawElementProvider + 0x1a44
0x52e49: UiaReturnRawElementProvider + 0x1779
0x22bff: SystemParametersInfoW + 0x24f
0x231dc: GetClassLongW + 0x58c
0xa4213: KiUserCallbackDispatcher + 0x23
0x14d3: NtUserPeekMessage + 0x13
0x21cfe: PeekMessageW + 0x1ce
0x21bcb: PeekMessageW + 0x9b
0x132d77: QEventDispatcherWin32::processEvents + 0x1c7
0x83564: QApplicationPrivate::translateTouchEvent + 0x884
0x109cf0: QEventLoop::exec + 0x230
0x420e3c: QDialog::exec + 0xec
0x6471c: AFCQ_MSG_DISPLAY::internal_error_display + 0x1dc
0xe497: MSG_REPORT::internal_error + 0x127
0x1ee2e: MSG_INTERNAL_ERROR::set_talkback_xml + 0x11be
0x1f209: MSG_INTERNAL_ERROR::report_fatal + 0x179
0x4200: err_report_fatal_exception + 0x70
0x4499: err_report_fatal_exception + 0x309
0x16bfeb: UnhandledExceptionFilter + 0x1eb
0xdac91: LdrResolveDelayLoadsFromDll + 0x1471
0xa417f: KiUserApcDispatcher + 0xaf
0xa527e: __chkstk + 0x12e
0x1e885: RtlFindCharInUnicodeString + 0xa95
0xa426d: KiUserExceptionDispatcher + 0x2d

0x45da63: QAccessible::queryAccessibleInterface + 0x33
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0xa4c0: CreateStdAccessibleProxyW + 0x1e0


0x5360e: UiaReturnRawElementProvider + 0x1f3e
0xefff0: UiaHasServerSideProvider + 0xa7e0
0x14ed0c: WindowPattern_WaitForInputIdle + 0x24b6c
0x53114: UiaReturnRawElementProvider + 0x1a44
0x52e49: UiaReturnRawElementProvider + 0x1779
0x22bff: SystemParametersInfoW + 0x24f
0x231dc: GetClassLongW + 0x58c
0xa4213: KiUserCallbackDispatcher + 0x23
0x14d3: NtUserPeekMessage + 0x13
0x21cfe: PeekMessageW + 0x1ce
0x21bcb: PeekMessageW + 0x9b
0x132d77: QEventDispatcherWin32::processEvents + 0x1c7
0x83564: QApplicationPrivate::translateTouchEvent + 0x884
0x109cf0: QEventLoop::exec + 0x230
0x420e3c: QDialog::exec + 0xec
0x6471c: AFCQ_MSG_DISPLAY::internal_error_display + 0x1dc
0xe497: MSG_REPORT::internal_error + 0x127
0x1ee2e: MSG_INTERNAL_ERROR::set_talkback_xml + 0x11be
0x1f209: MSG_INTERNAL_ERROR::report_fatal + 0x179
0x4200: err_report_fatal_exception + 0x70
0x4499: err_report_fatal_exception + 0x309
0x16bfeb: UnhandledExceptionFilter + 0x1eb
0xdac91: LdrResolveDelayLoadsFromDll + 0x1471
0xa417f: KiUserApcDispatcher + 0xaf
0xa527e: __chkstk + 0x12e
0x1e885: RtlFindCharInUnicodeString + 0xa95
0xa426d: KiUserExceptionDispatcher + 0x2d

0x45da63: QAccessible::queryAccessibleInterface + 0x33
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0xa4c0: CreateStdAccessibleProxyW + 0x1e0


0x5360e: UiaReturnRawElementProvider + 0x1f3e
0xefff0: UiaHasServerSideProvider + 0xa7e0
0x14ed0c: WindowPattern_WaitForInputIdle + 0x24b6c
0x53114: UiaReturnRawElementProvider + 0x1a44
0x52e49: UiaReturnRawElementProvider + 0x1779
0x22bff: SystemParametersInfoW + 0x24f
0x231dc: GetClassLongW + 0x58c
0xa4213: KiUserCallbackDispatcher + 0x23
0x14d3: NtUserPeekMessage + 0x13
0x21cfe: PeekMessageW + 0x1ce
0x21bcb: PeekMessageW + 0x9b
0x132d77: QEventDispatcherWin32::processEvents + 0x1c7
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


0x1259c: BaseThreadInitThunk + 0x1c
0x5af37: RtlUserThreadStart + 0x27

End-trace

Quartus II 64-Bit Version 13.0.1 Build 232 06/12/2013 SJ Web Edition
Service Pack Installed: 1

University Program

5 Replies

  • ShengN_altera's avatar
    ShengN_altera
    Icon for Super Contributor rankSuper Contributor
    1 year ago

    Hi,


    Make sure use compatible os. Try re-installing with all suspicious software such as anti-virus, anti malware or vpn turned off.


    Thanks,

    Regards,

    Sheng


    • Hung2's avatar
      Hung2
      Icon for New Contributor rankNew Contributor
      1 year ago

      thanks for your instructions. however, After trying all these method, i still could not fix it. fortunately, I try install with version 32-bit Quartus ii. And there are no issues and errors then. i dont know why, my computer works with 64-bit in others applications but not this

  • ShengN_altera's avatar
    ShengN_altera
    Icon for Super Contributor rankSuper Contributor
    1 year ago

    I try installed 64-bit in Window 11 and software can be launched without any problem. May be try installed with individual files. Also, try to launch it as administrator.


    Thanks,

    Regards,

    Sheng


  • ShengN_altera's avatar
    ShengN_altera
    Icon for Super Contributor rankSuper Contributor
    1 year ago

    Hi,


    May I know any further concern or consideration? Does the problem been resolved?


    Thanks,

    Regards,

    Sheng


    • Hung2's avatar
      Hung2
      Icon for New Contributor rankNew Contributor
      1 year ago
      I think I’m fine with that 32-bits ver. My friends laps have no error with 64 bit version except me. They also no need to turn off windown defense or anything same. Just install and you. Perhaps this comes from my Win that i downloaded or installed some sofwares, interfaces and structure. These make only my Operating system conflicted with Quartus II SJ Web Edition