This is the same bug as mentioned raygray's comment on bug#29; I'm opening a new issue since this is not really related to issue #29.
This is for version 1.8.1 on Windows 7 x64. My processor is a mobile Ivy Bridge one (you'll see why it matters).
So starting FastoNoSQL.exe gets me an Invalid Instruction exception (c000001d) at 00000000-00856533. Loaded modules are irrelevant since the exception occurs within FastoNoSQL.exe's code segment.
Re-running it within WinDbg*, I get:
[..]
ModLoad: 000007fe`ff080000 000007fe`ff0ae000 C:\Windows\system32\IMM32.DLL
ModLoad: 000007fe`fe9f0000 000007fe`feaf9000 C:\Windows\system32\MSCTF.dll
(2dd14.2b8f4): Illegal instruction - code c000001d (first chance)
(2dd14.2b8f4): Illegal instruction - code c000001d (!!! second chance !!!)
*** WARNING: Unable to verify timestamp for FastoNoSQL.exe
*** ERROR: Symbol file could not be found. Defaulted to export symbols for FastoNoSQL.exe -
FastoNoSQL+0x456533:
00000000`00856533 c4c261f7c7 shlx eax,r15d,ebx
*I actually had to update my debugging tools for WinDbg to be able to disassemble that instruction
Looking that up, I find that SHLX is part of the BMI2 instructions introduced (for Intel) with the Haswell line (~june 2013), which means my T430 is just one generation short of running the code.
Anyway, if downgrading the compiler's target or implementing a shim for older CPUs is not possible/desirable, either a support statement on the download page mentioning the minimum CPU architecture required *or* a detection & warning routine within the application itself (e.g.
Detecting BMI2 support at runtime) would be appreciated; at least people will know it's not your application that is at fault.
For my part, I can still run the application under Intel's Software Development Emulator, although having a native build supporting an older architecture would be best.