Hitman 2 - constant crashing with 0x80000003


#21

I have the same problem. From time to time have crash to desktop with Exception code: 0x80000003.
I have Gigabite Geforce RTX 2070. You guys calmed me down a bit cause I see that this is not RTX related only problem from what I read here.


#22

There is a update coming Tuesday, servers will be down for 3 hrs and patch notes will have info


#23

I’m still a bit apprehensive, but I just had a ~3 hour session, including Elusive Sean Target Bean, no issues. So the first signs say that the 2.11 patch helped with the crashes, I hope the test results are repeatable.


#24

Patch didn’t help, the issues for me started after the hotfix. Before that I finished the campaign fine…

The crashes are basically at random, sometimes after hours of play others after 5 minutes on different maps, in different locations etc. shit sucks.


#25

I thought 0x80000003 was resolved by updating the nVidia driver since it hasnt crashed for days, but it happened again just now:

Faulting application name: hitman2.exe, version: 2.11.0.0, time stamp: 0x5bec44f3
Faulting module name: hitman2.exe, version: 2.11.0.0, time stamp: 0x5bec44f3
Exception code: 0x80000003
Fault offset: 0x000000000114c295
Faulting process id: 0x1e28
Faulting application start time: 0x01d482bae328b9ab
Faulting application path: G:\Games\steamapps\common\HITMAN2\retail\hitman2.exe
Faulting module path: G:\Games\steamapps\common\HITMAN2\retail\hitman2.exe
Report Id: b1d59659-fdba-4e33-ad90-ca839e46a254
Faulting package full name:
Faulting package-relative application ID:


#26

Yeah, I had the issue again as well. I thought 2.11 helped, but it still crashed 3 times for me last night, even if less frequently than previously. First crash was after playing for about 3 hours, then after 2 hours and then after half an hour… which is not a reassuring trend.

My last resort will be to get a new PSU (I read somewhere that 0x80000003 can be due to power problems…), even if it’s quite an expensive fix for a single game.


#27

I really doubt it would be a PSU thing over so many users… I have a brand new system with a 1100W titanium PSU and I’m still getting these random crashes


#28

I doubt its the PSU.
0x80000003 is a Breakpoint reached, its when a programmer sets a break in the code for debugging. When the app reaches that code address, it tells the debugger to stop the app so you can check the variable values.
Its nothing to do with hardware imo.


#29

Ive started getting this as well now, played the first couple of missions fine and now just crashed all the time.
But i notice after a crash it has killed one of my other processes (none related to the game, just normal stuff).

I’d put money on it is their anti-cheat/piracy software thinking my valid system processes arr trying to interact with the game somehow.

Really bugging buying the gold edition of the game and being treated like a criminal with game breaking code.
Bad enough the always-online and data collection but was willing to look past that as I’m a big fan of the series, but this is getting ridiculous now…

…that’s my theory at least.


#30

I suppose its possible that Denuvo has the breakpoint. Maybe IOI could update Denuvo to the latest build and see how that goes.


#31

Same for me since november 9, game update 2.11 doesn’t help, 5 crashs today.

Nom de l’application défaillante hitman2.exe, version : 2.11.0.0, horodatage : 0x5bec44f3
Nom du module défaillant : hitman2.exe, version : 2.11.0.0, horodatage : 0x5bec44f3
Code d’exception : 0x80000003
Décalage d’erreur : 0x000000000114c295
ID du processus défaillant : 0x1264
Heure de début de l’application défaillante : 0x01d483fe5a09803c
Chemin d’accès de l’application défaillante : D:\Games\Steam\steamapps\common\HITMAN2\retail\hitman2.exe
Chemin d’accès du module défaillant: D:\Games\Steam\steamapps\common\HITMAN2\retail\hitman2.exe
ID de rapport : 7ab76b0d-0ccd-484b-9ae2-1bca6016972c
Nom complet du package défaillant :
ID de l’application relative au package défaillant :

Same error every time in the system logs :

Display driver nvlddmkm stopped responding

  • Windows 10 Professional 1803 Build 17134.407
  • Intel Core i7 9700K 4.9 GHz
  • MSI GeForce RTX 2080 Gaming X Trio
  • 16 GB DDR4 2666 MHz
  • Nvidia drivers : 416.94

Do you have any workaround ?


#32

Thank you, I will try that asap :stuck_out_tongue:


#33

Anyone of you don’t have RTX 2070 or 2080 and have this bug? I’m hopeing its not cause of the new RTX cards


#34

I’m starting to believe that it is. I’m a RTX owner myself and constant crashes.


#35

I have a friend, with a RTX 2070, who has the exact same issue (0x80000003).


#36

Yup, I have an RTX 2080, and I keep crashing with 0x80000003. Created an account on the forum just to find a fix for this. Super annoying.


#37

I see that a lot of people reported this issue having GTXes here.


#38

Same issue with my RTX 2080. I’ve just sent the card back to RMA.

Just to clarify, I have the 0x80000003 error, associated with the “nvlddmkm stopped responding” error


#39

Just noticed I get similar crashes in other games. It feels like a driver problem for sure in my situation.


#40

@JayE How do you make that visual studio doesn’t block the game when 0x80000003 exception occur ? I would like to trap the exception silently. I removed the checkmark in the ‘thrown’ column for the whole Win32 namespace, without effect.