This one is my favorite:
 

This one is my favorite:

XOLOX caused an invalid page fault in
module <unknown> at 0000:00000000.
Registers:
EAX=00000000 CS=0000 EIP=00000000 EFLGS=00000000
EBX=00000000 SS=0000 ESP=00000000 EBP=00000000
ECX=00000000 DS=0000 ESI=00000000 FS=0000
EDX=00000000 ES=0000 EDI=00000000 GS=0000
Bytes at CS:EIP:

Stack dump:


This one’s not too bad:

Exception EInvalidPointer in module XOLOX.EXE at 000027FC.
Invalid pointer operation

A rare treat:

Exception EExternalException in module XOLOX.EXE at 011EAAF0.
External exception C000001D.

Here’s a new one:

Exception EAccessViolation in module XOLOX.EXE at 00003E82.
Access violation at address 00403E82 in module XOLOX.EXE. Read of address FFFFFFFF


I get these errors when I exit Xolox from the system tray. Is this supposed to be some sort of punishment for closing Xolox during a upload?? Its just that I don’t like to have it running when I play HalfLife, it becomes a lag generator.
000099 :p :rolleyes: :D ;)

Hi Gliptal,

LoL. You do have humor !!!:D

The bad thing is, that it doesn't crash in our test situation when people are downloading from XoloX.

I would like to solve the problem, but I dunno where to start..

Greets,
Pasman

Hmm...
 

Preface:

When using AOL, sometimes you get kicked off when other people on your account sign on because the network sucks and doens't always check roperly if someone is already on. When this happens, Programs think there's an internet connection there, but the server has stopped responding, so nothing gets through. I regognize this by looking at my sysmon bytes sent/recieved per second rates; when they drop down to almost nothing I'm disconnected, and know it'll take AOL a couple minutes to 'time out' and close my network stuff. So I usually just force-kill AOL and start it again.


The error described above just happened to me today (version 1.11)... The conditions were as such:

AOL closed my connection, so web pages stopped resolving, IRC stopped recieving messages, and XoloX started looking for hosts as it was disconnected from the network. Before killing AOL, I closed down XoloX, and got the error. All registers equaled 00000000. All the times I can think of actually crahsing with XoloX have been when it is disconnected from the network un-gracefully. I'll do some tests later tonight closing AOL, and unplugging from the wall, to see how network termination affects stability. If you don't have dial up, try pulling the plug on your LAN for a similar effect.

Of course, I'm using 1.12 now, which runs with 5 or 6 threads at any given point (only creating two more temporarily when telling it to share the D drive with over 100 folders.) so it may be impossible to re-create the bug now ;-p

I think I figured it out
 

I should have thought of this before, I’m running the evil Norton Antivirus corporate edition. I disabled Norton and Xolox works fine.

I don’t have the retail version of NAV, has anyone had this problem with the retail version?