I tried running bitcoind.exe, that ran happily for a few minutes till I stopped it.
I found this (debug.log)
-snip-
2023-10-01T14:07:29Z Default data directory C:\Users\bill\AppData\Roaming\Bitcoin
2023-10-01T14:07:29Z Using data directory F:\bitcoin
So you set the data directory through the GUI given by the log which didn't indicated "
Config file arg" or "
Command-line arg" before the data dir.
So, it's something in your F: drive's data directory, probably a corruption in your "
block index" where the logs are cut off.
The daemon might have worked because it's using the default data directory if not supplied with --datadir arg or config file inside the default data dir.
(
it's a guess because you haven't given any information about that working session of bitcoind)
You can probably solve it by launching Bitcoin Core with
--reindex command line option. (
instructions)
If it starts, it'll have to rebuild your block index which could take a while to complete so be patient while waiting for it to finish.
Bitcoin Core may look like frozen and unresponsive during reindex or IBD, but don't kill its process because it's 100% working in the background.