EVGA

AnsweredHot!PX1 1.0.x.0 Won't Automatically Start with Windows [SOLVED AGAIN?]

Author
DaveLessnau
New Member
  • Total Posts : 67
  • Reward points : 0
  • Joined: 2012/11/05 20:22:08
  • Status: offline
  • Ribbons : 1
2019/10/26 08:54:20 (permalink)
I just did a Fresh Start re-install of Windows 10 Professional x64.  Precision X1 1.0.1.0 won't autostart when I boot even though all the boxes are checked to do so in Setup.  I'm even having issues where it won't manually start, but I just uninstalled/re-installed it and it didn't happen this time.  It does tend to autostart if I just sign out/sign in instead of Restart or Shut Down. Before I head back to MSI Afterburner again (I REALLY want to use Precision X1 so I can control that second fan on my EVGA GeForce GTX 1080 FTW2), I wanted to post any data I have on the problem.  So, from my last boot:
 
Here's the information from Security and Maintenance > Reliability Monitor:
 
"Source
Precision X1

Summary
Stopped working

Date
‎10/‎26/‎2019 8:33 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.1.0
Problem Signature 03:    5da6e49e
Problem Signature 04:    mscorlib
Problem Signature 05:    4.8.4042.0
Problem Signature 06:    5d7a9e97
Problem Signature 07:    1692
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:    6a67
Additional Information 4:    6a67d1f6f5cd30db1f4d08bcaba41e51

Extra information about the problem
Bucket ID:    8fe5fb265bab2be43f6b854cab01a74c (2264049802016827212)"

From Event Viewer:
 
"Log Name:      Application
Source:        Application Error
Date:          10/26/2019 8:33:45 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.1.0, time stamp: 0x5da6e49e
Faulting module name: KERNELBASE.dll, version: 10.0.18362.449, time stamp: 0x2bdaa583
Exception code: 0xe0434352
Fault offset: 0x000000000003a839
Faulting process id: 0x780
Faulting application start time: 0x01d58c12bb9db928
Faulting application path: C:\Program Files\EVGA\Precision X1\PrecisionX_x64.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 42a8ca1f-2547-485a-b269-83240d166a15
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-26T15:33:45.799737900Z" />
    <EventRecordID>1777</EventRecordID>
    <Channel>Application</Channel>
    <Computer>WIN10-DAVE</Computer>
    <Security />
  </System>
  <EventData>
    <Data>PrecisionX_x64.exe</Data>
    <Data>1.0.1.0</Data>
    <Data>5da6e49e</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>10.0.18362.449</Data>
    <Data>2bdaa583</Data>
    <Data>e0434352</Data>
    <Data>000000000003a839</Data>
    <Data>780</Data>
    <Data>01d58c12bb9db928</Data>
    <Data>C:\Program Files\EVGA\Precision X1\PrecisionX_x64.exe</Data>
    <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
    <Data>42a8ca1f-2547-485a-b269-83240d166a15</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>"

 
and
 
"Log Name:      Application
Source:        .NET Runtime
Date:          10/26/2019 8:33:45 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-26T15:33:45.720986900Z" />
    <EventRecordID>1776</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>"

post edited by DaveLessnau - 2019/11/09 16:12:32


#1
Cool GTX
EVGA Forum Moderator
  • Total Posts : 18624
  • Reward points : 0
  • Joined: 2010/12/12 14:22:25
  • Location: Folding for the Greater Good
  • Status: online
  • Ribbons : 114
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/10/27 19:03:50 (permalink)
"Run As admin" & give X1 elevated privileges
 
Did you try everything listed in this ? How Do I Troubleshoot Precision X1 Issues?
 
Good info in this thread:  why doesnt Percision x1 boot on start up after latest update

RTX Project EVGA X99 FTWK-5930K,EVGA2080Ti EVGA-1200P2  Nibbler EVGA X99 3-GPU Water Loop 1600P2  AIO Folding  1080Ti FTW3 Hybrid, 1200P
Thank You for Your Support


#2
bob16314
CLASSIFIED ULTRA Member
  • Total Posts : 5996
  • Reward points : 0
  • Joined: 2008/11/07 22:33:22
  • Location: Planet of the Babes
  • Status: online
  • Ribbons : 471
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/10/27 23:34:23 (permalink)
Yep, this ^^^
 
It's been an ongoing Precision issue with Win10 Pro, I assume due to the extra elevated security measures it has..Along with Run as administrator, right-click on Precision..Then Properties..Then edit to give all users full control in the Security tab and see how any or all that rolls.

