systeminformer: Crash on start 3.1.24258.0

Brief description of your issue

dump in attachment dump.zip

Steps to reproduce (optional)

No response

Expected behavior (optional)

No response

Actual behavior (optional)

3.1.24244.0 - Worked 3.1.24258.0 - Crash on start

Environment (optional)

System Informer 3.1.24258.0
Windows 11 22631.4169

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 2
  • Comments: 16 (8 by maintainers)

Most upvoted comments

@dmex Many modern software (his newest version) run without problems on the processor 2008 year: Win10, Far, Windows Terminal, Chrome, Firefox, VirtualBox, Aimp,7z… I think 99% modern software is work.

15 years is probably too old

New and new generations of processors do not bring such a performance increase as before, since they are stuck at the technological barrier of the element size. That is why planned obsolescence is introduced in the form of AVX2, AVX512, AVX100500, only so that people buy more and more new generations, which are actually useless. Focusing on steam is pointless, since its users are those who play performance-intensive games, and therefore buy new hardware much more often than ordinary users, who are quite satisfied with the performance of what was created in 2013. If PH requires AVX2, I will simply stay on the old version and will no longer update it, if I find an alternative, I will throw it out completely. Of course, it is unpleasant that you went the way of adobe with their f***ing AVX2.

Why should I buy a new computer? Just so that it has AVX100500? I do not play performance-intensive games.

our CPU too old??? 😃 Intel Core 2 Duo E8400

15 years is probably too old.

AVX2 support was enabled in commit https://github.com/winsiderss/systeminformer/commit/de6d1c9c11106632834d351f6da24c4c1bc52fe3 most likely by mistake.

I assumed there wasn’t anyone using processors from 15 years ago with 64bit Windows. The Steam hardware survey is also showing 95% support for AVX2:

image

new version 3.1.24266.0 (bf387c77) works on my old CPU again:

image

So issue can be closed.

AVX2 support was enabled in commit https://github.com/winsiderss/systeminformer/commit/de6d1c9c11106632834d351f6da24c4c1bc52fe3 most likely by mistake.

Not done by mistake, this was done intentionally by @dmex.

I started to spot-check a bindiff of the two builds and - yes, this is prevalent thing all over the binary. So we need to make a decision to stop supporting these processors or have a better strategy for optimizing the paths that matter to retain support for the older processors. At this point in time I’m of the opinion that we revert the changes to ISA enhancements until we have better communication or strategy here. I’m discussing offline with @dmex.

image

Absolutely same, i’m user amd phenom ii x6 processor, that supports only maximum SSE4 instructions. I think that all these optimizations with the help of avx avx instructions are insignificant, and now the program cannot be run, and this is sad

which CPU do you both use? On my older Core i5 Ivy Bridge laptop SI also crashes. Looks like AVX2 is required now.

@MagicAndre1981 I have really old CPU here, Intel Core i3 350M, released in 2011. So yeah, that’s why also I got crashed too on the latest Canary build.

About this, I got the same issue when updating to that Canary build. But for now, I’ll wait another build comes out soon for this.

AVX2 support was enabled in commit de6d1c9 most likely by mistake.