Menu
Well, I uninstalled Hitman Absolution and redownloaded it (12 GB) from Steam rather than use the original backup I had stored on one of my external USB drive. The game still refuses to start on my system and continues to give the same 0xc0000005 error in the Event log.
What is HMA.exe and How To Fix It? Download Now WinThruster 2018 - Scan your PC for HMA.exe registry errors Compatible with Windows 10, 8, 7, Vista, XP and 2000.
The weird thing is that after revalidating the files or (in this case) redownloading the game, Steam shows the usual 'Preparing to launch.' Window but with a progress bar that over the course of several minutes fills with blue squares. Not sure what it is doing here, considering it's a fresh install, but whatever it is it doesn't help me play this game! Not sure what is preventing this game from starting.
Everything else I've played so far works exactly the same on Windows v1803 as v1709 despite the change to WDDM from 2.3 to 2.4. I'm not running any injectors, the RTSS overlay is disabled and the NVIDIA game profile is set to the default.
I have even reinstalled (repaired) a number of VC libraries (although Hitman Absolution oddly does not come with a Redist or VC folder so if it uses VC then I don't know what version). Game continues to refuse to launch (i.e. It crashes quietly!) on launch. Hey Darren, Sorry if others have already stated the same and if it doesn't add anything but on my system, which was upgraded from 1709 to 1803 and is on this new release of driver, the game starts OK via Steam. I didn't bother going all the way in game but I can launch from Steam, get the opening cinematic and get to the main menu OK.
This is with MSI Afterburner running and the RTSS overlay enabled as well. I have all the May Win10 patches installed. Edit: my Win10 build version is 17134.48 - standard release, I'm not on any fast or early release rings.
I'm also on the Steam Beta if that's relevant but I doubt it. Edit2: This is definitely Hitman Absolution I'm talking about, I see some others were getting mixed up with other Hitman games earlier in the thread. My HMA.exe is the same version as yours - 1.0.447.0. Seeing as it's a very vague error, all I can think of right now is simple steps like disabling any AV you have, making sure any display/graphics/monitor related helper apps are not running and trying a good old sfc and/or DISM /Online /Cleanup-Image /RestoreHealth. Well, I uninstalled Hitman Absolution and redownloaded it (12 GB) from Steam rather than use the original backup I had stored on one of my external USB drive. The game still refuses to start on my system and continues to give the same 0xc0000005 error in the Event log. The weird thing is that after revalidating the files or (in this case) redownloading the game, Steam shows the usual 'Preparing to launch.'
Window but with a progress bar that over the course of several minutes fills with blue squares. Not sure what it is doing here, considering it's a fresh install, but whatever it is it doesn't help me play this game! Not sure what is preventing this game from starting. Everything else I've played so far works exactly the same on Windows v1803 as v1709 despite the change to WDDM from 2.3 to 2.4.
I'm not running any injectors, the RTSS overlay is disabled and the NVIDIA game profile is set to the default. I have even reinstalled (repaired) a number of VC libraries (although Hitman Absolution oddly does not come with a Redist or VC folder so if it uses VC then I don't know what version). Game continues to refuse to launch (i.e. It crashes quietly!) on launch. Hey Darren, Sorry if others have already stated the same and if it doesn't add anything but on my system, which was upgraded from 1709 to 1803 and is on this new release of driver, the game starts OK via Steam.
I didn't bother going all the way in game but I can launch from Steam, get the opening cinematic and get to the main menu OK. This is with MSI Afterburner running and the RTSS overlay enabled as well. I have all the May Win10 patches installed. Edit: my Win10 build version is 17134.48 - standard release, I'm not on any fast or early release rings.
I'm also on the Steam Beta if that's relevant but I doubt it. Edit2: This is definitely Hitman Absolution I'm talking about, I see some others were getting mixed up with other Hitman games earlier in the thread. My HMA.exe is the same version as yours - 1.0.447.0. Seeing as it's a very vague error, all I can think of right now is simple steps like disabling any AV you have, making sure any display/graphics/monitor related helper apps are not running and trying a good old sfc and/or DISM /Online /Cleanup-Image /RestoreHealth. Click to expand.Thanks for trying to help. Alas, I've ran sfc /scannow and dism etc and no errors are reported with Windows. I am not using any other anti-virus software either except for the built-in Windows Defender (plus Malwarebytes Free which I run on demand approx.
Once a month otherwise it is not running in the background). I do use a few Stardock apps such as Start10 and Fences plus WindowManager, Corsair Utility Engine and usually have Uplay, Origin and Battle.net running the system tray so it is possible that one (or more) of those is interfering with the game launching. Will try a clean boot of Windows and see if that makes any difference. The error in the Event log is not much help as it only tells me that HMA.exe crashed and does not include any other files or DLLs that can cause these kind of crashes. Click to expand.I will try your first suggestion. I have already installed the DirectX 9.0c redistributable a few times already plus reinstalled the Intel chipset drivers etc along with various VC libraries.
Since every other game works fine then I suspect it is not an issue with the operating system but with something specific I have running in the background that is conflicting with the game.EDIT. I've just exited Steam and tried running it as an administrator. I then started Hitman Absolution and, again, I am getting the Preparing to launch. Window with the progress bar. Surely that is not normal? It already did all that yesterday (I have not rebooted since) and it is doing it again. This adds about two minutes to the game start!
What is it supposed to be doing here? Thanks for trying to help. Alas, I've ran sfc /scannow and dism etc and no errors are reported with Windows. I am not using any other anti-virus software either except for the built-in Windows Defender (plus Malwarebytes Free which I run on demand approx.
Once a month otherwise it is not running in the background. I do use a few Stardock apps such as Start10 and Fences plus WindowManager, Corsair Utility Engine and usually have Uplay, Origin and Battle.net running the system tray so it is possible that one (or more) of those is interfering with the game launching.
Will try a clean boot of Windows and see if that makes any difference. The error in the Event log is not much help as it only tells me that HMA.exe crashed and does not include any other files or DLLs that can cause these kind of crashes. So after some more testing I'm thinking that this might be the issue of NV's HDMI audio driver included in this and a previous couple of versions - for some mysterious reason it re-initializes the sound output in MPC-HC after a pause and this leads to it outputting only stereo, loosing all the other channels (out of 5.1 or 7.1 present in a video file).
It switches to 16 bit audio format output while doing this as well - which is the main indication of this being a driver issue. Could you look at this maybe? System is in the info, Win10 1803 x64. Thanks for trying to help.
Alas, I've ran sfc /scannow and dism etc and no errors are reported with Windows. I am not using any other anti-virus software either except for the built-in Windows Defender (plus Malwarebytes Free which I run on demand approx.
Once a month otherwise it is not running in the background). I do use a few Stardock apps such as Start10 and Fences plus WindowManager, Corsair Utility Engine and usually have Uplay, Origin and Battle.net running the system tray so it is possible that one (or more) of those is interfering with the game launching. Will try a clean boot of Windows and see if that makes any difference. The error in the Event log is not much help as it only tells me that HMA.exe crashed and does not include any other files or DLLs that can cause these kind of crashes.