Who is responsible for that?
Anyone who refused to upgrade, and want maximum control over Windows, might want to take a look at this cheatsheet of problematic updates to avoid, that I compiled from multiple sources, mainly http://www.askwoody.com/
If you want to know something more about Windows services, what they do, and if you can safely disable them,
check: http://www.blackviper.com
KB971033 – Update for Windows activation technologies
KB2876229 - Updates Skype, sets MSN/Bing as defaults
KB2902907 - Description not available, update was pulled by Microsoft
KB2922324 - Description not available, update was pulled by Microsoft
KB2952664
KB2966583 - Improvements for the System Update Readiness Tool in Windows 7
KB2976978 - Performs and collect compatibility appraiser logs in order to ease the upgrade experience to Windows 10
KB2977759
KB2990214 - Update to upgrade from Windows 7 to a later version of Windows
KB2999226 - Windows 10 Universal C Runtime for earlier Windows operating systems (required for GOG Galaxy)
KB3012973 - Upgrade to Windows 10
KB3014460 – Update for Windows insider preview /upgrade to Windows 10
KB3015249 - Update that adds telemetry points to consent.exe in Windows 8.1 and Windows 7
KB3021917 – Update to Windows 7 SP1 for "performance improvements"
KB3022345 – Update for customer experience and diagnostic telemetry
KB3035583 - Installs ‘Get Windows 10’ app in Win 8.1 and Win 7 SP1 (GWX)
KB3044374 – Update that enables you to upgrade from Windows 8.1 to Windows 10
KB3046480 – Update to migrate Microsoft.NET Framework 1.1 when you upgrade from Windows 8.1 or Windows 7 to a later version of Windows
KB3050265 – Updates Windows Update Client for Windows 7 (changes system files to support upgrade)
KB3050267 – Updates Windows Update Client for Windows 8.1 (changes system files to support upgrade)
KB3054476
KB3064683
KB3065987 – Updates Windows Update Client for Windows 7 and Windows Server 2008 R2 (changes system files to support upgrade)
KB3065988
KB3068708 – Telemetry (replaces KB3022345)
KB3072318 – Update for Windows 8.1 OOBE to upgrade to Windows 10
KB3074677
KB3075249 – Adds telemetry points to consent.exe in Windows 8.1 and Windows 7
KB3075851 – Updates Windows Update Client for Windows 7 and Windows Server 2008 R2 (changes system files to support upgrade)
KB3075853 – Updates Windows Update Client for Windows 8.1 and Windows Server 2012 r2 August 2015
KB3078667
KB3080149 – Telemetry
KB3081437
KB3081454
KB3083324 – Windows Update Client for Windows 7 and Windows Server 2008 R2 September 2015
KB3083325
KB3083710 – Windows Update Client for Windows 7 and Windows Server 2008 R2 October 2015
KB3083711
KB3086255
KB3090045 – Update applies to some reserved devices upgrading to Windows 10 from Windows 8.1 or Windows 7 Service Pack 1 (SP1)
KB3097877
KB3102810 – Update contains improvements for Windows Update Client in Windows 7 Service Pack 1 or Windows Server 2008 R2 SP1.
KB3102812 – Update contains improvements for the Windows Update client in Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2
KB3107998
KB3112336 - Windows Update Client for Windows 8.1 and Windows Server 2012 R2 December 2015
KB3112343 - Windows Update Client for Windows 7 and Windows Server 2008 R2 December 2015
KB3123862 - Updated capabilities to upgrade Windows 8.1 and Windows 7
KB3135445 - Windows Update Client for Windows 7 and Windows Server 2008 R2 February 2016
KB3136449
KB3138612 - Windows Update Client for Windows 7 and Windows Server 2008 R2 March 2016
KB3139929 - Cumulative security update for IE, carries KB3146449, Woody says avoid
KB3141092 - reportedly piggybacks on Security Update KB3134814 if IE11 is installed
KB3146449 - Updated Internet Explorer 11 capabilities to upgrade Windows 8.1 and Windows 7 (piggybacks on KB3139929)Comment has been collapsed.
Another bump!
Don't forget to check my first comment, if you're still on Windows 7 / 8.1, and don't want Microsoft to spy too much on you.
Comment has been collapsed.
I'd assume it's an AMD driver issue. Uninstall GPU driver and see if the problem persists, if it does: it wasn't the GPU drivers, if not: install older AMD drivers. Continue from there. I never had an AMD GPU though.
Comment has been collapsed.
I'd second this for a try. Can't really speak on new AMD drivers, I'm still using CCC 14.501 just because well... It still works, so I see no point updating and risking issues if everything runs good for me.
Comment has been collapsed.
You could also try a clean Windows 10 install, sometimes things brake if you mess with files too much.
Comment has been collapsed.
Okay, I just uninstalled the driver with DDU, and guess what? The problem persists, even with Microsoft's basic video driver.
Comment has been collapsed.
How weird, the issue seem to have been solved...
Don't ask me why, but I think it might have been related to either MSI Afterburner or Riva Tuner Statistics Server,
as after tinkering with their settings the flashing ended.
Comment has been collapsed.
Reminds me of a Digital Foundry video not long ago where they talked about FCAT. Might have been a setting in there doing something similar?
Comment has been collapsed.
Same issue, except mine had a monochromatic bar.
I'd point my finger towards Riva Tuner Statistics Server as the culprit, as it has screen recording capabilities (that I don't use anyway, I keep it just for hardware monitoring).
Comment has been collapsed.
Thread updated with a solution, as well as another tip.
I kept the old thread archived for reference, the above comments all refer to it.
And the poll! I like useless polls!
Comment has been collapsed.
do you remember the driver you had this problem? was it 16.7.2 or 16.7.3? i know you said "the latest" and 16.7.3 just came out, but since you reverted back to 16.3.2 and not 16.7.2 i'm confused. however if you were referring to 16.7.2, why i don't get a problem like this?
Comment has been collapsed.
If you refer to the "flashing bar" problem, every driver had it, even Microsoft's basic one.
I reverted to 16.3.2 because I need the underscan utility, which has been removed (although it was probably just an oversight).
There's a post on AMD's forum acknowledging this oversight, dating back to April, so I installed the March driver (16.3.2), which is also the latest WHQL certified one.
If you don't use particular software, especially those with screen recording capabilities (they hook up to the driver),
that's why you aren't experiencing the same issue.
Comment has been collapsed.
i do have riva something something that came with msi afterburner. ditto for windows 10 too. that's why i had a brain fart. well, as long as all is well i guess it doesn't really matter.
Comment has been collapsed.
I have the 16.7.2 and the underscan is now the HDMI Adapting... the scrollbar under the main menu' on the "Screen" tab.
Comment has been collapsed.
After a bit of tinkering, I came to the conclusion that the issue was caused by Riva Tuner Statistics Server,
But Riva Tuner is a program for NVidia cards only… why did you even install it in the first place for a Radeon? o.0
Comment has been collapsed.
TIL i have an nvidia card which was sold as an amd card to me. .-.
Comment has been collapsed.
It can work with ATi/AMD cards, but even its official introduction is this: RivaTuner is a complete powerful tweaking environment, providing you everything you may need to tune NVIDIA GPU based display adapters. AMD cards have another similar program made for them called RadeonPro. (Which in turn can work on NVidia cards.)
Comment has been collapsed.
i need a gif that is at least 5*[confused travolta]. why do they even make if work if it's not meant for it? what the hell, uhmm, whoever made this riva something something?!
Comment has been collapsed.
Some Russian, I think.
These are not hardware-specific, they just enable options most drivers don't put on their GUI. For the most part, GPUs work really similarly on software level, at least similar enough that these "hidden" options work on both. But strictly speaking, Riva is made to work with NVidia cards.
Comment has been collapsed.
Well, it's not the actual Riva Tuner overclocking utility (that is now long dead), it's just a hardware monitoring software that works with every GPU. In fact, it's needed to unlock the hardware monitoring section of MSI Afterburner.
Comment has been collapsed.
RIVA's always been a bit problematic between games, driver updates, etc.
I'm a bit surprised it's borked entirely on Win10, since it's usually limited to select applications.
EDIT: The dev for Riva was suing EVGA a while back for using bits of his code in their Precision tool. Oddly enough, they removed his code from their software and rewrote it, and now it works flawlessly -_-
Comment has been collapsed.
The most surprising part, is that I don't even actively use it, except for the hardware monitoring part.
Also, the FPS monitoring part is done by Steam already.
Apparently, just keeping those services enabled caused that issue.
Comment has been collapsed.
Old thread for reference:
After a bit of tinkering, I came to the conclusion that the issue was caused by Riva Tuner Statistics Server,
the hardware monitoring and screen recording applet that's installed with MSI Afterburner.
Most probably, some settings required for its screen recording capabilities were interfering with the Radeon Crimson driver,
and that would also explain those warning messages about "not being able to hook up to the required files".
Also, if you have non-standard monitors like me (mine is actually a TV), the latest version of the Radeon Settings App
don't have the "underscan" option, leaving you with a cut-out screen if you opt for higher resolutions.
Personally, I reverted back to the 16.3.2 WHQL driver, so I'm not sure if the following hotfixes / betas still have it.
Comment has been collapsed.