It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I can't play the game after the animated intro the moment the game starts to render and the space ship comes into view on the right the game crashes.

A dump file is created with:

The thread tried to read from or write to a virtual address for which it does not have the appropriate access.

If anyone can help me so I can play that be great.

I am on Windows 10 fall update, latest drivers, and hardware.
This question / problem has been solved by XPhilerimage
I am having the same issue, let me guess threadripper with 1080ti?

there is a thread on the game main technical support forum you may want to check out though no resolution as of yet.
Same here. But GTX 1080 (not Ti) and a Intel Xeon CPU E5-2630 V4 Processor.
avatar
XPhiler: I am having the same issue, let me guess threadripper with 1080ti?

there is a thread on the game main technical support forum you may want to check out though no resolution as of yet.
Yes! That is exactly my build(a 32 logical core 1950x).

:( damn it, well thank you very much for the info. I really have been dying to play the game, I really hope they fix it asap.
well seems like my theory is wrong, its not limited to threadrippers, so far i've seen 4 people report this same exact issue with threadrippers and 2 intel (one xeon, t3rminull above but one was a reqular quad core)

Cant figure out what it is but seems the exception is internal to the executable which makes it likely its a compiler issue i'd imagine.

Unfortuantely there is no news on the main forum either, as soon as something is posted there I will make sure to relay it here.
avatar
XPhiler: well seems like my theory is wrong, its not limited to threadrippers, so far i've seen 4 people report this same exact issue with threadrippers and 2 intel (one xeon, t3rminull above but one was a reqular quad core)

Cant figure out what it is but seems the exception is internal to the executable which makes it likely its a compiler issue i'd imagine.

Unfortuantely there is no news on the main forum either, as soon as something is posted there I will make sure to relay it here.
Yeah I have a friend who has the issue on a i7 as well. Hmm weird I wonder what it is, too bad they did not test it more :(

In Visual Studio the dump file only has "The thread tried to read from or write to a virtual address for which it does not have the appropriate access." and nothing else that can help isolate hint to the issue. I hope it is not the Fall Windows 10 update.

Cool that be really great, thanks again.
avatar
XPhiler: well seems like my theory is wrong, its not limited to threadrippers, so far i've seen 4 people report this same exact issue with threadrippers and 2 intel (one xeon, t3rminull above but one was a reqular quad core)

Cant figure out what it is but seems the exception is internal to the executable which makes it likely its a compiler issue i'd imagine.

Unfortuantely there is no news on the main forum either, as soon as something is posted there I will make sure to relay it here.
avatar
varkkon: Yeah I have a friend who has the issue on a i7 as well. Hmm weird I wonder what it is, too bad they did not test it more :(

In Visual Studio the dump file only has "The thread tried to read from or write to a virtual address for which it does not have the appropriate access." and nothing else that can help isolate hint to the issue. I hope it is not the Fall Windows 10 update.

Cool that be really great, thanks again.
hard to tell but if it was the fall windows 10 update i'd imagine there will be a truck load more with this issue.

I got a tiny bit more if you're interested:

FAULTING_IP:
ELEX+1a0a0c
00000001`401a0a0c 0f2941f0 movaps xmmword ptr [rcx-10h],xmm0

EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00000001401a0a0c (ELEX+0x00000000001a0a0c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000014136ce80
Attempt to write to address 000000014136ce80

DEFAULT_BUCKET_ID: INVALID_CLASS_PTR_WRITE

PROCESS_NAME: ELEX.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 000000014136ce80
WRITE_ADDRESS: 000000014136ce80

FOLLOWUP_IP:
ELEX+1a0a0c
00000001`401a0a0c 0f2941f0 movaps xmmword ptr [rcx-10h],xmm0

NTGLOBALFLAG: 0
FAULTING_THREAD: 0000000000004c68
PRIMARY_PROBLEM_CLASS: INVALID_CLASS_PTR_WRITE
BUGCHECK_STR: APPLICATION_FAULT_INVALID_CLASS_PTR_WRITE_INVALID_ POINTER_READ_INVALID_POINTER_WRITE
LAST_CONTROL_TRANSFER: from 0000000140f23018 to 00000001401a0a0c

STACK_TEXT:
ELEX+0x1a0a0c
ELEX+0xf23018
ELEX+0x13156
0xbd3b7f20
ELEX+0x1e40d
0x44dfc00
0xbd3b7f20
0xa0fc4ab0
0xa0fc4f70
0xa0fc4be0
0xa0fc4850
0xa0fc4980
0xa0fc4130
0xc04c540
0x10
0xa0fc3b40
ELEX+0x21a071
0xa0fc3c70
Attaching a picture of what we are seeing.
Attachments:
I have attached a picture as well of the crash/bug that is 100% reproducible in the exact same place every time no matter what you do. Basically all I do is start a new game and it happens every time, I have never gotten past this point in the game after the intro.

System specs:

MSI Geforce 1080 Ti * latest driver *
32 Gigs of 3200 DDR4
AMD Ryzen Threadripper 1950X
Windows 10 64bit with the Fall update
MSI X399 mobo
All the latest drivers
Attachments:
I run Shadowplay, it was causing the exact same crash you described above. So i turned it off and tried Afterburner, same crash... any overlay other then Galaxy crashes the game.

Whats odd is the first 2 hours Shadowplay worked fine!?
avatar
Starkrun: I run Shadowplay, it was causing the exact same crash you described above. So i turned it off and tried Afterburner, same crash... any overlay other then Galaxy crashes the game.

Whats odd is the first 2 hours Shadowplay worked fine!?
Hmm weird. I don't have Geforce Experience installed I use pure drivers only when I do a clean and custom installation on each new driver.

I don't have any monitoring software installed and am not even using Galaxy, I use the regular download files and then install the game manually.

Thanks for the heads up though, wish it solved my issue :( It is frustrating, I hate to refund the game have been waiting a long time to play it.
happy to report new patch 1.1 fixed the crash for me!
avatar
XPhiler: happy to report new patch 1.1 fixed the crash for me!
Same!!! The issues is 100% fixed when you apply patch 1.1. Looks like my weekend is going to own :)

Thank you devs for fixing the issue and XPhiler for the heads up on the patch.
Post edited October 20, 2017 by varkkon
avatar
XPhiler: happy to report new patch 1.1 fixed the crash for me!
avatar
varkkon: Same!!! The issues is 100% fixed when you apply patch 1.1. Looks like my weekend is going to own :)

Thank you devs for fixing the issue and XPhiler for the heads up on the patch.
I've got the same issue, but I'm getting only version 1.05c from GOG. Where did you guys get the 1.1 from?