Log4OM

I am using Log4OM 2 v2.13.0.0. I get repeat symptoms of misbehavior that include, not responding to input, and becoming difficult to kill even using the Win10 Task Manager. There are times when it just disappears from the active execution list. I can restart it and it will work just fine but it it's running for too long (a few hours) it will either freeze or disappear again.
This is the Windows Event Log from this morning:
----------------------------------------------------------------------------------------------------------------------------
Log Name: Application
Source: Application Error
Date: 5/23/2021 10:21:56 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Dans-PC
Description:
Faulting application name: L4ONG.exe, version: 2.13.0.0, time stamp: 0x60801ab4
Faulting module name: clr.dll, version: 4.8.4341.0, time stamp: 0x6023024f
Exception code: 0xc00000fd
Fault offset: 0x0000f775
Faulting process id: 0x6070
Faulting application start time: 0x01d74fe1e6d6cb8e
Faulting application path: C:\Program Files (x86)\IW3HMH\Log4OM NextGen\L4ONG.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: c089f0b7-4cc5-41b8-ab64-5e5a6251a09b
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-05-23T15:21:56.1550571Z" />
<EventRecordID>131330</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Dans-PC</Computer>
<Security />
</System>
<EventData>
<Data>L4ONG.exe</Data>
<Data>2.13.0.0</Data>
<Data>60801ab4</Data>
<Data>clr.dll</Data>
<Data>4.8.4341.0</Data>
<Data>6023024f</Data>
<Data>c00000fd</Data>
<Data>0000f775</Data>
<Data>6070</Data>
<Data>01d74fe1e6d6cb8e</Data>
<Data>C:\Program Files (x86)\IW3HMH\Log4OM NextGen\L4ONG.exe</Data>
<Data>C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll</Data>
<Data>c089f0b7-4cc5-41b8-ab64-5e5a6251a09b</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
-------------------------------------------------------------------------------------------------------------------------------
I have uninstalled and reinstalled to no avail. The previous version (v2.12.0.0) was flawless.

I will move your post to the correct forum I nearly missed it because you posted to the version 1 forum which I no longer monitor regularly because version 1 is only on maintenance.

OK two things,

From the log it seems that you are running a very old version of Microsoft .net framework (4.0.3) which dates back I think to 2018, please update to the latest version

I see you tried a reinstall but was it a clean reinstall including removing/renaming the C:\Users\YOUR USER NAME\AppData\Roaming\Log4OM2 folder

Thanks for the reply Terry. Best I can see from Microsoft, .Net Framework 4.8 is the latest available and was released (as you say) in 2018. I did try to download and install it but the install balked saying there was a later version already installed. Updates to Win10 is supposed to also update .Net Framework. I have kept up with Windows Updates and as we speak I'm downloading 20H2.

I have not done that clean of an reinstall of Log4OM 2. I will try that and let you know the result.

Check your windows update history for .net update data

Try renaming the directory rather than deleting it then you can always revert

Terry,
I've updated the system to 20H2. There was a recent update to .Net 4.8 but, no newer .Net.

dmalcolm wrote: 23 May 2021, 23:03 Terry,
I've updated the system to 20H2. There was a recent update to .Net 4.8 but, no newer .Net.

4.8 I beleive is the latest so now you should suspect a corupt xml file in the Log4OM2 user folder so try a rename of the folder and a clean install.

Yes. That will be the next step if the problem was not solved by the system update. I actually don't expect a fix at this point but when the problem is resolved I would like to know which step fixed it.

dmalcolm wrote: 24 May 2021, 12:57 Yes. That will be the next step if the problem was not solved by the system update. I actually don't expect a fix at this point but when the problem is resolved I would like to know which step fixed it.

As none of the thousands of other Log4OM users have reported this it must be a local issue so all I can do is to try and help you find issue and resolve it, its not something we can fix by a software change.

BTW it would help to have a description of your PC and the windows version

Terry,
Been tied up with other things but still having an issue. Here is the data you requested:
Device name Dans-PC
Processor Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz 4.20 GHz
Installed RAM 32.0 GB
Device ID 2625BC49-1A05-4D2A-9A55-373E5501EA82
Product ID 00330-71323-23736-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

Edition Windows 10 Pro
Version 20H2
Installed on ‎9/‎19/‎2020
OS build 19042.985
Experience Windows Feature Experience Pack 120.2212.2020.0

I agree the problem is on my computer. Log4OM is the only program I have that has difficulty. Things have improved. If I only use Log4OM for a few minutes it will shutdown on its own. After that, I have to use task manager to stop it. Curiously it appears to still allow logging even after it will not allow me to gracefully shut it down. Logging is accomplished through WSJT-X and JTAlert. Both of those are the latest releases.