search

albertobsd / keyhunt

privkey hunt for crypto currencies that use secp256k1 elliptic curve
MIT License
640 stars 349 forks source link

...electrical malfuntion, radiation or a cosmic ray #236

Open ovix opened 1 year ago

ovix commented 1 year ago

``[+] Version 0.2.211031 Trick or treat ¡Beta!, developed by AlbertoBSD [+] Quiet thread output [+] Stats output every 10 seconds [+] K factor 256 [+] Random mode [+] Mode BSGS random [+] Opening file tests/125.txt [+] Added 1 points from file [+] Range [+] -- from : 0x10000000000000000000000000000000 [+] -- to : 0x18ffffffffffffffffffffffffffffff [+] N = 0x100000000000 [+] Bloom filter for 1073741824 elements : 3680.66 MB [+] Bloom filter for 53687092 elements : 184.03 MB [+] Allocating 819.00 MB for 53687092 bP Points [+] Reading bloom filter from file keyhunt_bsgs_4_1073741824.blm .. Done! [+] Reading bloom filter from file keyhunt_bsgs_5_53687092.blm .. Done! [+] Reading bP Table from file keyhunt_bsgs_2_53687092.tbl .. Done! [E] Memory checksum mismatch, this should not happen but actually happened98813993601 keys/s) A bit in the memory was flipped by : electrical malfuntion, radiation or a cosmic ray Current Checksum: 5b8413fd7aa851e6b60a1993840bde238b0ff8c9383e3670d41f69c0950be632 Saved Checksum: 597afae9688ed6d9804f96646208eb401954b14ad33959bc604d59e0ce023d0d Backup Checksum: 597afae9688ed6d9804f96646208eb401954b14ad33959bc604d59e0ce023d0d Exit!

albertobsd commented 1 year ago

Is your type Memory ECC ?

Read: https://www.tomshardware.com/reviews/ecc-memory-ram-glossary-definition,6013.html

This error is caused because some bit or bits in the Bloom Filter or bP Table where modified by electrical malfuntion, radiation or a cosmic ray. ( Actually is really hard to know why the bits changed ) But they did it.

If your RAM is not ECC then this is somekind of normal behaivor after some Time running the tool.

If you RAM is ECC then this was a very rare situation, if the problem persist try to change your RAM type.

Regards!

ovix commented 1 year ago

I've been running the keyhunt application for over a year and it's the first time I've received this error message, which is actually very funny. I don't know what type of RAM I have, I only know that I have two Kingstone modules of 16 GB each. It is true that the modules are not identical and sometimes I get BSOD errors if I set the K factor higher. I received the error message after 3 weeks of non-stop running at the same time as 5 other instances that are still running. Thank you for answering me and good luck in your hobby and in everything you do for yourself and others.