"Socket 0 Error" / IRQ conflicts


D

David D.

I have W2K Pro SP4.

My system frequently crashes with a "Socket 0 error". It does not crash if
running in safe mode with no internet connection.

IRQ conflicts might be the culprit (although I could be wrong about that).

My system reports IRQ 11 conflicts:

11 RADEON 7500 SERIES
11 NEC PCI to USB Open Host Controller
11 NEC PCI to USB Open Host Controller
11 NEC PCI to USB Enhanced Host Controller
11 Win2000 Promise Ultra133 TX2 (tm) IDE Controller
11 HPT372 UDMA/ATA133 RAID Controller
11 CMI8738/C3DX PCI Audio Device
11 VIA USB Universal Host Controller
11 VIA USB Universal Host Controller
11 VIA USB Universal Host Controller
11 Realtek RTL8139/810x Family Fast Ethernet NIC

My other IRQs assignments are:

9 Microsoft ACPI-Compliant System
14 Primary IDE Channel
15 Secondary IDE Channel
8 System CMOS/real time clock
13 Numeric data processor
6 Standard floppy disk controller
4 Communications Port (COM1)
3 Communications Port (COM2)
1 Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
10 MPU-401 Compatible MIDI Device

Do you concur that IRQs is the likely culprit?

Which IRQ 11 devices should I try to reassign? And to where?

How do I force them to a new IRQ?

Any advice would be greatly appreciated.

- David
 
Ad

Advertisements

B

Bob I

Is it actually saying that there is a conflict? The IRQ numbers are a
"virtual numbering system" for legacy reasons. There are normally only 4
REAL hardware IRQ lines in a PCI system A,B,C and D. PCI systems are
designed around shared interupts. I would hazard a guess that the may be
an issue with your NIC driver, try updating it with the most recent
version from the manufacturer.
 
G

Gary Chanson

David D. said:
I have W2K Pro SP4.

My system frequently crashes with a "Socket 0 error". It does not crash if
running in safe mode with no internet connection.

IRQ conflicts might be the culprit (although I could be wrong about that).

My system reports IRQ 11 conflicts:

11 RADEON 7500 SERIES
11 NEC PCI to USB Open Host Controller
11 NEC PCI to USB Open Host Controller
11 NEC PCI to USB Enhanced Host Controller
11 Win2000 Promise Ultra133 TX2 (tm) IDE Controller
11 HPT372 UDMA/ATA133 RAID Controller
11 CMI8738/C3DX PCI Audio Device
11 VIA USB Universal Host Controller
11 VIA USB Universal Host Controller
11 VIA USB Universal Host Controller
11 Realtek RTL8139/810x Family Fast Ethernet NIC

My other IRQs assignments are:

9 Microsoft ACPI-Compliant System
14 Primary IDE Channel
15 Secondary IDE Channel
8 System CMOS/real time clock
13 Numeric data processor
6 Standard floppy disk controller
4 Communications Port (COM1)
3 Communications Port (COM2)
1 Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
10 MPU-401 Compatible MIDI Device

Do you concur that IRQs is the likely culprit?

No, IRQ conflicts happen at a much lower level then socket errors.
Which IRQ 11 devices should I try to reassign? And to where?

How do I force them to a new IRQ?

Any advice would be greatly appreciated.

I don't have much information to go by, but I'd start by looking for
viruses and spyware.
 
D

David D.

The actual error message is "Windows Socket Error 0", on a dialog box with
an "OK" button. I can run perhaps 20 minutes before getting the Socket
Error crash.

There was no error message about IRQ conflicts, but there the IRQ 11
hardware is listed under the "IRQ Conflicts" tab of the System Information
tool.
 
D

David D.

Gary Chanson said:
I don't have much information to go by, but I'd start by looking for
viruses and spyware.

I have removed some spyware and viruses. There could be some residual
corruption, though.

It may not be the NIC driver, because I disabled the NIC, but I still get
the "Windows Socket Error 0" error.

I will try to find an upgraded NIC driver. What is the best way to
completely uninstall the old driver, so that, when the system recognizes the
NIC as new hardware, it won't re-use components from the old version of the
driver?

- David
 
G

Gary Chanson

David D. said:
I have removed some spyware and viruses. There could be some residual
corruption, though.

It may not be the NIC driver, because I disabled the NIC, but I still get
the "Windows Socket Error 0" error.

I will try to find an upgraded NIC driver. What is the best way to
completely uninstall the old driver, so that, when the system recognizes the
NIC as new hardware, it won't re-use components from the old version of the
driver?

Off hand, I don't know. If it's a driver that was supplied as part of
Windows, it may not be easy to replace short of doing a repair install.
If it was supplied with an add-on card or with the motherboard, it depends
on how the original driver was installed. If it used a setup.exe program,
you probably can simply run it again. If not, you probably have to find
the oemxxx.inf file that it installed and delete it and then redetect the
device.
 
Ad

Advertisements

J

John John

David said:
I have removed some spyware and viruses. There could be some residual
corruption, though.

You might want to use winsockfix and LSPfix and see if things improve.
Do a search on the net for those and get the Windows 2000 versions.

John
 
D

David D.

Gary, John, Bob,

Thanks for the advice and suggestions. I will follow up on them.

I have been running stably in Safe Mode *with* Networking, and *with*
Internet access. In normal mode, on the other hand, even with the NIC
disabled, I still get the "Windows Socket Error 0" crash. So it is probably
a component other than the NIC driver.

This may be a hard one to find. I can't even say what changed, because
it started as a rare, infrequent problem, and gradually became more
persistent over time.

But I will start with the winsockfix and LSPfix.

If you have any other thoughts, kindly share them. If I can find the
XP CD that I bought a long time ago, or even my original W2K CD, I might
just rebuild. But I have been searching the house for days for them, so I
do not hold out much hope.

Thanks again for your help.

- David
 
G

Gary Chanson

David D. said:
Gary, John, Bob,

Thanks for the advice and suggestions. I will follow up on them.

I have been running stably in Safe Mode *with* Networking, and *with*
Internet access. In normal mode, on the other hand, even with the NIC
disabled, I still get the "Windows Socket Error 0" crash. So it is probably
a component other than the NIC driver.

This may be a hard one to find. I can't even say what changed, because
it started as a rare, infrequent problem, and gradually became more
persistent over time.

But I will start with the winsockfix and LSPfix.

If you have any other thoughts, kindly share them. If I can find the
XP CD that I bought a long time ago, or even my original W2K CD, I might
just rebuild. But I have been searching the house for days for them, so I
do not hold out much hope.

A repair install might fix it, but you need the Windows Setup CD for
that.
 
B

Bob I

It's listing shared and conflicts, IF there was a conflict you would
receive a "resources error" that the recsources were unavailable.
 
Ad

Advertisements

J

Jarek Czekalski

David said:
I have removed some spyware and viruses. There could be some residual
corruption, though.
No one mentioned to uninstall the tcpip protocol. I would do this first.
Of course you reinstall it later.

I guess it helped me after something malicious had destroyed my network.

Regards
Jarek
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top