Hitman 2 - constant crashing with 0x80000003

Just want to add some additional info here.

I’ve been running on a GTX 970 since launch without issues (other than so-so performance). I recently added a second GTX 970 in SLI, and since then, I’ve had this intermittent crashing issue. The performance boost with SLI was great, when it doesn’t crash.

One solution I found for the intermittent crashing issue with my setup is to set SLI mode to “single GPU mode”. This mostly disables the second GPU, and performance is about the same as using a single 970, but no crashes. I think “single GPU mode” is offloading some work to the second GPU because I see it’s GPU usage is 10-20% while playing Hitman 2. This is all DX11.

DX12 sort of “fixes” the issue, but seems to completely disable SLI no matter what settings I use in the nvidia control panel. When playing Hitman 2 on DX12, the second GPU is essentially idling (compared to 10-20% usage in single GPU DX11 mode). As expected, performance also drops significantly without SLI.

So for my setup, the best config is DX11 with SLI single GPU mode. Because I can’t use SLI effectively, I had to scale back the resolution to 1920x1080 from 2560x1440.

IOI, please fix the crashing issue when using SLI on DX11, and please allow SLI scaling when using DX12.

What error code do you get with your SLI in DX11 mode ?

Check the event viewer, and upload the crash dump here to help IOI.

Should be fixed at some point like Hitman 2016.

Faulting application name: hitman2.exe, version:, time stamp: 0x5c939f09
Faulting module name: hitman2.exe, version:, time stamp: 0x5c939f09
Exception code: 0x80000003
Fault offset: 0x00000000010998ed
Faulting process id: 0xef4
Faulting application start time: 0x01d4e745703e4d0c
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\HITMAN2\retail\hitman2.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\HITMAN2\retail\hitman2.exe
Report Id: fd241996-fd28-4fd9-b186-4f7d6f87bda3
Faulting package full name:
Faulting package-relative application ID:

Where can I find the crash dumps?


Got it, where should I upload it exactly?

Here :



The game is much more stable now with DX12, no more 0x80000003.

It still crashes with 0xc0000005 now and then, but its a rare occurrence. It usually happens when the game has been running for a few hours. I guess there’s a memory leak or something that happens over time.

…oh and the frame rates and input lag is much better now, I get 100FPS+ at 3440x1440 on my RTX2080.
With DX11 I was getting 65FPS with noticeable input lag.

1 Like

Uh oh. Got a 0x80000003 on Miami for the first time on DX12. It happened shortly after the “pink army” easter egg.

Hello Everyone,

i hope i am right here…
Following problem:

When i am playing the game it crashes after some colored flickering appears and without any error code just out of the game and the game is not running anymore…

Does anyone of you can tell me how to fix this ?

My Specs are:

  • i7 - 8700
  • 32 GB RAM
    -RTX 2080
    WIN10 64bit

Thanks in advance!

What is the Error Code in Event Viewer?

1 Like

And now I’m getting freezes in Directx12, so I’m back to Directx11 in windowed mode. This is getting annoying…

Edit: And now 0x80000003 in windowed mode. The game is now unplayable.

1 Like

After so many months waiting for a Fix that NEVER came the only workaround was playing in DX12. And they managed to break that too now.

@JoesGuy @Crashingtodesktop Game freeze with the latest Nvidia driver (430.39), I have this problem for 1 week now. Rollback to previous driver or download the hotfix 430.53 released by Nvidia yesterday, this hotfix does seems to solve the problem. And use DX12 of course.

Try this

Tried DX12 as per the April Update suggestion, reset my GPU (1080 Ti) underclocking to check: got 0x80000003 immediately as per usual (among some other lockup problems). Underclocked it again (just barely, -40 MHz, so it’s not affecting the performance much) and no crash.

So overall for me: DX12 doesn’t matter, underclocking is still the solution.
(I still get the 0xc0000005 memory problem, but that takes at least 3-4 hours of straight gameplay to rear its head).

If you are running the RAM at XMP speeds in the BIOS, set it back to JEDEC speed and see how that goes.

That describes both the problem and my current driver version, so I’ll give that a go and see how I get on. :slight_smile:

Edit: The freeze seems to be gone. I do still wish I could play in DX11 though, as it seems to perform a bit better.

Fixed my [0x80000003 ] issue by increasing my paging file size to 16GBmin-24GBmax.
EDIT: I’ll check back and post how it goes.

@Hardware hey, did you install new Nvidia driver?
How it works for you? Are crashes present?

@misterkiller It works pretty well, no crash or freeze during gameplay. However, since the last game update, game can crash when loading a ghost mode map.

Exception code : 0xc0000005
Exception offset : 0x00000000010bf7e6 (always the same)

I reported this issue on Official Bug Thread.

The game has crashed 6 times in these cisconstantes since May 1st. But I played a lot ghost mode since the last update, over 200 matches.