Crash Offsets

This will probably be better dealt with on the Starport discord in #help-and-support, but here goes. This seems unique to your system.

ntddll.dll is probably not the cause, it’s something else deeper in the system. Exception 0xc0000005 is something called STATUS_ACCESS_VIOLATION. It usually means there’s something trying to be read (from memory or storage) and it expects a value but isn’t getting one.

Do you have this same issue with any other games/software? This type of issue has been seen across a multitude of other software in the past. I’d lean more towards driver software, and potential hardware issues.

Maybe do a Memtest/Windows Memory diagnostic tool. And then do a benchmark/health test with CrystalDiskMark. Check your temps with HWInfo etc.

My system is good, it gets a hammering with modern games without issues, there’s nothing much else in there other than FL going back the whole year. The GOG launcher shows up a couple of times.

I’m not using anything here other than JFLP and a couple of Adoxa’s other DLL’s either, but windows 11 became a solid bitch to me for running FL.

I’ll run a few tests just in case, doesn’t hurt now and then. Thanks.

Please don’t take this as me dismissing what you are saying - this isn’t a common issue with FL, and the faulting DLL and offset isn’t directly Freelancer related its a more generic error, either in software, drivers, or hardware.

So, if you are saying it’s only happening with Freelancer then it’s isolated to how the game uses the system.

My only suggestions then are plugins, can you try disabling all plugins and play a while without them? Just to isolate this. It could be that since some of these plugins are quite old that they are making calls to Windows API that are no longer valid.

Also, since FL uses older DirectX components, you might want to run the DirectX web runtime if you haven’t installed FL from virtual CD/ISO.

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?

No, the original disc/ISO is known working, as is the Vanilla install, on Windows 11.

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.

That could be it - Discovery saves elsewhere doesn’t it? Plus it might explain the ntdll.dll generic error. Since it’s not a Freelancer module that’s faulting.

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: 0x0x13F0

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: 0x0x28E4

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: 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 0x000af6fc

Content.dll 0x000c458f (Possibly related to missing faction entries in an mbases.ini entry)
Content.dll 0x000d9021

EngBase.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

@Timmy51m said in Crash Offsets:

Common.dll, version: 1.0.1223.11

That’s the original 1.0 DLL, most patches assume 1.1 (1.0.1254.11; JFLP will work with both, but most of my other stuff is 1.1 only).

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.

@Bolte with regards to patches like JFLP, the version absolutely matters as memory addresses are different. This could very well be the cause of @Timmy51m’s crashes here.

If I’m remembering correctly here, his original issue was crashing to desktop on single player.

And he later said it happens on HD edition which is already 1.1

But, curiously not happening on Discovery.

" 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 2 potential problems here:

• Using old game files
• New PC build

"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! "

He’s using a plugin that works for 1.0, unless I’m missunderstanding things. But, would that even matter on singleplayer? Was Vanilla having CTDs every half hour or so on docking a thing when Vanilla was played beforr 1.1 came out?

In any case, it seems like the options are either:

1. A game files/plugin related issue
2. A system issue of some kind

So my thoughts still lean to going back to a clean setup with no plugins or alterations to see if the issue can be reproduced.

That is what I’ve been doing so our thinking is aligned. I’m running around on base jflp and it seems to be fine, without a 1.1 patch. I’m testing now with just Adoxa’s plugins I’ve mentioned on 1.0, so I’ll see how that goes. It might just be a case of ditching my old files, no big deal.

I don’t expect a game of this age to be flawless on windows 11 and newer hardware anyway, 10th gen intel and a 4060ti, an odd crash here and there will happen.

I’ve been flying a loop of planets, Manhattan to New Tokyo, to New London, to New Berlin and back to Manhattan. If it crashes on a dock with one of those planets, the autosave has me back to the system jumpgate entry, and then it docks fine at said planet. So it doesn’t seem to be related to the planet itself, which is what makes it hard to fathom. FLSpew has nothing other than system exit for the dock crash.

How to pin it down.

Process of elimination buddy.

Test, add a couple of plugins at a time, re-test until you experience the crash, then you can eliminate 1 by 1 until the crash is confirmed to be with the last plugin you removed.

Re-add that plugin and confirm if the crash is back so to confirm it’s not a fluke incidence.

Yeah cool, I’m wondering how the job board plugin works, is that something that only triggers when you open the job board itself, or would it cause something to happen on dock. The only other thing I have in mind, because it’s planets I’ve been seeing it on, is the scripts from this https://www.moddb.com/games/freelancer/addons/planetscapes-fixed-for-169-resolutions.

They’re all landing pad scripts, and it crashes as that would be loaded. That has a lot of downloads though and no mention of it.