So here's the thing, when you run intoan issue, you should solve the issue or at least try to understand it or the cause of it. Because as soon as you accept that things make act weird and break sometimes, you set yourself up for bigger "surprises" in the future.
getErrorString certainly works and when it doesn't for, then that's already the first sign of some problem.
Because strings implementation are rather complex and lots of optimizations are to be developed and thus they seem to be one of things that get changed for pretty much any new runtime version. For that reason, they are "good" indicator of wrong runtime usage.
Don't use release libraries in debug mode. Don't use debug libraries in release mode. Use the sane runtime library that yozr compiler uses. Use the correct redist.
Next make sure your Intel GPU driver is updated. Intel has a pretty bad record when it comes to GPU drivers, but they have gotten better, so if you're still using some old or default Windows driver, you shouldn't be surprised to run into issues.
Make sure you give SFML 2.4.2 a run. No modifications needed. If you do run into issues, write down when, how and what happened. SFML 2.4.2 comes with fixes to context handling that was broken in SFML 2.4.1. Since the release we haven't heard of any issues, so I'd be surprised if there still were some.
Do you use any multi-threading?
I do also recommend to create some minimal test case, e.g. just creating a render texture and nothing more. That way you can a) make sure it's not related to your more complex code and b) narrow down the issue to one specific area.
If you really want to build SFML 2.3.2, get the commit right after the release, it adds support for VS 2015, so no morr hoops to jump through, this one:
https://github.com/SFML/SFML/commit/6b9781475d70272538a5ce48ad96f583f3a373c3