DC++(0.707) repeated crashing: instruct at 0x7c901010 refrenced memory at 0x00000030 could not be read
Error: "The instruction at 0x7c901010 referenced memory at 0x00000030. The memory could not be read." This error is consistent with all the crashes so far. Uptime ranges from (max)1.5 days to (min)3 minutes, median of several hours.
Symptoms:
Crash dialog box pops up, with Close and Debug options. So far, each of the times, the hex numbers have been the same.
DC++ is usually minimized, however it can be restored after the dialog box pops up, and while all new connections are shown as "connection timeout", all existing transfers - including multipart transfers - continue until the connection fails or is closed or completed from either end, apparently. On more then one occasion, I have let transfers continue after getting the first error popup and gotten a second. Hitting Close, of course, immediately closes the DC++ application.
Hardware and Environment:
WinXPSP2, Netgear 10/100 hub, connected via Ethernet.
SPI firewall has a large range of port forwarding to this machine.
Functional connecting and downloading - although search has not worked the two times I've tried it.
Installed for less than a week, formerly ApexDC - switched after their bungled handling of their forced upgrade.
3 hubs, 5 slots.
Extensive download queue: 8mb in the Queue.xml, though starting with a clean Queue.xml also crashed after a few hours with the same error.
Nothing shown of the crash in system.log, DrWatson does not start when I click debug. No other dump or log files found where I tried looking for them.
HijackThis, AdAware, SpybotSD, and AVG show no anomalies, and no unknown / unapproved software.
Software:
Kerio firewall v4.2 (old ver) - DC++ given a full exclusion on all ports/addresses
AVG 8 - and YES, I am trying to find a better antivirus - After they've turned the best, most efficient no-frills AV product into DDOS bloatware . . . (sorry. : )
All other security software or anything else that may affect performance (Dragon Naturally Speaking, Azureus, etc.) disabled or uninstalled to ease diagnosing the cause of the error.
I had moved to ApexDC after having similar / the same problems with 0.699 and 0.704 - though I don't recall the hex at this point. With 0.704, I believe, the behavior was different - "This application has encountered an error and must close" was the dialog, however the behavior roughly described in the Symptoms section above still applies - connections usually continued until the crash dialog was closed, and only then would the application terminate, although new connections weren’t formed. In the case of 0.704, these crashes usually deleted or corrupted whatever files were in transit or completed , or possibly even opened for reading at the time the crash occurred - I lost several dozen files to the crashes, and many more were corrupted. Hence my move to ApexDC.
I'd really like to stick with the core DC app, so if one of your troubleshooters would like to contact me direct, I will provide any and all info that they would think might help, and run any tests you believe might help identify the issue. I have a brain, so it shouldn't be too difficult for you. : )
Thanks!
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- DC++ Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
|
Revision history for this message
|
#1 |
|
Revision history for this message
|
#2 |
|
Revision history for this message
|
#3 |
|
Revision history for this message
|
#4 |
|
Revision history for this message
|
#5 |
|
Revision history for this message
|
#6 |
|
Revision history for this message
|
#7 |
Can you help with this problem?
Provide an answer of your own, or ask joshuack for more information if necessary.
