F5F Stay Refreshed Hardware Desktop Rx470 isn't functioning on your PC yet, but it works elsewhere.

Rx470 isn't functioning on your PC yet, but it works elsewhere.

Rx470 isn't functioning on your PC yet, but it works elsewhere.

N
NALLE_PUH
Member
170
07-05-2022, 11:57 PM
#1
Hello! I recently purchased a used RX 470 (PowerColor) and tested it on my current Linux machine. After just a short period of use, everything froze abruptly. Since I was running Linux (Arch), I suspected a driver issue, but when I switched to Windows, the system reported an error code 1603 during installation—AMD described it as a software problem, possibly linked to a minimal custom ISO setup. It did install partially, and I ran FurMark, which also froze after a few minutes, showing a white window and a driver warning about unresponsiveness. I attempted the same with an updated driver via the 1603 resolution page, but the PC refused to restart, hanging during boot. At that point, I suspected the GPU was the culprit, as my PS (Seasonic SS-500ET) should handle it well despite its 85W rating. I tried using it on another machine with a 350W Hopely, which worked fine—no issues there. Running Unigine Heaven for Linux on that PC didn’t cause any problems even after about 30 minutes. It seems the GPU is functioning correctly. Still, I’m trying to identify the exact component causing this behavior in my setup. I thought the PS might be aging and producing lower voltage outputs, but its readings are stable under load (5.05/12.33V idle, 5.06/12.29V under stress). It measures only 15W more than spec, though it has a small radiator. Any suggestions on what could be the cause? (Posting from the GPU thread; feel free to suggest a way to remove the first issue if you know of one.)
N
NALLE_PUH
07-05-2022, 11:57 PM #1

Hello! I recently purchased a used RX 470 (PowerColor) and tested it on my current Linux machine. After just a short period of use, everything froze abruptly. Since I was running Linux (Arch), I suspected a driver issue, but when I switched to Windows, the system reported an error code 1603 during installation—AMD described it as a software problem, possibly linked to a minimal custom ISO setup. It did install partially, and I ran FurMark, which also froze after a few minutes, showing a white window and a driver warning about unresponsiveness. I attempted the same with an updated driver via the 1603 resolution page, but the PC refused to restart, hanging during boot. At that point, I suspected the GPU was the culprit, as my PS (Seasonic SS-500ET) should handle it well despite its 85W rating. I tried using it on another machine with a 350W Hopely, which worked fine—no issues there. Running Unigine Heaven for Linux on that PC didn’t cause any problems even after about 30 minutes. It seems the GPU is functioning correctly. Still, I’m trying to identify the exact component causing this behavior in my setup. I thought the PS might be aging and producing lower voltage outputs, but its readings are stable under load (5.05/12.33V idle, 5.06/12.29V under stress). It measures only 15W more than spec, though it has a small radiator. Any suggestions on what could be the cause? (Posting from the GPU thread; feel free to suggest a way to remove the first issue if you know of one.)

L
lb23kh
Member
141
07-05-2022, 11:57 PM
#2
Tried changing power supplies but it didn’t fix the problem, indicating the issue isn’t with the PSU. The components I didn’t replace were CPU, motherboard, soundcard, HDDs, and RAM. It seems unlikely RAM and CPU are the culprits since they’ve functioned well for years without problems. HDDs appear to be stable too. My guess is the motherboard might be the source of the issue.
L
lb23kh
07-05-2022, 11:57 PM #2

Tried changing power supplies but it didn’t fix the problem, indicating the issue isn’t with the PSU. The components I didn’t replace were CPU, motherboard, soundcard, HDDs, and RAM. It seems unlikely RAM and CPU are the culprits since they’ve functioned well for years without problems. HDDs appear to be stable too. My guess is the motherboard might be the source of the issue.

K
kungfutyla
Posting Freak
780
07-05-2022, 11:57 PM
#3
I think there could be a problem with the motherboard's 75W capacity for the GPU. There should be a method to verify this.
K
kungfutyla
07-05-2022, 11:57 PM #3

I think there could be a problem with the motherboard's 75W capacity for the GPU. There should be a method to verify this.