xSound logs
Log started: 24 Sep 2026 9:06:39pm
v1.2.13.0
Windows 10
x64
FxSound logs
Log started: 27 Sep 2026 4:18:33pm
v1.2.13.0 <<<< NOT LATEST get v1.2.15.0 (I’m just a user)
Windows 10 (actually its 11)
x64
Unhandled exception
Exception code: 0xC0000005 (means illegal address)
Exception flags: 0x0
Exception address: 0x00007FF7CF908913 (illegal)
Tony
EE since 1975
My “System Informer” module list for v1.2.15.0
Has no module at above address
I did an update just now – I had thought my installation was set to auto-update.
Ho do I tell which version I am currently using?
@integrate Thanks for sharing the crash dump file. I am looking into the fix to avoid the crash.
Can you please confirm if the physical RAM on your PC is 4GB?
When FxSound crashes can you please observe the applications/processes which are consuming most of the memory from Task Manager.
@sunnysky Can you please share the fxsound.dmp crash dump file at Submit Files - Dropbox. It will help me investigate if both crashes are the same.
I already did that
I do not know how to determine the RAM. Please advise
I never know when it actually crashes. It’s just there are times I go to use it after a few hours sometimes (not always) it is no longer there – closed down by itself.
I never have problems. But then I have 16 GB of RAM.
I was just analyzing @integrate’s log with Comet browser assistant called Perplexity AI.
WIth only 4GB, that is like a compact 4 cylinder engine driving a tank (Windoze).
