Screen Blanks After Gaming

[Arcnor]

Hi. Okay, not sure if this is the right forum for this question, but I could use some advice.

I recently completed my gaming build -- specs are in my sig -- and it seems to run fine. A mild overclock on the CPU, but nothing ridiculous. GPU running at dead stock -- didn't touch it at all. Now, sometimes (not always, just sometimes) when I quit out of a game, or a graphics benchmark like Unigine Valley, after a few seconds my screen blanks -- not a BSOD, it just goes a solid colour and is unresponsive. PC's still running, all lights on, but just a blank screen. I have to switch the power off completely and reboot.

I've checked both my CPU and GPU temps -- CPU's under 60C, GPU under 65 mostly, never more than 70 according to Unigine. And it doesn't crash under load, just afterward.

Anybody have any ideas at all? Is it a driver issue? My driver version is 331.82, and I'm using the HDMI output on the GPU, if that helps.

Thanks in advance for any help you guys can give!

 

[maniac]

Weird that it happens after and not during, try setting your cpu back to stock to start to rule out some things. I will try to keep you up to date with what decides to come to mind

 

[Arcnor]

Before you ask, yes, I am A Idiot

Weird that it happens after and not during, try setting your cpu back to stock to start to rule out some things. I will try to keep you up to date with what decides to come to mind

I know, right? I figured that if the issue was something like a bad PSU (or not enough power, but every PSU calculator I can find says I have more than enough for this system and then some), or a bad GPU, or a heat issue, then it would happen during the worst stress, not afterward.

Okay, so full disclosure (and I freely admit that I am A Idiot), I was messing around trying an offset voltage OC (same speed as my initial one -- 4.3 GHz) because I wanted to see if I could take advantage of the CPU downclocking a bit when I'm just messing around websurfing (like now). It seemed stable after a OCCT run (AVX turned off, you know, because offset), but maybe that was the culprit? I just did a Unigine Valley run and quit out of it fine using stock settings -- no offset. I let it go for fifteen minutes to make sure all temps were maxed out, and the GPU never broke 69C. CPU (at stock) was doddering along in the mid 50s. So I don't think heat is the problem.

Maybe my stupid attempt at offset messed up one of the other voltages?

 

[maniac]

Glad you sorted that out, tbh I'm not the one to talk about voltages and overclocking related stuf as I don't feel nearly confident enough to give advice, maybe someone who can shed some light will see this thread and be able to help you out

 

[Arcnor]

Some Ideas, Any More Out There?

Glad you sorted that out, tbh I'm not the one to talk about voltages and overclocking related stuf as I don't feel nearly confident enough to give advice, maybe someone who can shed some light will see this thread and be able to help you out

Yes, I'm thinking it's either one of the other voltages (when I tried offset, everything but VCore was on auto, so maybe the volts for one of the other bits weren't quite right) or possibly a problem with the C states (tries to enter one, messes up, you know the rest). I'll mess around with it a bit tomorrow, maybe try the same OC with C states totally disabled.

Actually, I think that may be it. Makes sense -- CPU comes out of a period of work, tries to power down some bits as it reaches idle, and because I am A Idiot, it can't successfully enter a lower power state without blanking out.

Anybody out there with more experience think I'm onto something, maybe?

 

[maniac]

Don't consider yourself an idiot cause you did one minor mistake, thats why the forums exist because of problems like that, its all a learning curve my friend.