Crash Offsets
-
I wasn’t thinking that, grateful for any feedback. I dug out some files of my own I had backed up last used on windows 10 , it wasn’t an issue I was experiencing then, but it is a newer pc build, so it could be hardware related even if it seems unlikely to me. I built it a couple of years ago now so if there were any instability issues I should have caught them long ago.
I tried FLScan on the files and didn’t catch any errors, but I think what I’ll do is try the HD install and see if that runs stable. That should tell me something useful.
Thanks for pointing me in some kind of direction.
-
I installed FL from my old disc, do you think that’s an issue nowadays?
-
Good to know.
-
Happens on Freelancer HD, interestingly doesn’t happen on Discovery. Can zip around online there no probs.
-
I wonder if the problem is your save directory since you mentioned it crashes on dock. Perhaps OneDrive sync or anti virus or something is causing a file lock? There’s an option in the HD installer to change the save location.
-
HD mod saves in its own folder, still in docs though. Are you saying to move it out of docs somewhere else. HD mod is installed on a different drive as well, on an ssd, could move the save folder onto that drive as well.
Disco deletes single player saves when you start the launcher, so I only play it online, but what it does store is in the standard FL save folder.
I thought maybe it was jflp.dll because I’m not using much at all, HD mod uses it but Disco doesn’t, so I disabled it, but it still crashed on dock after a while.
It did catch a couple of other errors last night when it crashed, all 3 errors at the same time, but in this order.
Faulting application name: Freelancer.exe, version: 1.0.1223.11, time stamp: 0x3e401b79
Faulting module name: Common.dll, version: 1.0.1223.11, time stamp: 0x3e401cd3
Exception code: 0xc0000005
Fault offset: 0x000af6fc
Faulting process id: 0x0x13F0Faulting application name: Freelancer.exe, version: 1.0.1223.11, time stamp: 0x3e401b79
Faulting module name: Common.dll, version: 1.0.1223.11, time stamp: 0x3e401cd3
Exception code: 0xc0000005
Fault offset: 0x000af6fc
Faulting process id: 0x0x28E4Faulting application name: Freelancer.exe, version: 1.0.1223.11, time stamp: 0x3e401b79
Faulting module name: Common.dll, version: 1.0.1223.11, time stamp: 0x3e401cd3
Exception code: 0xc0000005
Fault offset: 0x000af6fc
Faulting process id: 0x0x2E10 -
This is all the different offsets I have this year, mostly not in the crash offsets list, anyone have any info on how I debug this?
-----My Files-----
Common.dll 0x000c21de
Common.dll 0x00091eb8
Common.dll 0x00010d61
Common.dll 0x000af6fcContent.dll 0x000c458f (Possibly related to missing faction entries in an mbases.ini entry)
Content.dll 0x000d9021EngBase.dll 0x0000eab5
alchemy.dll 0x0000701b (Rare crash, occurs inconsistently when creating an instant jump fx)
SERVER.dll 0x0006d276
KERNEL32.DLL 0x0005b37e
ntdll.dll 0x00049585
ntdll.dll 0x00049575-----HD MOD-----
alchemy.dll 0x0000701b (Rare crash, occurs inconsistently when creating an instant jump fx)
ntdll.dll 0x00047418-----DISCO------
Common.dll 0x00091f38 (ship_archetype = <blank> in players file)
Freelancer.exe 0x0001b061 -
I’m actually only using jflp.dll, hudshift.dll, mp3codec.dll, and the stuff you very kindly made for me, matchjob.dll, poststorydiff.dll, and if I’m not using the last one I use matchplayer.dll instead.
I can remember when you made matchplayer I said it doesn’t work, and you said are you using 1.0, which I was, so you changed it to work with 1.0, being the saint that you are! So am I in a pickle here with using a mix of some things that should be 1.0 and some that should be 1.1, and what should I do about that, move to 1.1 do you think.
I am using the difficulty modifiers on the HD mod as well if that might cause an issue.
-
There’s no requirement for 1.1 on the client, it’s more a server side thing. He was pointing out the difference in the errors you are seeing.
HD edition should be the 1.1 common.dll afaik.
If you are installing the 1.0 version of the game from ISO, and then use the HD edition installer, you will end up with an up to date and patched version. During the installer/setup make sure to choose the different save folder option.
If in THIS state it still has the same issues with crashes then there is definitely something wrong that’s more systemic/unique to your machine/software setup.