Radeon VII CORE_RESTART BAD_WORK_UNIT again and again

[uuw82008]

Windows 10 Pro for Workstations
Adrenalin 22.10.3 Optional

The maximum number of allowed characters is 60000.

it‘s over 120000

so I upload the log here

https://pastebin.com/0pCauXwM


download the project ,then core restart and bad word unit,download another project, repeat again
about 5 time the win system crash

I have tried 6 different versions of the driver, all have the same problem
Adrenalin 22.10.3 Optional
Adrenalin 22.5.1
Adrenalin 22.3.1
Adrenalin 21.10.3
Adrenalin 21.3.1
Adrenalin 20.8.3


any one use Radeon VII recently？

[toTOW]

Since every WU is failing very early, I suspect something is wrong with your GPU ...

Can you test it with Furmark and OCCT ?

[uuw82008]

Since every WU is failing very early, I suspect something is wrong with your GPU ...

Can you test it with Furmark and OCCT ?

I just ran the test

[BobWilliams757]

Windows 10 Pro for Workstations
Adrenalin 22.10.3 Optional

The maximum number of allowed characters is 60000.

it‘s over 120000

so I upload the log here

https://pastebin.com/0pCauXwM


download the project ,then core restart and bad word unit,download another project, repeat again
about 5 time the win system crash

I have tried 6 different versions of the driver, all have the same problem
Adrenalin 22.10.3 Optional
Adrenalin 22.5.1
Adrenalin 22.3.1
Adrenalin 21.10.3
Adrenalin 21.3.1
Adrenalin 20.8.3


any one use Radeon VII recently？

I had similar problems after installing the new drivers, and had posted about it back in September. This was using just a Vega 11 onboard graphics on a Ryzen 2400G.

OK... am I the only one on F@H that had issues with the new drivers? I got a couple crashes after installing them, and ruled out everything but the drivers before changing them. Reverted back, no issues.

So if nothing else, it's out here in the forums if anyone else has any problems. Ryzen 5 2400G, ASRock MB, quick memory.... and rock solid with F@H until the driver update. It only happened with heavy use (video editing) by a second logged in user on the system with folding in the background, and only a couple times. But that's a couple times more than it ever crashed in the past. Once going back to an older driver, I intentionally torture testing with F@H, a couple of benchmarks, and some web browsing and video editing all going on at once. The system didn't even blink.


On another note a question, since I haven't had this issue before. It was getting a driver timout error, but wouldn't reset on it's own. But F@H kept running the client, but couldn't work properly with the driver issue. So after the initial crash, it downloaded and dumped 4 or 5 work units before my wife filled me in that she had computer problems. Since this happened twice, it dumped 10 or 12 work units with errors. If this happened and wasn't detected, will the assignment server shut it down at some point and not issue another WU?

It was only taking 2-3 minutes to download, try, set and error code, and dump a work unit. I'd just hate to jump on the computer one day and find out it had dumped a whole bunch of work.

Reverting to old drivers had it fixed... I thought. Then it started the same pattern of crash once, crash until the servers wouldn't issue any more work. I finally reverted back to Windows default drivers and they seemed to be more stable for a few weeks until I upgraded to a unique graphics card. In the two or so years I folded on that iGPU, I had nothing but stability. Of the (very few) work units that failed, many were reported as problematic for others as well. But even if they failed it picked up another work unit and was back up and working after the core restart. With the new drivers, one crash and it would continue.

[muziqaz]

I see a lot of projects failing from the same lab.

Any overclocks/underclocks? Specifically HBM?

[daratmp]

I see a lot of projects failing from the same lab.

Any overclocks/underclocks? Specifically HBM?

No, all default settings

[muziqaz]

Is the card second hand, or did you buy it new, and was there any signs in the past of it being unstable. Are PCIe settings in BIOS tweaked? I'm just shooting blanks here, maybe some ideas pop up. Other than that the card might be faulty

[pyrocyborg]

I had an issue similar to this with my 6700 XT on one of my PC. I had to use DDU to completely remove all traces (or most traces) of the earlier drivers and prevent Windows Update from updating and messing up with drivers, then install the drivers again (I installed 22.10.1, but it's irrelevant in your case as you can use ealier drivers without any negative impact on your PPD with your Radeon VII).

On another PC with a 6800 XT, I had to format and start anew as it had some bad work units from time to time. A fresh Windows install did help in that case as I couldn't pinpoint the problem.