+- Swisslog's Forum (https://www.swisslogforwindows.com/forum)
+-- Forum: Swisslog version 5.x (https://www.swisslogforwindows.com/forum/forumdisplay.php?fid=3)
+--- Forum: Error reports (https://www.swisslogforwindows.com/forum/forumdisplay.php?fid=6)
+--- Thread: Access violation (/showthread.php?tid=1309)
Pages:
1
2
Access violation - pa1adr - 29-11-2025
Hi, I'm getting an acces violation on regular basis, few times in a more hours session.
" Access violation at address 00C72F8 in module 'SwissIV5.exe'. Read of address 000005B4."
Is their someone already familiar with this error? is their a known solution?
Thanks in advance. 73 de pa1adr
RE: Access violation - pa1adr - 30-11-2025
Found an old post with a possible solution in a reply. Hopefully problem solved. Thanks. KR Adri, 73 de pa1adr
RE: Access violation - EA3GCV - 30-11-2025
Hello,
It would be good if you can post here the link to that post, this will help other users.
73
RE: Access violation - pa1adr - 05-12-2025
Hello,
An earlier post on this "error" was posted with reply. Thanks for advice to add link:
https://www.swisslogforwindows.com/forum/showthread.php?tid=1261&pid=4817&highlight=access+violation#pid4817
Unfortunatly it didnt solve my problem yet. To be continued.
Any ideas are welcome.
Thanks in advance.
Adri
RE: Access violation - EI4KF - 07-12-2025
Ideas..... yes, well Jordi's advice usually solves it. I can add a bit but don't hold me responsible for these not working!
You should not have to do any of the below. First I'd suspect the OS and not Swisslog. Try an elevated command prompt and sfc / scannow to check Windows system files. Check for malware. Otherwise....
1 If you run Windows with UAC (User Account Control) on, try with it off and check for any difference.
2 Add Swisslog to the Data Execution Prevention Exception (Advanced System Settings>Advanced>Performance>Data Execution Prevention>Turn on DEP for Programs> Add (select SwisslV5.exe)
3 Check SwisslV5 properties are really set to 'as administrator' and also check not in read-only mode.
4 Check SwisslV5.exe in compatibility trouble shooter (see tab in properties).
RE: Access violation - pa1adr - 15-12-2025
(07-12-2025, 11:00 AM)EI4KF Wrote: Ideas..... yes, well Jordi's advice usually solves it. I can add a bit but don't hold me responsible for these not working!
You should not have to do any of the below. First I'd suspect the OS and not Swisslog. Try an elevated command prompt and sfc / scannow to check Windows system files. Check for malware. Otherwise....
1 If you run Windows with UAC (User Account Control) on, try with it off and check for any difference.
2 Add Swisslog to the Data Execution Prevention Exception (Advanced System Settings>Advanced>Performance>Data Execution Prevention>Turn on DEP for Programs> Add (select SwisslV5.exe)
3 Check SwisslV5 properties are really set to 'as administrator' and also check not in read-only mode.
4 Check SwisslV5.exe in compatibility trouble shooter (see tab in properties).
Thanks Erik, I will try all four of them. I let you now the results.
RE: Access violation - pa1adr - 25-01-2026
Hello Erik, Jordi, have been qrt for a few weeks.
I ve tried all suggestions. There's also appearing a new violation at adress 00C7ADE8 in module SwissIV5.exe. Read of address 000005B4. (TRX TS-890)
As far I can see Swiisslog is working ok, so not really a problem but still curious. On my other laptop this volation(s) do not show up. (TRX = ic705)
Maybe the one type of rig is communicating smoother then the other. Thanks for advice, hope to see you around on radio.
RE: Access violation - EI4KF - 25-01-2026
Hello! We are sorry for problems and that all suggestions failed to help. I could refer you to a online search on "violation at address 00C7ADE8" and tell you about null pointers, buffer overflows, blah blah blah. But no, I don't want to waste your time. Jordi has done a fantastic job maintaining and developing Swisslog and has overcome and corrected many issues. These errors affect a few users but don't normally stop SWL from functioning. They are somewhat out of Jordi's control, being legacy remnants from Walter's programming many years ago and long before W11.
I have actually stopped all violation errors here but, as you say, their appearance depends on the radio used to some extent. Choice of memory modules and amount of RAM makes a difference too, not something you can do much about but if you ever make a hardware upgrade anyway, you may well find the issues are gone.
73 de Erik.
RE: Access violation - EA3GCV - 27-01-2026
Hello Adri,
You don't explain which transceiver option are you using in Swisslog. Please attach screenshots. Keep in mind that if you are using OmniRig as transceiver control, you have to run as administrator not only Swisslog but also OmniRig! otherwise you will get violation errors.
Sorry to insist on this but it's EXTREMELY important to add excepctions to the Swisslog folder and all software linked with Swisslog in your antivirus. Which antivirus are you using? The same applies to allow all communications in your firewall for all the executables. Swisslog and software used along with Swisslog such as WSJT-X, etc).
Could you please try to connect your TS-890 in your laptop to see if you still get these errors? Are you uisng latest Swisslog version? Do you have Swisslog installed in C:\Swisslog folder? There are many scenarios but you should not get any error at all. Occassionaly these kind of errors may arise but not on a regular basis as in your case.
Also perform a check in your operating system. Type CMD in the Windows's search field then run it as administrator. A command line (MS-DOS style) will be displayed. Then run this command:
SFC /SCANNOW
This will fix any operating system corrupted files. It's very common to had corrupted files! I run this command from time to time.
If you still experience the same issue contact me to arrange a remote Teamviewer or Anydesk session to try to find out the reason of this error. But first reply my question and do all the above instructions.
73
RE: Access violation - pa1adr - 27-03-2026
Hello Jordi, thanks for your tips/advice. I've run the SFC /SCANNOW and not seen the access violation since. Fingers crossed my guts says this was the solution. (more then over a month now. I now run SFC /SCANNOW on regular basis)
Antivirus is build-in Windows antivirus nothing fancy. My TRX is TS890 via HRD software, in Swisslog HRD is set as transceiver control. Swisslog 5.115 installed in C:\Swisslog folder. Running SDRplay RSP1B via Omnirig with SDRuno software. Omnirig set via HRD's 3th party serial port (com0com serial port emulator pair).
Also run WSJT, JTDX, MSHV without problems and communicating smoothly with Swisslog. HRD DM-780 is running just fine.
I also use FLdigi but gives conflict with HRD software so I only run FLdigi now and then but seperately.
Need to be said that in spite of the (past
) access viloation, Swisslog always worked and works very fine for me. I just was wondering why this violation kept appearing on display.Thanks again and good luck. If I can provide more info please let me know as far my knowledge reaches.
Kindest regards, Adri 73 de pa1adr