HITMAN World of Assassination

HITMAN World of Assassination

Not enough ratings
HITMAN™ 3 How to Fix: (Error Code: 0x80000003)
By SlickSocials | PR Services
This guide aims to help players who have this particular crash (code: 0x80000003) with HITMAN™ 3
3
   
Award
Favorite
Favorited
Unfavorite
It’s simple. If your game randomly crashes frequently, sometimes after 5/10 minutes of gameplay, sometimes right after you load a save.

Open the Windows Event Viewer (in start menu search bar). In application category, look for Hitman 3 application errors. If in the detail you see 0x80000003 exception code and if in System category, you see this too : “display driver nvlddmkm stopped responding”, it means that you are affected by the TDR crashing issue…

Event Log Error: 0x80000003 “A Breakpoint has been reached”
Faulting application name: hitman3.exe, version: 3.120.0, time stamp: 0x5be4326f Faulting module name: hitman3.exe, version: 3.120.0, time stamp: 0x5be4326f Exception code: 0x80000003 Fault offset: 0x0000000000e5b635 Faulting process id: 0x5ac Faulting application start time: 0x01d581f390d89dfb Faulting application path: E:\Program Files\SteamLibrary\steamapps\common\HITMAN3\retail\hitman3.exe Faulting module path: E:\Program Files\SteamLibrary\steamapps\common\HITMAN3\retail\hitman3.exe Report Id: ef23cbdf-6a51-4976-a5e4-cbfef3c68714 Faulting package full name: Faulting package-relative application ID:
According to my observations in the last couple of months, with DX11, Nvidia Turing architecture and HITMAN 3, the GPU randomly hits the timeout threshold defined in TDR Windows registry keys.
The nVidia driver doesn't have enough time to recover and this is what causes the crash

The Windows default threshold value is "2" seconds. to prevent this issue from occurring the value must be changed to "10" seconds
Couple off ways to test before doing the actual method:
    ----------------------------------------------------------------
  1. Try disabling V-sync.
  2. Try changing the Exclusive Fullscreen to Fullscreen, or vice versa.
  3. Try to launch the game in DirectX 12 mode (available in launcher settings).
    ----------------------------------------------------------------
The Actual Method:
If non of the methods above worked try doing the next solution:
  • Update your Nvidia drivers to the latest version available (search for the latest hotfix).
    Updated 06/28/2022 (GeForce Hotfix Driver Version 516.59)

  • Simply go to: Start --> Run --> Type in "Regedit" and navigate to:
    "Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers"
  • Create a key of type "DWORD (32-bit) for a 32-bit system. or a "QWORD (64-bit) for a 64-bit system.
  • Name it "TdrDelay" with a value of '10' as "Decimal value".
  • Reboot your system, launch the game, and the crashes won't happen :D

In a nutshell it gives the GPU 10 seconds to recover/respond vs. 2 seconds (default).


51 Comments
Literally Whiplash 30 Jun @ 10:49am 
Hey, I'm from the future, I can confirm this fix works universally for other games as well when facing the 0x80000003 and nvlddmkm issue, kudos to you, man :steamthumbsup:
FATCAT 30 Jan @ 9:25pm 
Is there a way to switch to DirectX 12 without using the launcher settings? The launcher doesn't work at all for me, just closing whenever I press any of the buttons on it. I've just been playing with the -skip_launcher launch code until now.
Sonvork 24 Jan @ 1:14pm 
I have done all the steps in this post and still the game freezes at any time, it can be in the menu, it can be while playing, it even happens to me in the loading screen, I still can't solve it.

Something interesting for me is that before I bought it on Steam I was playing it on Game Pass and it never froze like it does now, so I think Steam has something to do with the problem, because my pc ran it just fine from Game Pass.

Anyway if you can help me if you managed to solve it, it would help me a lot.
marcpad 22 May, 2023 @ 6:59am 
Sluep, that's the one thing that worked for me. Thanks! I think you should open a thread with this inforrmation.
Strumpet 30 Apr, 2023 @ 10:18pm 
For those of you that might still need help after trying all these options: When certain games are running and a computer crashes, it has a tendency to corrupt the shader cache. Navigate to C:\Users\**USER**\AppData\Local\IO Interactive\HITMAN3 and delete the files PipelineCache.bin and PipelineLibrary.bin. Then relaunch the game. This should build a new shader cache.
SlickSocials | PR Services  [author] 22 Apr, 2023 @ 1:22pm 
Fallub, i'm glad it worked for you :heartb:
Fallub 16 Apr, 2023 @ 7:36am 
I have tried both the RegEdit as well as downgrading to the 516.59 Nvidia driver and so far it works. Many many thanks.
LokkNar 16 Jan, 2023 @ 1:32am 
For those who tried all of the above to no avail (like me), I have another suggestion:
I googled a bit and found that the error is not only connected to the GPU, but also the "regular" memory.
What helped me was disabling any memory overclocking; on my B450 Gaming Pro motherboard I had A-XMP enabled.
After disabling memory OC the crashes have become very, very rare. In the past 60 hours or so of playing I had two or three crashes, I didn't even count because they have become so rare.
I hope this can help anyone.
EL bano 2 Nov, 2022 @ 9:45am 
thanks bro for posting this
Yorbihtter 27 Sep, 2022 @ 4:41am 
I did both. I'm not overclocking my GPU and there's actually no other choice than to play the game on DirectX 12 (at least for me). Moreover I know how it feels when my PC hits its max temperature for CPU and GPU and while playing HITMAN 3 I get to none of these two - more to say, my laptop is suspiciously cool for such graphically intense game (in RDR2 it heats up way more for example). The problem may be in my OS - I use a laptop with Windows 11 which is seemingly unsupported by the game. If that's so - I don't really know what to do, seems like I've just bought a game I can't play.