Quartus II 13 crash

[Lili_7]

hi,

i was using Quartus II 13 web edition for 2 years without any issues. suddenly 2 months ago it started crashing more often. so i uninstalled it, and installed it again. it did work for a month and now it crashes every time i try even to open the software. and this error message log appears: 

*** Fatal Error: Access Violation at 0X0000000067A5DA62
Module: quartus.exe
Stack Trace:
0x45da61: QAccessible::queryAccessibleInterface + 0x31
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0x9f06: CreateStdAccessibleProxyW + 0x4e6
0x32dad: UiaReturnRawElementProvider + 0x371d
0x7c546: UiaRegisterProviderCallback + 0x18336
0x74057: UiaRegisterProviderCallback + 0xfe47

0x1f217: DllCanUnloadNow + 0xd347
0x1c2ac: DllCanUnloadNow + 0xa3dc
0x1bf0f: DllCanUnloadNow + 0xa03f
0x1b5c8: DllCanUnloadNow + 0x96f8

0x3cfe4: UiaReturnRawElementProvider + 0xd954
0x3cca6: UiaReturnRawElementProvider + 0xd616
0x1e9b1: Ordinal2712 + 0x191
0x21632: SendMessageTimeoutW + 0x142
0xa13e3: KiUserCallbackDispatcher + 0x23
0x1063: NtUserPeekMessage + 0x13
0xa332: PeekMessageW + 0x1e2
0xa292: PeekMessageW + 0x142
0x132d77: QEventDispatcherWin32::processEvents + 0x1c7
0x83564: QApplicationPrivate::translateTouchEvent + 0x884
0x109cf0: QEventLoop::exec + 0x230
0x420e3c: QDialog::exec + 0xec
0x645ac: AFCQ_MSG_DISPLAY::internal_error_display + 0x1dc
0xe2c7: MSG_REPORT::internal_error + 0x127
0x1ebee: MSG_INTERNAL_ERROR::set_talkback_xml + 0x11be
0x1efc9: MSG_INTERNAL_ERROR::report_fatal + 0x179
0x4200: err_report_fatal_exception + 0x70
0x4499: err_report_fatal_exception + 0x309
0x12d826: UnhandledExceptionFilter + 0x1e6
0xcf4d7: LdrResolveDelayLoadsFromDll + 0xb37
0xa134f: KiUserApcDispatcher + 0xaf
0xa292e: __chkstk + 0x11e
0x52553: RtlRaiseException + 0x483
0xa143d: KiUserExceptionDispatcher + 0x2d

0x45da63: QAccessible::queryAccessibleInterface + 0x33
0x46403c: QAccessible::setRootObject + 0x153c
0x4652e9: QAccessible::setRootObject + 0x27e9
0x9f06: CreateStdAccessibleProxyW + 0x4e6
0x32dad: UiaReturnRawElementProvider + 0x371d
0x7c546: UiaRegisterProviderCallback + 0x18336
0x74057: UiaRegisterProviderCallback + 0xfe47

0x1f217: DllCanUnloadNow + 0xd347
0x1c2ac: DllCanUnloadNow + 0xa3dc
0x1bf0f: DllCanUnloadNow + 0xa03f
0x1b5c8: DllCanUnloadNow + 0x96f8

0x3cfe4: UiaReturnRawElementProvider + 0xd954
0x3cca6: UiaReturnRawElementProvider + 0xd616
0x1e9b1: Ordinal2712 + 0x191
0x21632: SendMessageTimeoutW + 0x142
0xa13e3: KiUserCallbackDispatcher + 0x23
0x1063: NtUserPeekMessage + 0x13
0xa332: PeekMessageW + 0x1e2
0xa292: PeekMessageW + 0x142
0x132d77: QEventDispatcherWin32::processEvents + 0x1c7
0x83564: QApplicationPrivate::translateTouchEvent + 0x884
0x109cf0: QEventLoop::exec + 0x230
0x420e3c: QDialog::exec + 0xec
0x64237: AFCQ_MSG_DISPLAY::prompt_display + 0x2f7
0x10648: MSG_O::prompt + 0x8
0x2683a: QUI_FRAME_WND::flow_finish_prompt + 0x91a
0x460d8: 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
0xef5b: CallWindowProcW + 0x60b
0xe683: DispatchMessageW + 0x4a3
0x132f69: QEventDispatcherWin32::processEvents + 0x3b9
0x83564: QApplicationPrivate::translateTouchEvent + 0x884
0x109cf0: QEventLoop::exec + 0x230
0x10e5ff: QCoreApplication::exec + 0xdf

