Blender destroy my GPU ? :(

Did blender damage my GPU?

I wanted to convert a texture from normal to PBR to make it more realistic. Then I played with Cycles, and rendering
During rendering, a GPU error popped up. Something like that, then I went into Unreal Engine 5, and noticed poor lighting and vibrations on the textures, so I reset both graphics cards, and it returned to normal, sharp objects, but the vibrations remained. Factory settings did nothing, as did improving the textures by a millimeter up, which is the standard option, to remove it. I don’t know what’s going on, please help. My laptop is an Acer Geforce RTX 4050.

if it’s broken then it broke on its on. software like blender can’t destroy gpus.

sounds like a thermal problem to me.Could be wrong though.
However you should check your temps.

1 Like

Temperatures are normal. Everything works smoothly.
I forgot to add that when I turn off real time and frame display it’s fine. However, if I turn them on the problem returns. I don’t know what’s going on

Welcome tada…

what do you mean by

??

If this is some sync feature for games… and it works when off for an non-game… then simply turn it of ??

https://www.youtube.com/watch?v=nnmFK4rsbqs And you can see this flickering on the edges of the textures
https://zapodaj.net/plik-MFYcd7SBLN
And here, when I turn off real time and frame display, I marked it with an arrow so we could understand each other, is this forum only for blenders? If so, I apologize for creating a topic. My English is broken

But this is in the real engine…

I still do not know what you mean by real time in this context… if there is some slightly movement then this aliasing is normal some anti-alias or blur filter may help.

If you want some more inforamtion about this you may also which

:question:

https://blenderartists.org/uploads/default/original/3X/d/b/dbfe344fc3ee6c50da5eb42f69a1a5aeb028291e.png
I just got this error while rendering a texture in blender
And after this error in Unreal Engine 5 these vibrations started, which was not the case before.

Well… maybe follow this hint… ??