From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105425] 3D & games produce periodic GPU crashes (Radeon R7 370) Date: Mon, 02 Apr 2018 09:33:21 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1948630271==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 8E37889704 for ; Mon, 2 Apr 2018 09:33:21 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1948630271== Content-Type: multipart/alternative; boundary="15226616010.D55bEE6d.24557" Content-Transfer-Encoding: 7bit --15226616010.D55bEE6d.24557 Date: Mon, 2 Apr 2018 09:33:21 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D105425 --- Comment #13 from iive@yahoo.com --- (In reply to MirceaKitsune from comment #10) > Created attachment 138438 [details] > Screenshot of the Blender window glitching >=20 > I should add another detail to the discussion. I know this may be a separ= ate > issue which might have nothing to do with the crash, but at the same time= I > wouldn't be surprised if it does: Glitched graphics often indicate someth= ing > going wrong with the display, such as corrupt textures in video memory, > which may ultimately lead to just such a lockup. >=20 > On occasion, certain programs (namely Firefox and Blender) glitch out and > draw broken rectangles all over the window. Some of those glitches are ju= st > boxes of random colors, others contain pieces of past images (for instanc= e I > saw patterns from my lock screen background). Sometimes they quickly > disappear on their own, at other times I have to restart the program as it > becomes illegible and unusable. If I move anything the squares flicker all > over the place. The glitches continue even after I disable desktop effect= s, > thus KDE compositing should have nothing to do with it. >=20 > Attached is a screenshot of the glitch happening in Blender, showing its > window covered in the corrupt squares. I'm curious what your opinion is. > Again I know this may be an unrelated issue, but I'm wondering whether it > indicates some video storage corruption that's also leading up to the > lockups. I think you should try running your hardware under Windows. You might also want to check if you still have warranty on the card and act quickly if it expires soon. I do suspect that it is a common hardware fault that happens with most video cards over time. I also had it on my very old HD5670, but with some help I = did manage to salvage it, for now. My first symptoms were problems with RAM, th= at could be "workaround"-ed by lowering the memory frequency to half of the nominal frequency. The problem is in micro BGA (Ball Grid Array). The GPU chip is the size of a fingernail and is placed on a "pad" that is usually about square inch size.= The chip and the pad are connected with microBGA. The pad has a normal BGA on i= ts other side that is soldered to the GPU card. With thermal expansion and contraction the soldier of the micro pad fractures and starts to misbehave. It's common to point out that lead-free soldier is not as reliable under temperature changes. You might have heard about solutions like baking the card or re-balling the BGA. I do not recommending trying these. Baking the card might damage other components on it (capacitors, everything plastic). Re-balling changes the soldier of the normal BGA, but it is very expensive manual labor that is not even fixing the BGA which causes the problems. All these "solutions" work because they also heat the small GPU chip and me= lt the microBGA soldier. If you are sure that this is your problem, you can find somebody who knows = how to use a hot air soldering station and heat just the small GPU chip with 200-250C for about 2-5 minutes. These the the temperatures and duration used for manufacturing the card, so they should be safe. Good luck. --=20 You are receiving this mail because: You are the assignee for the bug.= --15226616010.D55bEE6d.24557 Date: Mon, 2 Apr 2018 09:33:21 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 13 on bug 10542= 5 from iive@yahoo.com
(In reply to MirceaKitsune from comment #10)
> Created attachment 138438 [=
details]
> Screenshot of the Blender window glitching
>=20
> I should add another detail to the discussion. I know this may be a se=
parate
> issue which might have nothing to do with the crash, but at the same t=
ime I
> wouldn't be surprised if it does: Glitched graphics often indicate som=
ething
> going wrong with the display, such as corrupt textures in video memory,
> which may ultimately lead to just such a lockup.
>=20
> On occasion, certain programs (namely Firefox and Blender) glitch out =
and
> draw broken rectangles all over the window. Some of those glitches are=
 just
> boxes of random colors, others contain pieces of past images (for inst=
ance I
> saw patterns from my lock screen background). Sometimes they quickly
> disappear on their own, at other times I have to restart the program a=
s it
> becomes illegible and unusable. If I move anything the squares flicker=
 all
> over the place. The glitches continue even after I disable desktop eff=
ects,
> thus KDE compositing should have nothing to do with it.
>=20
> Attached is a screenshot of the glitch happening in Blender, showing i=
ts
> window covered in the corrupt squares. I'm curious what your opinion i=
s.
> Again I know this may be an unrelated issue, but I'm wondering whether=
 it
> indicates some video storage corruption that's also leading up to the
> lockups.

I think you should try running your hardware under Windows.

You might also want to check if you still have warranty on the card
and act quickly if it expires soon.

I do suspect that it is a common hardware fault that happens with most video
cards over time. I also had it on my very old HD5670, but with some help I =
did
manage to salvage it, for now. My first symptoms were problems with RAM, th=
at
could be "workaround"-ed by lowering the memory frequency to half=
 of the
nominal frequency.

The problem is in micro BGA (Ball Grid Array). The GPU chip is the size of a
fingernail and is placed on a "pad" that is usually about square =
inch size. The
chip and the pad are connected with microBGA. The pad has a normal BGA on i=
ts
other side that is soldered to the GPU card. With thermal expansion and
contraction the soldier of the micro pad fractures and starts to misbehave.
It's common to point out that lead-free soldier is not as reliable under
temperature changes.

You might have heard about solutions like baking the card or re-balling the
BGA. I do not recommending trying these. Baking the card might damage other
components on it (capacitors, everything plastic). Re-balling changes the
soldier of the normal BGA, but it is very expensive manual labor that is not
even fixing the BGA which causes the problems.

All these "solutions" work because they also heat the small GPU c=
hip and melt
the microBGA soldier.

If you are sure that this is your problem, you can find somebody who knows =
how
to use a hot air soldering station and heat just the small GPU chip with
200-250C for about 2-5 minutes. These the the temperatures and duration used
for manufacturing the card, so they should be safe.

Good luck.


You are receiving this mail because:
  • You are the assignee for the bug.
= --15226616010.D55bEE6d.24557-- --===============1948630271== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1948630271==--