Huge CPU load from small .doc file

[Knack]

WinXP Pro(SP2); Athlon-4 1.3 GHz; 1.0 GB RAM

One particular Word file results in a huge 92-99% CPU load on my system. The
offending file is only 214 KB. Other <.doc> files including some that are
far larger barely load the CPU at all. What's the cause, and how can the
problem be rectified?

 

[wyocowboy]

Where did the file come from - did you create it, or ?

If you received it, it is possible that it is infected with a macro virus.
If you created it, it sounds like it might be corrupted.

 

[Knack]

Yes, I created it. It's just some simple text (no columns) with a few
images. The images are nothing but diagrams and charts that were copied from
web sites. There is some hyperlinked text in the file.

When the file is first opened the winword.exe CPU load is 0%. Then
immediately afterward over a span of about 10 seconds the CPU load gradually
climbs to a maximum of 99%.

I have numerous other files that are very similar in content (which I also
made on the same machine) that do not behave like this one.

Is their a scanning/debugging tool available that finds problems within a
<.doc> file?

 

[wyocowboy]

Yes, I created it. It's just some simple text (no columns) with a few
images. The images are nothing but diagrams and charts that were copied from
web sites. There is some hyperlinked text in the file.

When the file is first opened the winword.exe CPU load is 0%. Then
immediately afterward over a span of about 10 seconds the CPU load gradually
climbs to a maximum of 99%.

After it settles down, does all seem normal?

I have numerous other files that are very similar in content (which I also
made on the same machine) that do not behave like this one.

Are the hyperlinks pointing to content on the web or on your local machine?

Is their a scanning/debugging tool available that finds problems within a
<.doc> file?

Not that I know of.

 

[Gene]

Well,what do you know, I have the same problem with no solution yet. It might
be in the registry. i have tried numerous fixes without success. I am trying
a link fixer tonight. If it works I will let you know.