Question Second screen flickering

[joaoint]

Hi there,

All of sudently my desktop starts to flickering the image, it goes black for half a second, and the behaviour is random, it only does on the TV and not on the main monitor. If i connect my laptop to the TV it works fine.


Here is the list of things i have done.

• Change the hdmi cable
• Disconnect the main screen (Asus VG248QE) and let only the TV (Samsung UE50AU7105KXXC)
• Update drivers including NVIDIA card
• Update BIOS
• Test only with 1x8gb RAM on the different slots
• Test with another graphic card from other desktop
• Disconnect CD/DVD sata cable
• Disconnect SD card readerd sata cable
• Using only Display port on graphics card
• Different resolution
• Different refresh rate
• Format Windows

My setup:

• Nvidia Geforce gtx 660
• Intel core i5-4590
• 2x4gb Corsair ddr3
• Corsair cx500
• Motherboard Asus H81M-E
• Samsung SSD 850 EVO
• Seagate HDD ST500

My Screens:

• Asus VG248QE
• TV Samsung UE50AU7105KXXC

 

[Ralston18]

Desktop PSU = Corsair CX500

PSU - age, condition (orginal to build, new, refurbished, used)?

History of heavy use for gaming, video editing, or even bit-mining?

 

[joaoint]

Desktop PSU = Corsair CX500

PSU - age, condition (orginal to build, new, refurbished, used)?

History of heavy use for gaming, video editing, or even bit-mining?

My Corsair cx500 PSU has 9 years, and i ocasionally play games but no video editing or bit-mining.

Thank you,

 

[Ralston18]

A 9 year old PSU is certainly suspect.

Very likely beyond its' designed in EOL (End of Life) and thus beginning to falter and fail.

Look in Reliability History/Monitor and Event Viewer.

What you are looking for are any errors, warnings, or even informational events being captured just before or at the times flickering begins.

Reliability Histor/Monitor is end user friendly and the timeline may reveal patterns.

Event Viewer is requires more time and effort to navigate and understand.

To help, from this Forum:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

And you can take screenshots of what you find and post the screenshots here via imgur (www.imgur.com).

Just ensure that the screenshots show the full tool window and are large enough to be viewable.

 

[joaoint]

I have uploaded two videos so you can see better what the issue is.

https://imgur.com/a/Iuxlfi6

View: https://imgur.com/a/Iuxlfi6


- Reliability History/Monitor

Critical event "Windows was not properly shutdown" which doesn´t make sense because the it does not do that.

- Event viewer

