Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
how can you run horizon zero dawn if it needs avx?
Patch v1.08 added support for non-AVX CPUs. CDPR probably will also patch that in Cyberpunk, but it might take a few months.
It's not "far below", any i7 can run this game. CPU gaming performance has peaked a long time ago on the higher end, first gens from 2009 are still overkill for gaming.
The only reason it and Xeon CPUs crash is because of a set of instructions which are OPTIONAL and can be switched for something it won't refuse to read. Horizon Zero Dawn wouldn't start until the AVX check at start was removed, once it was removed, game runs silky smooth.
https://forums.cdprojektred.com/index.php?threads/cyberpunk-2077-pc-crash-issues.11040656/page-41
Game crashing on old CPUs: possible fix
If you happen to have an old CPU you maybe having this crash:
Expression: EXCEPTION_ILLEGAL_INSTRUCTION (0xC000001D)
The game is trying to use a feature you don’t have: AVX.
At the beginning playing corpo when you sit it crashes. A possible temporal solution while they fix this issue is to remove this part of code:
Edit Cyberpunk2077.exe with a hexadecimal editor and search for
554881ECA00000000F2970E8
Change the first byte to C3 (return from the function):
C34881ECA00000000F2970E8
Please note this fix is extremely simplistic and naïve. Moreover, it could crash the game later. This change seems to fix this crash and you can continue playing the game. I have only tested a few minutes more.
FAQ: Why are they using AVX?
They are not doing it on purpose, it is probably the default configuration of the compiler.
https://www.nexusmods.com/cyberpunk2077/mods/34?tab=description
https://www.virustotal.com/gui/file/8a2e00a686dae14a4993c1d8eaa81e79480467f05ea89ce6227e3787539fea73/detection
No need to buy a new CPU as the "intelligent" people try to tell.
Someone released an assembly code edit of the .exe on Nexus. Get that here: https://www.nexusmods.com/cyberpunk2077/mods/34?tab=description
Delete your CACHE folder here at C:\Users\XXXXXXX\AppData\Local\CD Projekt Red\Cyberpunk 2077
Launch the provided .exe; Now the size of the provided .exe is the same in bytes as the original. This leads me to think that a line was changed in the code and no malicious code was added. Use at your own risk.
This fixes it on my X5675. I run the .exe provided after deleting cache. It wouldn't even load the cinematic without removing cache. :)
FYI CDPR is working on a fix as mentioned on the CDPR forums
This seems to work for people with older CPUs that get stuck at an early point in the game. I have an older CPU and cannot even get the game to launch. I tried both the nexus mod download and the hex edit method. No luck.
Have you tried removing cache? That last step fixed it for me
The cache is generated once the game is launched. My game has not started even once when hitting play in the REDlauncher.
Thanks for testing this. Saved at least one person from the pain.