Like the title suggests, I've tried to run the DX9 version, going to the bin folder and running it from there but nothing has helped. All that ends up happening is a black screen that looks like it'll play but then goes fully balack and stops working. Anyone having toruble like this?
specs:
AMD FX 8350(8 core)
670 gtx graphics card
8 gig ram
windows 10 64bit

Hello, I have exactly the same problem using the launcher.
Computer spec:
Intel i7-6700k
Nvidia Geforece 1080
16GB Ram
Win 10 64

What I do not understand is that launching Crysis Warhead in exactly the same way works fine but no matter what I try I cannot get Crysis 1 to get past the black screen and program has stopped running before the game initialises.

Having the exact same problem, the launcher didn't help. It keeps crashing 5 seconds into starting. Warhead works fine for me.

Same problem

in the bin

in bin64 both crisis exe render a failre

in bin 32 it works but not in 64 bit and crshes every other time


assume my rig is perfect, on win 7 64, crash, on win 8.1 crash , on win 2012r2 crash.


Only the gimped crisis 32 dx9 woks sporadically


this is a dx10 title, with 64bit exe --WHY will it not work????

Tried doing that and I checked one of the GameuxInstallHelper and this error popped up after it crashed,

TLOSS error
SING error
DOMAIN error
R6034
An application has made an attempt to load the C runtime library incorrectly.
Please contact the application's support team for more information.
R6033
- Attempt to use MSIL code from this assembly during native code initialization
This indicates a bug in your application. It is most likely the result of calling an MSIL-compiled (/clr) function from a native constructor or from DllMain.
R6032
- not enough space for locale information
R6031
- Attempt to initialize the CRT more than once.
This indicates a bug in your application.
R6030
- CRT not initialized
R6028
- unable to initialize heap
R6027
- not enough space for lowio initialization
R6026
- not enough space for stdio initialization
R6025
- pure virtual function call
R6024
- not enough space for _onexit/atexit table
R6019
- unable to open console device
R6018
- unexpected heap error
R6017
- unexpected multithread lock error
R6016
- not enough space for thread data

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
R6009
- not enough space for environment
R6008
- not enough space for arguments
R6002
- floating point support not loaded
Microsoft Visual C++ Runtime Library

<program name unknown> Runtime Error!

Program: InitializeCriticalSectionAndSpinCount k e r n e l 3 2 . d l l

I'm getting the exact same problem. I can run the game perfectly fine in 32 bit mode, which is really frustrating me right now.

Same here. Game crashes about 30 seconds after I get to the menu.

Specs:

i7 5930k
GeForce GTX 970 SLI
32 GB RAM
Win 10 x64

EDIT: 32-bit exe runs fine if I launch manually. If I launch using either GOG Galaxy or the CrysisLauncher, game crashes.

Windows 7 Pro SP1
core i7 6700 @4.0GHz
GTX 980 Ti
16 GB RAM


For me the game crashes when launched through Galaxy, but works fine when using the "Launch Crysis" shortcut or CrysisLauncher.exe.

Launching through Galaxy gives the following crash report:

Problem signature:
Problem Event Name: APPCRASH
Application Name: crysis64.exe
Application Version: 1.1.1.6156
Application Timestamp: 47d6d9cf
Fault Module Name: CrySystem.dll
Fault Module Version: 1.1.1.6156
Fault Module Timestamp: 47d6e0a0
Exception Code: c000008f
Exception Offset: 0000000000085bdc
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 60db
Additional Information 2: 60db409c8e62fe1fe3105063242f3fa5
Additional Information 3: 0fda
Additional Information 4: 0fda0e4cf1ebe277da1b34573a415a64

Tried to launch it multiple times but it still crashes.

Win 7 Pro SP1
Core i5-2500k @ 3.3 GHz
Radeon HD 6850
8 Gb RAM


I get the same error report as ThreeSon posted above when launching from GOG Galaxy. I tried all the other methods listed in this thread and none of them worked.

In the bin64 folder, crysis.exe works but crysis 64.exe does not work, i run directly crysis.exe but i do not know if it's really a 64 version

It really is a 64 bit. If you use high texture mods you find out that those can only be run of the x64 version without crashing.
The game never started with the crysis64.exe, not even back in 2007, but it is required I believe.

My main PC has an AMD FX 8350, R9 290 w/ a 2560*1440 monitor, & Win 7 x64 Home. Crysis crashes on launch on it.

My spare-parts PC has a Phenom II 955, Radeon HD 6850 w/ a 1920*1080 monitor, & Win 7 x64 Pro. Crysis runs on it.

What could be the holdup for Crysis? It's unfortunate that Crysis only runs on my significantly-less-powerful PC.

What exactly does CrysisLauncher.exe do aside from setting core affinity (and why is that even necessary)?