I support an office with 3 users all of whom access Pegasus 4.52 from the same network share that holds both the executables and the mail stores. One (only one) of the users has lately experienced frequent crashes apparently at random; sometimes creating mail, sometimes downloading, sometimes sending. It reportedly happens 2-3 times a day. In all cases, Pegasus gives the nondescript "encountered an error and had to close" message. In the Event Viewer I see frequent Application Hang error messages similar to the following, but I have not determined that each Pegasus crash generates this error, but I suspect it does:
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 11/14/2010
Time: 5:31:46 PM
User: N/A
Computer: XP-RUTH
Description:
Faulting application winpm-32.exe, version 4.5.2.0, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x000101b3.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 77 69 6e ure win
0018: 70 6d 2d 33 32 2e 65 78 pm-32.ex
0020: 65 20 34 2e 35 2e 32 2e e 4.5.2.
0028: 30 20 69 6e 20 6e 74 64 0 in ntd
0030: 6c 6c 2e 64 6c 6c 20 35 ll.dll 5
0038: 2e 31 2e 32 36 30 30 2e .1.2600.
0040: 35 37 35 35 20 61 74 20 5755 at
0048: 6f 66 66 73 65 74 20 30 offset 0
0050: 30 30 31 30 31 62 33 0d 00101b3.
0058: 0a .
In November, I saw 17 winpm-32.exe events. 14 were just like the above, one was pointing to the same dll but some other address, one pointed to kernel32.dll, and one was simply an "unknown" dll. The hardware is a P4 3.0Ghz 512Mb RAM
Any suggestions about how to troubleshoot further?
Thanks in advance,
Peter Smick
<P>I support an office with 3 users all of whom access Pegasus 4.52 from the same network share that holds both the executables and the mail stores.&nbsp; One (only one) of the users has lately experienced frequent crashes apparently at random;&nbsp;sometimes creating mail, sometimes downloading, sometimes sending.&nbsp; It reportedly happens 2-3 times a day.&nbsp; In all cases, Pegasus gives the nondescript "encountered an error and had to close" message. &nbsp;In the Event Viewer I see frequent Application Hang error messages similar to the following, but I have not determined that each Pegasus crash generates this error, but I suspect it does:</P>
<P>&nbsp;Event Type:&nbsp;Error
Event Source:&nbsp;Application Error
Event Category:&nbsp;None
Event ID:&nbsp;1000
Date:&nbsp;&nbsp;11/14/2010
Time:&nbsp;&nbsp;5:31:46 PM
User:&nbsp;&nbsp;N/A
Computer:&nbsp;XP-RUTH
Description:
Faulting application winpm-32.exe, version 4.5.2.0, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x000101b3.</P>
<P>For more information, see Help and Support Center at <A href="http://go.microsoft.com/fwlink/events.asp">http://go.microsoft.com/fwlink/events.asp</A>.
Data:
0000: 41 70 70 6c 69 63 61 74&nbsp;&nbsp; Applicat
0008: 69 6f 6e 20 46 61 69 6c&nbsp;&nbsp; ion Fail
0010: 75 72 65 20 20 77 69 6e&nbsp;&nbsp; ure&nbsp; win
0018: 70 6d 2d 33 32 2e 65 78&nbsp;&nbsp; pm-32.ex
0020: 65 20 34 2e 35 2e 32 2e&nbsp;&nbsp; e 4.5.2.
0028: 30 20 69 6e 20 6e 74 64&nbsp;&nbsp; 0 in ntd
0030: 6c 6c 2e 64 6c 6c 20 35&nbsp;&nbsp; ll.dll 5
0038: 2e 31 2e 32 36 30 30 2e&nbsp;&nbsp; .1.2600.
0040: 35 37 35 35 20 61 74 20&nbsp;&nbsp; 5755 at
0048: 6f 66 66 73 65 74 20 30&nbsp;&nbsp; offset 0
0050: 30 30 31 30 31 62 33 0d&nbsp;&nbsp; 00101b3.
0058: 0a&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </P>
<P>&nbsp;In November, I saw 17 winpm-32.exe events. 14 were just like the above, one was pointing to the same dll but&nbsp;some other address, one pointed to kernel32.dll, and one was simply an "unknown" dll.&nbsp;&nbsp; The hardware is a P4 3.0Ghz 512Mb RAM</P>
<P>&nbsp;Any suggestions about how to troubleshoot further?</P>
<P>&nbsp;Thanks in advance,</P>
<P>Peter Smick</P>