Backup the wallet.dat, delete the app data einsteinium folder, delete the wallet, redownload the wallet, launch it, close it, overwite new wallet.dat with the previously backed up one, ensure conf file has nodes, restart.

That's what I would try, but don't blame me if something goes wrong However feel free to tip me if this works haha

If it takes more than 1-2 hours, you have an issue most likely.

Does this not work for you?

http://cryptomining-blog.com/1883-download-the-latest-bfgminer-3-99-0-for-windows-with-gridseed-asic-support/

I'm assuming you're using Linux (I have no idea how to compile this under Windows nor should you attempt that - there are binaries available).

1) Install prerequisites:

libudev-dev build-essential libcurl4-gnutls-dev yasm libncurses5-dev git autoconf automake

E.g. on ubuntu and its clones you would run:

apt-get install libudev-dev build-essential libcurl4-gnutls-dev yasm libncurses5-dev git autoconf automake


2) run this in your home folder:

git clone https://github.com/nwoolls/bfgminer
cd bfgminer
./autogen.sh
./configure
make


This is just to get you on track, if you have any problems please report back and I'll try to help.

If you mean Linux, check out these steps:
https://bitcointalk.org/index.php?topic=168174.msg5734631#msg5734631

Instead of "git clone -b feature/gridseed-support https://github.com/nwoolls/bfgminer" you can do:
"git clone -b feature/gridseed-support-new https://github.com/nwoolls/bfgminer.git"

I think the "gridseed-support-clean" branch is even newer so you may want to try that one.
Not sure if this branch is advised to use though.

ps: How about individual freq. settings per miner that auto adjust automatically? Would be cool to get optimized results.

?

Care to elaborate on what the error is and which coin(s)? Have you tried logging a support ticket on CAve? This is the first I have heard of anyone having withdrawal issues today.

All CryptoAve maintenance is complete.