Jump to content
You must now use your email address to sign in [click for more info] ×

Problem with latest Windows beta release


Recommended Posts

Hi All,

 

It installs completely but won't run on my Win10 Pro x64 machine with latest version updated (anniversary release).

 

Processor Core I5 2500K @ 3.3GHz

8 Go Ram

GPU Card : Nvidia GeForce GTX 970

 

Two Application error messages can be found in the Windows application Log :

 

- <System>
  <Provider Name="Application Error" />
  <EventID Qualifiers="0">1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2016-11-12T21:34:28.414079300Z" />
  <EventRecordID>9505</EventRecordID>
  <Channel>Application</Channel>
  <Computer>PC-Photo</Computer>
  <Security />
  </System>
- <EventData>
  <Data>Photo.exe</Data>
  <Data>1.5.0.35</Data>
  <Data>5823c323</Data>
  <Data>KERNELBASE.dll</Data>
  <Data>10.0.14393.321</Data>
  <Data>57f4c4f0</Data>
  <Data>e0434352</Data>
  <Data>0000000000017788</Data>
  <Data>1bec</Data>
  <Data>01d23d2c8bf9eb42</Data>
  <Data>C:\Program Files\Affinity\Affinity Photo Public Beta\Photo.exe</Data>
  <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
  <Data>0a6e9260-4fb4-4dd9-9fde-20e340ea5386</Data>
  <Data />
  <Data />
  </EventData>
  </Event>
 
 
and 
 
- <System>
  <Provider Name=".NET Runtime" />
  <EventID Qualifiers="0">1026</EventID>
  <Level>2</Level>
  <Task>0</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2016-11-12T21:34:28.367199900Z" />
  <EventRecordID>9504</EventRecordID>
  <Channel>Application</Channel>
  <Computer>PC-Photo</Computer>
  <Security />
  </System>
- <EventData>
  <Data>Application : Photo.exe Version du Framework : v4.0.30319 Description : le processus a été arrêté en raison d'une exception non gérée. Informations sur l'exception : System.OutOfMemoryException à System.ModuleHandle.ResolveType(System.Reflection.RuntimeModule, Int32, IntPtr*, Int32, IntPtr*, Int32, System.Runtime.CompilerServices.ObjectHandleOnStack) à System.ModuleHandle.ResolveTypeHandleInternal(System.Reflection.RuntimeModule, Int32, System.RuntimeTypeHandle[], System.RuntimeTypeHandle[]) à System.Reflection.RuntimeModule.ResolveType(Int32, System.Type[], System.Type[]) à System.Reflection.CustomAttribute.FilterCustomAttributeRecord(System.Reflection.CustomAttributeRecord, System.Reflection.MetadataImport, System.Reflection.Assembly ByRef, System.Reflection.RuntimeModule, System.Reflection.MetadataToken, System.RuntimeType, Boolean, System.Object[], System.Collections.IList, System.RuntimeType ByRef, System.IRuntimeMethodInfo ByRef, Boolean ByRef, Boolean ByRef) à System.Reflection.CustomAttribute.GetCustomAttributes(System.Reflection.RuntimeModule, Int32, Int32, System.RuntimeType, Boolean, System.Collections.IList, Boolean) à System.Reflection.CustomAttribute.GetCustomAttributes(System.Reflection.RuntimeAssembly, System.RuntimeType) à System.Attribute.GetCustomAttributes(System.Reflection.Assembly, System.Type, Boolean) à System.AppDomain.GetTargetFrameworkName()</Data>
  </EventData>
  </Event>
 
It seems that .NET Runtime is mainly at fault, but I am not sure what to do to fix this.
Anyone with an idea ?
 
 
Link to comment
Share on other sites

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.