HITMAN™ 2

HITMAN™ 2

View Stats:
0x80000003 getting really old now....
Faulting application name: hitman2.exe, version: 2.14.0.0, time stamp: 0x5c7cf93c
Faulting module name: hitman2.exe, version: 2.14.0.0, time stamp: 0x5c7cf93c
Exception code: 0x80000003
Fault offset: 0x000000000108b975
Faulting process ID: 0x383c
Faulting application start time: 0x01d4dc99ee1e2932
Faulting application path: D:\Steam Games\steamapps\common\HITMAN2\retail\hitman2.exe
Faulting module path: D:\Steam Games\steamapps\common\HITMAN2\retail\hitman2.exe
Report ID: bf0325f9-1ecf-4544-9f6f-5b275575ef09
Faulting package full name:
Faulting package-relative application ID:
< >
Showing 1-10 of 10 comments
Hardware Mar 17, 2019 @ 2:41am 
Latest workaround to this issue is by adding "TdrDelay" registry key. By delaying TDR to 10 secondes for example, Windows will wait longer for a response from the gpu and thus wont reset it so quickly.

The default value is 2 seconds.

Windows + R > Type Regedit and add a new registry REG_DWORD x64 called "TdrDelay" with 10sec value (0x0000000a) here : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers

https://i.imgur.com/incaG9X.png

Documentation : https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys

2nd workaround is to use DXVK (Vulkan translator) but impact on performances is high.

https://www.hitmanforum.com/t/hitman-2-constant-crashing-with-0x80000003/27218/358

Last edited by Hardware; Mar 17, 2019 @ 2:56am
AussiePatriot Mar 17, 2019 @ 3:29am 
Originally posted by Hardware:
Latest workaround to this issue is by adding "TdrDelay" registry key. By delaying TDR to 10 secondes for example, Windows will wait longer for a response from the gpu and thus wont reset it so quickly.

The default value is 2 seconds.

Windows + R > Type Regedit and add a new registry REG_DWORD x64 called "TdrDelay" with 10sec value (0x0000000a) here : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers

https://i.imgur.com/incaG9X.png

Documentation : https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys

2nd workaround is to use DXVK (Vulkan translator) but impact on performances is high.

https://www.hitmanforum.com/t/hitman-2-constant-crashing-with-0x80000003/27218/358


Ive never heard of DVK until now, isn't that only for Linux or wine?
Hardware Mar 17, 2019 @ 6:03am 
DXVK works on Windows or Linux through Wine. You just need to put DXVK DLLs (dxgi.dll and d3d11.dll) in Hitman 2 retail folder. All GPU calls will be translated from DirectX11 to Vulkan.
Last edited by Hardware; Mar 17, 2019 @ 6:03am
AussiePatriot Mar 17, 2019 @ 5:26pm 
Im lost I got no idea how to use it lol
Tabsf1 Mar 18, 2019 @ 12:30pm 
Press Windows Key + R to open "Run" or Press Windows Key the type "Run"
Type “regedit” in the box and press Enter.
"Registry Editor" will open, navigate to the following file path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers

