Today 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 1.1.0.9 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. 

xtorting
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. 

@xtorting — Thanks for figuring out and sharing the failure mode causing Precision X1 v1.0.7 to crash!
 
In addition to xtorting's fix, here are two (2) other ways to correct Precision X1 crashing @ startup if auto-updates are enabled:

1. Disconnect your machine from the Internet and reconfigure Precision X1:
   1. Unplug Ethernet and disconnect from any wireless networks.
   2. Launch Precision X1;
      • ℹ  You can ignore the warning message that Precision X1 can not reach evga.com.
   3. Open the settings and change updates to "never".
   4. Press Apply and then press Save.
   5. Quit Precision X1 (since the configuration file is saved to disk when Precision X1 exits).
   6. Reconnect to the Internet.
   7. Launch Precision X1.
2. Manually edit your Precision X1 configuration file to never check for updates:
   1. Open %LocalAppData%\EVGA_Co.,_Ltd\PrecisionX_x64.exe_Url_vrvasebqwl5wesi2q3tshmshuzsvqfah\1.0.7.0\user.config with your text editor of choice.
      • ℹ   The config file location may slightly differ based on which CPU architecture you have. In general, you'll find the config file somewhere inside %LocalAppData%\EVGA_Co.,_Ltd\.
   2. Find the setting node named, "General_UpdateType" and change it's value to 0 — i.e., the numeric value zero.
   3. Save the user.config file.
   4. Launch Precision X1.

I set my updates to never, click "check now" every so often just to keep it upto date, I can confirm mine crashes as well when clicking that button now, if I do click it I have to launch the program again with the added bonus of reconfiguring my settings as they don't save after the update crash.
 
My friend who recommended this program to me had his set to auto & its been crashing his everytime, the fix...same as above, uninstall, clean what was left, re-install, reconfigure his settings.
 
Update crash, pure geniuses at work!
 
 

I can confirm - this worked... simpler for me though: I never had to reconfigure/reinstall anything other than do the following.
 
1) Disconnect from your wifi/network - (I just disconnected from wifi but easiest way besides unplugging a network cable is to just disable the network device through control panel temporarily)
2) Open x1 and you will see an error message saying it can't resolve the host, click OK
3) once X1 loads the normal screen - click the gear in the top right (setup)
4) on the left column under "general" there is a drop down box labeled "Check updates" set this to "never". Then save.
5) reconnect to your wifi/network
 
This EVGA, is a perfect example of what NOT to do!! Make sure your IT guys talk with your software engineers.  This is a F'n STUPID problem to have EVGA.

Its crashing for me as well.  Is there a update fix coming from EVGa?

I 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.

AlacrityF
I 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.

 
Very possible. Definitely too much of a coincidence right at the release of the 3000 version. Here is the full error but I don't see anything particularly interesting in there.
 

Application: PrecisionX_x64.exe
Framework Version: v4.0.30319
Description: 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()

xtorting
Today 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 1.1.0.9 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. 

Well that be the problem right there, yes sir, Dean Cain Sir...  LoL.  Last week this issue hit my computer.  Sadly, the error for me happened exactly after I updated to the new driver on the 7th so I just chalked it up to driver issues with precision x1.  DDU old drivers and in came the new one.  Then x1 refused to start no matter what I did.  This problem along with a MSI mobo driver issue led me to doing clean install.  On the plus side though comcast came through. They finally upgraded our hi-speed capabilities from a max 25Mbps to Gigabit in this raggedy, bass-ackwards living community with neighbors looking like they were plucked right out of the movie "Wrong Turn" type of town. Before I would truly hate having to do a clean install, but now the time it takes the download to finish is on par with the time the 970 Pro NVMe takes to install it.  
 
Thank you for this straight to the point answer.  I just tried to reinstall EVGA and one i changed those settings on getting it to start-up minimized and then checking updates weekly, like you said it is "NO BUENO".  Have a good one!

well that all sounds familiar,.. I had no issue with 1.0.4,prior to june2020, But I did have this issue with version 1.0.6 so I upgraded to 1.0. 7 problem still there, manual rip-out of old. review and clean reg. and remove folders,-reboot- verify clean/ clean install, whenever I hit update, program CTD. I have it set to never so I have no issues launching it again. but this isn't new to v .7-Nvidia driver =456.55/456.71[Evga1660XC](also all antivirus was disabled during any and all tests/installs)
windows 10 Pro,2004/build19041.508 with feature pack 120.2212.31.0(I was Leaning towards a driver/KB issue){Exception code: 0xe0434352}
So I would have to agree the update server is more the problem as manually this all installs and works fine.
FYI
Jammer
Jammersweb.com

I 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 v1.1.0.11 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 support@evga.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:

# 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 reproduce
1. 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.

 
Hopefully, EVGA will add support for additional GPUs into the Precision X1 v1.1 feature update soon!