[SOLVED] Did I mess up my GPU? Or is the motherboard fried? Or is it my PSU?

[fransfakta]

So recently I stumbled into this very peculiar and annoying problem pertaining to the output of my graphics card. Upon doing a party theme for my dorms Tour de Chambre it was nescessary to move my desktop around to make space for all the people visiting my room - unfortunately during the move i think something might have fallen on my male DP-cable plugged into the GPU essentially causing the plastic covering to slip off and make it very hard to remove the cable. Naive being that I am I yank it out trying to squeeze the remaining clip-on-function left. I succeed, buy a new DP cable and plug it in happily thinking that might be it!
Now however, I can't get the GPU to send signals beyond 60hz when switched to the DP-port. It simply cuts out, the monitor still left on and everything else running normally. What's weirder is that it seemingly works if the monitor is connected via HDMI instead of DP, but will now do random cut-outs for 2-3 secs (essentially blackouts like when i set it to 144hz DP), when the PC is under heavy graphic load (Mostly while i'm gaming). Furthermore I have had periods where it was hard to boot the desktop from cold and it would essentially go into a boot loop of some kind.
I have tried multiple things ranging from software reinstall (nvidia drivers fresh clean install), putting the DP-cable into all the different ports on the gpu, switching out the PSU for at more powerful one to see if it was faulty and not delivering enough power to the GPU and taking out a single ram stick and booting (both of these things cause boot loops for me after it is done). I have also tried to reseat the GPU to see if a loose connection could be the problem (has not solved the problem either)
Do any of you seem to have a clue as to what's happening with my PC? Have I busted my GPU because i messed up a DP cable while it was plugged into the GPU ? Or is it something different like my motherboard is done for? Cheers in advance for any friendly chat or pointers!

Specs
Motherboard: GIGABYTE B365 M AORUS ELITE
GPU: GIGABYTE GeForce RTX 2060 OC - 6GB GDDR6 RAM
CPU: Intel Core i5-9600KF Coffee Lake S CPU
PSU: Corsair TX650M
Monitor: MSI G241
Cabinet: Cooler Master MasterBox NR400
CPU-cooler: Arctic Freezer 34 eSports DUO
WLAN: TP-Link Archer TX3000E
Fans: Corsair AF120 LED Quiet (2018)
SSD: A-Data XPG SX8200 Pro M.2 SSD - 512GB
RAM: Corsair Vengeance LPX DDR4-3200 C16 BK DC - 16GB
Mouse: Logitech G502
Keyboard: Steelseries Apex Pro TKL
USB Mic: HyperX Quadcast

 

[MishterKirby]

Have you looked at the DisplayPort port carefully (maybe try with a flashlight and a magnifying glass)? Maybe there's a bent connector or or piece of the cable still stuck in there causing a short in the card, which would cause it to malfunction

 

[fransfakta]

Have you looked at the DisplayPort port carefully (maybe try with a flashlight and a magnifying glass)? Maybe there's a bent connector or or piece of the cable still stuck in there causing a short in the card, which would cause it to malfunction

I tried just now and theres is nothing to see in the GPU-ports im afraid :/

 

[Ralston18]

This motherboard?

https://www.gigabyte.com/fj/Motherboard/B365-M-AORUS-ELITE-rev-10/sp#sp

On-board graphics.....

Verify that the motherboard supports iGPU and test accordingly.

If the display works via the motherboard video ports (using a known working video cable) then the GPU may well have been damaged.

The key is to methodically test GPU's, motherboard slots, and cables to narrow down the culprit.

 

[Vic 40]

This motherboard?

https://www.gigabyte.com/fj/Motherboard/B365-M-AORUS-ELITE-rev-10/sp#sp

On-board graphics.....

Verify that the motherboard supports iGPU and test accordingly.

If the display works via the motherboard video ports (using a known working video cable) then the GPU may well have been damaged.

He has a cpu without igp,

CPU: Intel Core i5-9600KF Coffee Lake S CPU

Is there a way to test your RTX 2060 in someone elses pc? Likely more on your dorm have a pc.

 

[Ralston18]

He has a cpu without igp,

Noted: Thanks for the correction. My error.

 

[fransfakta]

This motherboard?

https://www.gigabyte.com/fj/Motherboard/B365-M-AORUS-ELITE-rev-10/sp#sp

On-board graphics.....

Verify that the motherboard supports iGPU and test accordingly.

If the display works via the motherboard video ports (using a known working video cable) then the GPU may well have been damaged.

The key is to methodically test GPU's, motherboard slots, and cables to narrow down the culprit.

Yeah that is my motherboard.
I have the screen plugged directly into my 2060 - not the motherboard

 

[fransfakta]

He has a cpu without igp,



Is there a way to test your RTX 2060 in someone elses pc? Likely more on your dorm have a pc.

I might ask a friend of mine - no one in my dorm besides me has a desktop unfortunately :/
Just for good measure - if the GPU is messed up and i put it in his system, it wont <Mod Edit> anything up in his rig right?

 

[Vic 40]

No if he has a good psu would the only thing you see be either a good working gpu or one that displays the troubles you have.

 

[fransfakta]

No if he has a good psu would the only thing you see be either a good working gpu or one that displays the troubles you have.

Why did my PC go into boot loop when i tried to change the PSU out for a Cooler Master V Series V850 Gold but not with the original PSU?

 

[Ralston18]

"Why did my PC go into boot loop ".....

Look in Reliability History and Event Viewer: any error codes, warnings, or relevant informational events?

Also: please verify for all of us that you are not mixing/matching in cables from other PSUs.

 

[fransfakta]

"Why did my PC go into boot loop ".....

Look in Reliability History and Event Viewer: any error codes, warnings, or relevant informational events?

Also: please verify for all of us that you are not mixing/matching in cables from other PSUs.

Cheers for keeping up the replies guys - I really appreciate it <3

There is no mixing/matching to do besides PCI-E as my current PSU (corsair tx650) has the cords for CPU and motherboard integrated into the PSU.
That said - I made sure of course to use the right cable for the PCI-E included with the alternate PSU (Cooler Master V Series V850) and not the one in use from the old PSU

Looking at the event viewer I was unable to identify an error from the time period where i experienced the boot loops.
Instead here is a hardware error from reliability monitor (of which there are 4 all the same) which stem from the time period in which boot loops were a problem for me (both with the old PSU and the alternate PSU connected) 11th of february to the 14th of february:

Source
Windows

Summary
Hardware error

Date
‎11/‎02/‎2022 15.57

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff9005183dd010
Parameter 2: fffff8028688bd5c
Parameter 3: 0
Parameter 4: 3160
OS version: 10_0_19044
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19044.2.0.0.768.101
Locale ID: 8192

 

[Ralston18]

Code 141.

Unfortunately there are quite a number of things that can cause that code to appear.

FYI:

https://softwaretested.com/windows/what-is-the-livekernelevent-code-141/

Microsoft links:

https://answers.microsoft.com/en-us...re-error/948ed67d-dc63-4eba-8f28-209846547bcf

https://answers.microsoft.com/en-us...41-error/080d501b-6b2e-454d-91c2-93e1a8717d1a

The second Microsoft link is a bit more "targeted".

My recommendation is to do a bit more research and reading about Code 141.

Take what you find and learn and compare to what you have tried thus far.

You may find a fix.

Do be careful about downloading any software claiming to fix the problem - some of those products show up no matter what problem is being addressed.

Also - no registry editing. That is a very last resort and only after fully backing up the system.

Even though "hardware" related I would try running the built in Windows Troubleshooters along with "sfc /scannow" and "dism".

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

How to use DISM command tool to repair Windows 10 image | Windows Central

As always, before doing anything, ensure that the system is backed up at least 2 x to locations off of the current problem computer. Verify that the backups are recoverable and readable.

 

[fransfakta]

Code 141.

Unfortunately there are quite a number of things that can cause that code to appear.

FYI:

https://softwaretested.com/windows/what-is-the-livekernelevent-code-141/

Microsoft links:

https://answers.microsoft.com/en-us...re-error/948ed67d-dc63-4eba-8f28-209846547bcf

https://answers.microsoft.com/en-us...41-error/080d501b-6b2e-454d-91c2-93e1a8717d1a

The second Microsoft link is a bit more "targeted".

My recommendation is to do a bit more research and reading about Code 141.

Take what you find and learn and compare to what you have tried thus far.

You may find a fix.

Do be careful about downloading any software claiming to fix the problem - some of those products show up no matter what problem is being addressed.

Also - no registry editing. That is a very last resort and only after fully backing up the system.

Even though "hardware" related I would try running the built in Windows Troubleshooters along with "sfc /scannow" and "dism".

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

How to use DISM command tool to repair Windows 10 image | Windows Central

As always, before doing anything, ensure that the system is backed up at least 2 x to locations off of the current problem computer. Verify that the backups are recoverable and readable.

Cheers and thanks for the reply.
I think im at the point i might just try and buy a new GPU to see if that fixes the problem - if not then I know i need to dig deeper and maybe even build anew with a new motherboard.

 

[vov4ik_il]

Did you try all 4 GPU monitor interfaces? (3DP/1HDMI)
You might have damaged one or two by using a bad cord, but the other might be still working.

 

[fransfakta]

It turns out the fault is down to bad cables. I just tried to connect the monitor with a different DP-cable and it solved the problem instantly.
Lesson learned - don't be a cheapskate and buy the cheapest DP-cables from the <Mod Edit> import hardware store in town.