Version 5.11.2.28 Crash after clean install

[adrianis86]

Version 5.11.2.28 crashes after clean install and fresh configuration
Windows 10, 21H1, OS build 19043.985, Windows Feature Experience Pack 120.2212.2020.0

No issues until version 5.11.2.27 included

[psieg]

When exactly does it crash? After a fresh installation the wizard should start, right?

Also try this please, just to make sure it's not the change in build environment.

[adrianis86]

Hi, psieg
Same issue with the version from the link.
My default mode is Moodlamp.
It starts ok with that mode.
As soon i try to switch to Screen grabbing mode - the app would unload and can't be started again.

[adrianis86]

Here are the logs from Event Viewer:
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Prismatik.exe because of this error.

Program: Prismatik.exe
File:

The error value is listed in the Additional Data section.
User Action

1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
   • It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
   • It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0

---

Faulting application name: Prismatik.exe, version: 5.11.2.28, time stamp: 0x60a6b366
Faulting module name: Prismatik.exe, version: 5.11.2.28, time stamp: 0x60a6b366
Exception code: 0xc000001d
Fault offset: 0x00000000000faf74
Faulting process id: 0x2858
Faulting application start time: 0x01d74dbabed4e60b
Faulting application path: C:\Program Files\Prismatik\Prismatik.exe
Faulting module path: C:\Program Files\Prismatik\Prismatik.exe
Report Id: 6842d585-9055-49d9-b9c9-4e9f8b4352b8
Faulting package full name:
Faulting package-relative application ID:

[psieg]

0xC000001D is STATUS_ILLEGAL_INSTRUCTION.
What system are you running on?

[psieg]

Looks like the culprit is somewhere in #426, but the change to simdupgrade looks ok. @zomfg in case you notice something

[psieg]

What hardware is it running on I mean, which CPU?

[adrianis86]

What hardware is it running on I mean, which CPU?

Intel Core 2 Duo E6750

[psieg]

Please try replacing the Prismatik.exe with this one.

It should show a message on startup about which extensions it detected

[zomfg]

I wonder if this isn't the same situation, but msvc #356

[adrianis86]

Please try replacing the Prismatik.exe with this one.

It should show a message on startup about which extensions it detected

[psieg]

Hm, so if your hypothesis for #356 was correct, it can't be entirely the same here because it didn't even detect SSE4.1. That would mean some normal code was automatically optimized to SSE4 or AVX2 (as the CPU supports neither).

@adrianis86, please try this version which has the optimization flags from #426 for windows removed. If that fails, try this, which has both lines reverted.

[zomfg]

SSE4.1 came with C2D E8xxx

[adrianis86]

Hm, so if your hypothesis for #356 was correct, it can't be entirely the same here because it didn't even detect SSE4.1. That would mean some normal code was automatically optimized to SSE4 or AVX2 (as the CPU supports neither).

@adrianis86, please try this version which has the optimization flags from #426 for windows removed. If that fails, try this, which has both lines reverted.

It works with both versions!

[psieg]

Hm, thanks. I guess we'll just revert the QMAKE_CFLAGS_AVX2 for Windows then...

[adrianis86]

Hm, thanks. I guess we'll just revert the QMAKE_CFLAGS_AVX2 for Windows then...

Thank you.

What are the advantages of that flag?
Maybe it should be enabled for the hardware, that does support it and disabled, if not supported?