As of yesterday morning my World of Warcraft: Classic and World of Warcraft: Battle for Azeroth are both acting like Fullscreen applications while they are in Windowed(Fullscreen).
Whenever I alt-tab back into the game all of my monitors go black, like you would expect from a Fullscreen application, before the game re-appears with as the focus. I can move my mouse to another application and interact with it fine, but once I click back into WoW my monitors flash black before re-appearing with WoW as the focus.
This is happening with only both versions of WoW. It does not happen with other Blizzard games or games from other developers.
I have done a fresh re-install of both versions, completely removed all addons, and reset all settings to default but had no success in solving this issue.
Before yesterday I could tab in and out of both versions of WoW without any black screens or delays.
I am having the exact same issue that you are having. It all started after I updated my Nvidia drivers. I had to roll back to much older drivers to stop this from happening.
The only game this happens with is WoW. I’ve been playing Breakpoint and a star wars MMO that will remain nameless among a few other random games and they’ve all been fine, but WoW acts like old school fullscreen with the monitor flickering black every time I alt-tab or click off the screen.
I’m running dx12 with 2x GTX 1080ti in SLI and dual identical monitors if that helps narrow it down at all. The driver update that is tied to the flickering is 440.97 from Nvidia’s website. The issue was also present with driver 436.48, but rolling back to 419.35 fixed it for now.
If you find a fix for this, please share. Good luck!
Howdy!
I can’t reproduce this on my own machine. I’d like to assist in locating the source of the issue. Can you try retesting with all background applications closed using the steps Here → Restart the PC → Retest.
If the issue continues, post up your Dxdiag for us to review. Copy the dxdiag contents into your reply, highlight the text then select the code block icon </>. This action will help us review the information faster.
Thank you!
I was able to fix this problem on my setup by selecting the GPU that did not have the primary monitor plugged in to it and manually configuring that to be the PHYS-X processor. In nvidia control panel.
I know it’s been a while, but I was forced to update drivers and this has happened all over again. I tried changing the physx processor configuration and it did nothing for me. Anyone able to overcome this issue?
Quick update: Everything goes back to normal once I set Graphics API to DirectX 11. It seems to be an issue with DirectX 12, but I have seen this issue on reddit and other sites claiming it has something to do with Windows 10 update 1909 and 2004.
If anyone has a solution that does not involve killing DX12, I’d appreciate it. TY
Update again ( lol sorry ) : I switched over to The Division 2 ( running DirectX 12 ) and had the exact same issue. I changed TD2 over to DirectX 11 and the problem is gone. DirectX 12 is at least part of the issue for sure ( for me ), but it may be an issue caused by other interactions that I mentioned above.
Just to clarify, I updated to Nvidia driver 456.38 and am on Windows version 1909.
1 Like
Quite the necro. Please start a new thread.
Not necessary. I had replied to the original post back when it was first posted. The problem hasn’t changed, only the time. From what is visible so far, the culprits are the same as well. Same problem, same thread, but a different date.
1 Like
Same solution here. Guess we’re playing the waiting game to see which software is actually causing the oops 
1 Like
Did you ever find a solution. I started having this issues a few months ago as well.
Disabling G-Sync in nvidia control panel fixed this for me.