Should we delete the repo for it, or fix the problem?
Since its unreliable, should we stop developing new things?
No, definitely not.
It looks very optimistic and fantastic

Let's try to develop it

Every new thing need to improve and I know that you'll make it

I'll keep it running and try to find those "stop" moments.
Could you please run it with the --coinbase-addr= populated? And the "-P" flag and the "--no-longpoll"? So far I havent exited with a coinbase addr populated.
Ill see what I can do about debugging it - we might have an exit program in there when it doesnt get work (in contrast to retrying).
Btw if you have a reproducible exit, let me know.
I was able to mine a block with the external miner:
https://chainz.cryptoid.info/bbp/tx.dws?1157341.htm (see version 1.4.5.0)
I'll help with -P
RE: Crashing
Crashtimes: 10:54:57 PM and again at 12:04:24 AM PDT
According to microsoft, the exception code is a heap corruption:
https://blogs.msdn.microsoft.com/calvin_hsia/2015/01/30/heap-corruption-exception-0xc0000374/Faulting application name: bbpminer-x86.exe, version: 0.0.0.0, time stamp: 0x5da08c5b
Faulting module name: ntdll.dll, version: 10.0.17763.802, time stamp: 0x125ac1e8
Exception code: 0xc0000374
Fault offset: 0x00000000000fb049
Faulting process id: 0x1af0
Faulting application start time: 0x01d580c325d339ff
Faulting application path: C:\Users\xxx\Downloads\bbpminer-x86.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: bfd34ddb-3275-41ba-ab8a-d9fc19a0ddaf
Faulting package full name:
Faulting package-relative application ID:
Youd have to run it in valgrind to get the actual trace info; how many hours at a time did it run with coinbase addr set?
Edit: thats great you mined a block; I assume the reward came to a brand new key.