...
update it's downloading
Not quite, it's building its own database by requesting details of past transactions presumably from your local running Bitcoin Core RPC server (your Core should run at least with
server=1 and
txindex=1 in bitcoin.conf file).
There are some speedup tweeks for this initial database build, but it depends on how much RAM your machine has. Main tweeks in fulcrum.conf are settings for db_mem, db_max_open_files and fast-sync, see their documentation in https://github.com/cculianu/Fulcrum/blob/master/doc/fulcrum-example-config.conf.I searched a little bit in the issues section on the Github and it seems the Fulcrum author recommends to leave those settings at default, particularly fast-sync is flagged more like experimental for newer versions of Fulcrum (I don't run the most recent one).
But it's not really necessary to fiddle around with the parameters, the defaults should be ok-ish, but slower than possible.
My Fulcrum runs on a Raspi with 8GB RAM (with Bitcoin Core and together with LND) and I had
db_mem=1024,
db_max_open_files=500 and
fast-sync=2048 during the database build.
Probably better don't use my settings, see above.How much RAM does your Windows box has?
It started well but it's stopped the sync after 935MB downloaded. I've deleted the folder to restart but it's the same error. I don't know why it's failed it won't sync. I'll make changes trying to discover what's wrong.
In your previous screenshot the sync looked fine. It's strange that Fulcrum complains that blocks are not found on disk. This could be an issue with Bitcoin Core failing to answer all requests from Fulcrum (more a
wild guess of mine).
I suggest to report your issue in Fulcrum's Github, the maintainer of Fulcrum is usually quite helpful and knows to interpret the error log messages much better.
The Fulcrum log says something of 8GB for the UTXO cache and available memory seems to say your machine might have 32GiB of RAM (not sure if this also accounts for configured virtual memory or real physical memory only; it says "physical").
I would try to mitigate your sync issue with an increased value for timeout from Core with a higher value than default bitcoind_timeout=30. See also that your Bitcoin Core can handle enough RPC requests from Fulcrum.
Maybe a bit too much on my Raspi but mine has
rpcworkqueue=512 and
rpcthreads=128 in bitcoin.conf.
You could also run Fulcrum with debug option -d to get more details in its log-file which may give you more clues what's going wrong.
Did you do anything special at the time when the getblock errors started to show up (2023-08-19 16:50:xx)?