Forum Discussion

New Contributor

4 years ago

Solved

Quartus II 13.0.1 access violation error

I am getting a weird access violation error with Quartus II 13.0.1 on a new PC. I installed Quartus II and it worked for a while. I installed other software (including Quartus Prime) and now when I run Quartus II I get an access violation for most actions in the UI.

So I uninstalled and reinstalled Quartus II. After that, it worked correctly and allowed me to build my project, edit files, and view timing reports in Timing Analyzer. All was good until I rebooted my PC and now Quartus II is back to giving me an access violation for many actions. An example error report is shown below.

I need to use Quartus II version 13 since that is the last version to support the FPGA I am targeting.

Any idea what might be causing this?

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

0x45da63: QAccessible::queryAccessibleInterface + 0x33
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0x9f06: CreateStdAccessibleProxyW + 0x4e6
0x29bb1: UiaReturnRawElementProvider + 0x7331
0x7c476: UiaRegisterProviderCallback + 0x171d6
0x739c7: UiaRegisterProviderCallback + 0xe727
0x2f346: UiaReturnRawElementProvider + 0xcac6
0x43df7: DllCanUnloadNow + 0xd987
0x40e8c: DllCanUnloadNow + 0xaa1c
0x40aef: DllCanUnloadNow + 0xa67f
0x401a8: DllCanUnloadNow + 0x9d38
0x2f7c6: UiaReturnRawElementProvider + 0xcf46

0x1e021: Ordinal2712 + 0x191
0x20bc2: SendMessageTimeoutW + 0x142
0xa0ba3: 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
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
0x10b876: UnhandledExceptionFilter + 0x1e6
0xcf367: LdrResolveDelayLoadsFromDll + 0xb37
0xa0b0f: KiUserApcDispatcher + 0x9f
0xa20ce: __chkstk + 0x11e
0x51453: RtlRaiseException + 0x433
0xa0bfd: KiUserExceptionDispatcher + 0x2d

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 Full Version
Service Pack Installed: 1

DCote3
4 years ago
Solved:

I have got Quartus II 13.0.1 running on my new PC by checking the "Run this program as an administrator" option on the Compatibility tab under Properties of the quartus.exe application at C:\altera\13.0sp1\quartus\bin64.

I now get a UAC prompt every time I launch Quartus II, but at least it runs. This was not necessary on my old PC, and I am logged in as an administrator on both machines. I don't know what the difference is, but I can live with this minor annoyance.

I hope this helps if anyone else runs into the same problem.

11 Replies

DCote3
New Contributor
4 years ago
Solved:

I have got Quartus II 13.0.1 running on my new PC by checking the "Run this program as an administrator" option on the Compatibility tab under Properties of the quartus.exe application at C:\altera\13.0sp1\quartus\bin64.

I now get a UAC prompt every time I launch Quartus II, but at least it runs. This was not necessary on my old PC, and I am logged in as an administrator on both machines. I don't know what the difference is, but I can live with this minor annoyance.

I hope this helps if anyone else runs into the same problem.
- fazerquartz
  New Contributor
  2 years ago
  Not working the error still comes
- Vian
  New Contributor
  1 year ago
  Worked for me. Thank you so much!
YEan
Contributor
4 years ago
Hi.

Hi,

Can you try by deleting the "db" and "incremental_db" folders from created project stored directory.

Thanks,
Ean
DCote3
New Contributor
4 years ago
I deleted those folders from the project. I opened the project and got the following error when I clicked on the Files tab in the project navigator:

*** Fatal Error: Access Violation at 0X000000006CA9DA62
Module: quartus.exe
Stack Trace:
0x45da61: QAccessible::queryAccessibleInterface + 0x31
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0x9f06: CreateStdAccessibleProxyW + 0x4e6
0x29bb1: UiaReturnRawElementProvider + 0x7331
0x7c476: UiaRegisterProviderCallback + 0x171d6
0x739c7: UiaRegisterProviderCallback + 0xe727
0x2f346: UiaReturnRawElementProvider + 0xcac6
0x43df7: DllCanUnloadNow + 0xd987
0x40e8c: DllCanUnloadNow + 0xaa1c
0x40aef: DllCanUnloadNow + 0xa67f
0x401a8: DllCanUnloadNow + 0x9d38
0x2f7c6: UiaReturnRawElementProvider + 0xcf46

0x1e021: Ordinal2712 + 0x191
0x20bc2: SendMessageTimeoutW + 0x142
0xa0ba3: KiUserCallbackDispatcher + 0x23
0x1063: NtUserPeekMessage + 0x13
0xa5c2: PeekMessageW + 0x1e2
0xa522: PeekMessageW + 0x142
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

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

End-trace

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

Then when I clicked on the copy button in that dialog (to post here) I got another error dialog with the following message:

*** Fatal Error: Access Violation at 0X000000006CA9DA62
Module: quartus.exe
Stack Trace:
0x45da61: QAccessible::queryAccessibleInterface + 0x31
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0x9f06: CreateStdAccessibleProxyW + 0x4e6
0x29bb1: UiaReturnRawElementProvider + 0x7331
0x7c476: UiaRegisterProviderCallback + 0x171d6
0x739c7: UiaRegisterProviderCallback + 0xe727
0x2f346: UiaReturnRawElementProvider + 0xcac6
0x43df7: DllCanUnloadNow + 0xd987
0x40e8c: DllCanUnloadNow + 0xaa1c
0x40aef: DllCanUnloadNow + 0xa67f
0x401a8: DllCanUnloadNow + 0x9d38
0x2f7c6: UiaReturnRawElementProvider + 0xcf46

