Burzmali wrote:
Here's a link to the error and the prior 200 lines run with +d3d http://pastebin.com/Qqkc3gGu
Here's 100 priors the with +relay
http://pastebin.com/JJsDBNcs
After the first seh, the system loops throwing an seh, waiting for a resolution, and then throwing the same seh again until something timeouts or breaks the deadlock or whatever. The issue always seems to raise when the application handles "context 0x32f6620"
Did someone ask you to post a log with +relay? If not, please repost
the log file without it. +relay shows inter-dll communication and
generates LARGE log files (which pastebin.com will not accept) and makes
it hard to determine what triggered the first seh error.
James McKenzie
