Captain_Johnny
-
Posts
6 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Captain_Johnny
-
-
Hi John, thanks for letting me know - I uploaded the file through here and received the positives this way:
https://www.virustotal.com/gui/home/upload -
Hi, I'm getting this virus warning upon downloading the new FSUPIC v7.5.0 (FortinetMalicious_Behavior.SB) - can you please advise further, thanks?
-
3 minutes ago, John Dowson said:
Yes - only log files from the current and previous sessions are available.
No need to post it unless FSUIPC actually crashed. As I said, it was most likely an exception due to the MSFS crash, and then FSUIPC7 would exit gracefully. Just look at your log file to confirm this, and only post it crashed, i.e. no closing log statements, like the following:
John
Got it, thanks John, wilco :).
-
On 10/6/2024 at 9:41 PM, John Dowson said:
That shows an exception in FSUIPC - did FSUIPC7 crash? Can you please show me/attach your FSUIPC7.log file from when it crashed.
If MSFS CTD'ed, are there any windows events for this? If FSUIPC7 CTDs, this should not affect MSFS in any way, as it is a separate app.
If MSFS CTDs, this can cause exceptions in FSUIPC7 (which will be reported in the windows events), but FSUIPC7 should handle this gracefully, and usually exits as it detects that MSFS is no longer running. Your log file would show if this is what is happening.John
Hi John, thanks for helping out. I can't recall if FSUIPC actually crashed or not. When I look at the FSUIPC log files, it seems I only have the current day and previous session log file available - so I'll have to wait until it happens again and save that file then post it here for you to take a look if you're able, thanks.
-
Interesting - I have almost the same setup ... running GSX, Fenix A320 and MobiFlight.
When I've been flying online with VATSIM using vPilot, and within the last 5 or 10 min of the flight (approaching the circuit area) my MSFS CTD. Unless coincidentally, it often happens when I go to adjust the HDG knob.
The reason I query FSUIPC as a possible culprit, is because when I go to Windows Event Logs (Windows+X keys / Event Viewer), and I look for the MSFS CTD, it says the cause of the CTD was FSUIPC (in each instance of this happening).
CTD Data excerpt from Windows logs:
Faulting application name: FSUIPC7.exe, version: 7.4.1.7, time stamp: 0x66d82cd2
Faulting module name: ntdll.dll, version: 10.0.22621.4111, time stamp: 0x518e67bb
Exception code: 0xc0000005
Fault offset: 0x0000000000033faa
Faulting process id: 0x0x120AC
Faulting application start time: 0x0x1DB0D9DC187A81D
Faulting application path: C:\FSUIPC7\FSUIPC7.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 931a5ee7-576a-49ed-b33c-a98b6e5734ea
Faulting package full name:
Faulting package-relative application ID:Are you able to please offer any assistance, thanks?
v7.5.0 potential virus warning? - Fortinet Malicious_Behavior.SB
in FSUIPC7 MSFS
Posted
OK thanks again John.