- Joined
- May 26, 2007
- Messages
- 5,545
- Reaction score
- 1,315
This indicates that the fault is in OS, not in anything any of us are doing. It may be worth looking at using "compatibility options" in Windows though.@ I tried opening the game by olly and worked regular
Now saving and opening the DLL without olly does not work ...
Windows does not close an application because it crashed (protection fault) without creating a log. I know it used to display it in the message box and now it hides the logs in the System Event Log and C:\Windows\blah... for later distribution via the Solution Centers' "Look for solutions online" or Error Reporting Service, but they are still there, and developers should know how to find that information on their version of Windows, and make use of it. If you have a decent Development Suite installed, it may well insert a system wide JIT Debugger, and you can set your system to use Olly if you don't, or just use Visual Studio and it's crap. (unless you only ever get crashes in your own C++ / C# source and only in the debug versions you have symbol files for)
I guarantee you Microsoft don't do anything with it except create pie charts of 60% of faults are caused by memory access violations and 20% are illegal instruction operations. 80% are in network, and probably internet aware applications and 30% of those are web browsers... But only 5% of all crashes are because of Internet Explorer, and only 1% in the latest edition so... We win! Yay!"