DaveLessnau
I don't know if this will carry over to this new version, but Precision X1 0.4.9.0 did not find this update.  I've got Check Updates set to On Startup Daily, it shows Last Checked to be this morning, and I got no notification or any other update available activity.

Same here, on my PC. Strange thing was, on my wife's PC, it did find the update and even downloaded the new installer itself.

I'm going to have to revert back to the previous version for now as the CPU usage is very high, almost 5%.

Previous versions it was close to 2% which was enough to effect benchmarks and games negatively.  I got around this by exiting Precision and using another program for my fan profile (which is a shame because I'd like to use Precision's fan control) but there seems to be another bug in this build, the power target doesn't stick when I close precision.

Deders
I'm going to have to revert back to the previous version for now as the CPU usage is very high, almost 5%.

Previous versions it was close to 2% which was enough to effect benchmarks and games negatively.  I got around this by exiting Precision and using another program for my fan profile (which is a shame because I'd like to use Precision's fan control) but there seems to be another bug in this build, the power target doesn't stick when I close precision.

Very strange ... definitely not normal ... what PX1 features do you have turned on (OSD? HWM?).  May I ask what CPU you have?

thunder-93
 
Very strange ... definitely not normal ... what PX1 features do you have turned on (OSD? HWM?).  May I ask what CPU you have?

kacan22
 
