F5F Stay Refreshed Hardware Desktop Troubles with graphics card TDR after RMA replacement—what should you do next?

Troubles with graphics card TDR after RMA replacement—what should you do next?

Troubles with graphics card TDR after RMA replacement—what should you do next?

Pages (2): 1 2 Next
L
Lips
Senior Member
624
04-21-2016, 06:11 AM
#1
L
Lips
04-21-2016, 06:11 AM #1

G
Go_Guten
Member
127
04-21-2016, 11:56 AM
#2
Consider using a CMOS reset. Check if XMP is overworking your setup. It might help to use just the lowest recommended power supply. Have you looked at your temperatures?
G
Go_Guten
04-21-2016, 11:56 AM #2

Consider using a CMOS reset. Check if XMP is overworking your setup. It might help to use just the lowest recommended power supply. Have you looked at your temperatures?

D
deadlyhusky
Member
71
04-21-2016, 03:53 PM
#3
I reset the CMOS and everything seems fine so far. GPU Idle at 28°C, CPU Idle at 27°C. GPU stress reached 68°C and CPU stress hit 89°C during Prime95 test. I don’t recall those numbers being that high before, though I’m not sure it’s the main problem since the system freezes when nothing is running. Honestly, I’m surprised by the temperatures but think they’re within normal ranges given the cooling setup—using a Hyper 212 to handle the heat from the 9700k inside the hot-box H500. The website suggests a PSU rating of 550 watts, so maybe I underestimated the load?
D
deadlyhusky
04-21-2016, 03:53 PM #3

I reset the CMOS and everything seems fine so far. GPU Idle at 28°C, CPU Idle at 27°C. GPU stress reached 68°C and CPU stress hit 89°C during Prime95 test. I don’t recall those numbers being that high before, though I’m not sure it’s the main problem since the system freezes when nothing is running. Honestly, I’m surprised by the temperatures but think they’re within normal ranges given the cooling setup—using a Hyper 212 to handle the heat from the 9700k inside the hot-box H500. The website suggests a PSU rating of 550 watts, so maybe I underestimated the load?

M
mcDavoz
Senior Member
544
04-22-2016, 10:35 PM
#4
It seems you might have searched for the wrong details—maybe the ASUS card performs better than the RTX reference. Also, I didn’t see a question about Event Viewer or system logs; did you forget to include that? Let’s check for any errors or critical messages in the logs.
M
mcDavoz
04-22-2016, 10:35 PM #4

It seems you might have searched for the wrong details—maybe the ASUS card performs better than the RTX reference. Also, I didn’t see a question about Event Viewer or system logs; did you forget to include that? Let’s check for any errors or critical messages in the logs.

Z
zebre78
Junior Member
34
04-22-2016, 11:12 PM
#5
The warning appears only during the third problem. I added it to the Google Drive link.
Z
zebre78
04-22-2016, 11:12 PM #5

The warning appears only during the third problem. I added it to the Google Drive link.

K
Kindeuredeu
Member
157
05-05-2016, 03:12 AM
#6
Additionally, I noticed this warning appears in the control panel at the very start of the problem.
K
Kindeuredeu
05-05-2016, 03:12 AM #6

Additionally, I noticed this warning appears in the control panel at the very start of the problem.

N
NylodnewgPlaZ
Member
187
05-06-2016, 05:53 AM
#7
Sorry, I can't access those links with my phone. It seems like a GPU-related issue. Since you ran DDU, it might indicate a faulty PSU if the CMOS reset didn’t work after replacing the GPU. You could try using a different RAM stick to confirm the problem isn’t with that component. Wishing you good luck!
N
NylodnewgPlaZ
05-06-2016, 05:53 AM #7

Sorry, I can't access those links with my phone. It seems like a GPU-related issue. Since you ran DDU, it might indicate a faulty PSU if the CMOS reset didn’t work after replacing the GPU. You could try using a different RAM stick to confirm the problem isn’t with that component. Wishing you good luck!

D
DBAlucard
Member
211
05-12-2016, 09:17 AM
#8
It's tough to confirm what worked since recreating the situation is hard. I've found a method to initiate it, but results often take over four hours. It would be strange if I had spent all that time on shipping the RMA card just to discover a simpler fix like resetting the CMOS. I'll try the RAM next if the CMOS reset fails, though I'm confident the issue isn't there based on MemTest86. Thanks for your assistance—I'll keep you updated.
D
DBAlucard
05-12-2016, 09:17 AM #8

It's tough to confirm what worked since recreating the situation is hard. I've found a method to initiate it, but results often take over four hours. It would be strange if I had spent all that time on shipping the RMA card just to discover a simpler fix like resetting the CMOS. I'll try the RAM next if the CMOS reset fails, though I'm confident the issue isn't there based on MemTest86. Thanks for your assistance—I'll keep you updated.

M
makan203
Junior Member
46
05-31-2016, 03:56 AM
#9
Well, after 24 hours nothing happened. I'll keep the thread open because I'm not sure it fully resolved the issue. Turning off XMP might have helped technically, since the memory is rated for that speed and the CPU can handle it. But it's unclear how this would impact the GPU (still uncertain, but possible).
M
makan203
05-31-2016, 03:56 AM #9

Well, after 24 hours nothing happened. I'll keep the thread open because I'm not sure it fully resolved the issue. Turning off XMP might have helped technically, since the memory is rated for that speed and the CPU can handle it. But it's unclear how this would impact the GPU (still uncertain, but possible).

D
DoctorOmar
Member
229
05-31-2016, 11:25 AM
#10
Only assumptions are made here, some essential drivers/services remain and can fail due to RAM or CPU upgrades (don’t quote me on this but I’m pretty sure the GPU driver is in RAM, not VRAM). Or maybe the power supply was slightly overworked if it’s worn out. There are dangers when dealing with technology
D
DoctorOmar
05-31-2016, 11:25 AM #10

Only assumptions are made here, some essential drivers/services remain and can fail due to RAM or CPU upgrades (don’t quote me on this but I’m pretty sure the GPU driver is in RAM, not VRAM). Or maybe the power supply was slightly overworked if it’s worn out. There are dangers when dealing with technology

Pages (2): 1 2 Next