(Solved) Exception Code 0xc0000005 Crash. Just Cause2 and for GTA-V

Problem:

Windows logs show following error/warning for crashing application:

Faulting application name: JustCause.exe, version: 1.0.331.1, time stamp: 0x552e6ef2
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000028034f49e
Faulting process id: 0x7ac
Faulting application start time: 0x01d07bbb26c375db
Faulting application path: P:\ JustCause\ JustCause.exe
Faulting module path: unknown
Report Id: 3b5a7330-e7bc-11e4-a41d-448a5b663f9d

Troubleshooting:

I have already done a full clean reinstall of my video drivers, changed out my RAM, repaired the game (i have the physical copy, not steam version) and a few other fixes that I cannot remember at this point. Nothing worked for me.

Solution:

1.

Delete the following 2 files: [cfg.dat] and [pc_settings.bin] in this Folder:

"C:\Users\YOUR-USERNAME\Documents\ JustCause\Profiles\ACCOUNT-CODE\" .

Or

2. 

You can delete the whole folder instead of just two files, this will be recreated on the next Run:

"C:\Users\YOUR-USERNAME\Documents\ JustCause"


Now just relaunch the game.

Note:

Don't forget to select right compatibility settings for you application before running it.


Have Fun.

(Solved) Problem with upgrading from ESXi 5.1 to 5.5 error “Cannot run upgrade script on host.”.

I was upgrading an ESXi 5.1 server via the update manager to version 5.5. I kept receiving following error during upgrade: “Cannot run upgrade script on host.” After seeing the error, the Host rebooted with version 5.1.

Exploration of the file/var/log/vua.log, showed me the following passage:


VUA exiting
Alert:WARNING: This application is not using QuickExit(). The exit code will be set to 0.@ bora/vim/lib/vmacore/main/service.cpp
--> Backtrace:
--> backtrace[00] rip Vmacore::System::Stacktrace::CaptureFullWork(unsigned int)
--> backtrace[01] rip Vmacore::System::SystemFactoryImpl::CreateBacktrace(Vmacore::Ref&)
--> backtrace[02] rip Vmacore::Service::Alert(char const*, char const*, int)
--> backtrace[03] rip Vmacore::Service::AppImpl::Init(Vmacore::Service::Config*)::do_quick_exit::invoke()
--> backtrace[04] rip /lib/libc.so.6
--> backtrace[05] rip /lib/libc.so.6
--> backtrace[06] rip /usr/share/vua/vua

Method 1: 

I fixed the problem by re-installing HA agents and then updating once more. This proved to be successful solution. 

Method 2: 

1. Disconnect Host from HA cluster
2. Delete/Switch off HA clusters (completely)
3. Execute the following command line on the Host:


cp /opt/vmware/uninstallers/VMware-fdm-uninstall.sh /tmp
chmod +x /tmp/VMware-fdm-uninstall.sh
/tmp/VMware-fdm-uninstall.sh

Above "Methods" resolves the issue.

Following link can be helpful for furthur details:
 http://virtualrealization.blogspot.ch/2013/12/vum-errror-during-remediation-of-esxi.html