The new beta version is ready. It is mostly a bugfix release, the more significant upgrades are coming next month. You can download PhoenixMiner 6.0a from here:


PhoenixMiner_6.0a_Windows.zip
PhoenixMiner_6.0a_Linux.tar.gz


The new features in this release are:

• Full LHR disable mode -lhrdis <n>  1 - yes (default), 0 - no
• Show the GPU vendor name in the list of GPUs to make it easier to identify the GPUs
• Added support for the latest AMD Linux drivers 21.40.1. There are some bugs in these drivers, particularly the clocks and voltages can't be set properly with older
  cards (RX4x0/RX5x0/Vega/RadeonVII)
• Validated support for the latest AMD Windows drivers up to 21.11.2
• Fixed issues with AMD RX6700XT cards with the latest AMD and Linux drivers
• Fixed issues with AMD Vega and Radeon VII cards on latest Windows and Linux drivers
• Fixed crash with very old Nvidia drivers (3xx.x)
• Other fixes and small improvements

The updated list of known issues (driver incompatibilities, etc.) and workarounds:
AMD Linux driver 21.40.1 has a bug preventing proper setting of clocks and voltages on older cards (RX4x0/RX5x0/Vega/RadeonVII). Given that these drivers are also
usually slower than the older drivers for these cards, we recommend using Linux drivers 20.30 for anything older than RX6000 series.
If you are using Linux drivers 21.40.1 with Radeon VII cards, you need to add the option -fpwm 1 in order to have proper fan control.
AMD Linux drivers 21.40.1 has finally removed the requirement of PCIe atomics but there are problems when you try to mix Polaris (RX4x0/5x0) cards and Vega or newer
cards on the same rig.
Some Nvidia cards will report a lot of stale shares under Windows 11. Using the same driver version under Windows 10 resolves the issue.

If you have an idea of the password used, or passwords used for other things then you might have a chance.
If it was random generated then you are most likely out of luck.

I can help, its up to you!!

It amazes me that at least once a week I am contacted by people with these fake wallets that literally give me the hints that are posted from the sellers of these fake wallets.
I am trying to run a legit password cracking business for people that have actual wallets that belong to them.
So if you are one of those legit people please reach out.

If you have an old Bitcoin wallet and it had funds in it up to recently then do not delete it. There were forks for other Bitcoin like Bitcoin Cash and if you did not receive you will never be able to.
Just save it, rename it, not hurting anything and takes up no space whatsoever.

Backup to external or cloud drive as well.

Is there any difference if the wallet was created long ago?
Because based from the context, it sounds like newer wallets are harder to crack compared to old ones.
[/quote]

Years ago people used very simple passwords, usually kids names with birth year or something stupid like that or password123.
As the years went on and the Hackers kept stealing people started making more complex passwords with special characters.

So wallets created in 2013 that have not been touched most likely have more general passwords like in the Rockyou list.

The best part to this entire thread is the owner still has 33.54 and did not have to share any of it.
Maybe one day Bitcoin will be worth some crazy dollar value and this topic starter will come back here begging for help.

Open Wallet in Bitcoin Core and look at the transaction history to get an idea of when wallet was created.
If it was created more recently then I can tell you that without any hints you will never solve.

If you dont want to give up then maybe visit hashbull.org and use there interface to extract hash needed to crack.
After that you can continue using their simple menu for cracking.

If you do find hints or something and still need help, reach out.

Dave

still looking for help on this, send me a PM please

Are you able to extract the hash from the wallet.dat file?
This can be done online or in Hashcat.
Need my help, send me a message.

Never send Wallet.dat to anyone, ever. No reason to do so.

I never claimed to be Dave from walletrecovery.
My name is Dave, so nothing false about that.

As for my services, they are legit. I work with a few cracking guys, they use my equipment to help them succeed.
PM me and I will give you my number to call to discuss.

as for currupted hard drives, there are many ways to recovery content without having to boot into it.

I am far from spam, nothing to hide here.
I am offering my services and my equipment to help recover someones funds.
The only spam is people like you negatively posting your remarks.
If the person responds to me via email, I will give him my number and we can chat.
I offer Wallet Recovery Services, my equipment is real 44 Core Dual Xeon with 4 Tesla V100's, with 2 more on order.
My knowledge as well, because without knowledge, my equipment would be useless.

what do you have to offer? Don't answer, because I already did!!

If you are the true owner of this Wallet.dat file, I will offer my services.
please send me an email dave@dafmarketing.com

I have some serious cracking power and can probably brute force the wallet.dat if it can be recovered.

Dave

Hi,

before you make things worse, stop trying to fix it.
my email address is dave@dafmarketing.com

not sure where you are located, but there are many ways to recover currupted files.
send me an email, and lets discuss exactly what you did and how it became this way.

Dave

Hi,

if anyone can help me solve this issue.

./LBC -h  this works fine, displays as it should

when I run ./LBC -x
i end up with this error

Will use 0 CPUs.
New BLF data found. (DL-size: 296.65MB)

bzip2: Compressed file ends unexpectedly;
   perhaps it is corrupted?  *Possible* reason follows.
bzip2: No such file or directory
   Input file = 171125-2642d3b0bdf4ff2fb6828801a39da3d3.blf.bz2, output file = 171125-2642d3b0bdf4ff2fb6828801a39da3d3.blf

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

bzip2: Deleting output file 171125-2642d3b0bdf4ff2fb6828801a39da3d3.blf, if it exists.
Some files were updated - please restart LBC.

I have restarted and tried over and over

2018.07.02:11:35:15.325: main Phoenix Miner 3.0c Windows/msvc - Release
2018.07.02:11:35:15.325: main Cmd line: -pool us1-etc.ethermine.org:4444 -wal 0x2497c06850cbe0c1b39068897bc5d001ad60112a.MiningRig1 -amd
2018.07.02:11:35:15.518: main Available GPUs for mining:
2018.07.02:11:35:15.518: main GPU1: AMD Radeon (TM) R9 390 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 44 CUs
2018.07.02:11:35:15.518: main GPU2: AMD Radeon (TM) R9 390 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 44 CUs
2018.07.02:11:35:15.518: main GPU3: AMD Radeon (TM) R9 390 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 40 CUs
2018.07.02:11:35:15.532: main ADL library initialized
FATAL ERROR: Debugger Detected

i tried with and without the -amd

I am getting this message and not sure why on 9.0.0
Watchdog has started
Starting miner on devices (0)
Failed to initialize miner Failed to create solver for device 0
miner died! It will be restarted soon...

Figured it out. I am using my D drive for Windows and all I had to do was put the NVSMI file on my C drive ""C:\Program Files\NVIDIA Corporation\NVSMI""

please issue a payment, it has been 15 days of no activity, thank you
463tWEBn5XZJSxLU6uLQnQ2iY9xuNcDbjLSjkn3XAXHCbLrTTErJrBWYgHJQyrCwkNgYvyV3z8zctJL PCZy24jvb3NiTcTJ.1e97b62cd5df47fa81254d828d72e445e1c74afa008e4f9384749e94c115ca e6