Skip to content

3rd generation CPUs #110

Open
Open

Description

@hamidft9

I tried to install it but it doesn't work on a 3rd generation CPU. Such a waste :(((

Activity

  1. shinyobjectz commented on Nov 12, 2026

    @shinyobjectz
    Owner

    Sorry it didn't run. I'd like to know what you saw: which download (the app installer, or the raea command line), what happened when you started it (an error message, a window that closed, nothing at all), and whether a 3rd-generation Core i-something is the processor (so Intel HD 4000 graphics) or a different generation. The processor itself isn't the limit: raea's builds target plain x86-64. What a 2012 machine is likely missing is a GPU that speaks DirectX 12 or Vulkan; Intel HD 4000 has neither on Windows, and the app's window and 3D need one. 2D video still renders on the CPU with the command line. I've added that to the install page so it's clear up front; with your details I can say exactly what failed.

  2. added
    waiting on reporterCan't be reproduced or fixed without more information from whoever filed it
    on Nov 12, 2026
  3. hamidft9 commented on Nov 14, 2026

    @hamidft9
    Author

    i asked my agent to install Raea on my pc. here is its report:

    {{{ Why raea does not run
    0xC000001D = STATUS_ILLEGAL_INSTRUCTION. Windows itself named the culprit:

    Code block

    Faulting module name: raea.exe ← the executable itself, not any DLL
    Exception code: 0xc000001d
    The CPU on this system is an Intel Core i5-3550 — an Ivy Bridge from 2012, which does not support AVX2 (that arrived with Haswell). The raea engine was compiled against a newer baseline.

    I eliminated the alternative hypotheses in four independent ways:

    I loaded each of the 11 imported DLLs separately in its own process → all returned LOADOK
    I also installed and tested the older version 0.1.0-canary.2 → same error
    Two other raea executables that do not depend on DirectML → they ran correctly
    The Windows WER log → the faulting module is raea.exe itself
    This problem cannot be fixed by any user-level change. The only real solutions are a newer CPU or a different raea build — and both are outside what I am allowed to do. }}}

    ps: my gpu is a 1060 6gb. so its not the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    waiting on reporterCan't be reproduced or fixed without more information from whoever filed it

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions