From: John Barnes on
Interestingly, if you Google the problem, one specific problem down to the
590 chip has to do with emule, so I would skip that one.


"Carlos" <Carlos(a)discussions.microsoft.com> wrote in message
news:ED95E38A-3103-4D33-A4EA-25B0E2C728FA(a)microsoft.com...
> Can you use another file sharing program?
> e-mule, bitcomet, ares, etc.?
> Give them a shot and see what happens.
> Carlos
>
> "S Murder" wrote:
>
>> It worked on my old computer though. And I don't think there's a problem
>> with
>> the ports, or else it woudn't work at all. The program can operate fine
>> for a
>> while, but I get the fatal error when the traffic heavily increases.
>>
>> "Carlos" wrote:
>>
>> > Hi:
>> > Does this BSOD happen only when using this file sharing program?
>> > If so, try using another one and see what happens.
>> > There are a lot hanging around there.
>> > For XP x64 I am using the NVidia NForce 4 chipset drivers v 6.86.
>> > I let it install everything except the dreaded NVidia firewall which
>> > happens
>> > to have a different name that I can't recall.
>> > Also try opening the ports that ApexDC++ requires, both in your Windows
>> > Firewall and in your router, if you happen to have one.
>> > Carlos
>> >
>> >
>> > "S Murder" wrote:
>> >
>> > > I already installed it and then uninstalled it. I'll try again
>> > > though.
>> > > I'm using ApexDC++. I just have a lot of open connections with it.
>> > >
>> > > "John Barnes" wrote:
>> > >
>> > > >
>> > > > If you followed Jane's instructions you should not have the file on
>> > > > your
>> > > > system or it won't be used and you can rename it with no impact.
>> > > > INSTALL the nVidia firewall and then uninstall it and the file you
>> > > > refer to
>> > > > will either be gone or not used.
>> > > > Again, what 'file sharing program' are you using, and what are you
>> > > > trying to
>> > > > do when the problem happens.
>> > > >
>> > > >
>> > > > "S Murder" <SMurder(a)discussions.microsoft.com> wrote in message
>> > > > news:D750B80F-0143-40F1-B324-7B26589C5017(a)microsoft.com...
>> > > > >I uninstalled the nVidia Network Access Manager, which had the
>> > > > >Firewall,
>> > > > >but
>> > > > > I'm still having problems. Do I need a different LAN driver?
>> > > > >
>> > > > > "Jane C" wrote:
>> > > > >
>> > > > >> NVTcp.sys It's that dreaded nVidia firewall again. If you
>> > > > >> haven't
>> > > > >> already
>> > > > >> done so, INSTALL the nVidia firewall and then UNINSTALL it. I
>> > > > >> know,
>> > > > >> sounds
>> > > > >> daft, but it has to be installed in order to be uninstalled. It
>> > > > >> has been
>> > > > >> an
>> > > > >> endless cause of problems in XP x64.
>> > > > >>
>> > > > >>
>> > > > >> --
>> > > > >> Jane, not plain ;) 64 bit enabled :-)
>> > > > >> Batteries not included. Braincell on vacation ;-)
>> > > > >> "S Murder" <SMurder(a)discussions.microsoft.com> wrote in message
>> > > > >> news:0CB8FAD0-D4B7-4E7B-AB0A-ECEE161B44BC(a)microsoft.com...
>> > > > >> >I reinstalled Windows for the new mobo. I also installed the
>> > > > >> >mobo
>> > > > >> >drivers.
>> > > > >> >
>> > > > >> > I just got the mobo a day or 2 ago.
>> > > > >> > I'm using XP Pro x64.
>> > > > >> > Yeah, it's really IRQL. It was a typo.
>> > > > >> >
>> > > > >> > In the System Event Viewer, I found this:
>> > > > >> > The computer has rebooted from a bugcheck. The bugcheck was:
>> > > > >> > 0x000000d1
>> > > > >> > (0x0000000000000068, 0x0000000000000002, 0x0000000000000001,
>> > > > >> > 0xfffffadfc69c0152). A dump was saved in:
>> > > > >> > C:\WINDOWS\MEMORY.DMP.
>> > > > >> >
>> > > > >> > I think it's the same code that the blue screen showed. It
>> > > > >> > also said
>> > > > >> > there
>> > > > >> > was a problem with NVTcp.sys
>> > > > >> >
>> > > > >> > "John Barnes" wrote:
>> > > > >> >
>> > > > >> >> It would be real helpful if you could give us some sort of
>> > > > >> >> idea what
>> > > > >> >> you
>> > > > >> >> are
>> > > > >> >> doing when this happens. Has it always happened since you
>> > > > >> >> installed
>> > > > >> >> the
>> > > > >> >> new
>> > > > >> >> mobo or since you installed some hardware. Also, are we
>> > > > >> >> talking about
>> > > > >> >> IRQL
>> > > > >> >> not IRWL What is your error code that goes with it? At
>> > > > >> >> least that
>> > > > >> >> would
>> > > > >> >> be a start. Also are you running XP PRO X64 or XP Pro.
>> > > > >> >>
>> > > > >> >>
>> > > > >> >> "S Murder" <SMurder(a)discussions.microsoft.com> wrote in
>> > > > >> >> message
>> > > > >> >> news:054CCF2F-4785-4B8E-B97A-4E6D3BB6CC21(a)microsoft.com...
>> > > > >> >> >I just got a new mother board
>> > > > >> >> > (http://www.epox.com.tw/eng/news_content.php?serno=50) and
>> > > > >> >> > keep
>> > > > >> >> > getting
>> > > > >> >> > the
>> > > > >> >> > blue screen of death with this error. I think it happens
>> > > > >> >> > when using
>> > > > >> >> > my
>> > > > >> >> > file
>> > > > >> >> > sharing program (maybe too many network connections). What
>> > > > >> >> > should I
>> > > > >> >> > do?
>> > > > >> >>
>> > > > >> >>
>> > > > >>
>> > > > >>
>> > > >
>> > > >

From: Tony Sperling on
As I am dual-booting, I installed and removed it for Win2K, then didn't
install it for XP x64, since I had just done it! Well, it was late and I
needed a bra on my glasses for the bags under my eyes, next morning Charlie
set me straight. . .


Tony. . .