Forum Thread: PSI Tray stops working shortly after boot (APPCRASH PSIA.exe)

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
PSI

This thread has been marked as locked.
NewBuild PSI Tray stops working shortly after boot (APPCRASH PSIA.exe)
Member 1st Aug, 2014 17:21
Ranking: 0
Posts: 1
User Since: 1st Aug, 2014
System Score: N/A
Location: UK
I am working with a fresh install of Windows 8.1 64 bit (installed 2 days ago) and of PSI 3.0. PSI 3.0 appears to work fine when executed by double-clicking and shows everything up to date. However, although the tray PSI starts to run fine immediately after booting and shows everything up to date, some error then occurs and it stops working.

This problem shows as an error in the Windows 8.1 Reliability Monitor, with the following technical details:

Description
Faulting Application Path: C:\Program Files (x86)\Secunia\PSI\psia.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: PSIA.exe
Application Version: 3.0.0.9016
Application Timestamp: 52a1d50f
Fault Module Name: ntdll.dll
Fault Module Version: 6.3.9600.17114
Fault Module Timestamp: 53648f36
Exception Code: c0000005
Exception Offset: 0003fcab
OS Version: 6.3.9600.2.0.0.768.101
Locale ID: 2057

Extra information about the problem
Bucket ID: 0cb17d4687f65f58b6510e6265905a2d (73316412333)

I'd welcome any suggestions as I'm not sure how to proceed. Many thanks.

NB. I have made only one change since uninstalling and reinstalling. The desktop PSI shows that Windows Update was not available, because my Windows Update Settings were not set to get updates for other Microsoft products. Once I ticked that box, the Windows Update warning went away. As far as I know, this change has not affected the crashing behaviour of the tray icon, which existed both before and after.

No one has replied to this thread yet - be the first
This thread has been marked as locked.