Question GPU causing computer to not turn on

[Gumla44]

I played some game and I guess it overheated at some point or something, screen went odd and computer turned off, found that the GPU is the cause after testing with onboard graphics Intel which works, I'm trying to fix my GPU now, but don't have the electronic tools to support at the moment, can you help me spot if anything is out of place, etc

I have R9 290x Sapphire Vapor x card which I took apart now:
https://ibb.co/7yqYyrp

17229653517438233372928953238723 hosted at ImgBB

Image 17229653517438233372928953238723 in Tech album

ibb.co

More:
https://ibb.co/ccC9J66
https://ibb.co/D4HJ0XP

To be precise the computer turns on for like 5 seconds no screen and then turns off and keeps restarting itself

 

[rgd1101]

full system spec? include brand and model of the psu

 

[Gumla44]

full system spec? include brand and model of the psu

PSU:
FSP HYPER HP600

Other system info:
OS Name Microsoft Windows 10 Pro
Version 10.0.19045 Build 19045
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-LLR6LFG
System Manufacturer Gigabyte Technology Co., Ltd.
System Model H61M-S2-B3
System Type x64-based PC
System SKU
Processor Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz, 3300 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date Award Software International, Inc. F5, 3/27/2012
SMBIOS Version 2.4
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
BaseBoard Product H61M-S2-B3
BaseBoard Version x.x
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume8
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.3636"
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.51 GB
Available Physical Memory 3.70 GB
Total Virtual Memory 17.0 GB
Available Virtual Memory 13.2 GB
Page File Space 9.50 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes