> Seth wrote:
>> Faulting application svchost.exe, version 5.2.3790.3959, faulting module
>> ntdll.dll, version 5.2.3790.3959, fault address 0x0002a0d0.
>>
>> I have done everything I can think of to fix this problem
So far, the only thing you've shared with us here is ONE thing... you ran a
script...
>> The following the one of the batch files I have used to try and fix this
>> problem.
What was the specific reason you tried *this* batch file to try and fix a
fault in svchost.exe/ntdll.dll ???
which, by the way, was pointless since throwing mud at a wall won't hold it
together if somebody is still drilling 2" holes from the other side...
This script (which is flawed on so many levels it's not even worth trying to
identify them all) likely did nothing of value for you at all.
First you need to find out what the PROBLEM is.... THEN you can try to fix
it.
So, please ... What ELSE have you done to try to "fix" this problem -- which
we've not even identified, yet. (All we've identified is a *symptom* of an
unknown problem -- the *symptom* is NTDLL.DLL is crashing).
Please enumerate what "everything" means with respect to the things you've
tried to "fix" your error. Frankly, it's pointless for us to spend any
amount of time trying to "fix" this problem until we know what else might
have been broken as a result of the mud-throwing -- and that's why PABear
included this link:
http://members.shaw.ca/dts-l/goodpost.htm -- so you can
help us get some helpful information about your situation.
For example (questions I'd like to have answers to):
[1 ] When was this machine first deployed to your network?
[a] Was it installed with Service Pack 2 slipstreamed?
[b] Was Service Pack 2 applied after installation? If so, was it applied
from media? from WU/MU? from WSUS?
[c] Was the original machine slipstreamed with Service Pack 1?
[d] Was Service Pack 1 applied after installation? If so.. yada yada...
[e] Was the Service Pack 2 applied directly to an RTM installation?
[2 ] What other services/applications are installed on this machine?
[3] When was the FIRST time this error appeared on your system?
[4] What was the most recent change made to the system prior to the error
appearing on the system?
[5] While you've showed us an error from the Application Event Log -- what's
logged into the WindowsUpdate.log?
[6] Does this error occur when you attempt INSTALLATION, or is it logged
every time the WUA initiates a DETECTION?
[a] If only during installation, what update are you trying to install?
[b] If during detection, what was the most recent update installed, and
when was it installed?
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website:
http://www.microsoft.com/wsus
My Websites:
http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile:
http://mvp.support.microsoft.com/pro...awrence.Garvin