Jump to content
The simFlight Network Forums

Captain_Johnny

Members
  • Posts

    6
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Melbourne, Australia

Captain_Johnny's Achievements

Newbie

Newbie (1/14)

  • Conversation Starter Rare
  • Week One Done
  • One Month Later Rare
  • First Post Rare

Recent Badges

0

Reputation

  1. 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
  2. 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. Got it, thanks John, wilco :).
  4. 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.
  5. 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?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.