Discussion Locked

WinXP Hang with BSOD related to Explorer

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a bit of a problem (in XP only Everything else works fine, I haven't tried Home Edition). You see, when I connect to a share via Windows Explorer or I connect to this particular machine (or from) in a way that is directly related to computermanagement, I get a STOP error on tcpip.sys. I can search the network from my pc, I can access my shares, remote desktop, print, ftp, ect from elsewhere. The pc also has no problems relaying that kind of data.

The full error is:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

STOP: 0x0000001 (0x0200000C, 0x00000002, 0x00000000, 0xB7A2137C)

tcpip.sys - Address B7A2137C base at B7BA1F000, DateStamp 3b7dc580

The system is an Athlon ThunderBird 1200 w/ 266 FSB, Asus A7V133 MotherBoard with latest BIOS, 1280 MB of PC133 SDRAM (Kingston), 140 GB Hd space running on Promise FastTrack100 RAID Controller, 3COM Etherlink 3C905B-TX, ATI All in Wonder 128 Pro, SB Live Platinum, Toshiba DVD-ROM and HP CD-Writer 8200.

I hope someone has an Idea because I am fresh out.

Verily,
Bryan

4 replies

by timthetoolman

Do you have the latest drivers for your 3COM Etherlink 3C905B-TX ?

My guess would be that its the nic's driver thats crashing.

I wouldn't rely on the Microsoft drivers. Get the ones specifically for the card if possible - but make sure they'rewritten for XP.

Cheers,
Tim.

by b_t_adams

Update:

I was able to steer around the problem by disableing anonymous enumeration of the SAM and Shares.

I also bought a new network card (a 3COM Etherlink 3C905C) and this seemed to reduce the instances of the problem.

When I upgraded my video card (which I suspect was part culprit) to the All-in-Wonder Radeon 8500DV and CDRW to a Yamaha. The problem disappeared.

I suspect that the issue was a conflict in memory addressing made by the video card and network card when in the Windows XP kernel which has been optimized for performance from Windows 2000. This optimization might have made it vulnerable to that particular configuration in those particular circumstances.

This discussion is closed to new replies.