[quote user="ndaustue"]

[quote]

2009-09-20#13-53-57.cab)? That's the most important part: I checked the

beta-reports account and you didn't send it, apparently? It would be

really helpful and is for now the only way to a possible solution.

[/quote]

Thanks for the instructions.

Log file is edited and cleaned; I finally found the cab; I deleted the password in the dmp and stored it in a new zip-file... Yet I am not sure if the dump file was created due the error ´too frequently login´ or due the main problem of disrupted network connection. The ´too many logins´ problem actually was on my side; gmx doesn´t accept repeated logins witin very few

[/quote]

Sounds like lots of work you're going through, but good to hear you could fix at least something. Now about the crash dump file: Editing it isn't a good idea as it isn't a simple text file: The one you provided is unfortunately unreadable for the debugger now (using a hex editor might allow you to modify it, but you'd need to know exactly what you're doing for trying this). Instead of posting it here as an attachment you should rather send them directly to my email address. But you're maybe right with your assumption above that it might not really help with your primary issue ...

I am getting frequent, seemingly random crashes of Pmail 4.51. I am running XP (32 bit) with all the latest patches on a brand new AMD Athlon 64 X2 dual core 2.7 GHz with 4GB of ram. This system has been perfectly stable otherwise. I haven't found a pattern to what causes the crashes. Sometimes immediately, sometimes after a few minutes of use. I have dropped back to 4.41 for now. I see that a lot of other people are having trouble with the new build, so I'll just wait.

[quote user="jdudeck"]I am getting frequent, seemingly random crashes of Pmail 4.51. I am running XP (32 bit) with all the latest patches on a brand new AMD Athlon 64 X2 dual core 2.7 GHz with 4GB of ram. This system has been perfectly stable otherwise. I haven't found a pattern to what causes the crashes. Sometimes immediately, sometimes after a few minutes of use. I have dropped back to 4.41 for now. I see that a lot of other people are having trouble with the new build, so I'll just wait.
[/quote]

I still need some more details about these crashes, please take a look at the this thread for finding out whether you can provide some more information, especially crash dumps (someone's got to do it, otherwise we won't be able to fix it!).

My installation crashed too but I renamed the words4.db3 to words4.db3.old then ran the install again and now it works fine.  Maybe that will work for you as well.

[quote user="Jeff Anderson"]

My installation crashed too but I renamed the words4.db3 to words4.db3.old then ran the install again and now it works fine.  Maybe that will work for you as well.

 [/quote]

I'd be extremely interested in a crash dump of this one for comparing it with other unsolved cases!

Is that a file that would have been created on my computer...how do I find it?

Thanks,

[quote user="Jeff Anderson"]

Is that a file that would have been created on my computer...how do I find it?,

[/quote]

In your current user's mailbox directory (usually a subdirectory of Pegasus Mail's installation directory, e.g. "C:\PMAIL\MAIL\Username\"), see Help => About Pegasus Mail... => Info => Home mailbox location: .....

Any idea what the file would be called?

[quote user="Jeff Anderson"]

Any idea what the file would be called?

[/quote]

I guess I have a problem: Can you please quote the post (using the respective button) you're replying to? I don't understand what file you're referring to: words4.db3 is a file and my previous post refers to its location while my post about crash dumps contains a link pointing to the download section from where you may select, download and install the appropriate MiniDump extension required for your system to create a crash dump. If you open the proper download location you'll also find some text linking to another thread explaining details about what this is good for.

[quote user="idw"][quote user="Jeff Anderson"]

Any idea what the file would be called?

[/quote]

I guess I have a problem: Can you please quote the post (using the respective button) you're replying to? I don't understand what file you're referring to: words4.db3 is a file and my previous post refers to its location while my post about crash dumps contains a link pointing to the download section from where you may select, download and install the appropriate MiniDump extension required for your system to create a crash dump. If you open the proper download location you'll also find some text linking to another thread explaining details about what this is good for.

[/quote]

Sorry I don't have the information you are looking for, I did not take note of where the file was and I'm not going to try to re-create the problem.

I was also having this same issue after upgrading to 4.51. I did go in yesterday, and renamed that file..  Program was stable until just a few minutes ago (after crashing multiple times throughout the day before this change)...  This time, I actually wrote down the error message, hope it gives someone some info:  The instruction at 0x7c910b0c referenced memory at 0x000000000. The memory could not be "written"...

