Horizons Regular CTD's since update

[revporl]

Hi

I know a couple of people have mentioned this in passing but I am getting concerned about how often the game CTD's (and sometimes a full blue screen job) following the latest update. Every half hour or hour at the moment the program will CTD. It never did this at all before the update. I assumed that it was my graphics card overheating, but I've dialled everything down to low quality on the card and game settings and that has made no difference. It ran on high settings without a problem before the update. Its a Geforce GTX 760, I've 8gb RAm and an intel i7 850 running at 2.8ghz so it should be well into the comfort zone of what the program can run.

Someone else has mentioned that it could be to do with instancing with multiple players so I'm going to try solo mode but this is really getting on my nerves!

Has anyone else had similar problems as bad and how did you rectify it?

Thanks,
Paul

 

[Shadowdancer]

Blue screens mean that something is fishy with your system, be it hardware or drivers.

 

[revporl]

Yes I ran some crash dump analysis software on it it said....

On Mon 30/05/2016 09:41:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053016-16567-01.dmp
This was probably caused by the following module: afd.sys (0xFFFFF88004356597)
Bugcheck code: 0x50 (0xFFFFFA7FB5D19FAC, 0x1, 0xFFFFF88004356597, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Apparently afd.sys errors cause the blue screen crash quite often, they are a wondows NT component. Have run Winthruster which is a registry analyser and will try running EDH again in a bit.

Running in solo mode made no difference.

Thanks,
Paul

 

[Shadowdancer]

Try Blue Screen Viewer: http://www.nirsoft.net/utils/blue_screen_view.html

It should show you a trace for the crash that may point to a specific driver. I had frequent complete system freezes in E:⁠D that turned out to happen every time an audio device had a buffer underrun because their drivers were (and still are) ****.

 

[revporl]

Thanks for that.

Yes, that's pointing to ntoskrnl.exe as being the source which could mean corrupted RAM I think? But thats different to the network error suggested by the initial dump?

No other programs or games create an issue though, only EDH and only since the update.

Is there anything to try short of replacing/removing the RAM?

Thanks,
Paul

 

[Shadowdancer]

I'm not talking about the ends of the trace, see if you have stuff that looks like 3rd party drivers in between.

What kind of network hardware are you using? If you're using onboard, see if you can use drivers straight from the mainboard manufacturer old as they likely are. If you aren't using onboard, maybe try doing so

For RAM issues, you could try memtest86+ http://memtest86.com/

 

[DogTailRed2]

I get CTD's with the latest update but no blue screens.
I can CTD by going into the Cartographic screen, selling some data, then clicking exit.
Game will display the space station menu then immediately CTD.
Does this every time.
Before update I maybe had two CTD's in 18 months.
So something IS wrong with the game.

 

[Shadowdancer]

I can CTD by going into the Cartographic screen, selling some data, then clicking exit.
Game will display the space station menu then immediately CTD.

Cartographics can be cranky at times when you sell them lots of data, from what I read it seems like the number of systems per page is now just too big under some circumstances

 

[Whiteball]

No blue screens but definitely an increase in CTD.
CTDs have gone from practically none since Ed original Beta (not the recent beta) to quite a few.

I tried re-binding the 'open galaxy map' key to a HOTAS button. I can CTD every single time using a certain button combo without fail yet any other button works fine.