C:\BitCrack>clBitcrack -o out.txt --keyspace f7051f27a09112d4:f7051f37b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN -b 96 -t 256 -p 256
[2022-09-26.21:14:51] [Info] Compression: compressed
[2022-09-26.21:14:51] [Info] Starting at: 000000000000000000000000000000000000000000000000F7051F27A09112D4
[2022-09-26.21:14:51] [Info] Ending at: 000000000000000000000000000000000000000000000000F7051F37B09112D4
[2022-09-26.21:14:51] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2022-09-26.21:14:51] [Info] Compiling OpenCL kernels...
[2022-09-26.21:14:51] [Info] Initializing GeForce 820M
[2022-09-26.21:14:53] [Info] Generating 6,291,456 starting points (240.0MB)
[2022-09-26.21:15:02] [Info] 10.0%
[2022-09-26.21:15:08] [Info] 20.0%
[2022-09-26.21:15:13] [Info] 30.0%
[2022-09-26.21:15:15] [Info] 40.0%
[2022-09-26.21:15:17] [Info] 50.0%
[2022-09-26.21:15:20] [Info] 60.0%
[2022-09-26.21:15:22] [Info] 70.0%
[2022-09-26.21:15:24] [Info] 80.0%
[2022-09-26.21:15:26] [Info] 90.0%
[2022-09-26.21:15:29] [Info] 100.0%
[2022-09-26.21:15:29] [Info] Done
[2022-09-26.21:15:29] [Info] Reached end of keyspace
C:\BitCrack>
Key not found because the keyrange is larger than 260000 keys!!!
As i told before clbitcrack doesn't work fine with more than 260000 keys, it simply skips to detect the key.
You suggested a keyrange of 268436000 keys..
f7051f27b09112d4 = 17799667357578236000
f7051f27a09112d4 = 17799667357309800000
17799667357578236000 - 17799667357309800000 = 268436000 keys
Why don't you post your result (without cuts) with cubitcrack too?
I will be very glad to see your demonstration with more keys and see the key found at the end of the software results!