Re: Debugging a STATUS_ACCESS_VIOLATION

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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"







[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux