Breakpoint reached (0x80000003)

CatsnShxt · 03 Jul 2017

Ever since I started playing a game called H1z1, I have disconnected very frequently from the game with the error code
"The exception Breakpoint.
A breakpoint has been reached.
(0x80000003) occured in the application at location 0x000000014243B8C4.

Click on OK to terminate the program."

I have asked my brother who is a computer programmer and he says it is a common error with the game and that is due to a memory leak with the game. That seems to be the popular belief in the community for the game as well but I just want to know if there is anything else I can do. I have seen other posts that say this is due to the system's processor overclocking because it gets too hot and that causes the game crash?

To fix that I went to my advanced power settings and turned Maximum Processor State to 90% on each category but I do not think this has helped yet.

I have done many other things to try to fix this problem such as setting everything for the game to run as admin, re installing, running ccleaner and trying that, and many more..

I figured it was time to ask the people that deal with Windows 10 Errors and maybe they can help.

I am pretty friendly with computers but if it is an advanced change that is needed to be made, I would appreciate a step by step guide because I am definitely not a professional.

Thank you.

EdTittel · 03 Jul 2017

If the message mentions a breakpoint specifically this usually indicates an executable that's been compiled in debug mode where instrumentation -- like breakpoints -- serves to interrupt or pause execution so developers can check status, variables, and look for possible errors. You might want to contact the developers and ask them what this means. As an end-user recompilation is pretty far outside the scope of things you can do on your own.
HTH,
--Ed--

Superfly · 03 Jul 2017

EdTittel said:

If the message mentions a breakpoint specifically this usually indicates an executable that's been compiled in debug mode where instrumentation -- like breakpoints -- serves to interrupt or pause execution so developers can check status, variables, and look for possible errors. You might want to contact the developers and ask them what this means. As an end-user recompilation is pretty far outside the scope of things you can do on your own.
HTH,
--Ed--

Correct Ed, however, breakpoints are only parsed in the IDE (in debug mode)... at runtime that points to a memory leak...

EdTittel · 03 Jul 2017

OK, thanks for the clarification Superfly. I've never encountered a breakpoint error during normal operation/at runtime, so I didn't realize it could also point to memory leaks. Probably some kind of stack pointer that would never appear otherwise, eh?
Thanks again,
--Ed--

CatsnShxt · 03 Jul 2017

So if it points to a memory leak, that would mean that it would be the game itself that is the problem and I cannot fix anything?

EdTittel · 05 Jul 2017

If somebody else compiles the code wherein memory is leaking, then yes, there's not a lot you can do to fix things. That said, you can use this sourceforge tool to pinpoint whence memory leaks originate: Windows Leaks Detector.
Try it out, and you might learn something useful!
HTH,
--Ed--