A little over a year ago, I wrote this on the forum:
https://forums.opera.com/topic/73279/opera-and-amd-rx6600

Now, in the middle of this year, I assembled a new PC with the RX 7800xt, installed Opera, and found that I was having the crashing issue again. I disabled hardware acceleration, tried everything I could in the settings, and the issue persists. I consulted with the AIs about the issue, and this was their analysis:

'The fact that your old RX 570 (GCN architecture) never had this problem is the strongest evidence that the error lies in the implementation of the RX 6000/7000 series driver when handling certain Opera-specific software calls, regardless of the CPU generation (Zen 3 or Zen 5).

Root Cause Analysis
The problem is not a simple rendering bug, but a timing issue or kernel-level deadlock triggered by this interaction:

Driver calls (Opera): When Opera makes a call to the GPU driver (for example, to load a video or update a complex animation in its interface), it uses a code path in the AMD drivers that is optimised for RDNA.

Kernel Lockup (RDNA Driver): Under certain circumstances (which only occur with Opera), the AMD driver (AMDKMDAG) enters a wait state or infinite loop that paralyses critical system resources, including the I/O manager.

Symptom: The system freezes completely (including Num Lock) because the frozen thread is vital to the functioning of the Windows Kernel.'

Data Loss: The loss of your Notepad confirms that the file system is inaccessible; the save operation cannot be completed because communication with the SSD is paralysed.

I think Opera and the new AMD architectures don't get along, so I have no choice but to switch to Firefox or Brave.

My specifications: R9 9950x, RX 7800xt, 64GB Corsair RAM, SSD m.2 Firecuda.