Windows update causing shdocvw.dll to get corrupted? Twice!

[Guest]

We have one XP Pro system that had this problem:

On Tues the 3rd, the user found that it kept rebooting. There was a brief
BSOD with the message that SHDOCVW.DLL was possibly corrupt (checksum
error). I was unable to boot into safe mode (same problem), so I ended up
doing a repair install. We eventually got the machine back.

The PC was set up to automatically redo all the windows updates last
Sunday. Monday morning, same problem all over again. We're starting the
repair install again, and we'll not do the windows updates for the moment,
but I'm at a loss as to why this is happening with just this one pc. Any
long-term suggestions? Or suggestions for further research or testing on
this?

 

[Gerry Cornell]

Dennis

I suggest you Disable automatic restart on system failure. This should
help by allowing time to write down the STOP code properly. Right click
on the My Computer icon on the Desktop and select Properties, Advanced,
StartUp and Recovery, System Failure and uncheck box before
Automatically Restart.

Enable automatic restart on system failure after you have captured /
copied and pasted the message in a further post here.

There will also be Error Reports in Event Viewer. Please post copies.
What you posted would be much easier to understand if you followed the
advice in the last paragraph of this message.

You can access Event Viewer by selecting Start, Administrative Tools,
Event Viewer. When researching the meaning of the error, information
regarding Event ID, Source and Description are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;308427&Product=winxp

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Double click the button and close Event
Viewer. Now start your message (email) and do a paste into the body of
the message. This will paste the info from the Event Viewer Error Report
complete with links into the message. Make sure this is the first paste
after exiting from Event Viewer.



--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[Guest]

Now if only I could actually get to the desktop to do some of the stuff you
suggest. Unfortunately, I get the BSOD during the boot process. And I cannot
get to safe mode.

I can only make out the name of the DLL and a bit of the message before it
reboots. I was hoping this may have been a known problem, or at least an
instance of a known behaviour in certain given circumstances. But everything
in google and deja.com (and your post) starts with the assumption that I can
get to the windows desktop.

I wonder, though, if the repair install would necessarily destroy the
records accessed by event viewer? I'll check that next time I'm on site,
although my guess is they'll probably just tell me in more detail that
shdocvw.dll is corrupt. And the real problem is not what specifically is
wrong with shdocvw.dll -- that's just an effect -- the real problem is why
does it go bad after all automatic updates are applied.

 

[Gerry Cornell]

Dennis

I have never tried method of accessing the computer.

How to install and use the Recovery Console in Windows XP
http://support.microsoft.com/kb/307654/en-us

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[GTS]

That is the specific file affected by the WMF (Windows Meta File)
vulnerability which has been in the news over the last week or so. See
http://support.microsoft.com/?kbid=912919 If the machine was infected, a
repair reinstall might not have been sufficient recourse.