XFX Issues

It seems that a lot of GPU problems revolve around specific versions of drivers. Though AMD has their own support structure, you can often learn from information reported by others who fold.

Moderators: Site Moderators, FAHC Science Team

Post Reply
Malique2
Posts: 14
Joined: Sat Jun 21, 2014 4:13 pm

XFX Issues

Post by Malique2 »

I Have a XFX 9070 Swift. I don't OC. Tried latest drivers, rolled back to prior drivers and same exact issue. I'm stumped. My other rig with 6 GPUs 5000/6000 series has zero problems.

I have been haven't been able to run FOH it yet. It downloads and starts folding, I watch the PPDs start counting down, that goes on for a few minutes then it fails and restarts over, and the process goes on and on and on.I did capture this in the log, which shows the failure.

23:58:25:I1:WU73:********************************************************************************
23:58:25:I1:WU73:Project: 18260 (Run 21, Clone 2, Gen 261)
23:58:25:I1:WU73:Digital signatures verified
23:58:25:I1:WU73:Folding@home GPU Core27 Folding@home Core
23:58:25:I1:WU73:Version 8.2.1
23:58:25:I1:WU73: GPU info: Platform: OpenCL: AMD Accelerated Parallel Processing
23:58:25:I1:WU73: GPU info: PlatformIndex: 0
23:58:25:I1:WU73: GPU info: Device: gfx1201
23:58:25:I1:WU73: GPU info: DeviceIndex: 0
23:58:25:I1:WU73: GPU info: Vendor: 0x1002
23:58:25:I1:WU73: GPU info: PCI: 10:00:00
23:58:25:I1:WU73: GPU info: Compute: 2.0
23:58:25:I1:WU73: GPU info: Driver: 3661.0
23:58:25:I1:WU73: GPU info: GPU: true
23:58:25:I1:WU73: Checkpoint write interval: 12500 steps (5%) [20 total]
23:58:25:I1:WU73: JSON viewer frame write interval: 2500 steps (1%) [100 total]
23:58:25:I1:WU73: XTC frame write interval: 5000 steps (2%) [50 total]
23:58:25:I1:WU73: TRR frame write interval: disabled
23:58:25:I1:WU73: Global context and integrator variables write interval: disabled
23:58:25:I1:WU73:There are 3 platforms available.
23:58:25:I1:WU73:Platform 0: Reference
23:58:25:I1:WU73:Platform 1: CPU
23:58:25:I1:WU73:Platform 2: OpenCL
23:58:25:I1:WU73: opencl-device 0 specified
23:59:54:I1:WU73:Attempting to create OpenCL context:
23:59:54:I1:WU73: Configuring platform OpenCL
00:00:12:I1:WU73:ERROR:exception: Error invoking kernel reduceEnergy: clEnqueueNDRangeKernel (-54)
00:00:12:I1:WU73:Saving result file ..\logfile_01.txt
00:00:12:I1:WU73:Saving result file science.log
00:00:12:I1:WU73:Folding@home Core Shutdown: BAD_WORK_UNIT
00:00:14:E :WU73:Core returned BAD_WORK_UNIT (114)
00:00:14:I1:Default:Added new work unit: cpus:0 gpus:gpu:10:00:00
00:00:14:I1:WU73:Uploading WU results
00:00:14:I1:WU74:Requesting WU assignment for user Maliki2 team 64
00:00:14:I2:OUT21:> POST /api/results HTTP/1.1
Joe_H
Site Admin
Posts: 8249
Joined: Tue Apr 21, 2009 4:41 pm
Hardware configuration: Mac Studio M1 Max 32 GB smp6
Mac Hack i7-7700K 48 GB smp4
Location: W. MA

Re: XFX Issues

Post by Joe_H »

Some things that might help are which OS you are using, which version of the F@h client, and how much RAM you have installed. I do know Project 18260 is particularly large and may use a larger amount of RAM during initialization.

