New
#11
The problem I see with that approach, is that systematically you cannot pinpoint any one culprit because it may not just be one; but a combination of settings that trigger the crash. In other words, one setting may be safe without the other; but how do you know exactly which one is safe with the others if you have more than twenty settings you have tweaked?
The built-in Windows steps recorder can possibly be a way to pinpoint the culprit rather than trying to unlock the combination of events that trigger the crash.
Adding one by one setting at a time doesn't necessarily pinpoint the culprit; but rather highlights when a combination of settings or events aren't suitable for normal Explorer.exe function processes. The problem then arises that you may never figure out the safe combination of settings to use together, because if you have more than twenty settings; the combination of settings is astronomical and it would be luck to figure out which settings can safely run together without a steps recorder program to capture the event log when the failure occurs.