There have been complaints that in the last page or two of this thread that posts have gone off target of the original OP.
 
I will give this thread one more chance to stay on topic otherwise it will be locked down.

Are your dp cables vesa certified?

Grrr, nope. Its not the locking screen. Its doing it now just sitting at the desktop, not in lock screen mode (although it WAS in lock mode way earlier today when I 1st posted).
The temp was at 140f/60C just sitting here, so it isnt spiking to 82c like before.
I turned on MSI afterburner, going to see if that fixes it.
I hope so, going to try to play some games tonight.
:(
 
Edit:
OMG
I just went to event viewer to check, and looked at the Device Manager 1st, and for the 1st time since I have gotten this system, the Monitor actually says the name of my monitor!
It used to just say 'Generic Monitor'.
Now its says 'Acer XB270HU'.
 
Hmmmmm........
Windows update?
Maybe thats  why its weirding out?
Shouldnt it be better with the OS knowing what the monitor is now though?
Although the driver date says 12/12/2014 ?
LOL, what the heck?
:(
 
Edit 2:
AHAh!
Drivers for monitor were installed yesterday.
From event viewer:
Installation Ready: The following updates are downloaded and ready for installation:
- Acer Incorporated - Monitor - Acer XB270HU
 
I wonder why that would make my screen flicker now though?
It didnt do this yesterday that I noticed, or before that when I KNOW that the event viewer didnt recognize the monitor, and hasnt, forever, since I have had this machine.
Is it safe to remove the driver for the monitor and make it go back to what it USED to be, just 'Generic Monitor' again?

Thanks a bunch Sajin.
Going to do that and go to bed, see if it flickers tomorrow.

Argggg.
Nope, it is still doing the flickering thing after removing the monitor driver and rebooting, left off overnight.
Sigh.
:(

On Topic:
I have had 3 different power supplies now.
1 bad evga 1300G2, 1 Corsair 1200AX, and 1 evga 1600G2.
 
And no, the card is going in and out of pci-e 16.1.0 to pci-e 16.3.0 just fine, like ever since I got this particular card back from evga (which seemed to be the best out of too many bad cards, which is why I stuck with it even though it was BSOD'ing for a long while when I first got it from evga, which I stopped with certain drivers and settings and special cooling and everything I have done to get it to game at all).
 
I have actually narrowed it down to the evga video card over the last years.
Whenever a DIFFERENT video card is in the system, everything is normal.
As soon as I put the Titan X in, everything goes to heck in a handbasket.
The mobo is perfectly fine. There are way more than enough pci-e lanes.
The memory checks fine in memtest+.
The cpu tests fine in prime and aida64.
The temperatures of EVERYTHING is in the 25-29c area, EXCEPT the evga titan x.
Other video cards, even the more power hungry 1080 ti that my buddy brought with him, as well as 2 GTX780 in SLI, work FINE in this system. Its JUST the titan X that doesnt work.
So, yes, we DO know what the problem is, evga just does not want to admit to it.
 
And, I have a 5 year warranty, and this card is still in warranty.
 
Responding to bcavenaugh about HIS off topic-ness:
Dude, its time to say someone dropped the ball seriously on this titan x.
Either evga kept sending back my 1st bad card back to me (because according to 'their' test it was fine), or they keep sending other peoples crud cards back to me (this was TOLD to me by an EVGA MANAGER. He said they had NO new stock to send me, and this was back when the 2nd and 3rd cards were terrible, not just last week or last month. Last year he told me that).
 
Also, evga TOLD me to make a new thread, since they gave me an rma card, they said it would be a new thread. And, they kept sending bad cards (OBVIOUSLY bad cards that were burnt, the DP ports NEVER worked, the GPU had no tim on it, etc).
I didnt want to keep making the same thread all over again, since all the cards were turning up bad. You know, like the RULES say not to make the same thread over and over?
Maybe we should make a thread called "people that ignore all of the problems of evga's bad video cards since the 900 series because Fanboi's" instead?
But see? YOU made this off topic, not me. I am just responding to you. And Rjohnson11 only said that because I said goodbye to evga products in a not so very good way (yes, I was a bit angry over yet another issue with my 6th titan x when I posted that, but he should really have PM'ed me about it and asked me to remove that piece of the post, but he said something totally different, which again I am not a moderator or evga employee so I am not going to tell them how to do their job, I am a mod in 3 other sites though and we do things more quietly, but it really was my bad and I do appologize for it).
BUT no one has EVER said anything about off topic to ME, in/about THIS thread, or PM'ed me, except that 1 a few days ago (that I can remember).
 
 
Back ON TOPIC, I checked and the computer re-installed the acer monitor driver back on bootup!
 
Sajin, how do I stop this from happening?
I have already told Windows Update to let me choose which updates to download and apply. I have NOT installed that driver update, nor has any update run since that monitor driver update.
But, it seems that there is something in the cache that the os is re-installing the driver?
I dont know win 8/10 well, I DO know all the OS' from 95c to Win7 VERY well.
So, how do I stop windows from re-installing, or re-pointing to whatever cached driver it is seeing?
I know its that monitor driver that windows updated, as I have not seen this issue in a LONG time, on a totally different titan x, and it didnt happen until windows updated that monitor driver.
 
Any help is appreciated.
 
And, once again, I have a 5 year warranty, and this card is still in warranty.
Should I rma it?
Or should I ask here for help because I narrowed down the issue to a windows update? (we didnt know that was happening until I did some things Sajin asked and I did some more poking around, so I thought it was just another issue from the card).
Or should I create a new thread asking how to stop windows from re-installing this driver on bootup? (its already been talked about here in this thread, so thats why I am responding again in this thread instead of making another thread).
(I am being serious in this whole post, not trying to make anyone mad, I am not mad, I am not trying to antagonize anyone, I am not trying to make anyone upset, I am just stating facts and answering questions. I really dont think this is an RMA'able problem, since its an old old old windows driver that somehow snuck through and updated. But, if asked a mod can delete these 2 off topic posts and I will make another thread asking about this in the software or os section?).
Again, not taking any offense or giving any offense to anybody.
 
Even after I get a new system, I will still try to help others here on the forum as much as I can (I HAVE been a member here since 2008, and probably before that just lurking), and I am sure my in-warranty titan x will still need to be addressed (unless I decide to just part out this machine when I get the new one, which I am seriously thinking of, but thats another subject and off-topic), since THIS system will become my backup system.
 
EDIT:
I just found another new (to me) setting in the nvidia control panel:
Manage 3d settings > Global Settings > Preferred Refresh Rate (XB270HU) = "Highest Available"
 
This settings was never there before, it was always in the Change Resolution > Refresh Rate (which is still there).
 
I just changed the Preferred Refresh Rate (XB270HU) to "Application Controlled", so I will reboot and check to see if its still doing the flickering.

Yeah, I did that.
:(
 
I also checked in the MS installed updates, and I dont see that particular update in the uninstall list.
:(
 
I hope that that new setting in nvidia settings for refresh rate fixes it.
This is my reboot.
Will know in about 10-20 minutes. Thats when it starts flickering.

Well, I have win 8.1 not 10.
 
But, WHOOHOO!
After changing that nvidia driver setting and uninstalling AGAIN I am not seeing the acer anymore, just plug n play monitor.
 
Now to see if it keeps flickering again or not.

Well, its been what?
12 minutes since I rebooted again.
I locked the screen.
I opened chrome.
I opened Steam. I opened Friends.
(all things I usually do just web browsing).
 
And, so far so good!
No flickering!
 
Woohoo!
 
Now to hope it doesnt happen tomorrow, or whenever the next time I boot the machine back up again is.
:)

Arggggg!!!!!
The blinking is back.
Just got out of a game, Strange Brigade, and was at the browser for no more than a few minutes, and it started blinking again.
I hope a re-seat takes care of it.

Well, its happening less often now, but it is still happening.
I see the Acer monitor update in the windows update now also, so it is definitely not installed anymore.
I also got the new DP cable yesterday, and it doesnt fix the flickering issue.
:(
Is it RMA time again?
It seems like the DP ports may be going out. Again (2 previous cards that I remember had bad DP ports).
 
Sigh, I dont want to go through the hassle of another freakin rma. But, this card seems to be going out, just like all the others.
:(
 
Edit:
I did notice that in my pci-e 2 slot, the card starts at 22% fan speed, where when in slot 1 it started at 20% fan speed. Is that normal, just un-seating the card and re-seating might reset the internal fan speed indicator.

OK for fan speeds. I havent seen any fluctuations in that before, since I guess it was in slot 1 almost all the time.
I am still getting huge drops in games with it in the 2nd pci-e slot also, so its not the mobo or cables (slot 1 gets set to disabled when I use slot 2, and vice versa, unless something is installed in that slot, I guess to save on pci-e lanes).
I am wondering if that winupdate did something that is cached somewhere in the os I cant get to, and is using some semblence of that 2014 driver for it even though everything is back to like normal now, with it not installed, being in winupdate again, and having uninstalled the driver 3x.
I think I will re-install the nvidia driver, in case nvidia cached it somewhere also.
 
I found out that I dont have to use precisionXoc or msi afterburner, that hardwaremonitor(64) can control the fan speeds.
I just started using that today, and the overhead seems to be less than with either precision or msi, when used to JUST clock the video card fan (I have it at 90% now, and it seems to run much cooler, not going over 152f/69C. So, its now 3-4c cooler than with msi. Also, it seems to 'release' the video card better than either PX or msi, as it runs MUCH cooler at idle now when I stop it from 90% fan. It now sits at 77f/25c at idle instead of at 89f/31.6c like it did with msi. I have no idea why msi would run that much hotter though. Like I said, it seemed to keep hold of the video card for some reason. Where HWM is releasing it correctly.
Just another weird thing with this card/setup.
 
As for rma, I will not be able to put it in a compaerable system to test it. I can only test it in an 8 year old machine, which wont be a test at all, since that is win7, vs 8.1 here, and pci-e 1.x? 2 at most? vs pci-e 3 here. Also ddr3 vs ddr4. And, amd vs I7 intel 6 core. Totally not even close to anything I have in my current rig.
Grrrrr, I wish I had a machine with win8.1 here that was similar to the one I have now. At least if I end up getting a new rig and I save this one, I can test with both ddr4 and win8.1/10, with kinda similar architechture in cpu's, even though its 3 years old now it hasnt changed much in the cpu area.

Crud.
Its still happening just as bad flickering again.

Dang it!
Now my games are doing that flickering/blinking!
ALL of my games are doing it.
It doesnt matter if I have msi afterburner on or not, it does it ALL the time now, just after it shows the desktop.
Grrrr, dang it, poo, crud!!!!!!
 
Is it RMA time again?

But the ony system I have to test it in is a 9 year old system.
That isnt even a valid test, right?
Its like pci-e 1.x or 2.x, and doesnt have the power saving mode like my current system has, and also it isnt the same OS (its windows 7, not windows 8.1).
I dont think that is a valid test at all.
Its like saying test in AGP vs pci-e x16 3.0
:(
 
But, it can narrow down whether its the monitor or not, so I will try it anyway.