Hitman 2 - constant crashing with 0x80000003

Nevermind on SSAO idea, I got 0x80000003 in the Chasing a Ghost level just now, within a minute of playing with SSAO off.

I don’t think i’m going to bother with this game anymore, IO doesn’t seem to care about this issue.

It would appear the higher you set the video settings the more likely it is to crash, but it’ll still crash eventually.

Well the 0x80000003 crash is back with the latest H2 patch (18 Dec), using the ‘good’ nVidia driver 417.22

Faulting application name: hitman2.exe, version: 2.12.0.0, time stamp: 0x5c176c65
Faulting module name: hitman2.exe, version: 2.12.0.0, time stamp: 0x5c176c65
Exception code: 0x80000003
Fault offset: 0x0000000001151095
Faulting process id: 0x2ddc
Faulting application start time: 0x01d49794642b62b5
Faulting application path: G:\Games\steamapps\common\HITMAN2\retail\hitman2.exe
Faulting module path: G:\Games\steamapps\common\HITMAN2\retail\hitman2.exe
Report Id: 5bc75a21-8aa0-4342-b2d4-81b8045c7ef1

@Travis_IOI could you please answer us, even if its just to tell us you have no idea what this is and are at least going to look into it, its effecting quite a lot of us here.

There’s a thread on the stream forum about it too, a LOT of people are having this crash problem, we need to know you actually care about it. The Silence isn’t helping anything.

417.35 seems stable, played the game for 2 hours today with no crash.
Need to play it more to be sure though…

(RTX2080)

Its not. I have that graphics card and those exact drivers

Same thing no improvement

If you have no crashes you’re just lucky but it will happen.

Play chasing a ghost that one always crashes on me

Multiple 0x8000003 crashes during the last elusive target (The Revolutionary)…

Can’t play more than 7 minutes without crash, so I managed to kill the target as quickly as possible to complete the contract.

I felt no pleasure playing this. Thank you IO.

=’(

1 Like

@Travis_IOI @Clemens_IOI @Nick_IO @Torbjorn_IOI @Bjarne_IOI @ioi_christianco @ioi_kristofer @IO_MartinVM @matte_ioi

Can any of you please respond to this situation, any of you at all? Some indication your company cares about this, some help?

A simple recognition would be nice.

1 Like

So. I decided to boot up Hitman 2 again after a couple of weeks off, and managed to play 3 minutes before CTD. :slight_smile: Sorry to say, but it only happens in Hitman 2, and it has been for a long time now.

I will try one last thing, limit my framerate with a stable value (60fps~), disable GSYNC, switch my monitor to 60Hz mode and play in 1080p. Maybe the game or nvidia driver don’t like huge fps drop (+120fps -> 50fps) due to (I suppose) DX11 draw call bottlenecking, or a problem with GSYNC, or i don’t know…

@IOI_Team : What information do you need to debug the situation ?

My specs :

Windows 10 Professional 1803 Build 17134.472
Intel Core i7 9700K 4.9 GHz
MSI GeForce RTX 2080 Gaming X Trio
16 GB DDR4 2666 MHz
Nvidia drivers : 417.35 (same issue with 417.22, 417.01, 416.94, 416.81, 416.34)
Gsync : ON
Monitor Refresh Rate : 144hz
Resolution : 2560x1440 DSR

Game settings :

settings

I have 0x80000003 error since day-4 (november 9), this issue drive me crazy.

It seems 417.35 is stable on my system with game version 2.12.0

I did an Express install of 417.35. (I dont change any other nVidia settings)
I have VSync disabled in the game.
The quality settings in the game are a mix of High/Ultra.
Resolution is at 3440x1440 (no GSync)
Windows 10 RS4 with latest patches.
Nothing is overclocked in my PC.

nVidia card details:

Try colombia or Mumbay asap.

Did a quick shoot em-up in Mumbai, can’t get it to crash.
I had played Colombia quite a bit yesterday, no problem.
I even did Sgail Master SASO and restarted a number of times, no probs.
Pretty sure it would have crashed by now. With 417.22 it would sometimes crash withing 10 minutes of playing the game.
I’ve played about 10 hours with 417.35 and its been completely stable.

If I were to guess the problem, I think it may be a multithreading race condition problem in the game that is triggered depending on the CPU and nVidia driver. Maybe its a shader problem or some other DirectX problem since it only seems to happen to people with nVidia cards.

Well I spoke too soon, it crashed with 0x80000003 again.
It didn’t crash at all when playing the H2 maps, but as soon as I fire up the game and play Colorado it crashes 1 minute into the game.

Faulting application name: hitman2.exe, version: 2.12.0.0, time stamp: 0x5c1b7bca
Faulting module name: hitman2.exe, version: 2.12.0.0, time stamp: 0x5c1b7bca
Exception code: 0x80000003
Fault offset: 0x0000000001150925
Faulting process id: 0x237c
Faulting application start time: 0x01d499e20b8803c9
Faulting application path: G:\Games\steamapps\common\HITMAN2\retail\hitman2.exe
Faulting module path: G:\Games\steamapps\common\HITMAN2\retail\hitman2.exe

What function is at offset 0x0000000001150925 ?
I did use nVidia Ansel moments before the crash, maybe Ansel has something to do with it.

They haven’t fixed it. its random, so you can get lucky and not have it happen for a while. Its been more stable the past day for me as well but i’m expecting it to crash eventually.

@JayE same offset for me : HITMAN2+0x1150925

STACK_TEXT:  
00000000`42ee7b70 00000000`887a0005 : 00007ffc`bf18f602 00000000`887a0005 00007ffc`00000400 00000000`42ee7c60 : HITMAN2+0x1150925
00000000`42ee7b78 00007ffc`bf18f602 : 00000000`887a0005 00007ffc`00000400 00000000`42ee7c60 00000000`00000000 : 0x887a0005
00000000`42ee7b80 00000001`00000009 : 00000001`00000048 00000000`00000000 00000000`00000008 00000000`00000000 : d3d11!CDevice::CreateShaderResourceView+0x12
00000000`42ee7bc0 00000001`00000048 : 00000000`00000000 00000000`00000008 00000000`00000000 00000001`85822348 : 0x1`00000009
00000000`42ee7bc8 00000000`00000000 : 00000000`00000008 00000000`00000000 00000001`85822348 00000010`00000010 : 0x1`00000048

d3d11!CDevice::CreateShaderResourceView

Ah so maybe it is a shader problem as i suspected.
Nice find, hardware.
Did you use Visual Studio to get that stack trace?

The issue persists. Just reported in the GeForce drivers official forum.

Please guys, do the same and fill out the NVIDIA feedback form too, the more the better.

@JayE Upload your dump file on http://www.osronline.com/page.cfm?name=analyze then check the stack trace.

@RodriGlez Done :wink:

1 Like

@Hardware Thank you! I hope NVIDIA listen to us … It would be nice if more affected users report to Nvidia too. As I said above, the more the better.

Agree that it can be a shader issue and I think it could have to do with the new graphic features/settings IOI added. Today and after several previous CTDs, I’ve been playing 6+ hours this afternoon without crashing with the new graphic settings all disabled.

Anyway, I’m going to do further test using different combinations of these new graphics settings to see what results I get.

Crashes happened before their new graphic settings. I like the shader theory.