by "enable/disable", what I meant was turning visibility on/off (using the lightbulb icon in the component browser).
A screencast isn't necessary, and I'd have to screencast all of my designs until it crashes and happens to record the instance and also be a file where there is an offset plane- which not every design needs or has.
essentially it's this:
1) create a file & save.
2) create sketch
3) offset plane using an item on that sketch as a reference point and stop sketch.
4) carry about your business
5) program crashes
6) recover auto-save data and continue working on file
7) try to go back and change the offset plane parameters (add or subtract distance)
8) error: reference geometry not found (sketch automatically turned off)
Maybe it's not a bug, but I wouldn't call it a feature (unless this product is developed by bethesda. lol jk)
IDEALLY, If I have a sketch turned off whilst designing parts at other stages of a file way further down the time line, and I choose to change the offset plane I created waaaaaaaaaaay back in the timeline, the sketch or reference geometry that it is based upon should automatically be turned on when I choose to edit it at a later time. perhaps the temporarily enabled visibility would be signified by the use of a different coloured lightbulb, like a purple one or something (akin to being visible only under UV/certain lights).
the idea proposed above only stems from the experience I had while troubleshooting what I think (or thought) might be a bug after the program crashed... But now I think it's more of a UI or productivity issue that could be addressed fairly simply as far as user intervention goes.
correct me if i'm wrong, but when creating new items/features, the prior sketch always gets automatically turned off, right? so not as to confuse the user, perhaps? so why then should the referenced sketch on something like an offset plane that has been automatically turned off require the user to manually turn it back on? If I am wrong and it works for you without any issues with F360 locating the reference geometry, then it's clearly a bug because it didn't automatically find it when I chose to edit the offset plane distance after reloading the program, post crash.
as roachslayer pointed out, this happens when merely saving and reopening the file at a later date as well- so it quite possibly has nothing to do with the crash at all.