-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Nvidia 572.16 bricked my GPU!
- Thread starter Mr Mcgoo
- Start date
The retailer tested my gpu after having it for 2 weeks and advised it is working fine without issues. Tested overnight night and it ran fine. Got it back today and it wouldn't work as before. Same issue. After testing it another system same issue with a different cable. Contacted the retailer and was told they tested in a test bench and therefore the gpu with vertical. Now questioning if the weight of the gpu even with an anti-sag bracket could be causing my issue somehow.
Well 3 hours later and i found my issue. Turns out the 2 sense pins were being disconnected. The weight of the cable (under my gpu) was pulling down on the cable and caused the sense pins to disconnect crashing my gpu. Found this out by chance when i pushed the power cable up with my finger while powering the system on and it worked. As soon as i let go it crashed again the same way. So i have fixed the 12vhpwr cable issue by using a zip-tie to hold the cable behind the motherboard to help take a lot of the weight to reduce the cable sag and voila. Guess i have a really sensitive power connecter for the sense pins.
However, the 572.47 driver gave me the same issue with crashing and black screens as have so many. But, fixed the issue with an older driver 560.94. Maybe the driver install coincided with the cable sag issue?
Well 3 hours later and i found my issue. Turns out the 2 sense pins were being disconnected. The weight of the cable (under my gpu) was pulling down on the cable and caused the sense pins to disconnect crashing my gpu. Found this out by chance when i pushed the power cable up with my finger while powering the system on and it worked. As soon as i let go it crashed again the same way. So i have fixed the 12vhpwr cable issue by using a zip-tie to hold the cable behind the motherboard to help take a lot of the weight to reduce the cable sag and voila. Guess i have a really sensitive power connecter for the sense pins.
However, the 572.47 driver gave me the same issue with crashing and black screens as have so many. But, fixed the issue with an older driver 560.94. Maybe the driver install coincided with the cable sag issue?
Think it is just the design - as I posted before not the first time I've encountered it, for some reason went for ages without encountering it then had 3 instances of that type of thing happening in a short space of time.
What a nightmare to troubleshoot. Glad you found out in the end.
Soldato
- Joined
- 31 Jan 2022
- Posts
- 3,583
- Location
- UK
I had a similar sort of weird problem with a 3080 years ago. I couldn't get the darn GPU working again and eventually tried swapping out the motherboard and BAM, it worked. To make matters even more mysterious, a year later I tried the motherboard again and it was fine. God knows how, but it seemed that the GPU had caused an issue with the BIOS on the motherboard. None of it made any sense. All I can say is try updating the motherboard BIOS and fully resetting the CMOS. I know, it's clutching at straws. and I can't give any logical reason why it should work.
Last edited:
Soldato
- Joined
- 30 Nov 2011
- Posts
- 11,522
All hardware and software has the potential to get itself in to a situation where simple fixes don't work. Things like updating bios, clearing CMOS, reinstalling windows etc. are an attempt to get yourself back to a known good base. Sometimes there isn't really a discernible why or how, it's just a bug somewhere that you probably couldn't even replicate if you tried, and having a good clear out resets it and gets it working again.
On the latest drivers, if my overclock fails on my 5080 it reverts to 2200mhz clocks, I have to run a command line reset and reboot the computer to get it back to stock clocks, just rebooting on its own doesn't fix it.
Last edited:
Associate
- Joined
- 31 Jan 2012
- Posts
- 2,310
- Location
- Droitwich, UK
I'm happy to hear you managed to find the problem and work out a solution.
I had something similar with my 5080 when I first got it, it would sometimes refuse to POST and the fans would spin up, though a power cycle would resolve it. After taking the side of the case off and working carefully to reduce any stress on the connector it worked every time.
Oddly it hasn't reoccurred since I did a platform upgrade, despite taking the side of my case off several times without inspecting the connector (which is firmly in place - something I was very careful to do knowing of the issues some have had).
I'm just sorry I didn't see this post at the time to highlight my experience sooner!
Last edited:
So the sense pins did their job? That's good to hear.
Why is the orientation of the GPU creating stress on the power connector, effectively disconnecting it?
If its a loose cable, I'd switch to another.
We should also fix thread title. As expected, a driver won't brick your GPU.
If its a loose cable, I'd switch to another.
We should also fix thread title. As expected, a driver won't brick your GPU.
Last edited:
If my gpu was vertically mounted the weight of the cable would be pushing down into the gpu connector, not causing any issues. However, horizontally mounted the cable is pulling down on the connector causing the 2 sense pins on top to not make full contact, thus making my gpu believe power had been pulled. The point of the sense pins are to sense themselves. It is designed to make sure the gpu is able to detected that power is connected and not to activate without it.
Unlike previous gpus that would work off the 75watt pci-e, without power cable, to at least get into the bios but would not boot without the pci-e power cable. The 4000 and 5000 series gpus with the new 12vhpwr cable, needs to be connected to work and receive a signal., otherwise you would get no display even into the bios.
Last edited: