It happened to me again last night, on 2.5.1.17, with Ansvr 0.18. Given how 2.5.1.15 hasn't failed once though, it's not Ansvr that's the issue. Clearly this is the case as well since you don't use Ansvr and have the same issue.
I'll be installing SGP 2.5.1.15 again. Hopefully the next release(s) sees this bug fixed. 