That was my idea to look into ERR-file from war2-directory.
It have been generated by war2 process during crash.
Not sure it's possible to add symbols for that ERR-file.
I spent last several evenings with experiments on dump-files.
If crash causes inside war2 process, you will not be able to find symbols for war2.
I don't think we need symbols from microsoft because we don't plan to debug windows ddls.
I cant because the broken war2 makes my mouse and window, bugged out so if i get the app open i cant click anything
Yes, when you get war2 crashed you press debug and then you are not able to use your GUI. I made my experiments with war2 loading in window mode. (That will not a goal for this situation).
Appreciate any ideas how to simply bypass that GUI blocking.
I also tried ProcDump by Mark Russinovich to get DMP-file, but stack trace in my test contained 1 address only. Instead of visual studio debugger in window mode (about 10 addresses in stack trace).
And then i looked into my ERR-file in war2 directory. In contained all the addresses i saw in visual studio debugger. Much more info than in full memory dump in DMP.
Maybe aqrit (or anybody else) can look into that addresses to find the problem.
As i understood from this log, the problem is related to this line:
10001284 0019ED54 0001:00000284 C:\War2anti\ddraw.dll
More precisely, it's already broken here, so need to look to the previous address (not listed in stack trace).
I'd say call for 0019ED54 looks like located here:
0x0019ebfc: 14 ec 19 00 b2 2a a3 6d 00 00 00 00 0c ed 19 00 .....*.m........
So location for previous call located here:
0x0019ec0c: 57 af a6 ed 2c ec 19 00 9e 73 c3 65 58 7f 59 00 W...,....s.eX.Y.
So, i'd look into aqrit's ddraw.dll, into function begin at 0019ec2c to check what happens there before call to 0019ed0c
Of course, 0019ED54 is also interesting address to look into...
Debugging in Visual Studio with the symbols file would be most preferrable.
If anybody can make symbols for current ddraw.dll, and explain how to enable it for degubbing that file, that would be appreciated.
Not sure if symbols can be built after ddraw.dll or both ddraw.dll and it's symbols should be created simultaneously...
Also, tupac, what version did you use for that log?
Also, can you attach your ddraw.dll you used for that? (Not sure if aqrit rebuilt that dll and updated the link recently).