0x4ae8: msg_exe_fini + 0x58
0x522c: msg_exe_fini + 0x79c
0x1524: MEM_SEGMENT_INTERNAL::~MEM_SEGMENT_INTERNAL + 0x194
0x5e0f: msg_exe_main + 0x8f

0x17343: BaseThreadInitThunk + 0x13
0x4cc90: RtlUserThreadStart + 0x20

End-trace

Quartus II 64-Bit Version 13.0.0 Build 156 04/24/2013 SJ Web Edition

[_AK6DN_]

Really important when you post something like this is to include details of your exact system and O/S configuration.

You are obviously running Windows, but ... what version and release.

Also useful but not as critical is the CPU type and amount of memory.

And some history, like did it start to happen after some specific Windows update?

[Lili_7]

quite right,

sorry for the lack of information,

running OS is 64-bit Windows 10,  Core(TM) i7-4790 CPU @ 3.60GHz + 8.00 GB.

honestly i cant recall for sure that if the crashing started exactly after some windows updates or no. since it was at the beginning twice a day but still working but after a while completely broke. and in this meanwhile there were plenty of windows update. 

[sstrell]

And what device are you targeting that you are running 11-year-old software?

[Lili_7]

this system is only used for some old devices with some old altera cyclone IV-E based .

[RichardTanSY_Intel]

Regarding fatal error, there are a few things that you can troubleshoot:

1. Ensure that you are using the latest version of Quartus as there are a few bug fixed. 

2. Please check that your machine system must meet minimum Hardware and Software Requirements. Ensure that your Operating System is supported. https://www.intel.com/content/www/us/en/docs/programmable/683472/current/system-requirements-and-prerequisite.html

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

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

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

6. Run Quartus as administrator. 

7. Install currprocess https://www.nirsoft.net/utils/cprocess.html and disable all the software running behind in the background. 

Regards,

Richard Tan

[Lili_7]

thanks a lot for all the help.

the version that was running just fine on the system was 13.0 while the latest version is 13.1 from the same year. so i dont expect that much of a difference. and i think the problem even got worse when i removed the current quartus and downloaded the 13.1 version. 

but i will try your solution and i will post the an update on result.

[_AK6DN_]

Running the latest version (or one of the later versions) of Quartus may or may not be possible. Depends on the device support.

That being said, I use QuartusII 13.0sp1 Web on Windows 10 64b 22H2 and on Windows 7 64b SP1.

I use it to support the MAX 7000S, MAX 3000A, and the CYCLONE II device families.

This version of Quartus is the last one that supports those device families and it is still offered for download by Altera/Intel.

Upgrading to the latest version is not always the solution, in either the QuartusII software, or in some cases the WindowsOS.

At some point you may have to freeze updates when an update to Windows breaks the old Quartus software you need.

If that happens, I will build a VM VirtualBox environment with the required Windows (or maybe Linux) environment and QuartusII.

I haven't had to do that yet, Windows 10 22H2 64b runs the existing QuartusII 13.0sp1 web release just fine.

[Lili_7]

exactly, latest version is for sure not always the solution, especially on Windows.

 i will also try to restore windows from some updates and then install both 13.0 and if didn't help 13.1 in turn , hope to get some achievements. if not possible try VM.

thank you for offering solutions. i will post the result

[FvM]

Hi,
as said, Quartus 13.0 (and even 9.0) runs well under recent Windows 10, although not officially supported. OP states that design is for Cyclone IV E which can be compiled with newer Quartus versions as well. Quartus 13 is only required for legacy devices like Cyclone II.

[Lili_7]

but since the hardware was developed basically on web edition, by not jumping to Quartus lite, i am trying to prevent some rising bugs here.

[RichardTanSY_Intel]

Do you able to resolve the issue ?

Regards,

Richard Tan

[Lili_7]

hi everyone,

i waited a few days to make sure of not crashing again and then post it.

i succeeded to solve the problem by restoring windows 10 to my last save, and uninstalling Quartus 13.0 +completely removing anything left from it.  and download and installing Quartus 13.1.

this so far is working just fine. 

best regards

Lili

[RichardTanSY_Intel]

I'm glad to know that your issue has been addressed.

Now, I will transitioning this thread to community support. If you have any further questions or concerns, please don't hesitate to reach out. Please login to ‘https://supporttickets.intel.com’, view details of the desire request, and post a feed/response within the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support.

The community users will be able to help you on your follow-up questions.

Thank you and have a great day!

Best Regards,

Richard Tan

p/s: If you find any answers from the community or Intel Support to be helpful, we encourage you to mark them as the best answer or rate them 4/5 in the survey.