BSOD with KB920685 and KB922582 updates

I have been using Windows automatic updates for years now and this is the
first bit of trouble I have ever run into using it!

For the last couple of months I have attempted to install these updates but
they never complete and Im presented with the BSOD. I usually use system
restore to go back and then never reinstall them again.

I have narrowed it down to TWO updates KB920685 and KB922582.

The error message I always get on the BSOD is:-

WORKER_THREAD_RETURNED_AT_BAD_IRQL

STOP 0X000000E1 0XF7422EF0 0X00000003 0X8A1715B0 0X8A1715B0

ousb2hub.sys
address F7422EF0
base at F741F000

Any ideas guys as this is really starting to annoy me now! (lol)

Many thanks

DJ Leekee

Here's a dumb idea ... install them one at a time to see which one is
casuing the BSOD. Or, did you do that already ?

ousb2hub.sys is a 3rd party driver. A search on Google reveals several
companies that use it. Perhaps it needs to be updated ??

FWIW, KB920685 is for a Moderate vulnerability; KB922582 is deemed High
Priority > for customers in keeping their systems updated. The update
addresses the following issue:
>
> You may receive error code 0x80070002 when you try to update a computer running on
> Microsoft Windows that has a minifilter-based application installed. This error code
> could occur when updating using any of the following Microsoft tools:
> • Automatic Updates
> • Windows Update Web site
> • Microsoft Update Web site
> • Inventory Tool for Microsoft Updates (ITMU) for Microsoft Systems Management Server
> (SMS) 2003
> • Software Update Services (SUS) 1.0
> • Windows Server Update Services (WSUS) 2.0

IMO, if the system is not throwing that error code, then skip it.

MowGreen [MVP 2003-2006]
===============
*-343-* FDNY
Never Forgotten
===============


DJ Leekee wrote:

> I have been using Windows automatic updates for years now and this is the
> first bit of trouble I have ever run into using it!
>
> For the last couple of months I have attempted to install these updates but
> they never complete and Im presented with the BSOD. I usually use system
> restore to go back and then never reinstall them again.
>
> I have narrowed it down to TWO updates KB920685 and KB922582.
>
> The error message I always get on the BSOD is:-
>
> WORKER_THREAD_RETURNED_AT_BAD_IRQL
>
> STOP 0X000000E1 0XF7422EF0 0X00000003 0X8A1715B0 0X8A1715B0
>
> ousb2hub.sys
> address F7422EF0
> base at F741F000
>
> Any ideas guys as this is really starting to annoy me now! (lol)
>
> Many thanks
>
> DJ Leekee

I did try installing all the updates that had built up and the only two that
wouldnt install are the two listed above.

I have now resolved the problem but not sure why it worked.

All I had done was copy the hal.dll file that was in the I386 folder and put
it in the windows/system32 folder and everything came good and I am able to
install those pesky updates now!

Can anyone shed any light on what the hal.dll file is and whether I have
created any damage or problems by replacing it?

Leekee

IF there was an issue with hal.dll, then the system would not have
booted and you would have received an error message pointing to that
specific file.
hal.dll is the Hardware Abstraction Layer DLL.
Locate hal.dll and right click it, choose Properties, then click the
Version tab.
For XP SP2, it should read :

File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Internal Name : halacpi.dll

On the General page it should show a Created date of Tuesday, August 03,
2004.

It's possible that the file was damaged/corrupted.

MowGreen [MVP 2003-2006]
===============
*-343-* FDNY
Never Forgotten
===============


DJ Leekee wrote:

> I did try installing all the updates that had built up and the only two that
> wouldnt install are the two listed above.
>
> I have now resolved the problem but not sure why it worked.
>
> All I had done was copy the hal.dll file that was in the I386 folder and put
> it in the windows/system32 folder and everything came good and I am able to
> install those pesky updates now!
>
> Can anyone shed any light on what the hal.dll file is and whether I have
> created any damage or problems by replacing it?
>
> Leekee

The system sporadically wouldnt boot at all. Even getting into safemode was a
struggle. BUt replacing this hal.dll has allowed the installation of those
affending files and sped the computer up!

The hal.dll file information is as follows

File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Internal Name : hal.dll
Created date of 19th September 2002.

So the file name is different and the date is also two years earlier. The
File Version is as you stated though.

Everything seems to be working fine apart from Internet Explorer which has
crashed a few times but that could be down to the upgraded google toolbar
which Ive only just installed.


"MowGreen [MVP]" wrote:

> IF there was an issue with hal.dll, then the system would not have
> booted and you would have received an error message pointing to that
> specific file.
> hal.dll is the Hardware Abstraction Layer DLL.
> Locate hal.dll and right click it, choose Properties, then click the
> Version tab.
> For XP SP2, it should read :
>
> File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
> Internal Name : halacpi.dll
>
> On the General page it should show a Created date of Tuesday, August 03,
> 2004.
>
> It's possible that the file was damaged/corrupted.
>
> MowGreen [MVP 2003-2006]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> DJ Leekee wrote:
>
> > I did try installing all the updates that had built up and the only two that
> > wouldnt install are the two listed above.
> >
> > I have now resolved the problem but not sure why it worked.
> >
> > All I had done was copy the hal.dll file that was in the I386 folder and put
> > it in the windows/system32 folder and everything came good and I am able to
> > install those pesky updates now!
> >
> > Can anyone shed any light on what the hal.dll file is and whether I have
> > created any damage or problems by replacing it?
> >
> > Leekee
>