I'm having some weird issues with my new build and I've narrowed it down to my GPU. I've tried to play some games but they always crash soon after I actually get into them. I've also been getting problems when my Chrome is running on Hardware Acceleration.

I've tried to benchmark it with Unigine and ran into some really weird issues. First of all my Core clock was displaying as 2100MHz which is definitely not right. Then it was black screening all the time and there was some horrible coil-whine going on but as time went by both of those issues disappeared. I also keep getting these random Memory clocks spikes to 7001MHz and core clock spikes to 1410MHz just while browsing:

Did I just stumble upon a faulty card? I've tried uninstalling and reinstalling drivers already so I think it's a hardware issue.

Any sort of help would be greatly appreciated!

Sajin
#1 What are your full system specs?
#2 What is the make/model/age of your psu?
#3 Does underclocking the card to max negative values on the core and memory stop the crashing?
#4 Unigine heaven always shows the wrong clock speeds.
#5 Getting clock spikes while browsing is normal when hardware acceleration is on.

#1 These are my specs:
PSU: EVGA SuperNOVA 750 G3
MB: ASUS Prime X470-PRO
CPU: AMD Ryzen 7 2700X
RAM: Corsair Vengeance LPX 16GB 3200MHz C16
SSD: Samsung 970 EVO
#2 Every part is brand new. I've listed the PSU specs above. This is the exact model: 220-G3-0750-X2
#3 Underclocking it doesn't seem to do anything.
#5 I've already turned hardware acceleration off.
I did some more digging around and found out that nvlddmkm Event ID 13 is probably the root of my issues. I get the error every time a game crashes. Not entirely sure how to go about fixing it though. I've tried so many things already with no effect.

I went ahead and replaced the 2070 with an old GPU. Reinstalled all the Nvidia drivers and the problem still persists so I don't think it's linked to the GPU directly but rather something with my other components or the drivers.

Yep. I usually launch a game, run it for a bit and at some point it freezes and can't recover so it just crashes to the desktop.

I did run Windows' integrated Memory Diagnostic Tool once but I'll try out memtest. Do I run it a few times?

Pass 1 got a cumulative error count of 17. Most of which happened during the 6th test (Block move 64 byte blocks). I'm guessing that's bad.

Got 88 so far in Pass 2. Is there no point in testing them all the way? I'll test them out separately when I can. Thank you for your help.

One of them was indeed defective. The other one went 2 passes with no errors at all. I even tried using that one alone and I wasn't crashing anymore. I'm going to be returning them and getting replacements. Thank you so much!