n new computer (WIN11) UcxLog sometimes stops working with error message

[oh1nd]

In old computer, WIN10 operating system, I had never the attached error situation. In new PC, WIN11 home, this happens about every week. To recover from the error I have to close UcxLog and start again. Is there anything I can do to avoid this situation?

73 Juha OH1ND

[DL7UCX]

Hello Juha,

Such an error has not been reported so far.
I have no chance to find the cause with the error number.
is there a relation to any event?
Have you implemented all the virus scanner tips?

Try to update to version 8.44 Beta, there are more runtime checks implemented ...

73 Ben

[DL1EZ]

Hi Juha,

does this error (or similar) also pop up with other programs running than UcxLog?
It might be an idea to check the RAM for consistency with memtest86+ or something like that..

just my 2 cents, Holger

[oh1nd]

Thank you for answers,

I have my PC on from morning to late evening and UcxLog too. Sometimes in 24/7 mode. This error message does not appear every day.

With Task Manager I can see that there is enough memory available.

I also use JTDX (improved version) for FT8 mode many hour's every day mostly just monitoring. I noticed that JTDX has a setting for threads in use. I suppose this means the CPU cores it uses for decoding. Maybe I am wrong with this. Anyway earlier the setting was AUTO. I did reduce it to 4 that gives fast enough decoding. Possibly AUTO setting did try to use all resources and then sometimes that was too much and caused problems with UcxLog.

After a week or so I know if the setting change in JTDX has any effect.

73 Juha

using UcxLog more than 10 years

[DL1EZ]

Hi Juha,

I do use a "small and fairly old" computer with 4 CPU cores for UcxLog and JTDX and never ran into this kind of problem.
Also I do not think that it is related to the amount of memory availabel or the number of concurrent threads for JTDX.

My assumption is more into a hardware error or malfunction related to RAM (bit switch or defect cell etc.), so I again
suggest to run a memtest86+ from a bootmedia (not within Windows).

73 de Holger

[DL7UCX]

Hello,

UcxLog requires much less memory than other programs.
It uses several tasks in parallel but this is managed entirely by Windows.

I fear that the stability of modern PC hardware (and Windows) has not improved ...
Normally there are on home PCs no memory checks/error corrections active.
Also the stability and quality of drivers is not getting any better.

73 Ben

[oh1nd]

Thank you again for answers,

last two weeks have been without any errors.

Yes, memory is non-ecc type meaning no error correction.

I did run windows own memory test. That seems to exit windows and start the error test program from a simple text based program.
No errors were found. Later I may use the more advanced program if needed.

I believe that UcxLog has been ok all the time so this is my last message about this subject.

73 Juha OH1ND

[dk1wi]

Moin zusammen,

ich hänge mein Thema mal hier mit an. Irgendwie könnte es passen ...

Ich habe meinen Rechner im Rahmen der Umstellung auf WIN 11 geklont. Soweit hat das alles geklappt. Beim Update auf BETA 5 habe ich die angehängte Fehlermeldung bekommen. Danach kamen 3-4 weitere Fehlermeldungen. Nachdem ich die weggeklickt habe ist das Update problemlos gelaufen.

Ich beschreibe es hier dennoch, falls der Fehler nachhaltig ist und beim nächsten Update wieder erscheint.

73s und einen schönen Wochenstart!

Erhard, DK1WI

[DL7UCX]

Hallo Erhard,

leider nützen die Daten der Fehlermeldung seit langem gar nichts mehr.
Du schreibst "Beim Update ..." ?
Das Update tauscht nur Dateien aus (unsichtbar) und startet dann das Programm neu.
Die Fehler sind also beim (regulären) neuen Programmstart aufgetreten.
Zwischen Beta 4 und Beta 5 gibt es im Programmcode gar keinen Unterschied, nur die Länderliste ist erweitert.

Hast Du die Hinweise zum Virenscanner umgesetzt ?

73 Ben

[dk1wi]

Hallo Ben,

ja, ist im Virenscanner exkludiert

Dann warte ich einfach mal ab. Und ja, der Fehler trat beim regulären Programmstart auf.

Danke Dir!

73s
Erhard