Anyone knows why this happens? WM crashes all the time and restarts itself after showing the failure message

"Andreas"

Crystal Ball in for servicing, so what does the failure message say?
Have you been to control panel and checked 'Problems, Reports and solutions'?

I guessed it was a generic well-known problem. Anyway,:
Faulting application WinMail.exe, version 6.0.6000.16386, time stamp 0x4549b0f9, faulting module ntdll.dll, version 6.0.6000.16386, time stamp 0x4549bdc9, exception code 0xc0000005, fault offset 0x0003b15f, process id 0xd3c, application start time 0x01c789a6edd75155.
No entry for Mail in Problems Reports although it has crashed many times. Does it work ok for the rest of you?
" mac"

Also I have a system log entry from ESENT:
WinMail (4636) WindowsMail0: A request to write to the file "C:\Users\Andreas\AppData\Local\Microsoft\Windows Mail\WindowsMail.MSMessageStore" at offset 14245888 (0x0000000000d96000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (639 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
My hardware is ok though.
" mac"

Andreas wrote:

I wouldn't go as far as to say that but it doesn't crash like yours.

"Andreas"

You can try compacting and repairing the database using the WMUtil program oehelp.com/WMUtil/ just in case?
No guarantees since it 'might' be a hardware problem?
You might try the question in the OS newsgroup also: microsoft.public.windows.vista.general It is a very busy group, so if you are not subscribed already, set your get headers to 50 and use the GoTo button after subscribing, then use catch-up.

"Andreas"

Maybe I'm lucky, but in six months of use, Windows Mail has never crashed, although I did get database corruption once. Gary VanderMolen