Win 2003 R2 x64 - Faulting appl. svchost.exe, fauling module ntdll

Hello everyone,



Windows server 2003 R2 enterprise edition x64 logs this error in application
event log and server service (and some other services) fails. If i try to
start server service, i get error "access is denied". I can temporary resolve
issue by restarting server. Symptoms are basicaly the same as desctibed in
the article kb910666, but this article is valid only for x86 operating
system. How to approach the problem on x64 system ?





Event Type: Error

Event Source: Application Error

Event Category: (100)

Event ID: 1000

Date: 23.10.2007

Time: 12:48:15

User: N/A

Computer: BLUE

Description:

Faulting application svchost.exe, version 5.2.3790.3959, faulting module
ntdll.dll, version 5.2.3790.3959, fault address 0x000000000003541a.



For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 41 70 70 6c 69 63 61 74 Applicat

0008: 69 6f 6e 20 46 61 69 6c ion Fail

0010: 75 72 65 20 20 73 76 63 ure svc

0018: 68 6f 73 74 2e 65 78 65 host.exe

0020: 20 35 2e 32 2e 33 37 39 5.2.379

0028: 30 2e 33 39 35 39 20 69 0.3959 i

0030: 6e 20 6e 74 64 6c 6c 2e n ntdll.

0038: 64 6c 6c 20 35 2e 32 2e dll 5.2.

0040: 33 37 39 30 2e 33 39 35 3790.395

0048: 39 20 61 74 20 6f 66 66 9 at off

0050: 73 65 74 20 30 30 30 30 set 0000

0058: 30 30 30 30 30 30 30 33 00000003

0060: 35 34 31 61 541a



Thanks & regards

Marko

The solution is to uninstall WSUS 3.0 x64 and svchost will not terminate
unexpectedly any more. But question remains - why is this happening and is
there any solution to have wsus 3.0 x64 installed on Win 2003 x64 server
without this error ?

I'm experiencing the same exact problem now. However, I don't have WSUS installed on this server. For one day this server was up and down about every 1-2 hours. After fixing a few incorrect entries in DNS, I've gotten to about 12 hours of consistent service. Now, I don't know what else to do. Does anyone have any ideas?

Since I can’t figure out what is going on and no online Tech Forums are able to assist in the matter, I called Microsoft and paid for their support. After spending about an hour to explain the situation, then troubleshooting, Microsoft resolved that the browser.dll file in the c:\windows\system32 folder was corrupt. They then emailed me a hotfix. Information about this hotfix can be found at http://support.microsoft.com/kb/932762.

Thank's very working