Bet Angel Crash

[Thrungus]

Hi Support / Anyone that can help.

I keep getting crashes: commonly once a day. I have a significant amount of markets in Guardian running (commonly 200+). Automation runs, either placing bets or simply getting values.

---
Windows Event View Error

Faulting application name: BetAngel.exe, version: 1.0.9476.28171, time stamp: 0x693ae5f5
Faulting module name: ucrtbase.dll, version: 10.0.26100.8521, time stamp: 0xac13ff6d
Exception code: 0xc0000409
Fault offset: 0x0002da71
Faulting process id: 0x8AF4
Faulting application start time: 0x1DD0DEA101FBEF5
Faulting application path: C:\Program Files (x86)\Bet Angel Limited\Bet Angel - Professional\BetAngel.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: bc35d631-8576-4417-a653-3e1ba918f4b8
Faulting package full name:
Faulting package-relative application ID:
---

Any suggestions on how to better use Guardian? Or a fix in general would be great.

Thanks.

[Monoxi]

Hi

I've had the same issue for a while now. Tried everything except for a fresh install, and nothing has worked. A fresh install will be a pain for me. I might look at running a Virtual Machine through Hyper V and having just BA run on there.

Link to a previous topic with some suggestions viewtopic.php?t=31199

[jamesedwards]

I run Bet Angel 24/7 on five separate computers. It runs flawlessly on four of them, with occasional crashes on one. It seems to be luck of the draw.

[Thrungus]

I run Bet Angel 24/7 on five separate computers. It runs flawlessly on four of them, with occasional crashes on one. It seems to be luck of the draw.

That's unfortunate. It'd be very helpful if it at least gave me an error code or notified me that it had crashed.

[jamesedwards]

I run Bet Angel 24/7 on five separate computers. It runs flawlessly on four of them, with occasional crashes on one. It seems to be luck of the draw.

That's unfortunate. It'd be very helpful if it at least gave me an error code or notified me that it had crashed.

Bet Angel definitely would benefit from the addition of a Telegram (or similar) notification option within the 'alert' function.

[Monoxi]

I run Bet Angel 24/7 on five separate computers. It runs flawlessly on four of them, with occasional crashes on one. It seems to be luck of the draw.

That's unfortunate. It'd be very helpful if it at least gave me an error code or notified me that it had crashed.

Bet Angel definitely would benefit from the addition of a Telegram (or similar) notification option within the 'alert' function.

I use a program called "Mail Alert Simple Mailer" which will email me when there is a crash event in Event Viewer.

[Euler]

Check your hard drive space. 99.9% of crashes are caused by whatever you're using running out of hard drive space, but you having loads of markets loaded in Guardian. Any market you put in Guardian will start to collect data the moment you list it in there, and the faster you refresh it, the more data it will collect.

[Thrungus]

Check your hard drive space. 99.9% of crashes are caused by whatever you're using running out of hard drive space, but you having loads of markets loaded in Guardian. Any market you put in Guardian will start to collect data the moment you list it in there, and the faster you refresh it, the more data it will collect.

Unfortunately / fortunately the drive that Bet Angel is installed on has plenty (300gb+) of space free on it. Does Guardian clear its own cache afterwards? And unfortunately I've found that most of my automation won't fire unless I have it on the fastest refresh speeds. I'm also using restrict refresh.

Maybe I could restrict the refresh even further?

[Trader724]

I’d try and get a dump file if it’s crashing that often.

Event Viewer is useful but it’s pretty vague tbh. It basically says BetAngel fell over and "ucrtbase.dll" was involved but not what BA was actually doing at the time.

You can enable crash dumps like this:

Create a folder called:

"C:\Dumps"

Then open Command Prompt as admin and run these:

Code: Select all

reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\BetAngel.exe" /v DumpFolder /t REG_EXPAND_SZ /d C:\Dumps /f

reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\BetAngel.exe" /v DumpCount /t REG_DWORD /d 10 /f

reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\BetAngel.exe" /v DumpType /t REG_DWORD /d 2 /f

Then just carry on using BetAngel as normal. Next time it crashes you should get a ".dmp" file in "C:\Dumps".

That should give a better idea whether it’s happening during Guardian cycling, automation, streaming, logging, Excel/stored values etc.

I’d also try cutting the Guardian load down a bit as a test. With 200+ markets loaded it’s def worth ruling that out.

Wouldn’t post the dump publicly though.

[Monoxi]

I’d try and get a dump file if it’s crashing that often.

Event Viewer is useful but it’s pretty vague tbh. It basically says BetAngel fell over and "ucrtbase.dll" was involved but not what BA was actually doing at the time.

You can enable crash dumps like this:

Create a folder called:

"C:\Dumps"

Then open Command Prompt as admin and run these:

Code: Select all

reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\BetAngel.exe" /v DumpFolder /t REG_EXPAND_SZ /d C:\Dumps /f

reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\BetAngel.exe" /v DumpCount /t REG_DWORD /d 10 /f

reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\BetAngel.exe" /v DumpType /t REG_DWORD /d 2 /f

Then just carry on using BetAngel as normal. Next time it crashes you should get a ".dmp" file in "C:\Dumps".

That should give a better idea whether it’s happening during Guardian cycling, automation, streaming, logging, Excel/stored values etc.

I’d also try cutting the Guardian load down a bit as a test. With 200+ markets loaded it’s def worth ruling that out.

Wouldn’t post the dump publicly though.

I've got two dump files now but I don't know what I'm looking for in them when using WinDbg to view. I can post the text here but I'm not sure if safe to do so. Any assistance would be appreciated.

[ShaunWhite]

If an app crashes and points to ucrtbase.dll as the "faulting module," it usually means the app hit an unhandled exception or bug, rather than the file itself being broken. However, if the file has been corrupted or misplaced, several steps can resolve the issue:

Repair Visual C++ Redistributable:
Many apps rely on Visual C++. Go to Control Panel > Programs and Features, locate the Microsoft Visual C++ Redistributable, right-click it, and select Change > Repair.

Run a System Scan:
System-wide file corruption can be checked using Windows tools. Open the Command Prompt as Administrator and run sfc /scannow to scan and restore missing or broken core system files.

Reinstall the Faulting Application:
If the error only happens when opening one specific program or game, it is usually a glitch in that specific software. Uninstall the program, download the latest version, and install it again.

Note that on modern systems like Windows 10 and 11, ucrtbase.dll is an official OS component and is primarily updated and maintained through standard Windows Update, not by external packages.