Event ID 1000 only with linksys router

[Joel]

From event log..........

Event 1000
Faulting application ****.exe, version 0.0.0.0, faulting module *****.dll,
version 0.0.0.0, fault address 0x000d1efe.


I don't have this problem with the Dlink 524 router, but I prefer to use the
linksys befsr41 because it is easier to set up and for some reason my pings
are higher on the Dlink. I get this error with the old firmware and the new
firmware. I have dloaded all MS updates.

Here is one more clue I have proven. It only does this when I run a game
server on my desktop and try to connect to the game using my laptop. It does
not matter if I connect through the lan or the internet, because I get the
same error either way and then the game shuts down.

Any ideas?

 

[Joel]

BTW, this did not happen when I was using XP SP2 Pro. But I just reformatted
and used the XP home edition that came with my laptop. I guess if I can't
figure it out, I am going to have to put XP Pro back on there just to rule
that out. Also, this problem is all over the internet in google, but I have
found no solution.

 

[Adrian Grigorof]

What is the application specified in the event description? There are quite
a few flavors of event id 1000 "Faulting application...". See:

http://www.eventid.net/display.asp?eventid=1000&eventno=1475&source=Application Error&phase=1

There is a comment about a game causing this but the culprit was the video
card driver.

Did you install some software from Linksys?

 

[Joel]

I am afraid you are probably right about the video card driver. I am using
the HP-zd8000 notebook (really a desktop made into a laptop) with the ATI
x600 mobility video card. I have heard alot of complaints about the video
card driver. ATI doesn't support it; they say to go to the HP site to get
the driver, which I have done.

Then again, the game will shut down on the desktop too and give me the same
error. Although I have an expensive ATI card in that desktop comp, I have
never had problems in it before connecting the router. I really think this
is going to be a router problem.