Is my GTX 760 faulty, or my PSU? Help me diagnose.

Zachary Roberts

Honorable
Dec 4, 2013
74
0
10,640
First things first, my PC has been performing nicely since I built it in December 2013. Two days ago, though, I decided to upgrade from an i5 4570 to an i7 4770 and add an extra 2x 4gb corsair vengeance ddr3 ram (upgraded from 8gb to 16gb). However, as is my custom after installing new hardware the every first thing I did was stress test it (using memtest for the ram and intel processor diagnostic tool for the CPU). It passed all tests without a single error. That same evening I used my PC, satisfied everything was working fine, and played AC4 Black a Flag in 3D mode without a single lag, noise, crash, bsod, or any other issue. At the end of the day I turned my PC off, as I do. The next day I go to turn it on and shortly after startup everything is lagging like heck. PC stopped responding then unfroze itself a few seconds later, etc. so I thought maybe something was corrupted so I wiped the os and reinstalled afresh, then reinstalled all drivers afresh. I thought that had solved the issues but then the lagging started again. I did a windows experience test and heard, for the first time, a coil whine type squealing sound coming from the PSU. I started googling for possible solutions and as I was scrolling I heard this scratching/clicking sound while I was scrolling (which subsequently stopped when I stopped scrolling). As the coil whine sound only happened during the graphics part of the windows experience test I started to suspect the GPU may be faulty (initially, you see, I thought it was the GPU making the whining sounds...it was only this morning, when I took the cover off the PC, that is realised it was the PSU...which, FYI, is a Corsair CX750). I chatted to nVidia and their first response was, "have you got the latest drivers?" I hadn't, I had driver 320.49. So I proceeded to update the drivers. After it downloaded them, without issues, it started to install them. Screen went black and there was a windows loading circle cursor on the centre of the screen. "Don't worry, this is normal" nvidia said. But shortly after they said that I got a BSOD: http://tinypic.com/view.php?pic=5drltk&s=8#.UxHOaX8gGK0 (I had set my computer to record memory dumps and not to automatically restart after a BSOD). However, after a reboot there was no memory dump file anywhere. I know the location of said files, before you ask. I even did a wildcard search on *.dmp, no results found. I then decided to disable gtx 760 and plug in onboard graphics. Did a windows experience test....no coil whining sound whatsoever. Switched back to gtx760, re-ran experience index, coil whining sound again...but only during direct3d part of the test. At that moment I realised it was in fact the PSU whining, not the GPU. It was definitely coming from the PSU. So I thought maybe the cable might be dying so I switched to another cable...same problem. Eventually I took the gtx 760 out of my PC and the issues seemed to stop after that. As a result of this I have absolutely no idea whether it's the GPU causing this, or the PSU. But I'm pretty sure it's not the ram or the CPU judging by the fact I've literally just finished doing diagnostics on those and they pass every single one. And how come I was battering the hell out of my PC in 3d gaming two evenings ago and then this happening from last night onwards...with nothing having changed in that 24 hour period? I've spoken to friends, colleagues, nVidia support. Checked event logs, tried to get my PC to write dumps (I've set it up so it should), the lot...I cannot get my head round this. So I've come on here to see what you guys think.
 

Zachary Roberts

Honorable
Dec 4, 2013
74
0
10,640
Stress test what? Memtest, intel processor diagnostic tool? Those already passed. Even with the gtx 760 plugged in. I initially thought the GPU had died but it's the PSU, not the GPU, that's whining unless my hearing is that bad that I'm misinterpreting from where the sound is coming.
 

Zachary Roberts

Honorable
Dec 4, 2013
74
0
10,640
Oh, no it isn't. Only when the GPU is plugged in. But my confusion is based on if this were a GPU problem then why is the PSU whining, not the GPU? Makes me wonder if it's not delivering a sufficient amount of power (hinting on a faulty PSU), or if the GPU is asking for too much (hinting on a faulty GPU). As I've no hard evidence to go on this I extremely difficult to diagnose.
 

Zachary Roberts

Honorable
Dec 4, 2013
74
0
10,640
Ok, I've just changed my PSU. Still getting whining noises when running windows experience index. This time, though, the whining is coming from the GPU. So far, though, I haven't had any BSODs. I'm now stress testing the GPU using furmark while booted into windows, using the gtx 760 as my graphics processor. Fans are running like the clappers but it hasn't died on me yet. Will leave it running and see what the outcome is, then report back. But I'm still confused as to what may have caused the wide range of issues discussed in my first post above. Anyone have any ideas?
 

Zachary Roberts

Honorable
Dec 4, 2013
74
0
10,640
Just to update everyone again, I ran furmark CPU burner as well. It battered the living day lights out of my CPU...it really did. But my CPU held its ground without BSODs or overheating. I can now rule out my PSU, and I think I can rule out my CPU as well. Now, even though I did a memtest for 10+ hours only 2 days ago, for the same of doubt...I am running a memtest again now. If the memtest passes I can rule out the RAM as well. Now, all this is well and good (I like it when things pass stress tests lol...don't we all). But I still can't help but wonder what the heck went on last night/this morning (see first post...I know it's a long paragraph but I typed it on the bus from my iPad lol).
 

Zachary Roberts

Honorable
Dec 4, 2013
74
0
10,640
It appears to be. Am reinstalling windows as we speak to give the machine a fresh start. But the GPU stress test passed, the CPU stress test passed, and memtest also passed. Still doesn't explain why what happened, happened (if you get what I'm trying to say), but at least it all seems to be working...at least for now. Need more time really, though, to monitor its performance. In the meantime I'm still open to ideas as to what you think may have gone wrong.