y-aji

Distinguished
Feb 20, 2009
26
0
18,530
I have a client who reported he was having issues with accessing the internet.. Upon looking into it, I found that his dhcp client had failed with the following error report:

Product
DHCP Client

Problem
Stopped working

Date
3/5/2009 10:03 AM

Status
Not Reported

Problem signature
Problem Event Name: APPCRASH
Application Name: svchost.exe_Dhcp
Application Version: 6.0.6000.16386
Application Timestamp: 4549adc4
Fault Module Name: ntdll.dll
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bdc9
Exception Code: c0000005
Exception Offset: 00043df3
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033
Additional Information 1: 24aa
Additional Information 2: 150e0ec22a8a6fcd1c249e067a668265
Additional Information 3: 6a8a
Additional Information 4: 16a03aff3bac55f9d25b7a7f6f29ef8d

Files that help describe the problem
Version.txt
AppCompat.txt
memory.hdmp
minidump.mdmp

The exact messages is:

Host Process for Windows Services stopped working and was closed

A problem caused the application to stop working correctly. Windows will notify you if a solution is available.

Thus, he's no longer able to attain an ip address and there appears to be no problem with the network card, directly.

This is on a Dell Inspiron 1521 with an Athlon 64 X2 Dual-Core Processor on a 32-bit version of Windows Vista Home Premium. I am currently downloading service pack 1 to see if this resolves the issue..

Does anyone have any further thoughts on this? Anything to try before I install service pack 1? Anything to try after?

Thank you,

Keith
 
(1) Click on Start button.

(2) Type Cmd in the Start Search text box.

(3) Press Ctrl-Shift-Enter keyboard shortcut to run Command Prompt as Administrator. Allow elevation request.

(4) Type netsh winsock reset in the Command Prompt shell, and then press the Enter key.


(5) Restart the computer.



You can also reset the IP stack the same way, except the command in step 4 is netsh int ip reset
 

y-aji

Distinguished
Feb 20, 2009
26
0
18,530


Sorry for the late reply. I don't believe I got it fixed and after trying resetting winsock the problem persisted so I assumed the network card had went bad. I'm afraid I dont have a solid answer for you. Good luck to you.