0x1e021: Ordinal2712 + 0x191
0x20bc2: SendMessageTimeoutW + 0x142
0xa0ba3: 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
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
0x10b876: UnhandledExceptionFilter + 0x1e6
0xcf367: LdrResolveDelayLoadsFromDll + 0xb37
0xa0b0f: KiUserApcDispatcher + 0x9f
0xa20ce: __chkstk + 0x11e
0x51453: RtlRaiseException + 0x433
0xa0bfd: KiUserExceptionDispatcher + 0x2d
0x45da61: QAccessible::queryAccessibleInterface + 0x31
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0x9f06: CreateStdAccessibleProxyW + 0x4e6
0x29bb1: UiaReturnRawElementProvider + 0x7331
0x7c476: UiaRegisterProviderCallback + 0x171d6
0x739c7: UiaRegisterProviderCallback + 0xe727
0x2f346: UiaReturnRawElementProvider + 0xcac6
0x43df7: DllCanUnloadNow + 0xd987
0x40e8c: DllCanUnloadNow + 0xaa1c
0x40aef: DllCanUnloadNow + 0xa67f
0x401a8: DllCanUnloadNow + 0x9d38
0x2f7c6: UiaReturnRawElementProvider + 0xcf46

0x1e021: Ordinal2712 + 0x191
0x20bc2: SendMessageTimeoutW + 0x142
0xa0ba3: KiUserCallbackDispatcher + 0x23
0x1063: NtUserPeekMessage + 0x13
0xa5c2: PeekMessageW + 0x1e2
0xa522: PeekMessageW + 0x142
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

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

End-trace

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

Then I clicked OK on the error dialog which closed the application. After that I opened the application and selected the same project and I got another error dialog before I did anything (no clicks, no typing, nothing, just waited for a second or two).

*** Fatal Error: Access Violation at 0X000000006CA9DA62
Module: quartus.exe
Stack Trace:
0x45da61: QAccessible::queryAccessibleInterface + 0x31
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0x9f06: CreateStdAccessibleProxyW + 0x4e6
0x29bb1: UiaReturnRawElementProvider + 0x7331
0x7c476: UiaRegisterProviderCallback + 0x171d6
0x739c7: UiaRegisterProviderCallback + 0xe727
0x2f346: UiaReturnRawElementProvider + 0xcac6
0x43df7: DllCanUnloadNow + 0xd987
0x40e8c: DllCanUnloadNow + 0xaa1c
0x40aef: DllCanUnloadNow + 0xa67f
0x401a8: DllCanUnloadNow + 0x9d38
0x2f7c6: UiaReturnRawElementProvider + 0xcf46

0x1e021: Ordinal2712 + 0x191
0x20bc2: SendMessageTimeoutW + 0x142
0xa0ba3: KiUserCallbackDispatcher + 0x23
0x1063: NtUserPeekMessage + 0x13
0xa5c2: PeekMessageW + 0x1e2
0xa522: PeekMessageW + 0x142
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

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

End-trace

Quartus II 64-Bit Version 13.0.1 Build 232 06/12/2013 SJ Full Version
Service Pack Installed: 1
DCote3
New Contributor
4 years ago
Further information. I uninstalled both Quartus II and Quartus Prime (and Visual Studio Community Edition which I believe was the last thing I installed before these troubles began). I then rebooted and reinstalled Quartus II.

The installer launched Quartus II. I deleted the db folders in the project directory as suggested earlier. I opened the project. Everything worked as expected. I could build the project and run the timing analyzer. I closed that project and opened a second project with a testbench to try the Modelsim simulator. That worked as expected as well, I rebuilt the project and ran the simulation. I closed that project and quit Quartus II.

Then I re-launched Quartus II and re-opened the first project again. I was again greeted with the access violation error dialog a second or two after opening the project, before doing anything else (no clicking of any controls etc.). A few seconds later a second access violation error dialog was presented (over top of the first, but with different content and visible as a third Quartus window). Clicking the OK button in any error dialog causes Quartus II to quit.

One successful run per installation is frustrating, since it takes an hour or so to uninstall and reinstall Quartus II.

Any suggestions? How do I ask for more direct support from Intel?
sstrell
Super Contributor
4 years ago
Is there a reason why you have to use such an old version of Quartus? What device are you targeting?
- DCote3
  New Contributor
  4 years ago
  Yes, Quartus II v 13 is the last version to support the FPGA I am targeting (as I said earlier). I can't switch to a newer version, and I can't switch to a different FPGA.
  
  This version was working fine on my previous PC with Windows 10 Pro 64 bit. The problem is likely something in or missing from my new PC, but the error message doesn't give me any useful information about what the cause is.
FvM
Super Contributor
2 years ago
Hi,
you reported your old PC was running Windows 10 Pro. If the new OS is Windows 11, I won't be surprised if you have problems with Quartus.
- fazerquartz
  New Contributor
  2 years ago
  my device was always running windows 11 how can i resolve this issue if the above fix is not applicable
  - FvM
    Super Contributor
    2 years ago
    Hi,
    just notice that no Quartus version before 23.x is specified to work with Windows 11. According to my experience, previous versions back to 9.0 run still under Windows 10, but Windows 11 is generally known to bring up many incompatibility issues. If you are though stuck to Windows 11, you may think about running Quartus in a virtual machine.

Forum Discussion

Quartus II 13.0.1 access violation error

11 Replies

Recent Discussions

Need a license for Encrypting - Quartus Prime Lite

Agilex 5 – Critical HSSI Error in JESD204B Example Design

recovery timing issue

Once again about CTRL+L

timing signoff