Distributed-Com Event ID 10016

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscCloudBackupProvider
and APPID
Unavailable
to the user DESKTOP-2T1DKH4\Windows SID (S-1-5-21-2740517169-4031929359-1590776690-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Kernel-PNP Event id 219

The driver \Driver\SASDIFSV failed to load for the device ROOT\LEGACY_SASDIFSV\0000.

 

[joaoint]

A 9 year old PSU is certainly suspect.

Very likely beyond its' designed in EOL (End of Life) and thus beginning to falter and fail.

Look in Reliability History/Monitor and Event Viewer.

What you are looking for are any errors, warnings, or even informational events being captured just before or at the times flickering begins.

Reliability Histor/Monitor is end user friendly and the timeline may reveal patterns.

Event Viewer is requires more time and effort to navigate and understand.

To help, from this Forum:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

And you can take screenshots of what you find and post the screenshots here via imgur (www.imgur.com).

Just ensure that the screenshots show the full tool window and are large enough to be viewable

Besides the info i have posted, i also checked this error on Event Viewer.

Distributed-Com Event ID 10016

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.securityappbroker
and APPID
Unavailable
to the user DESKTOP-2T1DKH4\Windows SID (S-1-5-21-2740517169-4031929359-1590776690-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

[Ralston18]

Windows not being properly shutdown indicates a loss of power somewhere that Windows "did not expect" as it would otherwise expect if the power down icon is used. Or some equivalent code/script.

There are many things that represent a loss of power: loose connection, a drop in voltage, etc..

Improper shutdowns can and do cause file corruption. And that can lead to even more problems.

Try running "dism" and "sfc /scannow" to allow Windows to look for, find, and hopefully fix any corrupted files.

FYI:

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

 

[joaoint]

Windows not being properly shutdown indicates a loss of power somewhere that Windows "did not expect" as it would otherwise expect if the power down icon is used. Or some equivalent code/script.

There are many things that represent a loss of power: loose connection, a drop in voltage, etc..

Improper shutdowns can and do cause file corruption. And that can lead to even more problems.

Try running "dism" and "sfc /scannow" to allow Windows to look for, find, and hopefully fix any corrupted files.

FYI:

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

I did the commands you recommended, windows has repaired the corrupted files and i had no issues for five days, but unfortunately today the flickering started again.

https://imgur.com/a/QUnZukG

View: https://imgur.com/a/QUnZukG

 

[Ralston18]

Are the same files corrupted again?

If so look in Reliability History/Monitor, Event Viewer, and Update History for any logged entries just before or at the time the file corruption and/or other problems began again.

 

[joaoint]

Are the same files corrupted again?

If so look in Reliability History/Monitor, Event Viewer, and Update History for any logged entries just before or at the time the file corruption and/or other problems began again.

I have no corrupted files this time, and i have this errors on event viewer and reliability history.

https://imgur.com/a/LZHV1Pi

View: https://imgur.com/a/LZHV1Pi

 

[Ralston18]

What are those Misc. Failures that appeared on Sept 19th?

Look through the Event Viewer Logs for other entries that started appearing/ reappearing again at the 5 day mark.

Then look for any updates just prior to the problems returning and any log entries being captured.

Especially problem updates but do not exclude sucessfully updates.

Then run the commands again to determine if those errors stop.

In Control Panel > Date and Time > Internet Time > Change settings

What time server is being used My system is using time.nist.gov but also offers time.windows.com

Do not change anything - just check and post the setting.

(There was another post not too long ago that had DeviceManagerSetup errors. I had noted some link/reference to the time server - not sure if the link is relevant at this time.)

However, if "dism" and"sfc /scannow" solves the problem (even if only temporarily) then the next step is to discover what is causing corruptions to re-occur. Hopefully that would be found in Reliability History/Monitor and Event Viewer. Perhaps Update History as well.

 

[joaoint]

What are those Misc. Failures that appeared on Sept 19th?

Look through the Event Viewer Logs for other entries that started appearing/ reappearing again at the 5 day mark.

Then look for any updates just prior to the problems returning and any log entries being captured.

Especially problem updates but do not exclude sucessfully updates.

Then run the commands again to determine if those errors stop.

In Control Panel > Date and Time > Internet Time > Change settings

What time server is being used My system is using time.nist.gov but also offers time.windows.com

Do not change anything - just check and post the setting.

(There was another post not too long ago that had DeviceManagerSetup errors. I had noted some link/reference to the time server - not sure if the link is relevant at this time.)

However, if "dism" and"sfc /scannow" solves the problem (even if only temporarily) then the next step is to discover what is causing corruptions to re-occur. Hopefully that would be found in Reliability History/Monitor and Event Viewer. Perhaps Update History as well.

For the misc failures on 19th i have uploaded another screenshot, time setting is time.windows.com, and now when the flickering occours it also cuts the sound of the speakers at the same time and i hear a little "crack" from the TV.

I dont know if it is related but the problems reappear after this update. (Screenshot on the link)

Regarding event viewer i didnt see anything different.

https://imgur.com/a/h0BEyFf

View: https://imgur.com/a/h0BEyFf

 

[Ralston18]

Try "dism" and "sfc /scannow" one more time.

If the problem stops then it appears that there is a pattern.

And all the more so if the problem returns with a future update or seemingly at random.

What speakers are being used: TV, soundbar, I/O panel?

The little "crack" being heard could be some sort of discharge that could be a power problem that also causes corrupted files.

Is there anyway that another PSU can be installed for testing purposes? Simply as a matter of elimination.

(Remember to use only the cables that come with the test PSU.)

Trying to avoid going in circles and eliminate potential culprits.

Do keep an eye on Reliability History/Monitor and Event Viewer.

It will be easier to find and note new entries if you clear the Event Viewer logs.

 

[joaoint]

Try "dism" and "sfc /scannow" one more time.

If the problem stops then it appears that there is a pattern.

And all the more so if the problem returns with a future update or seemingly at random.

What speakers are being used: TV, soundbar, I/O panel?

The little "crack" being heard could be some sort of discharge that could be a power problem that also causes corrupted files.

Is there anyway that another PSU can be installed for testing purposes? Simply as a matter of elimination.

(Remember to use only the cables that come with the test PSU.)

Trying to avoid going in circles and eliminate potential culprits.

Do keep an eye on Reliability History/Monitor and Event Viewer.

It will be easier to find and note new entries if you clear the Event Viewer logs.

I have run the commands again but the problem remains, unoffortontely i dont have another PSU so i have to buy a new one, my current is 500w do i need to go higher wattage or this is enough?

One thing i have noticed is when the flickering begins, if the i disconnect/connect the hdmi cable it usually stops for the rest of the day, but then it start again.

Thank you,

 

[Ralston18]

Do you have anothere known working HDMI cable to swap in?

May be narrowing down to a port, a cable, or a plug problem.

 

[joaoint]

Do you have anothere known working HDMI cable to swap in?

May be narrowing down to a port, a cable, or a plug problem.

i have tested before with another hdmi cable and the problem stays the same