Its not the one i have in mind. But it may well contain the solution. The one I vaguely remember is older than that. Like I said, never tried it myself, so I don't know what is required to fix it. I would have remembered more details. There are atleast 2 ways in windows to asign a file and folder as read-only. The checkmark in the properties screen, which is a leftover of the DOS days. And by more fine-controlled user and group based "Access Control Lists" in the (NTFS) security tab in properties. I don't know which method is the one that works in any condition.
The O.P. seems he is not very sure of which of the 2 solutions (or some part of it) fixes his crashes. Infact, nowhere in his message did he say it was related to Steam. So I wouldn't consider this to fix the problem in this thread. It may be completely unrelated and be caused by another quirk. It can crash due to many reasons, and we have no clear way to find out why it did. It doesn't leave an easy to read crashlog.
|