Intel® FPGA University Program
University Program Material, Education Boards, and Laboratory Exercises
1174 Discussions

QUARTUS II INTERNAL ERROR

nathantaylor
Beginner
473 Views

Everytime I run Quartus II, I get this error: 


*** Fatal Error: Access Violation at 0X00000000741FDA62
Module: quartus.exe
Stack Trace:
0x45da61: QAccessible::queryAccessibleInterface + 0x31
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0xa4c0: CreateStdAccessibleProxyW + 0x1e0
0x4e60e: UiaReturnRawElementProvider + 0x34d4e
0x54e89: UiaReturnRawElementProvider + 0x3b5c9
0x37c4e: UiaReturnRawElementProvider + 0x1e38e
0xec180: UiaHasServerSideProvider + 0xa840
0x14b32c: WindowPattern_WaitForInputIdle + 0x24e9c
0x37754: UiaReturnRawElementProvider + 0x1de94
0x37489: UiaReturnRawElementProvider + 0x1dbc9
0x22a4f: SystemParametersInfoW + 0x24f
0x2302c: GetClassLongW + 0x58c
0xa33b3: KiUserCallbackDispatcher + 0x23
0x14d3: NtUserPeekMessage + 0x13
0x21b4e: PeekMessageW + 0x1ce
0x21a1b: 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
0x15baab: UnhandledExceptionFilter + 0x1eb
0xda351: LdrResolveDelayLoadsFromDll + 0x1471
0xa331f: KiUserApcDispatcher + 0xaf
0xa441e: __chkstk + 0x12e
0x1e465: RtlFindCharInUnicodeString + 0xa95
0xa340d: KiUserExceptionDispatcher + 0x2d
0x45da61: QAccessible::queryAccessibleInterface + 0x31
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0xa4c0: CreateStdAccessibleProxyW + 0x1e0
0x4e60e: UiaReturnRawElementProvider + 0x34d4e
0x54e89: UiaReturnRawElementProvider + 0x3b5c9
0x37c4e: UiaReturnRawElementProvider + 0x1e38e
0xec180: UiaHasServerSideProvider + 0xa840
0x14b32c: WindowPattern_WaitForInputIdle + 0x24e9c
0x37754: UiaReturnRawElementProvider + 0x1de94
0x37489: UiaReturnRawElementProvider + 0x1dbc9
0x22a4f: SystemParametersInfoW + 0x24f
0x2302c: GetClassLongW + 0x58c
0xa33b3: KiUserCallbackDispatcher + 0x23
0x14d3: NtUserPeekMessage + 0x13
0x21b4e: PeekMessageW + 0x1ce
0x21a1b: 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
0x15baab: UnhandledExceptionFilter + 0x1eb
0xda351: LdrResolveDelayLoadsFromDll + 0x1471
0xa331f: KiUserApcDispatcher + 0xaf
0xa441e: __chkstk + 0x12e
0x1e465: RtlFindCharInUnicodeString + 0xa95
0xa340d: KiUserExceptionDispatcher + 0x2d
0x45da61: QAccessible::queryAccessibleInterface + 0x31
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0xa4c0: CreateStdAccessibleProxyW + 0x1e0
0x4e60e: UiaReturnRawElementProvider + 0x34d4e
0x54e89: UiaReturnRawElementProvider + 0x3b5c9
0x37c4e: UiaReturnRawElementProvider + 0x1e38e
0xec180: UiaHasServerSideProvider + 0xa840
0x14b32c: WindowPattern_WaitForInputIdle + 0x24e9c
0x37754: UiaReturnRawElementProvider + 0x1de94
0x37489: UiaReturnRawElementProvider + 0x1dbc9
0x22a4f: SystemParametersInfoW + 0x24f
0x2302c: GetClassLongW + 0x58c
0xa33b3: KiUserCallbackDispatcher + 0x23
0x14d3: NtUserPeekMessage + 0x13
0x21b4e: PeekMessageW + 0x1ce
0x21a1b: 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
0x15baab: UnhandledExceptionFilter + 0x1eb
0xda351: LdrResolveDelayLoadsFromDll + 0x1471
0xa331f: KiUserApcDispatcher + 0xaf
0xa441e: __chkstk + 0x12e
0x1e465: RtlFindCharInUnicodeString + 0xa95
0xa340d: KiUserExceptionDispatcher + 0x2d
0x45da61: QAccessible::queryAccessibleInterface + 0x31

End-trace

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

 

Unfortunately, I am stuck using the Web Edition, as that is what the university requires. If anyone has any ability to help I would greatly appreciate it. 

Labels (1)
0 Kudos
1 Solution
RichardTanSY_Intel
444 Views

Does this fatal error occur when you try to open the Quartus software or when you attempt to compile a design using Quartus?


If the error is due to design compilation, kindly share your design by archiving the project (Project > Archive Project) so that I can duplicate the issue.


The fatal error could also be a result of issues with the PC environment setup.

There are a few things that you can troubleshoot:

1. Try restarting Quartus and your computer. This can help clear any temporary issues that may be causing the error.

2. Check your system resources, including memory, CPU usage, and disk space. Make sure you have enough available resources to run Quartus.

3. Try disabling any antivirus or firewall software temporarily, as they may be interfering with Quartus.

4. Run Quartus as administrator. 

5. Install currprocess https://www.nirsoft.net/utils/cprocess.html and disable all the software running behind there

6. If possible, try to run in another machine to see whether the error is machine related.


Regards,

Richard Tan





View solution in original post

0 Kudos
3 Replies
RichardTanSY_Intel
445 Views

Does this fatal error occur when you try to open the Quartus software or when you attempt to compile a design using Quartus?


If the error is due to design compilation, kindly share your design by archiving the project (Project > Archive Project) so that I can duplicate the issue.


The fatal error could also be a result of issues with the PC environment setup.

There are a few things that you can troubleshoot:

1. Try restarting Quartus and your computer. This can help clear any temporary issues that may be causing the error.

2. Check your system resources, including memory, CPU usage, and disk space. Make sure you have enough available resources to run Quartus.

3. Try disabling any antivirus or firewall software temporarily, as they may be interfering with Quartus.

4. Run Quartus as administrator. 

5. Install currprocess https://www.nirsoft.net/utils/cprocess.html and disable all the software running behind there

6. If possible, try to run in another machine to see whether the error is machine related.


Regards,

Richard Tan





0 Kudos
nathantaylor
Beginner
393 Views

Well, after making sure no antivirus was running and restarting the computer a few times, it has not crashed since. Thank you for the help.

0 Kudos
RichardTanSY_Intel
405 Views

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 let us know. 

Thank you for reaching out to us!


Best Regards,

Richard Tan


0 Kudos
Reply