Quote from: Tony8989 on Today at 09:30:33 PM

Bro Tried all these configs — all crash with too many resources requested for launch

/bin/cuBitCrack --keyspace 5206e53083080a29e7:5206eef59f4d2c09e8 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU -b 132 -t 256 -p 6048
[2025-08-04.22:05:51] [Info] Compression: compressed
[2025-08-04.22:05:51] [Info] Starting at: 00000000000000000000000000000000000000000000005206E53083080A29E7
[2025-08-04.22:05:51] [Info] Ending at: 00000000000000000000000000000000000000000000005206EEF59F4D2C09E8
[2025-08-04.22:05:51] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2025-08-04.22:05:51] [Info] Initializing NVIDIA H200 NVL
[2025-08-04.22:05:51] [Info] Generating 204,374,016 starting points (7796.2MB)
[2025-08-04.22:06:30] [Info] 10.0%
[2025-08-04.22:06:31] [Info] 20.0%
[2025-08-04.22:06:31] [Info] 30.0%
[2025-08-04.22:06:32] [Info] 40.0%
[2025-08-04.22:06:32] [Info] 50.0%
[2025-08-04.22:06:32] [Info] 60.0%
[2025-08-04.22:06:32] [Info] 70.0%
[2025-08-04.22:06:32] [Info] 80.0%
[2025-08-04.22:06:33] [Info] 90.0%
[2025-08-04.22:06:33] [Info] 100.0%
[2025-08-04.22:06:33] [Info] Done
NVIDIA H200 NVL 19244 / 143156MB | 1 target 3079.91 MKey/s (11,444,944,896 total) [00:00:01]

It's mean your device max support -t 256
Now expand -p 6048 to on word
-p 6048 + 64. Or 32 every time test with add into -p 6112
When last stop that time just minus 32 for get final -p value workable
By these setting u will get highest speed print ur last final value of -p