Hope someone could solve the problem...   If not, i may have to go back to the prior version (which I don't have the install for)...Is the prior version out there somewhere for download?

Thanks!

[quote user="mcorrow"]

I was also having this same issue after upgrading to 4.51. I did go in yesterday, and renamed that file..  Program was stable until just a few minutes ago (after crashing multiple times throughout the day before this change)...  This time, I actually wrote down the error message, hope it gives someone some info:  The instruction at 0x7c910b0c referenced memory at 0x000000000. The memory could not be "written"...[/quote]

The error message does not help here, but a crash dump might do: Please read the first aid post for further instructions.

[quote user="mcorrow"]

Hope someone could

solve the problem...   If not, i may have to go back to the prior

version (which I don't have the install for)...Is the prior version out

there somewhere for download?[/quote]

Check the Downloads section.

I did download the 4.41 version (won't install it yet)..  I've installed the minidump, hoping to give you folks the ability to solve the problem.  I'll use 4.51 for the day, hope it doesn't blow up too many times.. 

Hope this helps.

[quote user="mcorrow"]

I did download the 4.41 version (won't install it yet)..  I've installed the minidump, hoping to give you folks the ability to solve the problem.  I'll use 4.51 for the day, hope it doesn't blow up too many times.. 

 [/quote]

Thanks for trying to help! BTW: It may be required to run the MiniDump

extension as "stand-alone" debugger, see its ReadMe file for details

about why and how.

From the error message you provided I would expect it to not happen very frequently. It would help a lot if you could duplicate the crash, e.g. if a special (probably HTML) message is involved - which we would like to see then, preferably sent as a zipped CNM file (the message format in your new mail folder, more details if required).

[quote user="idw"][quote user="mcorrow"]

I did download the 4.41 version (won't install it yet)..  I've installed the minidump, hoping to give you folks the ability to solve the problem.  I'll use 4.51 for the day, hope it doesn't blow up too many times.. 

 [/quote]

Thanks for trying to help! BTW: It may be required to run the MiniDump

extension as "stand-alone" debugger, see its ReadMe file for details

about why and how.

[/quote]

Matt, I now got some of  these crash dumps, but unfortunately they didn't contain any information (zero file size) and my replies to these messages always return with an undeliverable error. Like I wrote above, you may need to run the MiniDump

extension as "stand-alone" debugger (easily be done by starting Pegasus Mail via the respective Start menu entry), take a look at its ReadMe file.

Hi,

 after using Pegasus for many many years I now ran into trouble the first time.

My installation also crashes repeatedly. Crashes are reproducable:

After 2 contacts to the mail server (checking or sending mails) the network connection is disabled and impossible to fix. The System must be rebooted. Avoiding the use of Pegasus prevents the connection from crashing. Closing Pegasus after 2 connection attempts results in the well known error message: The instruction at 0x.... referenced memory at 0x.... The memory could not be "written"..

The following has been tested:

Uninstallation of Pegasus (4.51), registry cleaning, new installation. No success.

Stepping back to 4.41: no success; yet I will try to delete Pmail and its registry settings; then do a brand new 4.41 setup.

Uninstalling Pegasus 4.51, registry cleaning, defrag, chkdsk with repair, entirely new setup (including new profiles, identities etc.); no success.

Presently I am using Outlook; just my years of mails are stored in the Pegasus folders and can hardly be used....

Machines (I have the identical problems on two independent PCs): HP Pavillon dv5000 and Fujitsu Siemens I860 PC. XP2nd Ed, all updates; no unusual Programs; all up to date. My netbook and my office PC (also same OS, more ore less same programs) both (still) work fine, but I am afraid that these crashes show up in more or less due course....

I already have these problems since quite some time, when I was using the beta version of 4.51, German edition.

I will try to install MiniDump and test it as debugger; presently there are no solutions or messages in sight....---Update: MiniDump is installed, but does not report. When trying to connect to the server after two successfull connections, Pegasus stalls completely. It must be killed with the Task Manager; its interesting; Pegasus consumes 98 % CPU power when it has stalled. For the moment I must stop the use of Pegasus; its too sad, but rebooting the PC every few minutes is not acceptable.

Is somewhere a description that explains the setup of IMAP and the transfer from Pegasus mails to Outlook. I need to access my mail quite frequently and it is quite frustrating to constantly look up mails in Pegasus, copy them into Outlook and then punching in the replies....

Any help or even better solution would very much be appreciated; I would be glad to support you with all and additional details.

ND

[quote user="ndaustue"]I will try to install MiniDump and test it as debugger; presently there are no solutions or messages in sight....---Update: MiniDump is installed, but does not report. When trying to connect to the server after two successfull connections, Pegasus stalls completely. It must be killed with the Task Manager; its interesting; Pegasus consumes 98 % CPU power when it has stalled. For the moment I must stop the use of Pegasus; its too sad, but rebooting the PC every few minutes is not acceptable.[/quote]

There are two modes of using MiniDump: As a simple extension (which is the default after installing it) which may fail as Pegasus Mail may crash it as well - or in what I call "stand-alone" mode, i.e. the debugger launches Pegasus Mail (there's a Start menu group entry after installation for doing this, see the ReadMe file for more details).

Your problem may be related to authentication using certificates: Do you use any of the SSL or STLS security options with your POP3 or SMTP accounts? If so try a different option or disable it (at least for testing). You may also create so-called session logs (instructions) to be enabled on the Internet Mail Options page (accessible via Tools => Internet options). I've seen some certificate related crashes reported recently by crash dumps.

[quote user="idw"]

There are two modes of using MiniDump: As a simple extension (which is the default after installing it) which may fail as Pegasus Mail may crash it as well - or in what I call "stand-alone" mode, i.e. the debugger launches Pegasus Mail (there's a Start menu group entry after installation for doing this, see the ReadMe file for more details).

[/quote]

Hi and thanks for the rapid answer.

I used the stand alone mode; the problems persist and there is no debug function visible after the crashes as the program simply is not responding any more. Is the MiniDump suitable for 4.4?

In the meantime I uninstalled 4.51, cleaned the registry, deleted old mail folders, set up a new installation of 4.4, Problems are still present. I assume its not version related. Any third attempt to contact the mailserver results in a stall of the program; launching any new programs needing a network connection makes these programs to not launch, a session log is not created. Yet there is a file in the folder which is named mailboxp.lck which I am not aware being present before (but this may be incorrect). The computer must be restarted, after this everything is fine until the third try to establish contact to the mailserver. I am connecting to the standard pop3 mailserver from GMX, Germany (mail.gmx.de / pop.gmx.net) 

[quote user="idw"]

Your problem may be related to authentication using certificates: Do you use any of the SSL or STLS security options with your POP3 or SMTP accounts? If so try a different option or disable it (at least for testing). You may also create so-called session logs (instructions) to be enabled on the Internet Mail Options page (accessible via Tools => Internet options). I've seen some certificate related crashes reported recently by crash dumps.

[/quote]

Previous settings (over the past 10 years) were: ssl or stls disabled. I just tried with active stls, and, yepp, after two connects via network connection to the mailserver, Pegasus 4.4 crashed again. My home PC is connected to the web via LAN and DSL; the identical Problems are visible. This all is really strange; there were no updates on any programs but the regular MS XP updates. Meanwhile I fear that one of the XP updates does interfere with pmail.exe. Nevertheless the problems were not as drastic as they are now; in early 2009 these problems only showed up once in a while.

Again, thanks for any hint solving these problems.

ND

presently in Vienna

[quote user="ndaustue"]Hi and thanks for the rapid answer.

I used the stand alone mode; the problems persist and there is no debug function visible after the crashes as the program simply is not responding any more. Is the MiniDump suitable for 4.4?[/quote]

Yes, it is, you may find files named like 2009-09-20#13-53-57.dmp in your system's TEMP directory if a crash dump is created (probably not if the system just "hangs").

Your problem may be related to authentication using certificates: Do you use any of the SSL or STLS security options with your POP3 or SMTP accounts? If so try a different option or disable it (at least for testing). You may also create so-called session logs (instructions) to be enabled on the Internet Mail Options page (accessible via Tools => Internet options). I've seen some certificate related crashes reported recently by crash dumps.

[/quote]

[quote user="ndaustue"]Previous settings (over the past 10 years) were: ssl or stls disabled. I just tried with active stls, and, yepp, after two connects via network connection to the mailserver, Pegasus 4.4 crashed again. My home PC is connected to the web via LAN and DSL; the identical Problems are visible. This all is really strange; there were no updates on any programs but the regular MS XP updates.[/quote]

Please provide a session log like described in Thomas Stevenson's instructions (take care to remove user names and passwords before doing so).

[quote user="ndaustue"]Previous settings (over the past 10 years) were: ssl or stls disabled. I just tried with active stls, and, yepp, after two connects via network connection to the mailserver, Pegasus 4.4 crashed again. My home PC is connected to the web via LAN and DSL; the identical Problems are visible. This all is really strange; there were no updates on any programs but the regular MS XP updates.[/quote]

Just another idea: Do you have Display remote-linked graphics ... set to Automatically ... on Tools => Options => Message reader? And do you have Load Windows Internet Services ... set to On demand only? If you regularly download images you should set the latter to Always.