If on 32 bit system:
Right Click New > DWORD (32-bit) Value
Call it "TdrDelay"
Double-click the entry set the value as “20” (Hex Value, others have stated 10 in Decimal but this didn't work for me
Then Right Click New > DWORD (32-bit) Value
Call the 2nd one "TdrDdiDelay"
Double-click the entry also set the value as “20”
If on 64 bit system: use "QWORD (64-bit) Value” for both but keep names and 20 the same
marcusarow Oct 30, 2019 @ 11:13am 
I'm absolutely sick of this crash. The TdrDelay/TdrDdiDelay to 10 or 20 didn't work for me. I've copied and pasted the Exception code: 0x80000003 Fault offset: 0x000000000108b975 code from my Event Viewer, and have gone through EVERY SINGLE SOLUTION on the first 50 pages that pop up on Google.

I've also used a LatencyMon and got

Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more ISR routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.

Ran through the first 50 pages looking for answers for that. Tried everything in all of the pages...you name it. STILL NO FIX.

Even went as far as buying an new motherboard, new RAM, new GPU, new CPU, new HDD, new SSD, new PSU....still nothing. Funny thing is, I never once had this problem in Windwos 7
Hardware Oct 30, 2019 @ 11:36am 
https://www.hitmanforum.com/t/crash-to-desktop-turing-0x80000003-display-driver-nvlddmkm-stopped-responding/38630

How can I fix 0x80000003 crashes ?

1. First, try to start the game in DirectX 12 mode (available in launcher settings), if you can.
2. If it does not work, update your Nvidia drivers to the latest version available.
3. If it does not work, use the Nvidia reference clock speeds for your GPU. Nvidia has added a feature called “Debug Mode”, which will downclock any factory overclocked graphics card to Nvidia reference clock speeds. To turn on Debug Mode, open the Nvidia Control Panel, then go to the Help menu, and check the Debug Mode option.
4. And if it does not work either, rollback to 430.86. It’s one of the best drivers for HITMAN 2 to date. Before rollback, don’t forget to use Display Driver Uninstaller to uninstall your driver properly.
5. If you don’t want to rollback because you have games that depend on a newer driver, follow the instructions below to install DXVK and use it above of DirectX.
Last edited by Hardware; Oct 30, 2019 @ 11:37am
marcusarow Oct 31, 2019 @ 6:48am 
Originally posted by Hardware:
https://www.hitmanforum.com/t/crash-to-desktop-turing-0x80000003-display-driver-nvlddmkm-stopped-responding/38630

How can I fix 0x80000003 crashes ?

1. First, try to start the game in DirectX 12 mode (available in launcher settings), if you can.
2. If it does not work, update your Nvidia drivers to the latest version available.
3. If it does not work, use the Nvidia reference clock speeds for your GPU. Nvidia has added a feature called “Debug Mode”, which will downclock any factory overclocked graphics card to Nvidia reference clock speeds. To turn on Debug Mode, open the Nvidia Control Panel, then go to the Help menu, and check the Debug Mode option.
4. And if it does not work either, rollback to 430.86. It’s one of the best drivers for HITMAN 2 to date. Before rollback, don’t forget to use Display Driver Uninstaller to uninstall your driver properly.
5. If you don’t want to rollback because you have games that depend on a newer driver, follow the instructions below to install DXVK and use it above of DirectX.

Yeah, like I've said...I've done it all. Crashes in DX11 and DX12. Updated, Rolled back, Clean installed, used DDU on every driver from 417.71 to 440.97. Using DXVK makes the game look absolutely horrible. I have a 1080TI with 32GB of DDR4 RAM....actually, I'll just post my Speccy Summary:

Operating System
Windows 10 Pro 64-bit
CPU
Intel Core i7 7700 @ 3.60GHz 31 °C
Kaby Lake 14nm Technology
RAM
32.0GB
Motherboard
Gigabyte Technology Co. Ltd. Z390 AORUS MASTER-CF (U3E1) 30 °C
Graphics
GTW KX2703 (1920x1080@60Hz)
3071MB NVIDIA GeForce GTX 1080 Ti (ASUStek Computer Inc) 35 °C
Storage
465GB Samsung SSD 860 EVO 500GB (SATA (SSD)) 29 °C
1863GB Western Digital WDC WD30EZRX-00SPEB0 (SATA ) 30 °C
232GB Samsung SSD 840 EVO 250GB (SATA (SSD)) 23 °C
465GB Seagate ST500LM021-1KJ152 (SATA ) 24 °C
Optical Drives
HP DVD Writer 1265d
HL-DT-ST BD-RE BH16NS40
Audio
Realtek High Definition Audio


If you name something I haven't tried, I'll let you know. I have Debug Mode on now. We'll see...
Hardware Oct 31, 2019 @ 10:43am 
I helped some people using Nvidia reference clock speeds with debug mode enabled to get rid of 0x80000003 crashes with Hitman 2.

The final solution is DXVK on top of DirectX but the performances are not very good like you said.
Last edited by Hardware; Oct 31, 2019 @ 10:44am
Doc Holiday Oct 31, 2019 @ 11:40am 
I'm glad I don't have any of these issues. Using AMD here. Good luck
< >
Showing 1-10 of 10 comments
Per page: 1530 50

Date Posted: Mar 17, 2019 @ 1:31am
Posts: 10