2023/07/13-18:11:32.3661|IMP] *** LOG FILE STARTED ***
2023/07/13-18:11:32.3661|IMP] XtuCore Version 7.9.1.3
2023/07/13-18:11:32.3737|IMP] Initializing DriverWrapper for driver \\.\IOCBIOS2
2023/07/13-18:11:32.3812|IMP] Initializing DriverWrapper for driver \\.\IOCBIOS2
2023/07/13-18:11:32.4711|IMP] Initializing performance tuning application mutex
2023/07/13-18:11:32.4813|IMP] Attempting to perform Unity Initialization against Library HardwareServices
2023/07/13-18:11:32.4913|IMP] Handling Unity Intialization for HardwareServices->ServicesUnityInitializer->Initialize
2023/07/13-18:11:32.5612|IMP] Initializing ServicesUnityInitializer
2023/07/13-18:11:32.5657|IMP] Initializing DriverWrapper for driver \\.\IOCBIOS2
2023/07/13-18:11:32.5657|IMP] Starting watchdog initialization
2023/07/13-18:11:32.5657|IMP] Get driver path called for guid: c2e625a9-8693-4dea-bac4-b15ca98f9ee9
2023/07/13-18:11:32.5712|IMP] Initializing DriverWrapper for driver \\?\acpi#intc1099#4&3549f8ff&0#{c2e625a9-8693-4dea-bac4-b15ca98f9ee9}
2023/07/13-18:11:32.5762|IMP] Attempting to perform Unity Initialization against Library HardwareAccess
2023/07/13-18:11:32.5863|IMP] Handling Unity Intialization for HardwareAccess->_Wfew0NNCjwligEfBACyO1JugU3x->_MG6ccO2NJiJx3aJGzNOH920JUKL
2023/07/13-18:11:32.6455|IMP] Initializing AccessUnityInitializer
2023/07/13-18:11:32.6515|IMP] AccessUnityInitializer Initialized
2023/07/13-18:11:32.6515|IMP] Attempting to perform Unity Initialization against Library XtuApplication
2023/07/13-18:11:32.6565|IMP] Handling Unity Intialization for XtuApplication->_ekiHrMfEV0Ql1Bs7vFBBzy4mQ8H->_MG6ccO2NJiJx3aJGzNOH920JUKL
2023/07/13-18:11:32.7463|IMP] Processor Family is: AlderLake
2023/07/13-18:11:32.7513|!ERR] XTU Registry folder is null
2023/07/13-18:11:32.7563|IMP] Processor model is H
2023/07/13-18:11:32.7664|IMP] InitializeMsrFields called
2023/07/13-18:11:32.7914|IMP] Initializing BiosMailboxFields
2023/07/13-18:11:32.7914|IMP] BiosMailboxFields Initialized
2023/07/13-18:11:32.7914|IMP] Processor Family is: AlderLake
2023/07/13-18:11:32.7914|!ERR] XTU Registry folder is null
2023/07/13-18:11:32.7914|IMP] Processor model is H
2023/07/13-18:11:32.8536|IMP] Processor Family is: AlderLake
2023/07/13-18:11:32.8536|!ERR] XTU Registry folder is null
2023/07/13-18:11:32.8536|IMP] Processor model is H
2023/07/13-18:11:32.8536|IMP] Initializing DriverWrapper for driver \\.\IOCBIOS2
2023/07/13-18:11:32.8612|IMP] Processor Family is: AlderLake
2023/07/13-18:11:32.8612|!ERR] XTU Registry folder is null
2023/07/13-18:11:32.8612|IMP] Processor model is H
2023/07/13-18:11:32.8612|IMP] Processor Family is: AlderLake
2023/07/13-18:11:32.8612|!ERR] XTU Registry folder is null
2023/07/13-18:11:32.8612|IMP] Processor model is H
2023/07/13-18:11:32.9013|IMP] Processor Family is: AlderLake
2023/07/13-18:11:32.9013|!ERR] XTU Registry folder is null
2023/07/13-18:11:32.9013|IMP] Processor model is H
2023/07/13-18:11:32.9013|!ERR] XTU Registry folder is null
2023/07/13-18:11:32.9013|IMP] Processor model is H
2023/07/13-18:11:32.9214|IMP] Initializing MailboxFields
2023/07/13-18:11:32.9335|IMP] MailboxFields Initialized
2023/07/13-18:11:32.9465|!ERR] XTU Registry folder is null
2023/07/13-18:11:33.0263|IMP] Initializing Watchdog Timer
2023/07/13-18:11:33.0263|IMP] Watchdog Present = True
2023/07/13-18:11:33.0263|IMP] Aux Wdt Recovery Flag = False
2023/07/13-18:11:33.0263|IMP] Watchdog Recovery Flag = False
2023/07/13-18:11:33.0263|IMP] Combined WDT/AUX Recovery Flag = False
2023/07/13-18:11:33.0293|IMP] Watchdog Running = False
2023/07/13-18:11:33.0293|IMP] Watchdog OS Load Coverage = True
2023/07/13-18:11:33.0293|IMP] Watchdog Capabilities = Min 1000ms, Max 1008000ms, Resolution 1000ms
2023/07/13-18:11:33.0293|IMP] Selected Runtime Timeout = 10000ms
2023/07/13-18:11:33.0293|IMP] Selected Reboot Timeout = 600000ms
2023/07/13-18:11:33.0314|IMP] Arming Watchdog Timer
2023/07/13-18:11:33.0314|IMP] Watchdog Timer Initialized
2023/07/13-18:11:33.0314|IMP] Watchdog Control Thread Started - Watchdog Armed
2023/07/13-18:11:33.0364|IMP] Initializing WMI Based Platform Detection
2023/07/13-18:11:33.3653|IMP] Platform detection found integrated graphics device
2023/07/13-18:11:33.3863|IMP] Initializing BiosMailbox Tuning
2023/07/13-18:11:33.3863|IMP] BiosMailboxTuning Controls Initialized
2023/07/13-18:11:33.3913|IMP] Initializing MSR Tuning
2023/07/13-18:11:33.3964|IMP] Initializing MSR Control Mappings
2023/07/13-18:11:33.4264|IMP] Initializing MSR BIOSless Control Map
2023/07/13-18:11:33.4264|IMP] MSR Tuning Initialized
2023/07/13-18:11:33.4264|IMP] Initializing TDP Controls
2023/07/13-18:11:33.4365|IMP] TDP Controls Initialized
2023/07/13-18:11:33.4415|IMP] Initializing TDP Time Window Controls
2023/07/13-18:11:33.4415|IMP] TDP Time Window Controls Initialized
2023/07/13-18:11:33.4511|IMP] Initializing OC Mailbox Tuning
2023/07/13-18:11:33.4561|!ERR] Attempted to read OCMB fieldId 58 on an invalid platform
2023/07/13-18:11:33.4561|!ERR] Attempted to read OCMB fieldId 54 on an invalid platform
2023/07/13-18:11:33.4561|!ERR] Attempted to read OCMB fieldId 56 on an invalid platform
2023/07/13-18:11:33.4561|!ERR] Attempted to read OCMB fieldId 80 on an invalid platform
2023/07/13-18:11:33.4561|!ERR] Unable to retrieve fieldinfo for fieldId 306
2023/07/13-18:11:33.4561|!ERR] Attempted to read OCMB fieldId 306 on an invalid platform
2023/07/13-18:11:33.4561|!ERR] Unable to retrieve fieldinfo for fieldId 307
2023/07/13-18:11:33.4561|!ERR] Attempted to read OCMB fieldId 307 on an invalid platform
2023/07/13-18:11:33.4611|!ERR] IronCity.Common.DriverAccessException: OC_MAILBOX write did not complete successfully
   在 IronCity.HardwareServices.OcMailboxService._WcshgDvK4UacSIIs5UARGHUP9vD(UInt64 , Boolean , IEnumerable`1 )Exception thrown during mailbox command submission
2023/07/13-18:11:33.4762|!ERR] - Mailbox 85 is invalid for this platform
2023/07/13-18:11:33.4772|!ERR] Attempted to read OCMB fieldId 63 on an invalid platform
2023/07/13-18:11:33.4772|!ERR] Attempted to read OCMB fieldId 63 on an invalid platform
2023/07/13-18:11:33.4772|!ERR] - Mailbox 68 is invalid for this platform
2023/07/13-18:11:33.4772|!ERR] Attempted to read OCMB fieldId 59 on an invalid platform
2023/07/13-18:11:33.4772|!ERR] Attempted to read OCMB fieldId 59 on an invalid platform
2023/07/13-18:11:33.4772|!ERR] - Mailbox 64 is invalid for this platform
2023/07/13-18:11:33.4772|!ERR] Attempted to read OCMB fieldId 61 on an invalid platform
2023/07/13-18:11:33.4772|!ERR] Attempted to read OCMB fieldId 61 on an invalid platform
2023/07/13-18:11:33.4772|!ERR] - Mailbox 66 is invalid for this platform
2023/07/13-18:11:33.4772|!ERR] - Mailbox 52 is invalid for this platform
2023/07/13-18:11:33.4772|!ERR] - Mailbox 51 is invalid for this platform
2023/07/13-18:11:33.4772|!ERR] - Mailbox 311 is invalid for this platform
2023/07/13-18:11:33.4812|!ERR] Attempted to read OCMB fieldId 59 on an invalid platform
2023/07/13-18:11:33.4812|!ERR] Attempted to read OCMB fieldId 61 on an invalid platform
2023/07/13-18:11:33.4812|!ERR] Attempted to read OCMB fieldId 63 on an invalid platform
2023/07/13-18:11:33.4812|IMP] OC Mailbox Tuning Initialized
2023/07/13-18:11:33.4812|IMP] OC Mailbox Tuning Initialized
2023/07/13-18:11:33.5063|WARN] Failed to initialize ICC hardware tuning: exception encountered.
2023/07/13-18:11:33.5063|WARN] Failed IccLibGetCurrentClockSettingsEx: 3
2023/07/13-18:11:33.5113|IMP] Initializing AlderLake-Based Turbo Ratio Limit Controls
2023/07/13-18:11:33.5218|IMP] AlderLake-Based Turbo Ratio Limit Controls Initialized
2023/07/13-18:11:33.5464|!ERR] IronCity.Common.DriverAccessException: OC_MAILBOX write did not complete successfully
   在 IronCity.HardwareServices.OcMailboxService._WcshgDvK4UacSIIs5UARGHUP9vD(UInt64 , Boolean , IEnumerable`1 )Exception thrown during mailbox command submission
