Yet Another "getbalance" Problem.

Good afternoon guys. I'm having a problem with DCR being stuck in "immaturestakegeneration".

Long story short I upgraded to v0.8. I noticed that none of my tickets were being called as I usually have about 5 or 6 a day that get called to vote. I ran the usual commands to revoke them and they were all missed despite being connected to Mainnet. Okay no prob, this has happened before twice, and both times they were after a thunderstorm power outage.

After the 256 block maturity all but 455 DCR were available to spend/stake, as shown by > getbalance * 0:
{
"balances": [
{
"accountname": "default",
"immaturecoinbaserewards": 0,
"immaturestakegeneration": 455.10862366,
"lockedbytickets": 1381.1294189,
"spendable": 18.65827924,
"total": 1854.8963218,
"votingauthority": 0
},
{
"accountname": "imported",
"immaturecoinbaserewards": 0,
"immaturestakegeneration": 0,
"lockedbytickets": 0,
"spendable": 0,
"total": 0,
"votingauthority": 0
}
],

Now there is another thread regarding the same problem and Ive done everything @davecgh said in that thread: make sure --enablevoting flag is is set, revoke, wait 256 blocks, etc. but after 3 days these 455 are still stuck.

What has me nervous is prior to the upgrade "getbalance" and "getbalance default 0 all" had both shown a 455 DCR discrepancy as does "getbalance" and "getbalance * 0" in the newer version, but as I was staking i had always assumed this was just what was locked at the time.

Am I outta luck on this one, or am I missing anything? Any help is greatly appreciated.

 

I did, no change unfortunately. I also backed up the .dcrwallet folder and created a new wallet, and .dcrd folder. No change either.