Forum Replies Created
-
Posts
-
Yes, I have removed port forwarding for Breakway Remote and I am using TightVNC for remote access. Still no crashes to report since I closed port 8200.
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.
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.
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”.
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] =====
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.
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] =====
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?
I too am experiencing this issue. Breakaway crashes roughly every 24 hours resulting ins silence for 10 seconds or so while the service restarts itself. It only started to happen since updating to the latest release a few months ago. My Windows install has had Windows Update disabled permanently, so this in not a problem in my case.
Crash logs look like this:
// 2024-03-08 BreakawayOne Event log
17:24:11.220 EMRG CRASH: 2024/03/08 17:24:09
17:24:26.269 INFO ————- Startup – CLogMgrInstance::Init() ————
17:24:26.405 INFO BreakawayOne 3.30.93 starting up as service
17:24:26.405 INFO Product: BreakawayOne version 3.30.93 x64 (svc) – host WGRT-AUDIO – compiled 2023-02-25 12:33:05Thanks for taking a look at it. Opus is not a high priority for us either, so no worries. We were just exploring low-bit rate options, and based on what you've said about opus, aac may be the better choice anyway.
