64 Bit crashing woes

I've got the exact same issue on RES sites. Mostly High and Hazardrous. Usually when i'm attacking condas. Now this is really annoying. Bugs can be tolerated. Crashes like these need to be fixed ASAP.

I have the exact same issue. Only ever crashes in a High or Haz Res, when fighting an Anaconda. Usually at close range. And this is with 1.5.0.2 (64bit) on
AMD FX 8320
8GB DDR3
Sapphire HD 6870
Windows 10 64bit

It's never cost me anything, except If I'm fighting alone, the RES is empty when I get back and reloads different ships.
 
The 64 bit version does crash in RES sites, it's a known issue and the devs are investigating. I run the 32 bit version atm, waiting for the fix. There's a thread on it somewhere in the bug reporting forum.

Edit: I've not actually noticed any difference between the 32 and 64 bit versions, other than the crashing. You can even land on planets still.

My spec:
i7 4790k
16GB DDR3
GTX 980
Win 7 x64
 
Last edited:
Sigh, if the devs are still investigating there are no hopes for today's update. Damn.. I'm a hunter. How do ppl expect me to do a living if I don't have RES sites? :(
 
Happens to me as well, usually after being on the surface after a few minutes :( In space, no problems at all.
 
Ok, so here is the deal for me. I was experiencing either freeze up screen with the sound keeps going or the Black screen or even a complete drop to the desktop. Sound familiar? Mostly when leaving a Hi Res or any Res zone.
I simply turned off my Elite Dangerous Launcher at the beginning of my Client launch. I only play with the Client running in the background and guess what? ALL my problems have been solved. I had not one drop or frozen screen since, for over a week now. I cannot speak to your own personal problems, but some of you may benefit from this idea to one degree or another. Good Luck.
 
Last edited:
This is downside to PCs.

The code can run perfectly on one system, and crash on another.

While it could be a "bug" there are a lot more possibilities:

Virus
Dust
Poor ventilation of the case
marginal power supply
flaky but not failing components
old drivers
old firmware
corrupt files
etc.
etc.
etc.

Horizons really pushes the edge of most rigs. I would expect to see problems on a system that had an issue but is never stressed enough to cause continuous failures while just web browsing or using Office.
Horizons is no different than when Crysis came out, or other game that really stressed systems. It is just the nature of the beast since there is no fixed config like the XBone

Horizons 2.0 crashes for me no more often than 1.0
 
If overclocking CPU or GPU it's important to ensure absolute stability.

My PC is heavily overclocked: CPU at 4.8ghz, GPU = 145mhz on core and 155mhz vram, my 16gb DDR3 is overclocked from 1866 to 2133mhz. I ensure system stability with prime32 test once in a while. It should be able to prime for many hours without issue.

GPU overclock can be tested with EVGA precision X with the additional artifact scanner addon.

Also the MSI GPU burn test is another option.

Of course if you're not overclocking then I just wasted my time typing all this.

Then again perhaps you take part in liquid nitrogen overclocking parties in which case I just wasted my time typing all this.

Also important are the windows performance and stability updates.
 
Last edited:
Well, the thing is, it's just Elite: Dangerous 64 bit. No other games or programs are crapping out. If it was overclocking, wouldn't you think you would have issues with other programs? Or is Elite: Dangerous just the most sensitive program to CPU clocks?

The game its self is not really taxing my system, so I don't think it's a stress issue either. i7 4790k / 16GB 1800 RAM / R295X2 GPU

The only other thing I can think of is that it might be a multi-GPU thing.
 
No issues here.

Well I had a small issue sounding like yours, but in all games. Very rare tho.

Was due to an unstable driver for my Intel(R) 100 Series/C230 Series Chipset Family SMBus - A123 and Intel(R) 100 Series/C230 Series Chipset Family Thermal subsystem - A131. After update I haven't experienced anything.
 
Hi OP. I think I had something akin to your problem. After an hour or so ED would freeze/stutter in CZs. I reported it to FD who helped me try and solve the problem. With some of their ideas, and my own, I removed Geforce Experience and reinstalled GFX, WiFi, and other drivers. This seemed to do the trick, but I am keeping a weary eye just in case it happens again.

Good luck OP! :)
 
This is downside to PCs.

The code can run perfectly on one system, and crash on another.

While it could be a "bug" there are a lot more possibilities:

Virus
Dust
Poor ventilation of the case
marginal power supply
flaky but not failing components
old drivers
old firmware
corrupt files
etc.
etc.
etc.

Horizons really pushes the edge of most rigs. I would expect to see problems on a system that had an issue but is never stressed enough to cause continuous failures while just web browsing or using Office.
Horizons is no different than when Crysis came out, or other game that really stressed systems. It is just the nature of the beast since there is no fixed config like the XBone

Horizons 2.0 crashes for me no more often than 1.0

There is some truth in this, however, the developers have acknowledged that this is an known issue and they are currently investigating.
 
My system was freezing/crashing out after Horizons as well.... but I found out the problem.

1> I recently upgraded from a 560ti to a 970 vid card.
2> I was stressing a very old 600 watt power supply that I carried over through the last couple system upgrades.

Though the power supply supposedly had plenty of juice given my system components, it was very old and with the vid card upgrade it changed the power requirements for the system overall. This change in load caused my PSU to become unstable. It completely died soon after. I threw in a 750 watt PSU and my system has been very stable since.

Power supplies are finicky beasts.. especially when they get grey hairs.
 
Last edited:
Back
Top Bottom