Did you see WUs from other projects at all?
Image
Malique2
Posts: 14
Joined: Sat Jun 21, 2014 4:13 pm

Re: XFX Issues

Post by Malique2 »

Joe_H wrote: Fri Nov 07, 2025 12:23 am Some things that might help are which OS you are using, which version of the F@h client, and how much RAM you have installed. I do know Project 18260 is particularly large and may use a larger amount of RAM during initialization.

Did you see WUs from other projects at all?
OS is Windows 11. Version is 8.4.9 but did it in previous versions. 32 GB ram. I'm only seeing WUs from my CPU. I've let the GPU run a bunch of times with same results of BAD WORK UNIT. I'm just stumped. No overclock. Brand new card. 6 GPU rig next to me with 5000/6000 series cards, folding away, but this turd just doesn't want to. The code below is what I just got trying to run it again.

Code: Select all

03:03:24:I1:WU92:Version 8.2.1
03:03:24:I1:WU92: GPU info: Platform: OpenCL: AMD Accelerated Parallel Processing
03:03:24:I1:WU92: GPU info: PlatformIndex: 0
03:03:24:I1:WU92: GPU info: Device: gfx1201
03:03:24:I1:WU92: GPU info: DeviceIndex: 0
03:03:24:I1:WU92: GPU info: Vendor: 0x1002
03:03:24:I1:WU92: GPU info: PCI: 10:00:00
03:03:24:I1:WU92: GPU info: Compute: 2.0
03:03:24:I1:WU92: GPU info: Driver: 3661.0
03:03:24:I1:WU92: GPU info: GPU: true
03:03:24:I1:WU92: Checkpoint write interval: 100000 steps (5%) [20 total]
03:03:24:I1:WU92: JSON viewer frame write interval: 20000 steps (1%) [100 total]
03:03:24:I1:WU92: XTC frame write interval: 25000 steps (1.2%) [80 total]
03:03:24:I1:WU92: TRR frame write interval: disabled
03:03:24:I1:WU92: Global context and integrator variables write interval: disabled
03:03:24:I1:WU92:There are 3 platforms available.
03:03:24:I1:WU92:Platform 0: Reference
03:03:24:I1:WU92:Platform 1: CPU
03:03:24:I1:WU92:Platform 2: OpenCL
03:03:24:I1:WU92: opencl-device 0 specified
03:03:44:I1:WU92:Attempting to create OpenCL context:
03:03:44:I1:WU92: Configuring platform OpenCL
03:04:02:I1:WU92:ERROR:exception: Error invoking kernel reduceEnergy: clEnqueueNDRangeKernel (-54)
03:04:02:I1:WU92:Saving result file ..\logfile_01.txt
03:04:02:I1:WU92:Saving result file science.log
03:04:02:I1:WU92:Folding@home Core Shutdown: BAD_WORK_UNIT
03:04:02:E :WU92:Core returned BAD_WORK_UNIT (114)
03:04:02:I1:WU92:Uploading WU results
03:04:04:I1:WU92:Credited
muziqaz
Posts: 2169
Joined: Sun Dec 16, 2007 6:22 pm
Hardware configuration: 9950x, 9950x3D, 5950x, 5800x3D
7900xtx, RX9070, Radeon 7, 5700xt, 6900xt, Intel B580
Location: London
Contact:

Re: XFX Issues

Post by muziqaz »

Windows drivers hijacked your AMD drivers. Please reinstall AMD adrenalin software from AMD website
FAH Omega tester
Image
Malique2
Posts: 14
Joined: Sat Jun 21, 2014 4:13 pm

Re: XFX Issues

Post by Malique2 »

muziqaz wrote: Fri Nov 07, 2025 6:55 am Windows drivers hijacked your AMD drivers. Please reinstall AMD adrenalin software from AMD website
Reinstalled. Folding started with no percentage update. It was folding for awhile too! Rebooted and back to failing again. :e?:
Post Reply