Please contact support so we can get more info.

https://esupport.stardock.com/index.php?/Tickets/Submit

Perhaps the more pertinent question is "Why am I having system crashes?".

Actually, it isn't. 

There's something wrong with your computer: Stable, updated systems don't crash.

I bet when you solve the problem of crashes, your Object Dock problem gets mysteriously solved, as well.

Damn Dave you beat me to it.

Here's a link of what Dave's talking about https://forums.wincustomize.com/404232/page/1/#2879207

Actually I was searching for the link. Then I took a nap.

I'll have to disagree with you on that point - I've been in software, and working in Windows environments, for long enough to know how frequently Windows systems of various stripes BSOD; it happens often enough that the frequency with which it happens on my systems does not surprise me.

It is likely NOT system instability CAUSING ObjectDock to lose its settings - for that to happen without it being the fault of ObjectDock's design, then I likely would be seeing the cause be corruption of the ObjectDock .init file itself, triggering ObjectDock to recover as best it can.  And if this were true, then I'd be seeing one or all of the below:

1. Disk corruption elsewhere on my system

2. Corruption in regularly accessed files of other sorts

3. Outright driver and system code failures

4. More frequent crashes than the very infrequent ones I've seen.

5. All-out system flakiness on a regular basis

... since the above does not happen, and the only thing on the entire system that "goes bad" after a crash is the content of ObjectDock's .ini file, that seems terribly suspicious to me.  Were I assigned to debug this problem, as a developer, I would be looking at the ObjectDock code to see when it attempts to write to the .ini file:

1. Does it do it after any crash?

2. Does it do it if it was in a certain state during a crash?

3. Is it constantly attempting to update the .init file without making a backup during the update, thus causing corruption itself in the case of a system crash?

These are all important questions; and the fact that ObjectDock is the ONLY thing that gets broken after a crash means, to me, that something in ObjectDock's design is at fault.

If you have a better theory with some details involved, please let me know.

Please see my comment above - no other corruption happens, no other apps lose these settings, I get no disk structure corruption - there are absolutely NO other bad effects of the BSOD's I've occasionally had.  The ONLY bit of software (Windows system code, drivers, settings files, apps, etc.) that goes haywire after any BSOD I've ever had... has been ObjectDock.  That's meaningful.

I don't keep my system up 24/7/365.  However, I do have several "exotic" add-in boards and their accompanying drivers, which I believe are likely the cause of the BSODs (nothing too crazy, just some very specific video, audio, and I/O boards).  And the BSODs happen reasonably infrequently - not all the time, more like once every few months, as mentioned.

One thing I do with my computer that is different than the way lots of people use theirs these days, is I put my desktop to sleep, and wake it for use.  Laptops usually handle this with ease, but desktops don't always recover cleanly (less gracefully than laptops, in my experience).  Also, all my desktop machines are ones I've built myself (and I've been building them for about 10 years, so I'm not new at this).  Thus, they haven't been vetted for perfectly behaving combinations of hardware that all play well together.  The BSODs happen so infrequently that debugging which the culprit(s) is/are would be pretty difficult - I'm willing to put up with it if it means I don't have to spend weeks that I don't have trying to nail down the issue.  It could be something as minor as memory timings that VERY occasionally cause issues, but which aren't identified by running MemTest for a day or two.

I suspect what is happening is you have had a number of BSOD in a row and ObjectDock may well have code to detect it failed to shutdown itself cleanly multiple times in a row in which case it might decide the file is corrupted and causing ObjectDock to crash.  Fences for example would shut itself down in such a situation if it happens within a set time of starting up.

I cannot be sure as I am not involved in the development of that product, but it seems logical that may be happening.  It probably believes something in the configuration is bad so reverts to safe settings.

That's what I would guess.  The odd thing is, both the settings file AND the settings backup that ObjectDock keep are reverted to default when this happens.  Not sure what to make of that.