Excel Boom, Crash after XP SP2

E

ExcelHatesMe

Using DocsOpen version 3.9.5 from Hummingbird. Using
Trend Micro OfficeScan 6.5 anti-virus. Using Office
2000, SP3 on Windows XP Pro computers. Using Passive
Integration with Excel, but problem happens when I switch
to full integration as well.

Problem: Before XP SP2, life was good. Since applying
the service pack two weeks ago, when I try to open an
Excel document from the Recent Edits screen, my computer
blue screens and restarts. The error is "Stop 0x0000008E
(0xC0000005, 0x80564435, 0xF4730BAC, 0x00000000). This
happens to everybody at my work. This problem also
happens when starting a new spreadsheet, clicking Save As
in the Docs menu, entering the profile information,
clicking OK, and then BOOM... reboot. Documents can be
opened fine when the anti-virus is uninstalled or
disabled. Documents can be opened fine using native
windows (outside of DocsOpen).

Thanks for any suggestions.
 
M

M V Mitchell

I have a VERY similar problem.

DOCS 3.7.2 (full integration)
XP SP2
Office 2003 (patched to current level)
OfficeScan 6.5

I am currently experiencing the problem on dissimilar hardware platforms
(IBM desktop and Dell laptop - both relatively new and updated with current
drivers).

BSOD is similar:

Stop 0x0000008E (0xC00000005, 80579217, F5309B08, 0x0000000)

After reboot and performing same steps (Document->New->Same template) I will
get:
Stop 0x00000024 (001902FE, F575A3B8, F575A0B4, 8057FE35)

Currently, this is an intermittent problem on the affected machines. Also, I
do not have SP2 or Office 2003 deployed consistantly in the office (got to
test this configuration first, eh?). I'm not sure that the problem is DOCS
related either.

I have found that deleting the User's Temp directory contents (and
\Windows\Temp directory as well) tends to temporarily correct the problem on
the affected machine(s). I am also unsure how to consistantly trigger the
problem.

I would be interested to 'compare notes' and hope that you are monitoring
this thread. Please feel free to contact me! If anyone else has ideas I would
be interested in hearing them!
 
M

M V Mitchell

I have a VERY similar problem.

DOCS 3.7.2 (full integration)
XP SP2
Office 2003 (patched to current level)
OfficeScan 6.5

I am currently experiencing the problem on dissimilar hardware platforms
(IBM desktop and Dell laptop - both relatively new and updated with current
drivers).

BSOD is similar:

Stop 0x0000008E (0xC00000005, 80579217, F5309B08, 0x0000000)

After reboot and performing same steps (Document->New->Same template) I will
get:
Stop 0x00000024 (001902FE, F575A3B8, F575A0B4, 8057FE35)

Currently, this is an intermittent problem on the affected machines. Also, I
do not have SP2 or Office 2003 deployed consistantly in the office (thank
goodness!! got to test this configuration first, eh?). I'm not confident that
the problem is DOCS related either ...

I HAVE found that deleting the User's Temp directory contents (and
\Windows\Temp directory as well) tends to temporarily correct the problem on
the affected machine(s). I am also unsure how to consistantly trigger the
problem.

I would be interested in 'comparing notes' and hope that you are monitoring
this thread. Please feel free to contact me! If anyone else has ideas I would
be interested in hearing them!
 
M

M V Mitchell

Grrr ...

Sorry for the repeat, folks. Said there was an error, but it appears to have
worked both times...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top