Caught it. Its SiaUI v1.3.1 Bug – Memory Management.

[premkumar]

Caught it. Its SiaUI Bug – Memory Management.

In consistence with my previous suspect, today again I was again not able to remote connect my VM OS. The VM Server indicated that the SiaCoin VM was demanding 8 GB memory, simple 4 time more than the Siacoin Server OS has (4 GB).
I could not capture above statement at the exact time but here is what I am saying.

Thanks to Windows HyperV (Virtualization Manager) which somehow, after my few try to connect SiaCoin Server, I was able to connect. And here boom, I see that it was SiaUI which is having memory write fault and ultimately got closed.

1. So what is my fault in this that I will be reported less available. It is impacting my total uptime availability. How should I be compensated for this by Sia company?
2. Will someone from Sia development team will agree that this is the Memory mgmt. problem in SiaUI 1.3.1 and will they fix it in next release

[premkumar]

It happened again after 5 days. Windows (the VM where my SiaUI v1.3.1 is running) says- An error occurred. windows closed the program.

this is really decreasing my server availability.

Exctly what is the error ? How can I see? Which error log file ?

[premkumar]

@premkumar
Update-

Either the exactly mentioned above error or a similar error is happening every 3 - 5 days, consistently. since last couple of weeks.

good job - SiaUI v1.3.1 Core developers.

[premkumar]

Update -
Even after updating to v1.3.2 - I get this and similar error.

I checked windows "Event Viewer". EventViewer documents couple of error caused by SaiUI.exe, but no details. Only error message is - 0xc0000005

A deeper research about this error message (see some of search results below) suggests me that Develper has written a bad code.
Developers - Can you help ?

----------------------- internet search result ------------------
DEP has been enabled for both hardware and software components since Windows XP SP2. However, some programs are still unable to be fully compatible with it. Some applications adopt a technique, usually called dynamic code generation, which doesn't tag these codes with an execute permission. As a result, this conflict gives rise to the problem. Besides, if software is developed without SafeSEH, it tends to cause 0xC0000005 error when DEP is enabled on the computer.

If you encounter the error code because of DEP, you can contact the developer of the software causing the issue and ask whether they have a solution. Alternatively, you can disable DEP for the software in question and this can be done through following steps: