- This topic has 35 replies, 4 voices, and was last updated 2 weeks ago by
.
-
Posts
-
Thank you johnzs180 for your additional input. I am also using the built-in encoder (AAC/192) and reading a txt file for the titles, as well as running a “local” HD core. My laptop is an Asus i7 with Windows 11.
The second machine (a 4 year old Dell i7 laptop) is 50 kilometres away (whatever that is in miles), running a similar configuration, but through a different provider. Neither gives an ounce of grief.Could it be power related? Maybe a noisy or over/under voltage power supply? Although you do say that you have tried it on two different machines, presumably with different power sources. Is your environment particularly electronically “noisy”?
I’ve been using the FLAC encoder and the HD encoder for streaming (MP3 streams). I’m on windows 10 pro rather than windows 11.
I’ve tried it on my desk rather than with the other kit with a different power supply and it still gives me the same issue.
I have disabled breakaway for now and I’m running MB-Recaster with zero issues on the same machine/same sound card etc. That leads me to believe it’s something that the breakaway software/service is doing that is crashing it or perhaps the built in encoders are causing it?
My system:
It’s been running for many years with only one issue (BaRemote access fails to connect after service runs for a long time without a restart).
My daily crash problem only started after I updated to the latest BreakwayOne release.Intel i3-8100 with 8GB RAM
Windows 10 Pro build circa 2016
AudioScience ASI5611 for audio input
Using Realtek Optical out to a DAC for MPX output
Running FM with RDS
Running an HD core for streaming mp3 to a remote icecast server.
Now Playing/RDS data is collected via URL from a NodeJS script running on the same machine as Breakway.
Windows update has never been run on this machine since it was put into service (disabled via policy).Is there a way to get a more detailed crash report?
My latest crash dump:
2024/03/12 12:52:17
Please forward these two files to the author:
C:\Users\WGRT\AppData\Local\BreakawayOne\dump\BreakawayOneSvc_crash_2024-03-12_12-52-17.txt
C:\Users\WGRT\AppData\Local\BreakawayOne\dump\BreakawayOneSvc_crash_2024-03-12_12-52-17.dmpC:\Users\WGRT\AppData\Local\BreakawayOne\dump\BreakawayOneSvc.exe caused an Access Violation (0xc0000005)
in module BreakawayOneSvc.exe at 0033:00007ff67fa3f621.Exception handler called in global utilityTimerSingleton thread.
Fine debug text: long way — this is a very pleasant sounding preset, excellent for maximizing TSL..
Command Line: “C:\Program Files\BreakawayOne\BreakawayOneSvc.exe” servicerun.
Error occurred at 3/12/2024 12:52:18.
C:\Program Files\BreakawayOne\BreakawayOneSvc.exe, run by SYSTEM.
Operating system: unknown Windows version (10.0.14393).
4 processor(s), type 8664.
15% memory in use.
8056 MBytes physical memory.
6845 MBytes physical memory free.
9336 MBytes paging file.
7914 MBytes paging file free.
134217728 MBytes user address space.
134217218 MBytes user address space free.===== [end of CRASH.TXT] =====
I see that Microsoft claims this “may” be the result of “memory corruption”.
Access Violation (0xc0000005)
Maybe RAM is going bad? I kind of doubt it, because one would expect Windows to also eventually bluescreen if that was the case.
This just happened:
// 2024-03-14 BreakawayOne Event log
11:11:58.042 ALRT CPU Cores 0, 1, 2, 3 pegged
11:11:59.042 ALRT CPU Cores 0, 1, 2, 3 pegged
11:12:00.042 ALRT CPU Cores 0, 1, 2, 3 pegged
11:12:01.042 ALRT CPU Cores 0, 1, 2, 3 pegged
11:12:02.042 ALRT CPU Cores 0, 1, 2, 3 pegged
…CPU Core Pegged messages squelched, 5 in 10000 ms.
11:12:12.685 INFO …CPU Core Pegged messages unsquelched.
11:28:08.032 INFO NfTcp New Connection from 68.43.226.220
11:59:19.293 EMRG CRASH: 2024/03/14 11:59:17
11:59:34.357 INFO ————- Startup – CLogMgrInstance::Init() ————
11:59:34.498 INFO BreakawayOne 3.30.93 starting up as service
11:59:34.498 INFO Product: BreakawayOne version 3.30.93 x64 (svc) – host WGRT-AUDIO – compiled 2023-02-25 12:33:052024/03/14 11:59:17
Please forward these two files to the author:
C:\Users\WGRT\AppData\Local\BreakawayOne\dump\BreakawayOneSvc_crash_2024-03-14_11-59-17.txt
C:\Users\WGRT\AppData\Local\BreakawayOne\dump\BreakawayOneSvc_crash_2024-03-14_11-59-17.dmpC:\Users\WGRT\AppData\Local\BreakawayOne\dump\BreakawayOneSvc.exe caused an Access Violation (0xc0000005)
in module BreakawayOneSvc.exe at 0033:00007ff67fa3f621.Exception handler called in global utilityTimerSingleton thread.
Fine debug text: 6103364A5C65F48DD3F3.62D1B8FF33063FBC855ABC20816E89.id.chestnost.com.
Command Line: “C:\Program Files\BreakawayOne\BreakawayOneSvc.exe” servicerun.
Error occurred at 3/14/2024 11:59:18.
C:\Program Files\BreakawayOne\BreakawayOneSvc.exe, run by SYSTEM.
Operating system: unknown Windows version (10.0.14393).
4 processor(s), type 8664.
13% memory in use.
8056 MBytes physical memory.
6932 MBytes physical memory free.
9336 MBytes paging file.
7918 MBytes paging file free.
134217728 MBytes user address space.
134217262 MBytes user address space free.===== [end of CRASH.TXT] =====
So what is this doing in the debug text?
6103364A5C65F48DD3F3.62D1B8FF33063FBC855ABC20816E89.id.chestnost.com
I can’t find any information on it other than it is a registered domain, “chestnost” seems to be Russian for “trustworthy”.
Thanks for the dump details. I will forward these on.
No idea on the URL, unless it is something to do with the developer of Virtual Audio Cables (Eugene (Evgenii) Muzychenko) which is licensed to BA1 as “Breakaway Pipeline”. Are you using the pipeline as your input to BA1?
BTW, I am using it as the output from my playout software, and therefore the input to Breakaway One, but with no issues. If you are using it, is it the latest version (4.66)?
I haven’t done anything but the crashing has stopped. No crashes since the 14th. I was about to close the remote access ports at the router on a hunch that it was related to Breakaway remote management access.
Thanks for the update. This is what makes it so hard to track down – the very inconsistency of it. Keep us posted, and we’ll continue to “dig”.
The crashing started up again with that same “chestnost.com” in the debug text several days ago. I closed the remote access ports on the router to cut off access to Breakaway’s remote management. So far, no crashes after about 3 days.
That’s very interesting. I believe that it is possible to change the default port address of 8200. I’ll check and let you know so that you can change your port forwarding rules.
I have found that you can change the default port address simply by adding the preferred number to the end of the IP address you use to access Breakaway One in the BARemote GUI.
Simply add a colon after the IP, and then the preferred port address. You should then change your firewall and router port forwarding to the new address. For instance 192.168.1.100:8500 will try to open port 8500 instead of the default 8200.
If you are being hacked or DDOS attempts are flooding port 8200, this should move it to a safer port.
EDIT: Leif has contacted me back to say that, whilst BaRemote can connect on any specified port, BreakawayOne only listens on port 8200. You could create a temporary fix by opening BaRemote on (say) port 8300, but forward all traffic on that port back to 8200 in your router. This would work, but, if “chestnost.com” is monitoring that port, the problem will still occur.
He asks why you are exposing BreakawayOne to the internet anyway. In my case, I connect to the BA1 PC using Team Viewer and then use localhost (127.0.0.1) to open the configuration. A more robust approach would be to create a VPN and then have a virtual circuit from your location to your Breakaway PC, free from the Internet.
@johnzs180 Perhaps you could try the same solution as “wgrt” in case you are suffering the same vulnerability.
- You must be logged in to reply to this topic.