Page 1 of 1
BEX64/StackHash error
Posted: Tue Jul 19, 2016 1:29 pm
by griff
After installing the 2.7 or 2.8 beta software on either of two Windows 7 (64 bit) laptops, I get this BEX64/Stackhash exception. The splash screen displays before the exception. I see this issue for other software but not with cloud compare. Seems to be a graphics issue, but I don't really know. Does anyone have any experience with fixing this?
Thanks!
Re: BEX64/StackHash error
Posted: Tue Jul 19, 2016 2:52 pm
by daniel
Never heard of such an error, sorry.
Have you any of the several programs listed here?
https://www.reddit.com/r/GrandTheftAuto ... ash_error/
Re: BEX64/StackHash error
Posted: Tue Aug 02, 2016 9:05 pm
by mercedesmorita
Hi, did you solve the problem? I had the same BEX64 problem .
I checked that site, and the only software I have that is on that list is the Geforce Experience. Should I uninstall it?
I look foward to your reply, thanks!
Re: BEX64/StackHash error
Posted: Wed Aug 03, 2016 1:39 am
by griff
Both versions 2.7 and 2.8 were tried on a third (desktop) Windows 7 machine. Here slightly different result, that it dies in qt5gui.dll on startup. (Not even a splash screen on that one.)
Then, I tried 2.6.0 and it works on all three computers. However, the auto align function hanged.
According to various sources, the BEX64 error is usually due to the DEP (data execution prevention), which you really don't want to defeat.
I ran 2.8.0 from within gdb and it said the FTH (fault tolerant heap) was activated before a segmentation fault. Another indication of a stack overflow on startup.
All of these computers are up-to-date. All have Norton Internet Security and I have been wondering if it is the issue.
Re: BEX64/StackHash error
Posted: Wed Aug 03, 2016 4:53 am
by daniel
Well, since the 2.7 version we do use Qt 5 instead of Qt 4. And it clearly changed a lot of things related to the GPU management. Somes for the better... but not always (for instance we lost the compatibility with a lot of old Intel / ATI cards).
In this case, I can't find any known bug of Qt 5 related to this BEX64/StackHash error. And considering people are experiencing this error with various mainstream programs and games, I still think another application is messing with CC / Qt execution.
The most probable culprit in this case is an antivirus. Especially if there's a memory leak (CC is tested against this, but sadly Qt has some known and assumed leaks...). Do you have an antivirus (AVG maybe?). Can you try disabling it and start CC again?