05-05-2025 08:32 AM
Hi guys,
I recently switched from CVI2017 to the newst version of CVI (20.0.0).
My software now randomly crashes while in idle (seems to be random) with the error:
Unrecoverable Internal Error at 0023:622A8B1B.
LabWindows/CVI will be aborted.
I never had this issue with CVI2017. My used OS is Windows 11.
Any ideas how to fix this?
05-05-2025 01:06 PM
Did you check the Windows Event Viewer?
The crash explanations there might shed some light on the issue.
Regards,
05-05-2025 02:32 PM
Anything useful here?
- | System |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- | EventData |
[15:25:30.986] [FATAL] [GeneralSignalHandler] [.\source\jeff\i386\except.c:179] General Protection |
05-05-2025 09:10 PM
I was waiting something like this.
It can also be in the Application sub-group of the tree on the left.
05-06-2025 02:02 AM
Thats where I checked. But since my OS is in german, I decided to copy the "Details"-menu, not the "General".
In "General", the same information is given. Only in the box above is a german description that is not in "Details", but it is completely useless, here a translation with DeepL:
"The description for the event ID “0” from the source “CVI” was not found. Either the component that triggers this event is not installed on the local computer or the installation is damaged. You can install or repair the component on the local computer.
If the event occurred on another computer, the display information had to be saved with the event.
The following information was saved with the event:
[15:25:30.986] [FATAL] [GeneralSignalHandler] [.\source\jeff\i386\except.c:179] General Protection
The message resource is available, but the message was not found in the message table"
05-09-2025 09:09 AM
@tsmc wrote:
Hi guys,
I recently switched from CVI2017 to the newst version of CVI (20.0.0).
My software now randomly crashes while in idle (seems to be random) with the error:
Unrecoverable Internal Error at 0023:622A8B1B.
LabWindows/CVI will be aborted.I never had this issue with CVI2017. My used OS is Windows 11.
Any ideas how to fix this?
We are using 2017 as well, and have have been working on migrating away from LabWindows. We did consider "one last update" to 2020 to get official Windows 11 support, though I see that requires some patches since the stock 2020 was not listed as Win 11 compatible. (Neither is 2017, but what we use seems to work except for some second-monitor graphical glitches in the IDE.)
What patch level do you have your 2020 at?
05-12-2025 06:20 AM
It might be related to compatibility issues between CVI 20.0.0 and certain Windows 11 updates. Try running the software in compatibility mode for Windows 10 or check if any background processes are interfering. You may also want to monitor arrest update NJ resources when debugging system logs for context, as they sometimes highlight activity patterns tied to system instability. Let us know if any specific DLLs are mentioned in the crash log.