Crash Offsets
-
IrateRedKite Administrators Historic Supporter Wiki Contributorreplied to josbyte on last edited by
@josbyte I鈥檒l add this to the wiki, but which dll file is the crash occurring in? My guess would be common.dll or freelancer.exe but I don鈥檛 have the time to replicate the crash at the moment
-
Nombre de aplicaci贸n con errores: Freelancer.exe, versi贸n: 1.0.1223.11, marca de tiempo: 0x3e401b79
Nombre del m贸dulo con errores: unknown, versi贸n: 0.0.0.0, marca de tiempo: 0x00000000
C贸digo de excepci贸n: 0xc0000005
Desplazamiento con errores: 0x2a397241
Id. de proceso con errores: 0x3FE4Right! sorry, tho it says unknown, maybe it is just fl.exe itself
-
Curious, I鈥檒l hold off on adding this and see if I can鈥檛 replicate the crash on a pure vanilla install and get a faulting module this afternoon. At what point does the crash occur, presumably when attempting to spawn the NPC?
-
I keep getting crashes on docking in single player, usually after about 30 mins or so of playing, always on dock, but could be any base, anywhere. The process id changes but the rest remains the same. Weirding me out now, this game is getting hard to run stable as time goes on. Any of this mean anything to anyone please?
Faulting application name: Freelancer.exe, version: 1.0.1223.11
Faulting module name: ntdll.dll, version: 10.0.22621.4541
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dllsome examples
Exception code: 0xc0000005
Fault offset: 0x00049575
Faulting process id: 0x0x1D9CException code: 0xc0000005
Fault offset: 0x00049575
Faulting process id: 0x0x2EE0Exception code: 0xc0000005
Fault offset: 0x00049575
Faulting process id: 0x0x90Exception code: 0xc0000005
Fault offset: 0x00049585
Faulting process id: 0x0x3C9CException code: 0xc0000005
Fault offset: 0x00049585
Faulting process id: 0x0x39A8Exception code: 0xc0000005
Fault offset: 0x00049585
Faulting process id: 0x0x367CException code: 0xc0000005
Fault offset: 0x00049585
Faulting process id: 0x0x6B8Exception code: 0xc0000005
Fault offset: 0x00049585
Faulting process id: 0x0x3F84 -
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鈥檚 something else deeper in the system. Exception 0xc0000005 is something called STATUS_ACCESS_VIOLATION. It usually means there鈥檚 something trying to be read (from memory or storage) and it expects a value but isn鈥檛 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鈥檇 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鈥檚 nothing much else in there other than FL going back the whole year. The GOG launcher shows up a couple of times.
I鈥檓 not using anything here other than JFLP and a couple of Adoxa鈥檚 other DLL鈥檚 either, but windows 11 became a solid bitch to me for running FL.
I鈥檒l run a few tests just in case, doesn鈥檛 hurt now and then. Thanks.
-
Please don鈥檛 take this as me dismissing what you are saying - this isn鈥檛 a common issue with FL, and the faulting DLL and offset isn鈥檛 directly Freelancer related its a more generic error, either in software, drivers, or hardware.
So, if you are saying it鈥檚 only happening with Freelancer then it鈥檚 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鈥檛 installed FL from virtual CD/ISO.
-
I wasn鈥檛 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鈥檛 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鈥檛 catch any errors, but I think what I鈥檒l 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鈥檚 an issue nowadays?
-
Good to know.
-
Happens on Freelancer HD, interestingly doesn鈥檛 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鈥檚 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鈥檓 not using much at all, HD mod uses it but Disco doesn鈥檛, 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鈥檓 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鈥檓 not using the last one I use matchplayer.dll instead.
I can remember when you made matchplayer I said it doesn鈥檛 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鈥檚 no requirement for 1.1 on the client, it鈥檚 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鈥檚 more systemic/unique to your machine/software setup.