Yse, unfortunately My work is on linux os so I can't use windows all the day. Knowing that this bug is very random and not often happening I can't tell on windows because i'd have to use it many days but I can't because I work on linux . I tried lauching a game on linux for about 5 minutes it worked without issue, also I did some browsing for 30 minutes without issues. But it doesn't mean it's okay because even on linux this bug happens sometimes after some days of work :/

I have 16GB , 2x8GB in dual channel.
Free command:

Well mokrane, not sure what else I can tell you. It's either a driver issue, or it's hardware issue. Kernel 5.3 certainly doesn't have an amdgpu driver that provides decent support for the card we're talking about here, so you will need to upgrade the kernel (and thus the amdgpu driver), and/or the amdgpu kernel driver itself (but better to upgrade the kernel and you'll get a better amdgpu driver with it). At the end of the day, it's the kernel driver that actually sends commands to the hardware itself, in other words, the kernel driver directly interfaces with the hardware it's written to support. You can try downloading the driver from AMD themselves here, but it depends on whether their driver supports your particular distro or not. Again, from what you've said so far, my guess is it's a driver issue - and it certainly is with kernel 5.3 Since even with kernel 5.5 I had problems with the exact same video card, like I said before. Like I also said before, my card works fine since upgrading the kernel and therefore getting a better amdgpu driver.

I seriously doubt your problems have anything to do with RAM, since the minimum RAM requirement for the video card in question is 4GiB. With 8GiB of RAM recommended for it - which you have.

So like I said above, you'll have to try and find out if it's a hardware or a software issue, and then go from there - you cannot fix a hardware issue with software. Like I also said, make sure the hardware itself is installed correctly, verify that *first*, then move on to the driver - this is troubleshooting, we can't do that from here, only you can. Focus on determining if it's a hardware or software issue like I said before first before you get sidetracked with RAM and whatever else.

I apreciate your support really, you are right. I've just installed kernel v5.10.15 which is apparently the latest stable one. I stressed my GPU under windows for about 5 minutes without issue, As I said it seems that under windows there is no issue.
I'll investigate with my ssd since it's a diferent one for linux and windows. And i'll try to test my ram.

For drive link there is no opensuse one I'll see if I can go with SLED/SLES 15 SP2 one. For one I'll stick with my driver and see if new kernel fixed my issue so I can work peacefully (I wish)

Many thanks again for your help and patience, especially for a newbie like me .

You're welcome mokrane. Let us know how it works out for you.

Vanilla 5.3, no doubt. Leap kernel, you can't know without going through its patch set inventory. All openSUSE's non-vanilla kernels are loaded with backports. I've seen an openSUSE kernel developer recently report that Leap 15.2's 5.3 kernel is equivalent to upstream 5.9 WRT graphics.

I recommend OP report this to openSUSE's developers as described here. Developers don't often fix problems they don't know about.

Thank you mrmazda, As I said in my first post, this issue apeared in Manjaro distro before using opensuse, so I think it's not distro specefic error.
Didn't know that 5.3 is equivalent of 5.9, this is a good info since in Manjaro the issue persisted even with kernel 5.9.
I installed kernel 5.10.15 yesterday to see if this fixed the issue. I'll wait and see.
Thank yo uagain for your support

And openSUSE is the only distro that backports stuff to their kernel's ? (rhetorical question) Kernel 5.5 [that didn't have a good enough amdgpu driver for the card in question] that I was using on OpenMandriva 4.1 was installed from packages, not downloaded from kernel.org and built by myself. I know OpenMandriva dev's also add patches to the kernels they build for OpenMandriva. So what makes you think that openSUSE is the only distro that patches their kernel? (rhetorical question) I dare say most distro's patch their kernel's to at least some extent, so that's by no means unique to openSUSE.

That doesn't necessarily mean that openSUSE's 5.3 kernel has the same version of amdgpu that a so-called "vanilla" 5.9 kernel would provide. That could just be DRM patches for all we know, given your very vague statement above.

Besides, if you're going to patch a 5.3 kernel to a 5.9 kernel, then given the gap between those two versions; why on earth wouldn't you just download the source for a 5.9 kernel in the first place and configure and add whatever patches to it? It doesn't make sense as to why a distro developer would do that unless it's something like antiX that's actually designed for older hardware. So I'm not sure you actually understood their statement, given it's hard to believe a distro developer could say something like that.

Red Hat & Fedora do it to be sure. I once grabbed a Fedora kernel with the patches separated, and there was over a Meg's worth!

I can see why it's done; to try to get later functionality (bugfixes, security issues & some new features) while keeping older library compatibility. One of the RH systems using 2.6.32 kernels used run in one of the older RH systems that had support dropped in the last few years.

That developer is an SLE employee. 15.2 is the last Leap release to use a kernel merely derived from an SLE kernel. 15.3 is approaching beta and will use SLE kernels as-is AIUI. My understanding of why is too nebulous to be sharing. I'm sure if you want to know why you'd be able to find it somewhere in SLE or openSUSE documentation.

https://bugzilla.opensuse.org/show_b...?id=1180742#c1 is a comment from same developer similar to the one I had in mind writing comment 12. It might be the same one.