290 Windows 10 flickering in games (weird image

[newconroer]

I noticed after moving to Windows 10 *using 15.10* drivers, that at random I get flickering and flashing on the screen.

It happens in full screen 3d programs/games, and it's not image corruption as in horizontal lines or red /yellow artificating that we usually associate with image issues.
Rather the actual game image itself is distorted, where upon it flickers briefly (sometimes two or three times in succession) a view of some previous frame that I've already viewed a few moments ago.

I may have a menu open in the game, then the menu closes and the image flickers a couple shots as if the menu window was still there(though in a less obvious, more transparent version).

Hard to describe - hard to video record as well.

I've reseated my cards, reinstalled driver, put all graphics settings to default.
I also get intermittent system crashing when I try to view the Display Properties from the desktop. This is something I found mention of quite a bit with Windows 10 and wonder if the two problems are related.

 

[fullinfusion]

Did you do a clean W10 install by chance?

Also is that the driver W10 gave you or the one you installed? I see in your system spec's your in crossfire is that still the case?

 

[OneMoar]

sounds like the monitor to me

 

[AsRock]

Gaming with my 290X in windows 10 was very positive there was some gains to be had with Farcry4 with the driver release for that game and had no isse's with any other.

What the crash logs say ?,

 

[Divide Overflow]

I never see anything like this with my 290X and Windows 10. When you say you get intermittent system crashing when you try to view the Display Properties from the desktop, do you mean Display settings or the AMD Catalyst Control Center?

 

[newconroer]

I never see anything like this with my 290X and Windows 10. When you say you get intermittent system crashing when you try to view the Display Properties from the desktop, do you mean Display settings or the AMD Catalyst Control Center?

Right click destkop > screen resolution > results in dxgkrnl.sys crash of system.
It happens at random, no pattern to it.

Gaming with my 290X in windows 10 was very positive there was some gains to be had with Farcry4 with the driver release for that game and had no isse's with any other.

What the crash logs say ?,

Still trying to find one related to the issue.

Did you do a clean W10 install by chance?

Also is that the driver W10 gave you or the one you installed? I see in your system spec's your in crossfire is that still the case?

This was an upgrade from Windows 7.

sounds like the monitor to me

Will switch monitors around or turn off one of them.

 

[Ferrum Master]

Sounds like bad RAM chip to me.

 

[OneMoar]

Sounds like bad RAM chip to me.

generally faulty vram shows as a checker-board pattern or corruption
this sounds like either the driver board on the monitor or perhaps a bad cable
ghosting is generally a signal to panel issue

 

[stinger608]

If your spec's are correct, I would be more inclined to believe its a CrossfireX issue with Windows 10.

Uninstall the AMD drivers and install the newest driver set and give it another try. You could also shut down the Crossfire and uninstall one of the video cards to test this theory. You will probably get poor frame rates in the games but it would confirm or deny the theory.

 

[fullinfusion]

you know there's at times issues with overlapping windows 10 over 7 right.

Personally, sense you already migrated to 10 id do a clean OS install.. I betcha the problem goes away

Also another thing, goto device manager and if you feel like spending a bit of time go through the system device tab and manually check driver updates..

W10 didn't pick up my chipset driver through its updates but doing it manually fixed a world of issues I was having.

 

[stinger608]

W10 didn't pick up my chipset driver through its updates but doing it manually fixed a world of issues I was having.

That is good to know brother!

 

[newconroer]

Sounds like bad RAM chip to me.

I suspect you mean the crash at desktop when accessing Screen Resolution?
It's error free RAM that doesn't fall down any where else.

you know there's at times issues with overlapping windows 10 over 7 right.

Personally, sense you already migrated to 10 id do a clean OS install.. I betcha the problem goes away

Also another thing, goto device manager and if you feel like spending a bit of time go through the system device tab and manually check driver updates..

W10 didn't pick up my chipset driver through its updates but doing it manually fixed a world of issues I was having.

Done already!

If your spec's are correct, I would be more inclined to believe its a CrossfireX issue with Windows 10.

Uninstall the AMD drivers and install the newest driver set and give it another try. You could also shut down the Crossfire and uninstall one of the video cards to test this theory. You will probably get poor frame rates in the games but it would confirm or deny the theory.

I have tried it with 15.11 driver now, same problem. Though starting to think it's only happening in one game from further testing. If so, that's not too bad I suppose.

Unfortunately the dxgkrnl crash still happens. Also, I can't find any mention of it in the event viewer.

 

[Dethroy]

Does eventviewer report any problems? If not, then it's probably hardware related.

 

[newconroer]

Nothing that points to the graphics adapters.
Maybe I would find mention of the dxgkrnl.sys errors in the memory dumps.

 

[Aquinus]

I noticed after moving to Windows 10 *using 15.10* drivers, that at random I get flickering and flashing on the screen.

The drivers on my 390 were borked up after upgrading, so if you didn't do a clean installation, use DDU and re-install the latest drivers to see if it makes a difference. Simply uninstalling and re-installing didn't work for me, you need to clean out the old ones.

 

[Ferrum Master]

I am starting to think these are some weird UEFI related problems there, that would explain why win10 upgrade triggered it. Are there any more fresh BIOSes for the cards and mobo?

Google also mentions dxgkrnl errors connected to secure boot albeit for nvidia card. You have GPT table? Not the old MBR one?

 

[newconroer]

The drivers on my 390 were borked up after upgrading, so if you didn't do a clean installation, use DDU and re-install the latest drivers to see if it makes a difference. Simply uninstalling and re-installing didn't work for me, you need to clean out the old ones.

Both 15.10 and 15.11 would not install with the normal 'install over old drivers' method. They would get stuck at 'detecting display driver' indefinitely. I had to use DDU to install them.

I am starting to think these are some weird UEFI related problems there, that would explain why win10 upgrade triggered it. Are there any more fresh BIOSes for the cards and mobo?

Google also mentions dxgkrnl errors connected to secure boot albeit for nvidia card. You have GPT table? Not the old MBR one?

Ya am using UEFI and GPT.


Been trying some other games, haven't noticed it. I suppose my initial observation was inaccurate and it has only happened in one title.

 

[Ferrum Master]

Ya am using UEFI and GPT.
Been trying some other games, haven't noticed it. I suppose my initial observation was inaccurate and it has only happened in one title.

Does the display properties error still create the BSOD? Yes they may be actually two things. Texture flashing like z fighting are a usual thing for AMD cards. But that dxgkrnl error is a different animal.

 

[Aquinus]

you know there's at times issues with overlapping windows 10 over 7 right.

Personally, sense you already migrated to 10 id do a clean OS install.. I betcha the problem goes away

I personally had to re-install because the upgrade destroyed .NET and it got to the point where re-installing would be less headache then trying to fix it. I suspect that there could be an issue with direct x libraries themselves. If it were bad VRAM you would get artifacts in 2D as well, so it's definitely not that. It's not drivers (directly,) since the OP has cleaned them out. The crash on a microsoft library is probably the most concerning thing out of all of this. I suspect that not everything in Windows is working properly (much like mine after the upgrade.) As the OP uses it more, it very well might get worse like mine did. I too suggest a clean install if it hasn't been done already since the upgrade from 7 to 10.

But that dxgkrnl error is a different animal.

Reminds me of the issue I had with .NET after upgrading.

 

[newconroer]

I only did the upgrade because I had to see it to believe it and I have had no issues - certainly not like I thought I would. Having been a staunch supporter of clean installs, I have been impressed.
If there was components out there on the market worth upgrading too, then I may slap Windows 10 on a new drive and start again. Though I can't justify the costs for new equipment when I am not convinced there's anything out there that will provide me any significant improvement over what I have already.

 

[newconroer]

Hopefully helpful to some one - looks like it was a dying graphics card. Why it only manifested itself in one particular game I do not know.

What I have observed though is that without it in the system, the flickering has stopped and so has the crashing when trying to open screen resolution from the desktop.

I spent about ten minutes opening and closing it over and over, the freedom was liberating.