Difference between a GPU or a PSU issue

[Spacepc]

Hello!

This thread is in part connected to a previous thread I made here, but it is still a different question, so I figured that a new topic would be in order.

After testing a lot of different possibilities I am almost certain that I have a hardware issue with either my power supply or graphics card. If I put my graphics card under heavy load it will crash within about 3 minutes.

If I do the OCCT power supply test, which supposedly even manages to wreck some lower power supply units, my pc can keep on going for at least 10 minutes without any issues. The thing that confuses me though, is that if I remove everything connected to the usb ports and the audio-jack, my graphics card can go for at least twice as long before crashing (one time it even took 15 minutes), even though it got to higher temperatures, by simply running for longer.

If the graphics card is at fault, then surely disconnecting things from the ports, shouldn't help? At the same time, shouldn't my PSU have gotten a problem with the power supply test? Or am I relying too much on it?

I don't have anyone I can switch cards or power supply with, so any help in finding out what has gone wrong, would be greatly appreciated.


Previous thread: http://www.sevenforums.com/graphic-...river-has-stopped-responding-error-0x117.html

 

[Boozad]

It would help if you listed what PSU you actually have.

 

[Spacepc]

I have a corsair GS600W 80+

 

[Boozad]

What drivers are you running for your GPU? It does certainly point to it being the GPU when taking your other thread into account too.

 

[Spacepc]

I have the newest one, 14.4. I started getting issues while I had an older driver (it didn't coincide with a driver update), so I thought I'd try updating it, but it didn't help. Then I tried amds driver clearing utility, which went as far as wiping my usb drivers (luckily the front ports still worked) and I just reinstalled everything again, only to have no improvement.

I don't know if this is worth mentioning, but windows failed with installing the new .NET framework update since february, right until about this started happening, but that might just be a coincidence.