Marlene, I just found this message of yours in the archives,
thanks.  Never saw it posted.

As a matter of fact, I just checked my "Message rules" and one
was indeed invalid, I don't know what happened to it.  It was a
rule to move specific subjected email to a specific folder, and
somehow the specific folder area was removed!  I no longer
subscribed to the list, but I fixed the rule anyway, then
unchecked it.  I also had about 35 other rules which were ALL
for my ISP email thanks to BellSouth selling members' email
addresses to spammers.  I can now remove all of them since I
started fwd'ing my ISP email through my web server's filters.

Maybe this will help, thanks for the info.  :-)
-Clint

God Bless
Clint Hamilton, Owner
http://OrpheusComputing.com )


From: Marlene Coldwell

Hi Clint,

Any chance you are using message rules? Cut & Paste from
http://insideoe.tomsterdam.com/problems/errors.htm#badrules

Invalid Message Rules errors:
MSIMN caused an Invalid Page Fault in module unknown
MSIMN caused an invalid page fault in module MSOE.DLL at memory
address
MSIMN caused an Invalid Page Fault in module kernel32.dll
These errors can occur if a message rule uses invalid logic. If
the Criteria
of the rule specifies a condition that can only be determined
after the
message body is downloaded, but the Action of the rule is "do
not download"
or "delete from server", the logical contradiction causes OE to
crash.
Conditions that require the message body to be downloaded are:

Where the message body contains specific words
Where the message is secure
Where the message has an attachment

If you include these conditions in a rule, you must not select
either "do
not download" or "delete from server".

Good Luck,
Marlene

--------------------------------
I've wasted enough days trying to search for an answer to this
problem.  I can't find anything on it.  About half the time
when I close Outlook Express (OE), I get an error window.  It's
always a "Faulting application" and for msimm.exe which is OE.
I can close out of the window and all is fine.  I can reopen OE
and all is fine.  There are no crashes going on, just that
error window.  Sometimes when I reopen OE there is that
message on the preview pane of where a message body
should be stating OE was not correctly shut down and it may
be the email message that did it, so it's not being showed:

"Outlook Express did not shutdown correctly
The last time you ran Outlook Express it did not exit
correctly. In case this was due to a problem with the last
message you were viewing, the message is not being shown."

But, it's not the email message that's doing it since it of
course changes by the minute.  The Event Viewer (XP
Pro) shows things such as the following:

Faulting application msimn.exe, version 6.0.2800.1123, faulting
module unknown, version 0.0.0.0, fault address 0x00942fa9.

Details
Product: Windows Operating System
ID: 1000
Source: Application Error
Version: 5.2
Symbolic Name: ER_USERCRASH_LOG
Message: Faulting application %1, version %2, faulting module
%3, version %4, fault address 0x%5.

Fault bucket 113515155 (or sometimes 112031885)
Details
Product: Windows Operating System
ID: 1001
Source: Application Error
Version: 5.2
Symbolic Name: DW_BUCKET_LOG
Message: Fault bucket %1.

The file appcompat.txt that's created during an error shows
nothing of any use.  It only shows file versions.

This happens WITH OR WITHOUT SP1 for OE6 installed, so it's
not update related.  There are no other updates for OE 6 after
the SP1 for OE6 is installed.  ALL of my .dbx folders are ok as
far as attributes go.  They are not read only.  The OE storage
folder is not in the default location, but it hasn't been for
years so that has nothing to do with it since this only started
happening recently.  I had the folder hidden (but all mail
files inside were NOT hidden), and I changed the folder to
non-hidden folder and that didn't help.  I tried deleting the
folders.dbx file and that didn't help.  The SFC did not help.
This problem has been going on with NEW INSTALLS, so I'm at a
lost as to what could be doing it since it's never happened
before on other XP Pro installs.

I have also gotten the same type of faulting app type error
when CLOSING the Event Viewer!  They could be related.
This is a 3.4ghz P4, dual-channel PC4000 @ DDR560
memory, and a WD740 10,000rpm SATA Raptor, so I'm
wondering if this is somehow "too fast" when closing some
XP apps???

I don't know if this has anything to do with it, but I did an
XP Restore yesterday using the integrated restore function and
some files on my G partition (which is ONLY a STORAGE partition
and NOT EVEN MONITORED by the system restore) were deleted!!
Even stranger is the files it deleted were there LONG BEFORE
that particular restore point was even created!
-Clint
============= PCWorks Mailing List =================
Don't see your post? Check our posting guidelines &
make sure you've followed proper posting procedures,
http://pcworkers.com/rules.htm
Contact list owner <[EMAIL PROTECTED]>
Unsubscribing and other changes: http://pcworkers.com
=====================================================

Reply via email to