Dcopymope

Prominent
BANNED
Aug 13, 2018
471
27
695
To start off, the game has been running smoothly ever since I turned off the 'Override Memory Safeguards' feature shown below. When I had it on though, the game kept crashing to the desktop. I kept trying until I finally got this error message, also shown below. I'm just curious, does this particular error message occur due to my GPU running out of video memory and being unable to allocate the data? The correlation is very strong since the issue disappeared when I cut the memory safeguards back on. I'll play the game again right now just to make sure my mind isn't playing tricks on me or something.

The Error Message Says: "The exception break point.......A break point has been reached. (0X0000003) Occurred in the application at location 0x00000001410C413D"

f0cdee1328677045.jpg



The Override Memory Safeguards Feature:

aa7de71328677047.jpg
 

Dcopymope

Prominent
BANNED
Aug 13, 2018
471
27
695
From where did you download the game? Also, are all available patches/updates (if any) applied?

I got it from Steam. I thought that was the only place you can get it from unless you get a hard disk version on the console or something. Cutting off the 'memory safeguards' was the deal breaker, it couldn't stop crashing, and then I got this error message. Its been working fine ever since I cut it back on though, which makes me curious.
 

COLGeek

Cybernaut
Moderator
Dubiously acquired games often have such errors (pirated). In your case, that doesn't apply (a good thing).

The next time is dies, look in Event Viewer for additional clues. Are your video drivers current? Same for Windows, in general.
 

Dcopymope

Prominent
BANNED
Aug 13, 2018
471
27
695
Dubiously acquired games often have such errors (pirated). In your case, that doesn't apply (a good thing).

The next time is dies, look in Event Viewer for additional clues. Are your video drivers current? Same for Windows, in general.

My operating system and drivers are up to date. It does me give the option to install a feature for windows 10 version 1909 though. I have no idea what that feature is.
 

Dcopymope

Prominent
BANNED
Aug 13, 2018
471
27
695
1909 is just the latest major release version. I installed on all of my systems, easily. No issues whatsoever afterward.

It is recommended for use. After installing, update your video drivers.

Well, I'll consider it if I start having issues again. I just wanted to know what the error message was about. It seemed to be related to video memory.
 

Dcopymope

Prominent
BANNED
Aug 13, 2018
471
27
695
Dubiously acquired games often have such errors (pirated). In your case, that doesn't apply (a good thing).

The next time is dies, look in Event Viewer for additional clues. Are your video drivers current? Same for Windows, in general.

Here is what the event viewer reported at the time it crashed:

Application Error:

Faulting application name: hitman2.exe, version: 2.72.0.0, time stamp: 0x5dd542fa
Faulting module name: hitman2.exe, version: 2.72.0.0, time stamp: 0x5dd542fa
Exception code: 0x80000003
Fault offset: 0x00000000010c413d
Faulting process id: 0x2538
Faulting application start time: 0x01d5b955152026be
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\HITMAN2\dx12retail\hitman2.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\HITMAN2\dx12retail\hitman2.exe
Report Id: d9bb8b28-b4a0-4237-b8f9-c5b4e59a677f
Faulting package full name:
Faulting package-relative application ID:
 

Dcopymope

Prominent
BANNED
Aug 13, 2018
471
27
695
Yesterday the game crashed on me again twice in a row. They were both reported as an "application error" but the exception codes were different from each other. It seems like I fixed it by running a chkdsk scan at boot time, so it was obviously happening due to some corrupt or missing files relating to this game. I'm just wondering how I would know this just by looking at these event logs. Would I know by both logs being titled "Application Error" or is there more to it? Its hard to find out what exactly these exception codes even mean without running it through some kind of debugger. :unsure:

Faulting application name: hitman2.exe, version: 2.72.0.0, time stamp: 0x5dd542fa
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x1d90
Faulting application start time: 0x01d5d56a39e12014
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\HITMAN2\dx12retail\hitman2.exe
Faulting module path: unknown
Report Id: 959985bc-4d2a-4d3a-8ed2-07012e4e8fd4
Faulting package full name:
Faulting package-relative application ID:


Faulting application name: hitman2.exe, version: 2.72.0.0, time stamp: 0x5dd542fa
Faulting module name: hitman2.exe, version: 2.72.0.0, time stamp: 0x5dd542fa
Exception code: 0x80000003
Fault offset: 0x00000000010c413d
Faulting process id: 0x28c0
Faulting application start time: 0x01d5d56a4949737f
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\HITMAN2\dx12retail\hitman2.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\HITMAN2\dx12retail\hitman2.exe
Report Id: 9d7060c9-ea0f-4967-9312-9ffd8e84ddb4
Faulting package full name:
Faulting package-relative application ID: