xtortingThe update server is crashing the 1.0.7 version every time. If you have yours set to auto check for updates, it will eventually crash and brick itself shut down. Unable to open the application again. Because everytime X1 opens it is checking for updates.
AlacrityFI rather think the update crash problem has something to do with the new RTX 30 fork in the code. They added a digit to the version number; PX1 can't parse it so it crashes. Just a theory.
Application: PrecisionX_x64.exeFramework Version: v4.0.30319Description: The process was terminated due to an unhandled exception.Exception Info: System.IndexOutOfRangeException at PX18.ViewModel.GeneralVM.isNewVersion() at PX18.ViewModel.GeneralVM+<CheckNowAsync>d__73.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at PX18.ViewModel.GeneralVM+<initialUpdate>d__36.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 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()
xtortingToday I found EVGA Precision X1 1.0.7 was crashing every time I tried to open it. I tried everything, uninstall and reinstall. Nothing was working. The system file was not able to be fully deleted. Everytime I tried to download the application from the website, the download would break 10% through because the file could not be removed. "Another application is using the file." Even after I uninstalled the application, the system file was blocking the ability for a new clean version. How to remove the application from using this system file: First, try to remove everything to trash bin from the folder EVGA Precision is in. A system file could be left over because another application is using it. Second, drag the system file to the desktop. Three, begin a new install from EVGA website. Four, after install is completed you can move the old system file from the desktop to the trash bin. Five, empty trash bin. Total mess. What I ended up finding out is quite shocking. The update server revolving around the Precision X1 22.214.171.124 is corrupting the older version of Precision X1 to the point of crashing. After a clean install, try to check for updates. The update server is crashing the 1.0.7 version every time. If you have yours set to auto check for updates, it will eventually crash and brick itself shut down. Unable to open the application again. Because everytime X1 opens it is checking for updates. X1 connects to the update server, the application crashes and bricks itself until the setting is changed to "Never." The only way it will not brick itself over and over again is by having "check for updates?" turned to "Never." How to unbrick Precision x1: First, follow the steps above for a clean install. Second, go to settings and and make sure the check for update setting is turned to never. If the setting is set to daily, the application will connect to the update server and crash until you follow these steps again. Hope this helps. What a pain.
# Bug Report## What is happening?Precision X1 crashes when checking for updates. If automatic updates are configured, Precision X1 may crash immediately after the app is loaded. ## What should happen — i.e., what is the behavior the user expects?Precision X1 should inform the user if updates are available after checking for updates. ### System information<Your CPU model><Your GPU model><Add Windows 10 info vYYMM (BUILD #)>Precision X1 v1.0.7 ## Steps to reproduce1. Open Precision X1.2. Open the “setup” menu.3. Under “General” → “Last Checked” menu, press the “Check now” button.4. Precision X1 will unexpectedly quit.
battleskardIts crashing for me as well. Is there a update fix coming from EVGa?
tc006I ended up filing a formal bug report with EVGA support about the “crash when checking for updates“ with v1.0.x of Precision X1, so EVGA is aware of the issue.EVGA support asked me to install the v1.1 feature upgrade for Precision X1 and determine whether v1.1 is also affected — and v1.1 is not affected.As I write this post, EVGA released Precision X1 v126.96.36.199 and added support for my 20-series GPU — so installing the v1.1 feature upgrade solves my issue. For folks whose GPUs are not yet supported by the Precision X1 v1.1 feature update, I’d recommend contacting EVGA technical support via e-mail at email@example.com;EVGA might raise the priority of investigating and fixing this crash in Precision X1 based on how many support requests they receive.For anyone interested, I‘m including a bug report template you can use when beginning a conversation with EVGA tech support:[code]# Bug Report