Take a backup copy of hte file you play with then experiment. "What does THIS control do?" Software blowing up a computer with spitzensparken and all that stuff is Hollywood special effects. I only ran across one computer that had a "DETOMATE" instruction in its assembly language. "This function has no return." It meant the Minuteman missile warhead was sent the electrical signal to explode.

In recent years I've found that all I need is a backup of the file I am modifying. In the past it was fairly easy to cause a BSOD that required resusitative efforts on a computer. Over time you had to work more and more seriously hard to do this. On this particular computer I swear the level of software closest to the machine's USB hardware had a "crash randomly" instruction. Eventually ASUS found the problem and fixed it. At least the problem went away with a "keep your computer secure" BIOS update. Since then - no problems. So I fee safe recommending "play with the controls". Don't wonder "what does this or that control do?" Try it and find out. Worst case stop the program, restore the backup of the file you're playing with, and start back up.

{^_^}