2023/07/13-18:11:33.5464|!ERR] Multi mailbox write failed when writing to domain with write command 
2023/07/13-18:11:33.5615|IMP] Initializing AlderLake-Based E-Core Turbo Ratio Limit Controls
2023/07/13-18:11:33.5665|IMP] AlderLake-Based E-Core Turbo Ratio Limit Controls Initialized
2023/07/13-18:11:33.5665|IMP] Initializing Per Core Ratio Limit Controls
2023/07/13-18:11:33.6312|IMP] Initializing ring ratio control
2023/07/13-18:11:33.6362|IMP] Initializing Graphics ratio control
2023/07/13-18:11:33.6372|IMP] Initializing tuning aggregation
2023/07/13-18:11:33.6713|IMP] Initializing XTU tuning system
2023/07/13-18:11:33.6853|!ERR] Attempted to read OCMB fieldId 59 on an invalid platform
2023/07/13-18:11:33.6853|!ERR] Attempted to read OCMB fieldId 61 on an invalid platform
2023/07/13-18:11:33.6853|!ERR] Attempted to read OCMB fieldId 63 on an invalid platform
2023/07/13-18:11:33.6963|!ERR] Max proposed AC ratio resolved to <= 0.
2023/07/13-18:11:33.7174|!ERR] Max proposed AC ratio resolved to <= 0.
XtuService.exe Error: 0 : Exception caught during manifest download - 未能解析此远程名称: 'downloadmirror.intel.com'
2023/07/13-18:11:33.8061|IMP] Initializing MSR Monitoring system
2023/07/13-18:11:33.8061|IMP] MSR Monitoring system Initialized
2023/07/13-18:11:33.8111|IMP] Initializing CPU Monitoring system
2023/07/13-18:11:33.8132|IMP] CPU Monitoring system Initialized
2023/07/13-18:11:33.8362|WARN] Could not Resolve Type Registration IronCity.HardwareAccessInterfaces.IHardwareMonitorAccess(MemoryTimingMonitors)
2023/07/13-18:11:33.8452|WARN] Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "IronCity.HardwareAccessInterfaces.IHardwareMonitorAccess", name = "MemoryTimingMonitors".
Exception occurred while: Calling constructor IronCity.HardwareAccess.MemoryTimingMonitors(IronCity.HardwareAccess.IPlatformInformation , IronCity.HardwareServices.IMchBarService , IronCity.HardwareAccess.ISPDAccess ).
Exception is: InvalidOperationException - 序列不包含任何元素
-----------------------------------------------
At the time of the exception, the container was:

  Resolving IronCity.HardwareAccess.MemoryTimingMonitors,MemoryTimingMonitors (mapped from IronCity.HardwareAccessInterfaces.IHardwareMonitorAccess, MemoryTimingMonitors)
  Calling constructor IronCity.HardwareAccess.MemoryTimingMonitors(IronCity.HardwareAccess.IPlatformInformation , IronCity.HardwareServices.IMchBarService , IronCity.HardwareAccess.ISPDAccess )
 ---> System.InvalidOperationException: 序列不包含任何元素
   在 System.Linq.Enumerable.First[TSource](IEnumerable`1 source)
   在 IronCity.HardwareAccess.MemoryTimingMonitors._eW4BPJe7knYLkD79heYa26E5Cvt()
   在 IronCity.HardwareAccess.MemoryTimingMonitors..ctor(IPlatformInformation , IMchBarService , ISPDAccess )
   在 lambda_method(Closure , IBuilderContext )
   在 Microsoft.Practices.ObjectBuilder2.DynamicBuildPlanGenerationContext.<>c__DisplayClass1.<GetBuildMethod>b__0(IBuilderContext context)
   在 Microsoft.Practices.ObjectBuilder2.BuildPlanStrategy.PreBuildUp(IBuilderContext context)
   在 Microsoft.Practices.ObjectBuilder2.StrategyChain.ExecuteBuildUp(IBuilderContext context)
   在 Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name, IEnumerable`1 resolverOverrides)
   --- 内部异常堆栈跟踪的结尾 ---
   在 Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name, IEnumerable`1 resolverOverrides)
   在 Microsoft.Practices.Unity.UnityContainer.Resolve(Type t, String name, ResolverOverride[] resolverOverrides)
   在 Microsoft.Practices.Unity.UnityContainerExtensions.Resolve[T](IUnityContainer container, String name, ResolverOverride[] overrides)
   在 IronCity.Common.IoC.Resolve[T](String name)
   在 IronCity.Common.IoC.TryResolveAll[T]()
2023/07/13-18:11:33.8452|IMP] Initializing all monitors
2023/07/13-18:11:33.8512|IMP] Starting graphics driver reset event watch
2023/07/13-18:11:33.8512|IMP] Initializing Application Persistence Component
2023/07/13-18:11:33.8512|IMP] Application Persistence Enabled: True
2023/07/13-18:11:33.8512|IMP] Watchdog Failure Status: False
2023/07/13-18:11:33.8512|IMP] ISO Persistence Enabled: False
2023/07/13-18:11:33.8563|IMP] Application Persistence -> Restoring Persisted Settings, Total of 6 Changes
2023/07/13-18:11:33.8613|!ERR] Attempted to read OCMB fieldId 59 on an invalid platform
2023/07/13-18:11:33.8613|!ERR] Attempted to read OCMB fieldId 61 on an invalid platform
2023/07/13-18:11:33.8613|!ERR] Attempted to read OCMB fieldId 63 on an invalid platform
2023/07/13-18:11:33.8663|!ERR] Attempted to read OCMB fieldId 59 on an invalid platform
2023/07/13-18:11:33.8663|!ERR] Attempted to read OCMB fieldId 61 on an invalid platform
2023/07/13-18:11:33.8663|!ERR] Attempted to read OCMB fieldId 63 on an invalid platform
2023/07/13-18:11:33.8663|!ERR] Max proposed AC ratio resolved to <= 0.
2023/07/13-18:11:33.8713|!ERR] Max proposed AC ratio resolved to <= 0.
2023/07/13-18:11:33.8773|IMP] Activating Proposed Changes; ForceReboot = False
2023/07/13-18:11:33.8813|IMP] Core Server Initialized
2023/07/13-18:11:33.9094|IMP] Starting Tuning Remoting Service
2023/07/13-18:11:34.0664|IMP] Starting Monitoring Remoting Service
2023/07/13-18:11:34.0714|IMP] Starting Service Info Remoting Service
2023/07/13-18:11:34.0714|IMP] Starting XTU Events Remoting Service
