I am trying to get my application that was created on windows 10 (64 bit), Visual Studio 2015 (32 bit) to work on other computers (win 7 - 64 bit and vista - 64 bit.) I decided to use the application with a static library, however I do have questions otherwise for later.

I set the : Configuration Properties -> C/C++ -> Code Generation -> Runtime Library to multi-threaded (/MT) and multi-threaded debug (/MTd) for release and debug configurations respectively so that they would work with the static libraries instead of the dlls.

The actual application setting on Visual Studio toolbar is for Debug x86. Both computers works momentarily (displays some graphics using blits, etc. and interact with keyboard) and then seemingly at random points (maybe 3-5 seconds) their screen turns white and I am getting this error report on the windows 7 computer :

Wow, thanks I never knew about a crash dump before. It didn't think of using a debugger on the other computer either. If anyone else is new like me see this for a quick well written article on crash dumps and using the task manager.

https://blogs.msdn.microsoft.com/debugger/2009/12/30/what-is-a-dump-and-how-do-i-create-one/

Thank you,

Josheir

It may not be the cause of your crashes in this case, but for future reference you can use this tool (or similar) to find which dlls your .exe needs to run, and this is highly recommended before distributing your program:

http://www.dependencywalker.com/

Not a direct solution to your problem, but a hint that I found helpful:

Microsoft provides a number of free virtual machine images:

https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/

These are ostensibly for testing IE compatibility, but are a great way to test out your game on a "clean" install of Windows without having to have a computer dedicated to that purpose. You might have issues with DirectX compatibility with your virtualization software, but I've gotten great use from these.

Hope that helps someone,

Geoff

The program didn't crash, it hung. That implies that either you stopped processing the message queue, or you entered an infinite loop somewhere.