* Corsair Obsidian 450D Mid-Tower - Airflow Edition * ASUS ROG Maximus X Hero (Wi-Fi AC) * Intel i7-8700K @ 5.2GHz * 16GB G.SKILL Trident Z 4000MHz * Crucial MX500 M.2 1TB * WD Black 500GB (x2) * Seasonic M12 II 750W * Corsair H80i V2 * EVGA GTX 760 SC * Dual-Boot Win7 Home 64-bit/Win10 Home 64-bit * 
 
Confucius say "He who has the most guns wins"
 
 
 
#3
DaveLessnau
New Member
  • Total Posts : 67
  • Reward points : 0
  • Joined: 2012/11/05 20:22:08
  • Status: offline
  • Ribbons : 1
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/10/28 20:03:44 (permalink) ☼ Best Answerby Cool GTX 2019/10/30 09:35:55
EDIT:  Nope.  It turns out my post here did NOT solve the problem.  See further down the thread for something else that appears to be working.
_______________
OP:  I had uninstalled PX1 and re-installed MSI Afterburner.  But, I ran across something that indicated "Virtualization Based Security" (VBS) was enabled on this computer (here's a link to the Windows Feedback Hub item I created for it):
 
https://aka.ms/AA6evlj
 
Anyway, after I managed to disable that, I re-installed PX1.  So far, it's auto-starting just fine (even without Run as Administrator).  I'm guessing that VBS was doing bad things to PX1 and that it's turned on for some reason with the latest 1903 Cumulative Updates.
 
EDIT:  and for those who want to see the VBS issue but don't want (or have) the Windows 10 Feedback Hub necessary to view the above link, here's a copy of the text:
 
"AMD Ryzen Master Suddenly Can't Run Because of Virtualization Based Security
A couple of days ago, AMD's Ryzen Master ran fine on my system.  Today, when I tried to run it, it came back with:

"Ryzen Master can only run with Virtualization Based Security (VBS) disabled in the Windows operating system.  Please disable VBS and re-start Ryzen Master."

Well, I have no idea what VBS is or how it got turned on.  I've been searching the internet for the last hour and have found things to turn VBS and the associated Credential Guard off.  But, according to my system, none of that is turned on in the first place.  I'm assuming this is caused by the recent 1903 Cumulative Updates (KB4522355) which hit my system over the last couple of days.  Please fix whatever is causing this or at least update documents somewhere on how to turn VBS off on a system where it's theoretically not on.
 
[LATER] Figured out how to disable this (I have no idea if that's good or bad since I'd never heard of VBS or Credential Guard before this problem popped up.  I went to:

https://www.microsoft.com.../details.aspx?id=53337

and downloaded their Device Guard and Credential Guard Hardware Readiness Tool (just search for that tool and restrict yourself to Microsoft sites if you don't trust the link). I ran that Powershell script with -Ready to confirm nothing was on.  Then ran it with -Disable where it didn't find anything to do.  But, after the prompted reboot, it asked me to opt out of Credential Guard and VBS (which I agreed to).  I can now run AMD Ryzen Master.

Microsoft needs another document explaining all this and the ramifications of it (one way or another)."
post edited by DaveLessnau - 2019/11/09 17:44:12


#4
bob16314
CLASSIFIED ULTRA Member
  • Total Posts : 5996
  • Reward points : 0
  • Joined: 2008/11/07 22:33:22
  • Location: Planet of the Babes
  • Status: online
  • Ribbons : 471
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/10/28 20:16:29 (permalink)
Well, that's exceptionally cool..Maybe that's the problem so many people are having with Precision starting on Win10 Pro..Thanks for that info  

* Corsair Obsidian 450D Mid-Tower - Airflow Edition * ASUS ROG Maximus X Hero (Wi-Fi AC) * Intel i7-8700K @ 5.2GHz * 16GB G.SKILL Trident Z 4000MHz * Crucial MX500 M.2 1TB * WD Black 500GB (x2) * Seasonic M12 II 750W * Corsair H80i V2 * EVGA GTX 760 SC * Dual-Boot Win7 Home 64-bit/Win10 Home 64-bit * 
 
Confucius say "He who has the most guns wins"
 
 
 
#5
DaveLessnau
New Member
  • Total Posts : 67
  • Reward points : 0
  • Joined: 2012/11/05 20:22:08
  • Status: offline
  • Ribbons : 1
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/10/29 06:27:37 (permalink)
It could be mere coincidence.  But, it sure feels like that was the problem. I'd really liked to have had the additional security of those things (Virtualization Based Security and Credential Guard).  But, I need to run Ryzen Master and it just won't run with that active (and tells me that).  The trouble with it possibly being related to PX1 not wanting to start is that it's just a possibility.  I'd hate for people to turn off a security feature if that's not what's causing the problem.


#6
Cool GTX
EVGA Forum Moderator
  • Total Posts : 18624
  • Reward points : 0
  • Joined: 2010/12/12 14:22:25
  • Location: Folding for the Greater Good
  • Status: online
  • Ribbons : 114
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/10/30 09:37:20 (permalink)
Give an update in about a Week and tell us if it has remained Functional ---> through Several Cold Reboots

RTX Project EVGA X99 FTWK-5930K,EVGA2080Ti EVGA-1200P2  Nibbler EVGA X99 3-GPU Water Loop 1600P2  AIO Folding  1080Ti FTW3 Hybrid, 1200P
Thank You for Your Support


#7
bob16314
CLASSIFIED ULTRA Member
  • Total Posts : 5996
  • Reward points : 0
  • Joined: 2008/11/07 22:33:22
  • Location: Planet of the Babes
  • Status: online
  • Ribbons : 471
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/10/30 09:44:29 (permalink)
Cool GTX
Give an update in about a Week and tell us if it has remained Functional ---> through Several Cold Reboots



For sure.

* Corsair Obsidian 450D Mid-Tower - Airflow Edition * ASUS ROG Maximus X Hero (Wi-Fi AC) * Intel i7-8700K @ 5.2GHz * 16GB G.SKILL Trident Z 4000MHz * Crucial MX500 M.2 1TB * WD Black 500GB (x2) * Seasonic M12 II 750W * Corsair H80i V2 * EVGA GTX 760 SC * Dual-Boot Win7 Home 64-bit/Win10 Home 64-bit * 
 
Confucius say "He who has the most guns wins"
 
 
 
#8
DaveLessnau
New Member
  • Total Posts : 67
  • Reward points : 0
  • Joined: 2012/11/05 20:22:08
  • Status: offline
  • Ribbons : 1
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/10/30 10:14:24 (permalink)
So far, everything's still working.  This is a new system, so I've been rebooting (both cold and warm) many times while testing things and setting my fan curves in the BIOS.  I also see that there's a new version of PX1 out.  So, I'll wait for it to tell me about it (usually takes almost a week) and have it install the new version over itself.  I'll report back then.


#9
Sajin
EVGA Forum Moderator
  • Total Posts : 39070
  • Reward points : 0
  • Joined: 2010/06/07 21:11:51
  • Location: Texas, USA.
  • Status: offline
  • Ribbons : 195
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/10/30 10:43:49 (permalink)
Interesting. Gotta love when windows updates make things on your pc not work correctly.

Want to save 5 to 10% on your next EVGA purchase? Just click on the associates banner to save, or enter the associates code at checkout on your next purchase. If you choose to use my code I want to personally say "Thank You" for using it.
 

 
#10
DaveLessnau
New Member
  • Total Posts : 67
  • Reward points : 0
  • Joined: 2012/11/05 20:22:08
  • Status: offline
  • Ribbons : 1
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/11/09 06:58:44 (permalink)
Sorry it took so long to report back on this.  PX1 dropped my setting to check for updates.  I caught that yesterday, added it back in, and this morning it prompted me to update to 1.0.2.0..  Anyway, nope.  My supposed fix looks like it was just a fluke.  I'm back to the behavior of it not only refusing to Autostart, but refusing to start at all.  Same errors.  I'll fight with this some more and go through the standard stuff to see if I can get this thing running.


#11
Cool GTX
EVGA Forum Moderator
  • Total Posts : 18624
  • Reward points : 0
  • Joined: 2010/12/12 14:22:25
  • Location: Folding for the Greater Good
  • Status: online
  • Ribbons : 114
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/11/09 07:30:59 (permalink)
Thanks for the update
 
Its never a good idea to update just because there is a new version; unless the update addresses a functionality issue or security issue
 
That is why I'm still using version 0.2.9.0 of X1
 
"If it works, don't fix it" is the mind set

RTX Project EVGA X99 FTWK-5930K,EVGA2080Ti EVGA-1200P2  Nibbler EVGA X99 3-GPU Water Loop 1600P2  AIO Folding  1080Ti FTW3 Hybrid, 1200P
Thank You for Your Support


#12
DaveLessnau
New Member
  • Total Posts : 67
  • Reward points : 0
  • Joined: 2012/11/05 20:22:08
  • Status: offline
  • Ribbons : 1
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/11/09 08:14:39 (permalink)
Here's what I found:
  1. Reboot Windows after updating to 1.0.2.0.  PX1 won't Autostart and won't manually start.  Throws the errors noted, above.
  2. Sign Out and Sign In to Windows instead of rebooting and PX1 Autostarts just fine and sits there looking at me and saying "what's the problem?"
  3. Reboot and PX1 won't Autostart.
  4. Go to Task Manager > Startup and disable everything there.  Reboot, and PX1 won't Autostart.  OK.  It's not Task Manager stuff.
  5. Go to MSConfig.exe > Services, Hide All Microsoft Services, then disable everything else.  Reboot, and PX1 Autostarts.  Yay!  It must be something in MSConfig.
  6. MSConfig and re-enable half my services.  Reboot, and PX1 Autostarts. Hmm.  Not that half.
  7. MSConfig and re-enable all but Steam.  Reboot, and PX1 Autostarts.  Hmm.  Must be Steam.
  8. MSConfig and re-enable all my services.  Reboot, and PX1 Autostarts.  Sigh.  Now, it must NOT be something in MSConfig.
  9. Back to Task Manager, re-enable all startup stuff.  Reboot, and PX1 won't Autostart.  Sigh, again.  Now, it's Task Manager stuff?  Let's check MSConfig just to see.
  10. Back to MSConfig, disable all my services.  Reboot, and PX1 Autostarts.  MSConfig stuff again?
  11. MSConfig, re-enable all my services.  Reboot, and PX1 Autostarts.  Throw up my hands in disgust.
As far as I can tell, PX1 Autostarts (or manually starts) whenever it darn well feels like it.  It's not an Intel/AMD/Hardware thing because I had Autostart problems with my old Intel system as well as with this AMD one.  It's not a conflict with various startup things (as seen from above).  Maybe it's a timing thing.  But, that wouldn't explain why if it won't Autostart it also won't manually start.
 
And, just for giggles, here's what's in my Task Manager > Startup tab:
  • EpicGamesLauncher
  • GOG Galaxy
  • googledrivesync.exe
  • KeePass
  • KeePass
  • SpiderOakONE Client Application
  • Steam Client Bootstrapper
  • Windows Security Notification Icon
  • Xbox App Services
  • Xbox Autostart
And, my MSConfig > Services tab:
  • Adobe Acrobat Update Service
  • GalaxyClientService
  • GalaxyCommunication
  • Google Chrome Elevation service
  • Google Update Service (gupdate)
  • Google Update Service (gupdatem)
  • Mozilla Maintenance Service
  • NVIDIA LocalSystem Container
  • NVIDIA NetworkService Container
  • NVIDIA Display Container LS
  • Steam Client Service


#13
DaveLessnau
New Member
  • Total Posts : 67
  • Reward points : 0
  • Joined: 2012/11/05 20:22:08
  • Status: offline
  • Ribbons : 1
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/11/09 16:12:05 (permalink)
I have another possible solution.  Going back to the Event Viewer entry for the .NET Runtime error that comes up when PX1 won't launch, I see this:
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()

Noting the DirectoryNotFoundException and the initialScreenCapture lines, I remembered that I'd changed my screen capture location in PX1 to a directory on my NAS.  BUT, Windows has a tendency to fail to find that NAS on boot because it won't wait for the network to be available.  I've also had applications that flat-out refuse to use their version of a file manager to see the NAS even if Windows sees it fine.  So, I changed the PX1 screen capture location back to its default value (I think) on the C: drive (C:\Users\[username]\Pictures\Screenshots).  So, far PX1 seems happy and is Autostarting.  It could be another false sense of optimism.  But, we'll see.
 
If anyone else is having this problem and has also changed their screenshot location to a non-local folder, please let me know if changing it back to a local folder fixes this.
post edited by DaveLessnau - 2019/11/09 17:48:10


#14
DaveLessnau
New Member
  • Total Posts : 67
  • Reward points : 0
  • Joined: 2012/11/05 20:22:08
  • Status: offline
  • Ribbons : 1
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/11/11 07:21:03 (permalink)
I've warm/cold rebooted about a dozen times over the last couple of days and PX1 is still Autostarting just fine.  So, I'll say that changing the screen save location to a local drive is the solution.  This time, for sure!


#15
Sajin
EVGA Forum Moderator
  • Total Posts : 39070
  • Reward points : 0
  • Joined: 2010/06/07 21:11:51
  • Location: Texas, USA.
  • Status: offline
  • Ribbons : 195
Re: PX1 1.0.1.0 Won't Automatically Start with Windows 2019/11/11 13:54:47 (permalink)
DaveLessnau
I've warm/cold rebooted about a dozen times over the last couple of days and PX1 is still Autostarting just fine.  So, I'll say that changing the screen save location to a local drive is the solution.  This time, for sure!




Want to save 5 to 10% on your next EVGA purchase? Just click on the associates banner to save, or enter the associates code at checkout on your next purchase. If you choose to use my code I want to personally say "Thank You" for using it.
 

 
#16
Jump to:
  • Back to Mobile