cancel
Showing results for 
Search instead for 
Did you mean: 

PC Drivers & Software

stevens195
Adept I

AMD Software: Adrenalin Edition 22.11.2 "Fixed Issue" is not fixed and still happens with my 6800 XT

Hello.

In the AMD Software: Adrenalin Edition 22.11.2 release notes, on the "Fixed Issues" topic, there is an issue which supposedly was fixed, where during video playback and window switching, an intermittent driver timeout or black screen occurs on Radeon RX 6000 series GPUs using some 240Hz refresh rate displays primary displays plus low refresh rate secondary display configurations.

This is not the case, as it still happens ALOT with my RX 6800 XT. This was supposed to be fixed, since it's in the "Fixed Issues" topic, and not the "Known Issues" topic, but it turns out it isn't

Is there any way to fix this? Or will it only be fixed with a new driver update? (Which seems like it will take years to come, since AMD forgot RX 6000 Series still exists...)

Thank you in advance!

0 Likes
3 Replies
ardankyaosen
Miniboss

If it's still happening and you can reproduce it, use the Bug Reporting Tool at the top of the Adrenalin software screen to report it.

0 Likes

I already did that, but that doesn't help with my situation at all, it'll take months before it even gets fixed, I need a solution quickly since this is impacting my work

0 Likes
robertjoe1
Journeyman III

I understand how frustrating that can be, especially when you're under time pressure. Since direct integration between Purview and AWS Databricks isn’t currently supported, here are a few alternative approaches you might consider for a quicker solution:

  1. Custom Metadata Pipeline: Create a script or tool that extracts metadata from your AWS Databricks instance and pushes it to Purview using APIs. This way, you can automate the process and get the metadata you need.

  2. Intermediary Storage: If feasible, you could export relevant metadata to a temporary storage solution (like Azure Blob Storage) and then ingest that data into Purview.

  3. Third-Party Tools: Look into third-party data governance tools that support both AWS and Azure. Some tools may have the capability to bridge the gap more effectively.

  4. Manual Entry for Urgent Needs: While not ideal, consider manually entering critical metadata into Purview to alleviate immediate impacts on your work.

  5. Reach Out to the Community: Sometimes, other users may have found creative workarounds. Sharing your specific needs in community forums could yield some helpful suggestions.

I hope one of these options can help you find a quicker solution! If you have any specific requirements, feel free to share, and I can try to assist further.

0 Likes