Help, cable modem crashes XP

alexchannell · 08-11-2006, 08:15 AM

Wondering if you guys might have an idea what the problem is. I get the BSOD stating IRQ LESS OR NOT EQUAL tcpip.sys
This happens under the following circumstances:

FX60
Corsair ram 2gb
A32N deluxe MB
Nvidia 9750

The computer will stop talking to the modem (all lights lit and activity light still flashing) but not data will go through. (what is this indicative of? I checked the cable signal values, all are very good)
So I have to reset the modem by turning it off.
Every time (Unless the computer is still talking to the modem, then no BSOD) the computer will show the BSOD when the cable modem finishes fully booting up and the activity light goes on.

I tried updating the on board Ethernet drivers.....still BSOD
Then I disabled the on board Ethernet in device manager and plugged in a new Ethernet card of different make.....still got the BSOD with the new card under the same circumstances.

Any ideas?

**johnwill** · 08-11-2006, 02:37 PM

I'd suspect either a hardware issue or a corrupted Windows installation. Also, one can't discount malware/spyware causing the issue.

First off, try resetting the TCP/IP Stack to defaults with the following procedure, this configuration should work with any DOCSIS compliant cable modem.

TCP/IP stack repair options for use with Windows XP with SP2.

For these commands, Start, Run, CMD to open a command prompt.

Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log

If this doesn't to the trick, I'd do several hours of one of these memory diagnostics, we need to start eliminating hardware as the issue.

Microsoft Memory Diagnostic

MEMtest86

alexchannell · 08-11-2006, 02:43 PM

Quote:

Originally Posted by johnwill

I'd suspect either a hardware issue or a corrupted Windows installation. Also, one can't discount malware/spyware causing the issue.

First off, try resetting the TCP/IP Stack to defaults with the following procedure, this configuration should work with any DOCSIS compliant cable modem.

TCP/IP stack repair options for use with Windows XP with SP2.

For these commands, Start, Run, CMD to open a command prompt.

Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log

If this doesn't to the trick, I'd do several hours of one of these memory diagnostics, we need to start eliminating hardware as the issue.

Microsoft Memory Diagnostic

MEMtest86

I'll give those a shot. It certaintly appears like a driver issue thus far though.
This is a new install, spyware+antivirus protection was one of the first things I setup on it.

08-11-2006, 08:15 AM	#1 (permalink)
alexchannell Registered User Join Date: Aug 2006 Posts: 2 OS: XP	Help, cable modem crashes XP Wondering if you guys might have an idea what the problem is. I get the BSOD stating IRQ LESS OR NOT EQUAL tcpip.sys This happens under the following circumstances: FX60 Corsair ram 2gb A32N deluxe MB Nvidia 9750 The computer will stop talking to the modem (all lights lit and activity light still flashing) but not data will go through. (what is this indicative of? I checked the cable signal values, all are very good) So I have to reset the modem by turning it off. Every time (Unless the computer is still talking to the modem, then no BSOD) the computer will show the BSOD when the cable modem finishes fully booting up and the activity light goes on. I tried updating the on board Ethernet drivers.....still BSOD Then I disabled the on board Ethernet in device manager and plugged in a new Ethernet card of different make.....still got the BSOD with the new card under the same circumstances. Any ideas? Last edited by alexchannell; 08-11-2006 at 08:28 AM.

08-11-2006, 02:37 PM	#2 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,685 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	I'd suspect either a hardware issue or a corrupted Windows installation. Also, one can't discount malware/spyware causing the issue. First off, try resetting the TCP/IP Stack to defaults with the following procedure, this configuration should work with any DOCSIS compliant cable modem. TCP/IP stack repair options for use with Windows XP with SP2. For these commands, Start, Run, CMD to open a command prompt. Reset WINSOCK entries to installation defaults: netsh winsock reset catalog Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log If this doesn't to the trick, I'd do several hours of one of these memory diagnostics, we need to start eliminating hardware as the issue. Microsoft Memory Diagnostic MEMtest86 __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience