The way to keep it from trying to put a new driver version back in is to go to device manager, go to display adapters, find yours, and then ROLL BACK to the previous driver version. It won't update the driver again until there is a new version of Windows(going to Windows 10 or 11 22H1 for example). My other question though, is why PhoenixMiner just breaks with new AMD driver versions. If you intentionally install anything newer than Radeon Software 21.11.3 for RDNA 2 cards(including my Radeon 6800), the thing comes back with the unknown version issue and it won't mine without -clkernel 0. So, is that a hardcoded "look for driver version" and then break as a result, because it should TRY to use the proper code path for these newer drivers, but it seems to be doing a fallback if it doesn't recognize the driver version.
PhoenixMiner doesn't support anything newer than 21.11.3. I don't know if the drivers are so significantly different to cause this problem every three months, or if PM is just coded to look for specific driver versions and won't even TRY to use the AMD path with newer drivers than what it specifically looks for. It's annoying, that's for sure.
Hi there,
Got the same error this morning when I woke up:
GPU1: clSetKernelArg (-48)
Fatal error detected. Restarting.
Tried adding
-clkernel 0 - that worked, but noticed that avg hashrate dropped from
78-79 to
68-70Updated the drivers to
21.10.2 and the miner from
5.5c to
PhoenixMiner_5.9d_Windows.zipStill doesn't work without
-clkernel 0 and still loses around
10% of hashrate
Mining on my home gaming PC with
Radeon VII, so "use linux" is not an option.
Config I'm using to keep the GPU a bit underutilized to avoid raping it to death:
-clkernel 0 -pool aspac1-eth.hiveon.net:4444 -pool2 aspac1-eth.hiveon.net14444 -wal XXX -cclock 1550 -cvddc 850 -mclock 1000 -fanmin 70 -gpus 1
This results in following temp/power which previously resulted in
78 avg hashrate:
GPU1: 78C 47% 152W
GPUs power: 152.0 W
Now it results in
64-70.
PC config:
Can anyone advise how to fix to avoid the requirement to use
-clkernel 0 switch which apparently drops the hashrate?
Couple of days ago, my rigs stopped mining after a Windows Update, when the update replaced my AMD driver. In Device Manager, the driver is shown as
30.0.13023.1012. After restart, one of my rigs with newer GPUs is working fine with this driver, but my other rigs with Polaris cards are unstable or not working with it. I uninstalled this driver, DDU it, and installed the old drivers I had, disabled driver update in Windows Update, but that driver keeps coming back somehow. So check your driver version. I see yours and a couple more questions, are similar to my problem.
Also for your Radeon VII, read the first page of this treat. There were notes from the devs about specific drivers to use with Radeon Vega and Radeon VII.