Hey,
I have a problem with my Windows 10 system and probalby the AMD A8-6660K APU with Readon 8570D without any additional graphic card on a ASUS F2A85M-Pro motherboard. The screen flickers and makes working very exhausting. I've tried the recommended fixes from:
https://support.microsoft.com/en-us/help/12374/windows-10-troubleshoot-screen-flickering
1. I do not have any third party anit-virus program running, nor any apps that cause the problem. Also the flickering is visible while booting.
2. I updated to the newest driver (https://www.amd.com/de/support/apu/amd-series-processors/amd-a8-series-apu-for-desktops/a8-6600k-rad..., 15.7.1 WHQL). Previously unistalled the old driver and restarted.
3. I've uninstalled Realteak drivers, as I read in some forum that this might help. Do not remember where.
Can anybody recommend me a fix?
Thanks in advance,
Duro
My system is (as from msinfo32):
OS Name Microsoft Windows 10 Pro
Version 10.0.17134 Build 17134
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-6LQO4HI
System Manufacturer System manufacturer
System Model System Product Name
System Type x64-based PC
System SKU SKU
Processor AMD A8-6600K APU with Radeon(tm) HD Graphics, 3900 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 6601, 25/11/2014
SMBIOS Version 2.7
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Model Not Available
BaseBoard Name Hauptplatine
Platform Role Desktop
Secure Boot State On
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale Germany
Hardware Abstraction Layer Version = "10.0.17134.1"
Username DESKTOP-6LQO4HI\USER
Time Zone Mitteleuropäische Sommerzeit
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.20 GB
Available Physical Memory 1.36 GB
Total Virtual Memory 3.76 GB
Available Virtual Memory 2.02 GB
Page File Space 576 MB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualisation-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not InstantGo, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
