From Wine-Wiki

SEH

SEH is apparently Structured Exception Handling where the operating system handles a problem in the software. According to this link [1] In windows SEH then tries to clean up the exception either by invoking some more exceptions in chain or by terminating the program cleanly

err:seh:EXC_DefaultHandling Unhandled exception code c0000005 flags 0 addr 0xb7942bd2
err:seh:EXC_DefaultHandling Unhandled exception code c0000005 flags 0 addr 0xb7942bd2

D.Clark: try running wine like (assuming the bash shell):

WINEDEBUG=+relay wine battery & > wine.log

That will cause the program to run very slow, and can create a very large file (possibly 100s of MBytes) called wine.log. Search through the file for the first err:seh:EXC_DefaultHandling, and post a couple hundred lines prior to that to the Wine-Devel Mailing List. Wine Archive Link [Update: it appears these days, file a bug and provide a link]

trace:seh:__regs_RtlRaiseException code=c0000005 

M Meissner [Jun 05]: "c0000005" is the Windows "Segmentation fault" code. [...]I need the 1000 lines _before_ those :seh: lines. wine archive

---

warn:seh:setup_exception exception outside of stack limits in thread 000c eip 7bed9651 esp 7f9510f4 stack 0x7f950000-0x7fa50000
err:seh:setup_exception nested exception on signal stack in thread 000c eip 7bed99fd esp 7ffffcd0 stack 0x7f950000-0x7fa50000

R. Shearman [July 05]: Looks like a crash inside an exception handler. Use the +seh debug channel or run in winedbg to see the source of the problem.

---

err:seh:EXC_DefaultHandling Exception frame is not in stack limits => unable to dispatch exception.

S.Fievet: [oct 05] This error was with the game Warblade [...] According to Marcus it may be copy protection related. Wine Archive

---

000b:trace:seh:__regs_RtlRaiseException  info[0]=deadcafe
000b:trace:seh:__regs_RtlRaiseException  info[1]=deadcafe

A. Mohr [Oct 05]: deadcafe is another special magic value that might have been set by Wine code to indicate a problem. Wine Archive