Faulting application svchost.exe

EVENT 1000 error Faulting application svchost.exe
Source
windows 2003 server SP2, used for shared folder only.
suddenly spot work shared filder ... clients have ping but cant acces folder. Work only after restart.
and have this event
"Faulting application svchost.exe, version 5.2.3790.3959, faulting module unknown, version 0.0.0.0, fault address 0x02b6f4b6"
See Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
What I would suggest is a userdump dump of the svchost.exe process crashing:
Obtaining DebugDiag
You can download the latest version of DebugDiag (version 1.1) from the Microsoft download center   www.microsoft.com/downloads
at this place or from www.iis.net
Debug Diagnostic Tool v1.1 (DebugDiag)
2. Double-click the downloaded .exe file to extract the userdump installation files. By default, these will extract to C:\kktools\userdump8.1. Please click "Yes", then "Unzip" to extract the files.
3. Double-click the "setup.exe" file located in C:\kktools\userdump8.1\x86 to install the userdump utility. Please select the defaults when possible, and make certain to select the "Enable dump on process termination" feature when prompted.
NOTE: You may need to reboot the machine at this point for the installation to complete successfully.
4. Create a folder called C:\userdump.
5. Once installed, you will find a new icon in your control panel called "Process Dump". Please open this utility.
6. When the userdump window opens, please click the "New" button.
7. Please enter "svchost.exe" in the "Application name:" dialog box, and click "OK".
8. Click on the new listing for "svchost.exe", and click the "Rules" button.
9. Select the "Use custom rules" radio button.
10. Type "C:\userdump" in the "Dump file folder" dialog box.
11. Click the "Monitor Process Exit" box
12. Change the "MiniDump Type" to "Complete".
13. Click the "OK" button.
14. Click the "Apply" button, then click "OK".
The next time svchost.exe crashes, it should create a .dmp file (or series of .dmp files) in C:\userdump.
---------------------------
Install critical update kb890830 and after restart install all updates from microsoft site

---------------------------

[XADM: How to Use Userdump.exe]

You can install the Userdump.exe utility as part of the Microsoft Platform Software Development Kit (SDK), the Microsoft Windows Debuggers, or as a stand-alone application. You can download the Userdump.exe utility as part of the OEM Support Tools package from the following Microsoft Web site:

http://download.microsoft.com/download/win2000srv/Utility/3.0/NT45/EN-US/Oem3sr2.zip

You can install the Userdump utility by using Setup.exe, or you can also extract and manually invoke the executable file (Userdump.exe) by using the command line.

If you run Setup to install the Userdump utility, some additional features (described in detail in the Userdocs.doc that accompanies the Userdump utility) are enabled, such as the following:

• Process self dumping. The Userdump utility supports a feature that allows an application to cause itself to be dumped, for example, in an exception handler block or a top-level unhandled exception filter.
• Hot-key process snapshot. You can associate a single keystroke with an image binary and trigger a dump.
• Exception monitoring. The Userdump utility can monitor applications that are running for exceptions, and can automatically generate dumps when certain exceptions occur. You configure the rules that dictate whether an exception triggers a dump for each application by using a page in the Process Dump utility in Control Panel.

----------------------------

C:\>userdump
User Mode Process Dumper (Version 1.0)
Copyright (c) 1999 Microsoft Corp. All rights reserved.


Usage: userdump [-p | [ProcessSpec [TargetDumpFile]]

    -p displays a list of running processes and their process IDs.

    ProcessSpec - can be a decimal or 0x-prefixed hex process ID,
       or the base name and extension (no path) of the image file used to
       create the process.

    TargetDumpFile - is any legal Win32 path specification. If not
        specified, the dump file is generated in the current directory
        using a name based on the image file name.