LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

StackHash module error on a CVI app in a brand new PC

Solved!
Go to solution

Hello all, I am just facing a strange situation in which an application of mine is crashing without apparent reasons. The application is developed in CVI2017.

 

I am running the application on a brand new PC with just the Run-time Engine installed. Other application installed (Edge, Notepad, McAfee app, Photos) run without apparent problems. Another application of mine, developed in CVI2017 as well, runs without problems. The strange fact is that two weeks ago I installed that very same crashing app in another, identical PC and there it had no problems!

 

In the Event Viewer I find a Application Crashing Event note with unknown Faulting module name, immediately followed by a Window Error Reporting event that reports:

Fault module name = StackHash_2beb

Fault module versione = 0.0.0.0

Exception code = c0000005

Exception offset = PCH_26_FROM_ntdll+0x00076DCC

 

The machine is an Acer box with Windows 11 Pro installed, version 23H2 with automatic updates on

 

I tried a scan with McAfee LiveSafe that comes in bundle with the PC, which states no viruses found,

 

I'm a bit lost because I don't event know what that StackHash module is and does, but before trying to reinstall Windows from scratch I would like to know if anyone has had a similar issue running a CVI app and how they addressed it.

I will also try to rebuild the app, but I would like to understand the cause of this problem so that I may try to fix it and have no problems in the future.



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 1 of 5
(239 Views)
Solution
Accepted by topic author RobertoBozzolo

I did a bit of searches on this error and I eventually found the cause of it: there was a misalignment between the release of the exe and the associated .UIR. Luckily I keep track of all application builds and could install the correct .exe + .UIR pair coming back to a stable situation.

 

BTW, in my searches turned out that StackHash has no role in this error: according to Mark answer in this discussion:

When a program is corrupted in memory and Windows cannot tell where the code crashed then it does a stackhash of the stack to help in identifying similar problems. A stack is where parameters, local variables, and the return memory address is stored

 

Strange enough, the OS was not able to identify the location of fault in my application...



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 2 of 5
(210 Views)

So it means you didn't create a distribution and just copied the exe, right ? So many people bitten this way, I'm surprised it happened to you...  😉

0 Kudos
Message 3 of 5
(179 Views)

Hi

 

To Avoid this situation that the exe and the UIR are mismatch i always embed the UIR into the EXE by checking the flag at build->target settings

0 Kudos
Message 4 of 5
(135 Views)

@GabelDaniel  ha scritto:

Hi

 

To Avoid this situation that the exe and the UIR are mismatch i always embed the UIR into the EXE by checking the flag at build->target settings


That's a good idea. I normally don't like doing so but it's an habit rather than an actual decision, I have no real clues in favor or against this solution.



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 5 of 5
(127 Views)