LabWindows/CVI 2020 & Win10 - non debuggable thread caused a 'Unknown' fault at adress....

[der_Phil]

Dear LabWindows experts,

following issue has been reported a couple of times in the forum, however it still appears to be an actual problem:

I have a test code:

void main(void)
{
return;
}

System environment:

- LabWindows CVI 2020 - Full Development System , Version: 20.0.0 (49152)

- Windows 10, 64 bit

LabWindows is a fresh installation ... no update from a previous version.

The PC has also not seen any previous LabWindows installation before.

Running the code above ends up in the follwoing:

  FATAL RUN TIME ERROR:

  Unknown source position, thread id 11756:

  A non-debuggable thread caused a 'Unknown' fault at adress 0x6CFD1982.

  No source line information is available.

I have read this post.

https://forums.ni.com/t5/LabWindows-CVI/FATAL-RUN-TIME-ERROR-Unknown-source-position-thread-id/m-p/3...

At the end of the post a patch is mentioned to fix the error, however there is no link to the patch.

Question: Is the patch (12-22-2016) included in LabWindows/CVI 2020?

If not: How to find/install this patch?

If yes: How to fix the error?

Thank you,

Philipp

[Gaus]

Hi

Did a test using your source code and did not get any errors. So I guess it is fixed in CVI2020.

Jan

[der_Phil]

Thank you for the feedback.

Do you also use Win10?

Best Regards,

Philipp

[Gaus]

Yes

OS Name Microsoft Windows 10 Pro
Version 10.0.19041 Build 19041
System Type x64-based PC
Processor Intel(R) Core(TM) i9-9920X CPU @ 3.50GHz, 3504 Mhz, 12 Core(s)

[RobertoBozzolo]

The bug you are referring was happening with the original 2015 RTE on WIn10 Anniversary Update and was corrected by a patch ont he RunTIme Engine itself. See this complete discussion.

I haven't observed it with the RTEs 2015 (patched), 2017 and 2019 running under several Win10 releases. I have not yet installed CVI2020 and its RTE so I cannot discuss about this item, but maybe some other user can comment if they have 2020 installed?

[der_Phil]

Thanks for the reply.

I tested it also today on another PC, with this configuration:

- Win10, 64bit

- Labwindows/CVI 2017, FULL Development System, Version 17.0.0 (295)

I do get the same error.

Maybe an important note?

On both PC's is also the Vision Development Module installed.

BR

[der_Phil]

Following this thread:

Solved: Re: CVI executables causes Access Violation 0xC0000005 on Windows 10 Anniversary Update. - N...

The solution at hand is to implement:

   SetSystemAttribute(ATTR_TASKBAR_BUTTON_VISIBLE, 0);

into the code. This prevents the error.

However this is just a workaround and not the fix for the error.

For this I understand a patch must be installed...I however do understand that the solution given was for

LabWindows/CVI 2015 SP1...I am running LabWindows/CVI 2020.

Best Regards