Windows 10: Problems with errors in Event Viewer relating to AMD graphics

The error report below I believe is saying that permission is denied accessing a file under ProgramData. This I think is linked to Permissions which appear to be a hot topic with Windows 10. I do have loads of other errors in the ACCEEvent Log relating to the graphics but I thought I would start with this one.
The question I have is it possible that one of you could provide what the permissions should be for the ProgramData folder to check against what I have?
(I also have reports the fuel.xml is missing - which it is)
Error report below.

Log Name: ACEEventLog
Source: ACEEventLogSource
Date: 16/12/2016 15:56:33
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Home-PC
Description:
0000000040: 2016-12-16 15:56:33:139 Exception <Saving Xml Document>: Access to the path 'C:\ProgramData\ATI\ACE\Profiles.xml' is denied.
Exception Called by: System.Threading.ExecutionContext::RunInternal processID:09852 threadID*Sad32 ) domainName*SadCCC.exe ) assemblyName*Sadmscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
**************************************************************************************************** ********************

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ACEEventLogSource" />
<EventID Qualifiers="0">0</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-12-16T15:56:33.139808100Z" />
<EventRecordID>3484</EventRecordID>
<Channel>ACEEventLog</Channel>
<Computer>Home-PC</Computer>
<Security />
</System>
<EventData>
<Data>0000000040: 2016-12-16 15:56:33:139 Exception &lt;Saving Xml Document&gt;: Access to the path 'C:\ProgramData\ATI\ACE\Profiles.xml' is denied.
Exception Called by: System.Threading.ExecutionContext::RunInternal processID:09852 threadID*Sad32 ) domainName*SadCCC.exe ) assemblyName*Sadmscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
**************************************************************************************************** ********************
</Data>

:)

 

Windows 10 in bootcamp: "Bootcamp Graphics Driver update 6.0" crashes computer during install

I would first check Apple Support Communities to see if anyone else is having trouble with a Boot Camp update.

After, check the Event Viewer>Windows logs>System after the install crash (right-click the Start button and choose "Event viewer") and find errors relating to graphics or installations. See if anything pops up about what is failing.

 

Intermittent BLACK SCREEN On monitor happens once then display is frozen on black screen!

Have you checked the event viewer? Open even viewer go to Windows logs and check system. Look for anything graphics related. How are your temps for the video card?

 

Here's a Snip of programdata permissions
All listed access principles are listed.



the snip only shows permissions for the selection Users (showing principles for all would take 4 snips.)
But the permissions for all are:
Owner - no checks
System - full control - all checks
Administrators - - full control - all checks
Users - read & execute, List folder contents, read - 3 checks

Above is from a smooth runnin machine.

If ya want to insure access,
*** Try this at you own Risk!!!
*** First document what ya start with! Save it! ***
Chg Permissions: Edit, Add, Advanced, Find Now, double click "Everyone" , OK, Apply, out...
Now Everyone is in the top Group User list.
Select(click) Everyone - puts everyones access in bottom Permissions box
check all check boxes except full control (maybe a driver might even need Full Ctl, cause driver install may wanta delete whats there first, the re insert)
Now ya have allowed access to EVERYONE !!!
Ya shouldn't get Access denied anymore (but who knows with Win 10)

*** Again this is Not a Recommended approach, but can lead to identifying the problem... ***
*** If this doesn't lead to THE problem Fix - PUT Access back the way it was ****
*** Remember the Computer Doctor's Creed, DO No Harm! ***
*** And always have a "Real" recovery method in place! )***
*** Good luck, and Be Careful... ***

 

RPLewis Thank you for that. Doesn't appear to be that different to what I have. Is there any chance that you can provide a screen shot of the "Advanced" option from the ProgramData properties so that I can check further, as there must be something incorrect somewhere to generate the error message?
Thanks