I happy that im not alone with high cpu problem cos nobody even talks about it :(. I contacted EVGA support and guy wrote few emails back but seems they dont have these problems on their computers. He asked me for dxdiag and logs. You should provide same so they will fix it faster (i hope).

I've added a signature with my spec.  

So a little background, I decided it was time for a fresh install as my new EVGA 2080 FTW3 was arriving soon and I hadn't done one in ages, it was about time things were getting a bit messy and not working as expected.

It's worth noting that windows handles upgrades slightly differently from fresh installs.  For instance when you upgrade from win7,  for compatibilities sake it will run a lot of your old win7 drivers in compatibility mode which incurs a lot of latency as the processes pass through the compatibility layers, but at least people are up and running with minimal fuss.  I have a feeling this approach also applies to other parts of windows when upgrading to a newer build of windows 10 as opposed to a fresh install, so someone testing on a machine that has just done the upgrade might not have the same experience as someone who has done a fresh install.  E.g. the upgrade path will transition what you already have, but the fresh install will start afresh.

It doesn't help that Microsoft have moved to testing their builds on virtual machines instead of actual PC's so they can't catch as many issues before release.

I only noticed high (around 2%) CPU usage in some apps that reside in the tray like Afterburner, antivirus, LGBridge (Phone app) Steam, Argus Monitor (monitoring and fan control) ExperTool (Gainward's overclocking tool for my old 1080) etc after installing a fresh copy of the latest windows onto my machine.  Up until now, on windows 98/2000/XP/Vista/7 and previous versions of 10, the most I've had to worry about is about 0.1%.  All these added up to just over 10%.

I have managed to resolve a lot of these.  Currently the only things that have any real impact are Afterburner which I use to send realtime performance graphs to the screen on my keyboard (I'm happy to sacrifice 0.7% of my CPU for that), and PrecisionX which as I mentioned older versions use around 2% on their own, which when I tested was enough to impact benchmark scores and game performance.

The new version is at 5%, I have disabled all the extra features.  OSD, HWM, LED Sync (not even installed) and Boost clock.  I'm also having trouble saving my power target when I exit.  Do people from EVGA read these forums?

The way I fixed the original 10% was by installing the latest Intel Management Engine drivers from my motherboard's website.  I had always installed it before, but for some reason got it into my head that it was just firmware that was already installed on my motherboard.  It definitely isn't.

I also disabled all the unnecessary sensor probes in MSI Afterburner which took its CPU usage down a bit.

The rest was resolved by windows updates.

Edit: I should probably mention the only time I used to see CPU usage in system tray icons before in win10 was after waking from sleep, but that would go away after a restart.

Nattz
Which version is currently the best? Previous posts suggested that it's 0.3.17?

The newest most current version is at the first post of this thread and or in the title of this thread.  X1 1.0.0.0

1.0.0.0 either died at startup this morning or shortly thereafter.  From Reliability Monitor:
 
"Source
Precision X1

Summary
Stopped working

Date
‎10/‎9/‎2019 6:34 AM

Status
Report sent

Description
Faulting Application Path:    C:\Program Files\EVGA\Precision X1\PrecisionX_x64.exe

Problem signature
Problem Event Name:    CLR20r3
Problem Signature 01:    PrecisionX_x64.exe
Problem Signature 02:    1.0.0.0
Problem Signature 03:    5d818e9f
Problem Signature 04:    mscorlib
Problem Signature 05:    4.8.4018.0
Problem Signature 06:    5d4a6683
Problem Signature 07:    168f
Problem Signature 08:    fd
Problem Signature 09:    System.Windows.Markup.XamlParse
OS Version:    10.0.18362.2.0.0.256.48
Locale ID:    1033
Additional Information 1:    14d3
Additional Information 2:    14d33c21c24aac20b126b0e5ae485d94
Additional Information 3:    07f3
Additional Information 4:    07f3c1debc277f23c12aed697d91e15c

Extra information about the problem
Bucket ID:    88e91189c39ac4a5ceb87bc04118b948 (2213655282508675400)"

and from Event Viewer:
 
"Log Name:      Application
Source:        Application Error
Date:          10/9/2019 6:34:50 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      WIN10-DAVE
Description:
Faulting application name: PrecisionX_x64.exe, version: 1.0.0.0, time stamp: 0x5d818e9f
Faulting module name: KERNELBASE.dll, version: 10.0.18362.418, time stamp: 0xfba22159
Exception code: 0xe0434352
Fault offset: 0x000000000003a839
Faulting process id: 0xba4
Faulting application start time: 0x01d57ea6457ff2bf
Faulting application path: C:\Program Files\EVGA\Precision X1\PrecisionX_x64.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: dbea4043-554e-43fc-8243-b214a3e72fed
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-10-09T13:34:50.234926800Z" />
    <EventRecordID>6655</EventRecordID>
    <Channel>Application</Channel>
    <Computer>WIN10-DAVE</Computer>
    <Security />
  </System>
  <EventData>
    <Data>PrecisionX_x64.exe</Data>
    <Data>1.0.0.0</Data>
    <Data>5d818e9f</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>10.0.18362.418</Data>
    <Data>fba22159</Data>
    <Data>e0434352</Data>
    <Data>000000000003a839</Data>
    <Data>ba4</Data>
    <Data>01d57ea6457ff2bf</Data>
    <Data>C:\Program Files\EVGA\Precision X1\PrecisionX_x64.exe</Data>
    <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
    <Data>dbea4043-554e-43fc-8243-b214a3e72fed</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>"
 
and
 
"Log Name:      Application
Source:        .NET Runtime
Date:          10/9/2019 6:34:50 AM
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      WIN10-DAVE
Description:
Application: PrecisionX_x64.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.DirectoryNotFoundException
   at System.IO.__Error.WinIOError(Int32, System.String)
   at System.IO.Directory.InternalCreateDirectory(System.String, System.String, System.Object, Boolean)
   at System.IO.Directory.InternalCreateDirectoryHelper(System.String, Boolean)
   at PX18.ViewModel.GeneralVM.initialScreenCapture()

Exception Info: System.Windows.Markup.XamlParseException
   at System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri)
   at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
   at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
   at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
   at PX18.View.MainWindow..ctor()
   at PX18.App.App_Startup(System.Object, System.Windows.StartupEventArgs)
   at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
   at System.Windows.Application.<.ctor>b__1_0(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at PX18.App.Main()
   at PX18.Program.Main()


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-10-09T13:34:50.068926800Z" />
    <EventRecordID>6654</EventRecordID>
    <Channel>Application</Channel>
    <Computer>WIN10-DAVE</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: PrecisionX_x64.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.DirectoryNotFoundException
   at System.IO.__Error.WinIOError(Int32, System.String)
   at System.IO.Directory.InternalCreateDirectory(System.String, System.String, System.Object, Boolean)
   at System.IO.Directory.InternalCreateDirectoryHelper(System.String, Boolean)
   at PX18.ViewModel.GeneralVM.initialScreenCapture()

Exception Info: System.Windows.Markup.XamlParseException
   at System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri)
   at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
   at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
   at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
   at PX18.View.MainWindow..ctor()
   at PX18.App.App_Startup(System.Object, System.Windows.StartupEventArgs)
   at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
   at System.Windows.Application.&lt;.ctor&gt;b__1_0(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at PX18.App.Main()
   at PX18.Program.Main()

</Data>
  </EventData>
</Event>"

rsabatino
hey is there a way to change the size of the numbers for GPU temp... I have them in the system tray before I was able to see them but now they or way too small.

Check this out.  Hope it helps.

The new 4 digit taskbar temp is way too small to see. Especially as I only need 2 digits (can this be toggled back to how it used to be?)
I've never been able to view temp info on my keyboard LCD (G19s), has LCD worked for anyone?
 
The previous issues with not launching on startup etc. have been resolved with this new version.
Hoping that the next version can fix the 2 issues I mentioned above, and it'll be perfect (for me at least).

Still crashes my games.