Svchost error after winupdate; danger in /norestart?

I updated my XP SP2 with the recent security/hotfix updates #893086, 893066,
890923, 890859 and after reboot I received an svchost module error. I don't
enable error reporting and no error dump so I only managed to catch a glimpse
about the error, I think it says it can't run / hang / fail or something like
that and it's closed. There is a code (0x744e20bb) though not sure whether
it's a code or an address. Not sure either which update caused the error
since I ran them one after the other (from Run, with /norestart /nobackup
/passive options).

Also from EventViewer:
Category (100)
Faulting application svchost.exe, version 0.0.0.0, faulting module unknown,
version 0.0.0.0, fault address 0x00000000.

The error still occurred on the next reboot.

So what I did next was running SysRestore and reinstalling the 4 updates
again. Interestingly (or unfortunately?) since I used the /nobackup,
WinUpdate and MBSA cann't detect whether the updates were installed correctly
or not (before and after the reinstallation). The problem disappear after
the reinstall yet it still leaves me with some question.

1. Does the problem really disappear? How do I check for sure the updates
have been applied correctly (seems /nobackup can fool winupdate detection??)
2. Anyone with similar problem? My suspicion is toward 890923 (IE
related), 890859 (sys files) updates.
3. Any wisdom words regarding using the /norestart in installing winupdates?

Thanks