DW75

1st, the following is the only stuff in the exceptioninfo.txt concerning 1.0B2 Code: c0000094 (Integer division by zero) Version: 1.0.0B2 (2007-04-10) Major: 5 Minor: 0 Build: 2195 SP: 4 Type: 1 Time: 2007-05-14 03:28:16 TTH: CWLBR24QOCVAJHKKX2A6KQORSW4IRCWPJH36EYA Code: c0000005 (Access violation) Version: 1.0.0B2 (2007-04-10) Major: 5 Minor: 0 Build: 2195 SP: 4 Type: 1 Time: 2007-05-20 14:53:47 TTH: CWLBR24QOCVAJHKKX2A6KQORSW4IRCWPJH36EYA Code: c0000094 (Integer division by zero) Version: 1.0.0B2 (2007-04-10) Major: 5 Minor: 0 Build: 2195 SP: 4 Type: 1 Time: 2007-05-22 17:42:20 TTH: CWLBR24QOCVAJHKKX2A6KQORSW4IRCWPJH36EYA 2nd, ever since upgrading to 1.0B2 im getting "Bad Pool Caller" windows stop errors. Usually after Apex has been running 1-2 hours since last time the system was rebooted. A few times however it has stayed running for alot longer. I have also got several crashes where only the program crashes and says dbghelp.dll is to blame.(forgotten exact message, sorry) If i want to revert to 0.4.0, can i simply reinstall it "over" 1.0B2?

Ever since "upgrading" to 0.3.0 Apex crashes frequently. Then i tested reinstalling 0.2.0 and it tends to stay running longer but still eventually crashes most of the time. Before upgrade, 0.2.0 would generally crash maybe 1-2 per week of serious usage(8+ hours per day). 0.3.0 rarely stayed running more than 1 hour before crashing. 0.2.0 reinstalled now runs anything from 30 minutes to 12+ hours before crashing. Have tested having zero other programs running, as well as running normally. Windows media player crashes sometimes when running at same time as Apex but otherwise i have seen no correlation. And the above image is the only error message that appears. Now for the FUN part however, as long as i dont click ok on the error message, Apex still up and downloads fine. Not quite sure if it starts new transfers as well but it certainly seem to complete anything already running just as if there had never been any crash. However, whats that about "your op syst dont support the functionality needed..."? Win 2K isnt supported by Apex? Its just the 2nd most used o/s today... Sounds rather odd? My system is Win 2K Pro on: MSI K7-D Master L 2*Athlon XP(MP) 2400+ 1.5GB RAM Geforce 7600GS SB Live 5.1 120GB Hitachi HDD 2* 200GB Samsung/Maxtor HDD via Q-Tec IDE Raid card Genica 10/100 NIC LiteOn CDRW/DVD-RW LiteOn CDRW I dont have the slighest clue as to how to reproduce the crash as they seem to happen whenever. They have happened while i have been running workstation software, while running BSplayer just as often as its happened when the system has simply remained online running Apex overnight or merely browsing the web.

Additional info... Doing some logsearching the other day, i found a couple crashes correlating with "Creative service for CD-ROM access" starting up. Disabled said service, and only had Apex crash twice since, and it stayed alive twice now for over 10 hours until i shut it down. Far to early to say anything certain how large the improvement is, but the number of crashes has definetly been reduced it seems.

I get one just as "useful" as Balders. Wasnt clear on that, my apology. Code: c0000005 Version: 0.2.0 Major: 5 Minor: 0 Build: 2195 SP: 4 Type: 1 Time: 2006-12-17 18:51:30 TTH: 5FC7C6TKY4DJBVMWNFZGQI4WUUSFAJUMYAJLJDA

As im running dual physical cpu:s thats not an option, as it would require me to get XP Pro, and then it would almost be cheaper to get a new system altogether, which is also not an option. Yeah, and thats a real problem as even though its happened, certainly 50+ times already, there is no pattern in the crashes. I tested a bunch of stuff already, to no effect, RAM, cpus, HDD, mainboard all checks out ok... As i said: Its fully updated as of a few weeks ago. Dont forget, 0.2.0 worked decently, but once 0.3.0 had been installed once, even reinstalling the former only reduced the number of occurences, it didnt remove them. So, is there something the latter version installs, but not the former?

Its fully updated as of a few weeks ago.

Can you give any information on how to get the damn thing to "crash properly"(and before 0.3.0 upgrade this error msg did not appear the few times it crashed)? And why it can stay running even after it crashed(because that one really seems too odd)... Pity otherwise, guess ill have to find another client to run, too much of a nuisance to get errors all the time, because a couple of times it caused the whole system lock up. So far fortunately without any loss of work data.