64 Bit crashing woes

[OCD]

Yup its been a misery since the current update went live

when we are in busy res sites we get crashes every 20-30 mins

The game locks up on my system and I have to kill the process - no "send crash file" comes up

If we dont all get booted out the instance - when the person who crashes comes back in - everybody else gets kicked out

the common factor ive noted over the last week is it happens only in busy res sites and especially if youve just killed a conda (high object count!)

This is not, for me, a stable version

Have all the latest drivers etc and all other games are fine

- - - - - Additional Content Posted / Auto Merge - - - - -

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.

Yup - im SLI also (2 x 980ti's)

HOWEVER ... I have 4 mates - all with differing PC's and non SLI and they get this also with the 64bit current version ... since the last release
so these are just stability issues in the code due to the high level of change brought in .... and not put through a long enough beta programme
as they wanted it revenued before xmas !

- - - - - Additional Content Posted / Auto Merge - - - - -

since 2.0 is out I had about 30 crashes already. Bad bad bad

same here and I burn tested my pc earlier today for an hour at 100% cpu and gpu .... not a glitch

 

[Jypson]

Yup - im SLI also (2 x 980ti's)

HOWEVER ... I have 4 mates - all with differing PC's and non SLI and they get this also with the 64bit current version ... since the last release
so these are just stability issues in the code due to the high level of change brought in .... and not put through a long enough beta programme
as they wanted it revenued before xmas !

Yeah, I think that's the real culprit right there. It's a BIG update, and it felt kinda rushed out the door. I would say, let's hope 2.1 will fix things! But we already know how that works

 

[MottiKhan]

They're working on the freezing in RES issue. https://forums.frontier.co.uk/showthread.php?t=217773&p=3344247&viewfull=1#post3344247

We've been reporting it since 1.5/2.0 was released.

 

[EDbubba]

Crash? What crash?

Been playing ED since Beta, and generally speaking it's been really solid, maybe crashing once one twice over the course of the past year, and that is on at least four completely different platforms. Over 750 hours to date on my account, some sessions lasting 6+ hours.

2.0/Horizons didn't seem to be any issue at all, and I've recently been mucking-around with an ancient dual-Opteron workstation (dual-quad 2.7GHz Shanghai), and with a 290x, it still works fine, frame rates are only marginally lower than a 3.3GHz i5, running native 4k (real 4k, not super-sampled). Been running long-range smuggling missions and HAZ Res farming; zero issues, playing for upwards of 6+ hours continuously.


My past experience has shown that overclocking (i7 2600k) can lead to erratic results, with some applications apparently working absolutely fine, and others crashing.

Generally speaking, there's hardly any game in existence that will max-out a modern multi-core 'processor. Processor "speed" at 1080p+ resolutions and decent fidelity usually has a trivial impact on framerates. (is 90FPS really "better" than 80FPS? No, not in any perceptible way for the vast majority of gamers....)

Your GPU is the ultimate bottleneck, so messing around with CPU overclocking, and RAM timings are a fool's errand, looking for "performance" in the wrong places!

Revert to BIOS defaults and enjoy the stability!

 

[=Phoenix=]

Anyone else experiencing random crashes with the 64 bitt version? I get at least 1-2 random crashes when running the 64 bit version of Horizons... the screen just locks up with the sound looping. The scary bit is that it does it when I'm in the middle of heated battle in a HREZ. Luckily if Im quick enough to ctrl-alt-del and end the task and reload, I dont get penalized and can get back into the fight. Scary when you're sitting on a few million credits for bounties and there's a chance you might get blown up by the time you reload.
.
Don't seem to have any issues running the 32 bit version.

.
The problem could be due to a number of issues, my advice is to update your drivers and try turning all your graphics settings way down. Plus try turning on the vertical sync option OR the frame rate limiter. Reason being graphics card overheating can cause system freezes, although you would expect to see artifacts onscreen, its definitely worth exploring.
.
My experience of the client has been pretty good. I have had the odd crash for sure, but lately both the 32Bit and 64Bit client are pretty rock solid, which is what makes me suspect your hardware/drivers.
.
Although you say the 32Bit client runs fine, if you can't resolve it I would suggest going back to running that for doing combat sessions in Res/HiRes, until the next update.

 

[EDbubba]

They're working on the freezing in RES issue. https://forums.frontier.co.uk/showthread.php?t=217773&p=3344247&viewfull=1#post3344247

We've been reporting it since 1.5/2.0 was released.

Must be platform-specific since I've put at least 50 hours into the past few RES CG's (Hel and Dahan) and have zero issues, on two utterly different platforms (other than a common Radeon 290x).

 

[Kandarus]

I'm running a i7-4790k, 16GB 2400Mhz Corsair RAM, Gigabyte GTX970-4GB, Gigabyte H87-D3H MB, 480GB Corsair SSD etc etc.
NVidia drivers are all up to date etc and not having any other random crashes with anything else running.

Only red flag I see is that you are running a 4790k on a H87 mobo. Have you checked your voltages?

Reason why I ask:

[video=youtube;dRB22cx3EWo]http://www.youtube.com/watch?v=dRB22cx3EWo&t=0m30s[/video]

 

[EDbubba]

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.

This is a known bug with the ED launcher; you're not running the "32-bit" version with a Horizons account, it's just the same 64-bit version.

Placebo-effect in full-force...

 

[grammatonfeather]

Been playing ED since Beta, and generally speaking it's been really solid, maybe crashing once one twice over the course of the past year, and that is on at least four completely different platforms. Over 750 hours to date on my account, some sessions lasting 6+ hours.

2.0/Horizons didn't seem to be any issue at all, and I've recently been mucking-around with an ancient dual-Opteron workstation (dual-quad 2.7GHz Shanghai), and with a 290x, it still works fine, frame rates are only marginally lower than an 3.3GHz i5, running native 4k (real 4k, not super-sampled).


My past experience has shown that overclocking (i7 2600k) can lead to erratic results, with some applications apparently working absolutely fine, and others crashing.

Generally speaking, there's hardly any game in existence that will max-out a modern multi-core 'processor. Processor "speed" at 1080p+ resolutions and decent fidelity usually has a trivial impact on framerates.

Your GPU is the ultimate bottleneck, so messing around with CPU overclocking, and RAM timings are a fool's errand, looking for "performance" in the wrong places!

Revert to BIOS defaults and enjoy the stability!

Below DX12 CPU/GPU transfer isn't very efficient and when you have a powerful GPU that can be more demanding on CPU. I notice a big difference on my system even if I knock the overclock back to 4.2ghz. Now if you have a much more modern CPU then the overclocking isn't so critical. I'm using i5 2500k which is ancient now so I guess people with very recent designs can get away without it. Overclocking my GPU gives me an average of 20 fps more.

My overclock performance is very noticeable even on windows desktop.

It also depends on the game.

 

[vrsterling]

I didn't know this was a known issue, I thought it was just going to be another case of having to modify my settings afer a major update. I get random lockups in the heat of battle in extraction sites and sometimes just getting into the game can require a few restarts as the loading screen will sometimes freeze.
I'm running Elite on a custom build with the following:
CPU - i7 5960x (OC'd to 4.5GHz)
RAM - 32 Gb DDR4 @ 2.6 GHz
GPU - GTX 980 x2 SLI (spanned across three 1080p monitors)

In short I should have no problems running the game as I more than meet the specs required. I never experienced any technical issues until Horizons. Im sure this issue with be addressed quite soon if it is a known problem. Frontier is one of the rare companies that actually listen to their user base.

 

[EDbubba]

...My overclock performance is very noticeable even on windows desktop./QUOTE]

Huh?

Your CPU is basically idling while on the Windows Desktop... Open the Windows Resource Monitor and look at your CPU utilization, you'll see that it is probably less than 10% (usually less than 5%), with your core speed dropped to about 1/4-1/3 of maximum.

Active background processes (virus scans, etc) might increase the utilization in small bursts, but you'll find these baseline numbers to be pretty predictable.

Overclocking has next-to-no effect on the Windows desktop, even with lots of apparently active applications open (browsers, productivity apps, etc). If you don't see a consistent 100% utilization and speed at the default clockspeed while working in a typical manner, then your overclock is utterly meaningless. The same goes for any "taxing" game/application.

SSDs and other things, like more (not "faster") RAM, that increase throughput and decrease latency will make Windows feel "faster", but the CPU itself (Celeron vs. i7) will have a negligible impact.


If you look at the utilization history of a 3.0GHz i5 while playing ED (Horizons), you'll see that it's somewhere in the 40% range, with the CPU peaking between 50%-75% utilization/speed (utilization and core speed are highly-related), with the occasional burst to near 100%, and below 50% for most of the time.

Windows 7 and above are extremely good at dynamically adapting to the code overhead that is presented and CPU power management, with power and utilization changes happening in microseconds. Basically, the average desktop CPU spends most of it's life essentially idling...

As mentioned, "overclocking" is a major placebo-effect for most users, unless you like to run pointless "torture" apps that max-out the cores.


FYI, years ago I was running an i7 2600k and I hadn't noticed that the CPU fan had seized, and was not turning! We played our weekly LAN gaming sessions as usual with no noticeable effect, but it was only when I was running a CAD program that was rendering in the background did I get weird stutters (CPU throttling back, hard), and that is what led me to look inside the case and notice the stationary fan!

The takeaway was the vast majority of games we played didn't tax the CPU in any significant way.

Another thing I noted that even fairly modest air-cooled 2600k overclocks that seemed stable, would reliably crash the CAD program while rendering, but not trip-up Prime 95 or other tests like that. No idea why this happened, but it was probably a convergence of factors that normally didn't occur.

 

[CMDR Byr Goefin]

There is some truth in this, however, the developers have acknowledged that this is an known issue and they are currently investigating.

Well, that solves it then. Can you point us to that acknowledgment?

- - - - - Additional Content Posted / Auto Merge - - - - -

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.

Apparently already said by Devs there is an issue.

But... how many 64bit engine games do you play? There is less than 10 that I know of. Do they run ok?

 

[Jypson]

But... how many 64bit engine games do you play? There is less than 10 that I know of. Do they run ok?

Ah, an interesting question! I'm having a hard time finding a list of 64-bit games out right now; most recent list I can find is from 2014. Anywho, I'm a bit of a game junky and am able to play just about anything maxed out right now that supports crossfire. Games with known crossfire issues don't run that great (ie. Batman / Just Cause 3 / Shadow of Mordor)

 

[Fireslake]

I just purchased Dangerous last night and have been playing around with it today. I have not tried it in 32 bit mode, but in 64 bit it is completely unplayable. I will CTD in 5 - 10 minutes or I will get a blue screen of death. I am going to try it on 32 bit, but otherwise I'll move on. As others have stated I don't have any problems with any other games I play, and years ago I spent WAY too much time tweaking my system in order to get a game to run. No game is worth that to me these days. In any case, thanks for the information here.

- - - - - Additional Content Posted / Auto Merge - - - - -

Just tried to launch in 32-bit mode and the game won't even start. lol - have fun men...just not worth it.

 

[grammatonfeather]

...My overclock performance is very noticeable even on windows desktop./QUOTE]

Huh?

Your CPU is basically idling while on the Windows Desktop... Open the Windows Resource Monitor and look at your CPU utilization, you'll see that it is probably less than 10% (usually less than 5%), with your core speed dropped to about 1/4-1/3 of maximum.

Active background processes (virus scans, etc) might increase the utilization in small bursts, but you'll find these baseline numbers to be pretty predictable.

Overclocking has next-to-no effect on the Windows desktop, even with lots of apparently active applications open (browsers, productivity apps, etc). If you don't see a consistent 100% utilization and speed at the default clockspeed while working in a typical manner, then your overclock is utterly meaningless. The same goes for any "taxing" game/application.

SSDs and other things, like more (not "faster") RAM, that increase throughput and decrease latency will make Windows feel "faster", but the CPU itself (Celeron vs. i7) will have a negligible impact.


If you look at the utilization history of a 3.0GHz i5 while playing ED (Horizons), you'll see that it's somewhere in the 40% range, with the CPU peaking between 50%-75% utilization/speed (utilization and core speed are highly-related), with the occasional burst to near 100%, and below 50% for most of the time.

Windows 7 and above are extremely good at dynamically adapting to the code overhead that is presented and CPU power management, with power and utilization changes happening in microseconds. Basically, the average desktop CPU spends most of it's life essentially idling...

As mentioned, "overclocking" is a major placebo-effect for most users, unless you like to run pointless "torture" apps that max-out the cores.


FYI, years ago I was running an i7 2600k and I hadn't noticed that the CPU fan had seized, and was not turning! We played our weekly LAN gaming sessions as usual with no noticeable effect, but it was only when I was running a CAD program that was rendering in the background did I get weird stutters (CPU throttling back, hard), and that is what led me to look inside the case and notice the stationary fan!

The takeaway was the vast majority of games we played didn't tax the CPU in any significant way.

Another thing I noted that even fairly modest air-cooled 2600k overclocks that seemed stable, would reliably crash the CAD program while rendering, but not trip-up Prime 95 or other tests like that. No idea why this happened, but it was probably a convergence of factors that normally didn't occur.

Windows 7 is a slug that gets progressively slower. Out of 3 OS installed on an old laptop windows 7 performed the worst. Linux was slightly faster but windows 8 made it feel like a new machine.


http://www.bit-tech.net/hardware/cpus/2011/01/03/intel-sandy-bridge-review/10

Going back to the days of i5 2500k:

http://www.bit-tech.net/hardware/cpus/2011/01/03/intel-sandy-bridge-review/10

Overclocking brings significant boost for me with my old cpu. For the latest CPU it doesn't have any impact with a lot of games although I did note some increase on a few reviews.

I really do need to update to the latest CPU and I certainly will be overclocking it although it won't impact many games (FSX with HD scenery will certainly benefit) I do 3d rendering as well and already get a boost for that with my overclocked 2500k.

If I knocked my cpu back to default speed I would notice a slowdown in all areas. Booting, browser opening, page loading and certainly modeling and rendering.

It's certainly impressive that much newer CPU designs are able to max game performance at default speeds. That alone is incentive for me to upgrade.

 

[x76]

I've had a few instances where I have to do a cold boot, the computer is just plain locked up. Of course, it's a 20 minute process to reboot and get the game to load again. Yesterday I had a new error informing me that a player was on the same server but running an older version of the game.

Alternately, I've lost ships when I get dumped out too close to a target star! I try and pull away but it's all over. Is there some setting I'm unaware of that might dump me out maybe 50 clicks from a star for safety?!?

 

[grammatonfeather]

Why 20 mins to reboot?

You're on SSD?

 

[x76]

lol, no, I'm amongst the "Compute Shaders" crowd. The game appears to hang at that point, but if you leave it alone for a while, it will a) start the game b) generate a crash report c) play just fine! But from crash to game again, it's the better part of 20 minutes.

 

[CMDR Byr Goefin]

I've had a few instances where I have to do a cold boot, the computer is just plain locked up. Of course, it's a 20 minute process to reboot and get the game to load again. Yesterday I had a new error informing me that a player was on the same server but running an older version of the game.

Alternately, I've lost ships when I get dumped out too close to a target star! I try and pull away but it's all over. Is there some setting I'm unaware of that might dump me out maybe 50 clicks from a star for safety?!?

Throttle down before you exit jump.

 

[DanTheMan]

I too am getting lots of problems. Mostly Sound-freezes/stutters followed by CTD and out of the game.

Latest upgrades have been a new CPU and new RAM (as per minimum go fwd spec from FD).

I'm happy to believe its my rig (for the moment) but I have no crashes in any other applications (ED is the most demanding I have).