DHCP error causing Crash

[Welshchris]

for a few weeks off and on i have been experiencing random memory dumps and system restarts and when looking in event viewer after everyone i get the same error and i dont know whats causing it, the error is...

Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1003
Date: 29/08/2008
Time: 00:18:03
User: N/A
Computer: HOME-**********
Description:
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 00173186B098. The following error occurred:
The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

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


I have tried 2 other Ethernet ports and tried without a router in place and same thing happens every now and then.

Can anyone shed some light on this?

Thanks.

[Graham M]

Is this DEFINITELY happening when the PC crashes as I have plenty of those errors but no blue screen/reboos

[Welshchris]

i get the memory dump that happens ONLY when that error happens in the event log.

[Welshchris]

anyone help ?

[Bender]

first off, try the following commands from the command line in this order:

ipconfig /flushdns
ipconfig /registerdns

failing that, in manager, remove the network devices and then rescan.

---------- Post added at 18:38 ---------- Previous post was at 18:36 ----------

I'm assuming the machine is assigning itself a 169 address (APIPA). This would indicate it is still trying to obtain a lease. Are your network settings set to automatically gain an IP, or have you statically set yourself up?

[Welshchris]

tried what u said, its assigning itself a 86. ip not a 169 so that side of it is fine and its set to auto get an IP.

[DaiNasty]

Originally Posted by Welshchris

tried what u said, its assigning itself a 86. ip not a 169 so that side of it is fine and its set to auto get an IP.

But surely an 86.* address would not be handed out by a router? They only use the non-routable groups such as 192.* and 10.*

It almost looks like the system is not seeing the router and is picking up an IP from the cable modem.

[Welshchris]

i dont have my router in place atm because im trying to solve the problem.

[DaiNasty]

Originally Posted by Welshchris

i dont have my router in place atm because im trying to solve the problem.

Sorry, I misunderstood. Thought you'd only tried removing it temporarily.