- Sep 26, 2017
- 110
- 76
This could be on us, or not. Generally 0xc... errors ARE software related. The file that actually has the best info in this case is going to be your output_log.txt. This will be found at (or equivalent location on your system): C:\Users\Shitty\AppData\LocalLow\Eek\House PartyI also received this error on the original story.
I need one big screenshot of anything there that mentions (CTRL-F if you have to) an exception, and a shot of the ====OUTPUTING STACK TRACE==== section. Should resemble what's in the attachments.
Then, from the error.log file I need a shot of as much as you can get of the Stack: section. It will look like:
Stack:
0xb9d7eed0: 00000000 00000000 0dad09e0 0000008a ................
0xb9d7eee0: 0dad20a0 0000008a 5efa3320 0000008a . ...... 3.^....
0xb9d7eef0: bd25dd48 0000008a e9ffb050 00007ff8 H.%.....P.......
etc. etc.
The error and output_log files need to be obtained at the time of the crash, as while the error logs get saved away in folders with date and timestamps, the output_log file hangs out by itself and eventually overwrites itself. We are aware of a handful of method call issues that are causing similar errors for some users at times, but the more info we have the better. Thanks!