Re: Crash after 14.March.2017 Windows 10 update
Posted: Sun Mar 19, 2017 8:58 pm
Sorry, didn't help for me. :(
IncrediModerator wrote:To manually implement the crash fix in IncrediMail 2.0, please do the following:
1. Exit the IncrediMail application by right-clicking on the icon in your Windows taskbar and selecting "Exit".
2. In File Explorer, browse to the following path:
C:\Program Files (x86)\IncrediMail\Bin
3. Rename the file "PMC.dll" to "PMC.dll.old".
4. Relaunch the IncrediMail application.
Please let me know the results.
IncrediModerator wrote:Such unusual issues can often be solved by deleting the IncrediMail "Runtime" folder.
To delete the Runtime folder, please run the following executable:
http://www2l.incredimail.com/contents/s ... el_run.exe
When done, open IncrediMail and check the results.
If the problem continues, I would like you to open a new identity in IncrediMail and see if you still encounter the same problem.
To create a new identity, please click on Tools > Identities > New Identity.
Set up your identity, and check to see if problem continues to occur in the new identity.
Please note that I would like you to configure the same email address in your new identity, there is no need to create a new email address. While the identity name should be different, the email address should be exactly the same.
As everything is being done in the new identity, none of the data and settings in your original identity should be affected.
To switch back to your original identity, simply click on Tools > Switch Identity, select the appropriate identity, and click on OK.
hth wrote:I was going to post a separate thread, but its the exact same problem here, including the general timing. Been working on as time permits.
2 Major Problems
1) IM Crashing constantly (every 5-20 mins). Started about a week or two ago.
2) Cannot setup Send Mail without booting into safe mode for setting it up. After that can send in normal boot mode.
Platform: i7 on Intel Mobos, Win10, Scanned, Cleaned, etc ...professional IT serviced. Troubleshot in all sorts of clean and updated configurations, including safe mode (yes, it crashes running in safe mode as well).
Any repair mentioned here has been tried, and also a ton of hat tricks I threw at this over the last week.
The bottomline, imnsho, is ...this is purely and simply broken now. So either IM fixes what MS updates broke in it, or IM just lost a customer permanently (with many clients using this -and I mean whether they paid for it or not).
PLEASE LET US KNOW IN THIS THREAD IF/WHEN YOU POST ANOTHER UPDATE, AND WE WILL TRY IT OUT.
Typical Crash message
Exception: ACCESS_VIOLATION (C0000005) - on reading from 00000000
Faulting Offset: 0000346B
occassionally this one...
Exception: ACCESS_VIOLATION (C0000005) - on reading from 000018AC
Faulting Offset: 0001BCD2