ICS gateway restarts on attempting to connect to an FTP, clients also make it restart

Sentry24

Junior Member
Sep 12, 2001
23
0
0
Well, I'm currently sharing my connection with 2 other computers, the cable modem connects to a win2000 sp2 machine that has two NICs: One SMC, the other Macronix based.


My problem is that when I attempt to connect to >SOME< ftps, either through a client PC or the gateway itself, the gateway reboots automatically.

Upon checking the event viewer, this is what is logged:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x804b1e38, 0x00000002, 0x00000000, 0x804b1e38). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini041802-01.dmp.

I figure it's some kind of IRQ conflict or something or other, but I could sure use some suggestions as to troubleshooting this.

My gateway has this hardware in it:

WD 1.6gb HDD
SMC NIC
Macronix based NIC
Matrox Mystique 2mb (oh the power!)
Acer 12x cdrom
Generic FDD

I used to have a SB16 in it and tried taking it out but it didn't resolve the problem.

From looking in the Device Manager, the IRQs are as follow:

(ISA) 0 System timer
(ISA) 1 PC/AT Enhanced PS/2 Keyboard (101/102-key)
(ISA) 3 Communications Port (COM2)
(ISA) 4 Communications Port (COM1)
(ISA) 6 Standard floppy disk controller
(ISA) 8 System CMOS/real time clock
(ISA) 12 Microsoft PS/2 Mouse
(ISA) 13 Numeric data processor
(ISA) 14 Primary IDE Channel
(ISA) 15 Secondary IDE Channel
(PCI) 5 Macronix MX98715 Family Fast Ethernet Adapter (ACPI) #2
(PCI) 9 SMC EZ Card PCI 10 Adapter (SMC1208)
(PCI) 11 Matrox Mystique PCI - English
 

Rhi

Member
Dec 29, 2001
135
0
0
It looks like that stop message is referencing IRQ2, which is a bridge to IRQs 8-15 on older systems. Win2k requires a fully ACPI compliant system. Have you checked the HCL for your devices? I would say you could remedy the situtaion by trying new drivers, maybe switching slots if possible, try a different NIC if handy.

Do a run>msinfo32 and carefully look at your resource assignments. Often though Windows reports no problem even though there obviously is one. Different NIC prolly fix it. Maybe this reading will help. You should be able to follow the instructions near the bottom and determine which driver&device is causing the problem.

-Rhi