Hi there, I have observed this same behavior. I have not researched the root cause yet, but it seems to occur in very high memory usage scenarios (ex. standby/working set clears with <2 GB memory free, which is then consumed by memory intensive applications like a game). Adjusting the page file size does not seem to matter in this case, and it is not a fault of overclocking or running XMP, etc. Perhaps adjusting the parameters of ISLC would help, but I have not tested yet and I'm not sure it would help the issue anyways.
Try running a utility that will display your memory usage and keep your eyes on it while gaming and such, and see if you crash when approaching your RAM's capacity. It is a fairly reproducible issue so for now, I have simply opted to not run ISLC in such scenarios.