Pretty much reusing that old thread.
1) Click Start and type 'windbg' into search. It should give you an old-school looking gray item that you should run, then a gray and boring window should pop up. Create a directory named 'C:/websymbols' (Just go to C: and create a folder named 'websymbols'). Then, back in WinDbg, go to File->Symbol File Path and enter this:
SRV*c:/websymbols*http://msdl.microsoft.com/download/symbols1.5) go to Debug->Event Filters and set this item to these settings:

and hit Close, and resume with other steps.
2) In WinDbg select File->Open Executable in Windbg and point to the MassEffectConfig.exe.
(In the text window of Windbg there's an indicator bottom-left. If it says '*BUSY*' then WinDbg is working and you should wait before attempting another command. '0:000' or other numbers means it is ready for the next step.)
3) If it seems as if the program has stopped AND you see "int 3" on the last line of Windbg text window, then select Debug->Go; repeat this step until you don't see "int 3"
4) Once you don't see "int 3"
type this:
~* k 30 into the text window on the bottom-right next to 0:000 (or other numbers). After some info is outputted, select Debug->Go. This may occur multiple times. Repeat this step number 4 until it starts looking as if Debug-Go does nothing or otherwise you seem not to be able to proceed to repeat this step (aka the Go command does nothing).
5) I need all that text from Windbg.
P.S.
Don't know for others, but if you have at least basic knowledge of how programs work, then this is the most helpful information you can ever get when they stop working. I think the useless support thread should be updated to include the info on how to actually report problems with actual problem information; not generic user blabber.
Oh, and Bioware, just implement some proper crash reporting in your apps. Everyone does it.
Modifié par NewMessageN00b, 06 février 2011 - 07:51 .