KB920958 (MS06-049) compressed file corruption possible cause of Stop Error?

This morning MS rereleased MS06-049 due to an error "Compressed files that
are larger than 4 kilobytes may be corrupted when you create or update the
files" as described in KB article 925308.

I have 2 servers running W2000 Advanced Server that have been experiencing
intermitent Inaccessible Boot device stop errors on reboot since August. The
onset of this problem appears to aproximately coincide with when I applied
the original version of MS06-049.

To recover from the BSOD, I boot from the Windows CD and run chkdsk from the
recovery console. Chkdsk reports various file corruption errors. But after
chkdsk is run, the system boots normally.

On both servers the boot disk is on a RAID1 drive. We have done extensive
testing that seems to rule out any problems with the RAID controllers or
drives.

On one of the servers, eventually the system wouldn't even boot from a
windows 2000 CD. It appear to hang while examining the disks. Eventually we
did a complete rebuild of this system including a fresh OS install.

But the problem persists on the 2nd server.

Since the dllcache folder is compressed, is it possible that if WFP is
attempting to decompress one or more files for this folder on boot, getting
a corrupted dll and causing the BSOD?

Gary

Gary Kettner wrote:
> This morning MS rereleased MS06-049 due to an error "Compressed files that
> are larger than 4 kilobytes may be corrupted when you create or update the
> files" as described in KB article 925308.
....
> Since the dllcache folder is compressed, is it possible that if WFP is
> attempting to decompress one or more files for this folder on boot, getting
> a corrupted dll and causing the BSOD?

I don't think that's the problem because the fault caused by the
original August 8 release of KB920958 had to do with writing to or
copying compressed files. Existing files, such as those in your
dllcache folder, would not be affected. Of course, if you picked up
new EXE/DLL files via Windows Update it's possible they would get
corrupted. I wrote a scanner for corrupted files that's available at
http://marc.kupper.googlepages.com/scandf.

FWIW - My system was corrupting files for a little over a month and
none of my EXE/DLL files were hit. Most of the damage was to images
(GIF, JPEG, PNG, etc.) but I also had a few gzip files damaged.

Marc