Shareaza crashes every few hours

[edgars777]

After leaving Shareaza alone & working fine for a few hours, I come back and find a message from Windows XP that "Shareaza had to close.. work may be lost... Do I want to send a report to Microsoft" (roughly). If this is not happening to everybody, it's probably something about my installation. Does anyone have any suggestions of how to fix this, or how to gather more information?

[cyko_01]

what version are you using? This problem was commonly reported in prior versions. If you have not upgraded to 2.4.0.0 (latest release at this time) please do so

[edgars777]

I can confirm My Sharaza self-identifies as Shareaza File Sharing Client 2.4.0.0.

There has been another crash. This time I have gathered more data. The windows crash message

Shareaza.exe has encountered a problem and needs to
close. We are sorry for the inconvenience.
If you were in the middle of something, the information you were working on might be lost.
Please tell Microsoft about this problem.
We have created an error report that you can send to us. We will treat
this report as confidential and anonymous.
To see what data this error report contains, click here.

And when I click there, the following info is displayed.

Error signature -
AppName: shareaza.exe AppVer: 2.4.0.0 ModName: unknown
ModVer: 0.0.0.0 Offset: d01df601

To view technical information about the error report, click here.

And when I click there I get a very long report which starts out

The following information about your process will be reported:
Exception Information
Code: 0xc0000005 Flags: 0x00000000
Record: 0x0000000000000000 Address: Oxffffffffd01df601
System Information
Windows NT 5.1 Build: 2600
CPU Vendor Code: 756E6547 - 49656E69 - 6C65746E
CPU Version: 00000F41 CPU Feature Code: BFEBFBFF
CPU AMD Feature Code: 00DBE824
Module 1
Shareaza.exe
Image Base: 0x00400000 Image Size: 0x00000000
Checksum: 0x0057caeb Time Stamp: 0x48e39e8c
Version Information
Signature: feef04bd
StrucVer: 00010000
FileVer: (2.4:0.0)
ProdVer: (2.4:0.0)
FlagMask: 0000001f
Flags: 00000000
OS: 00000004
FileType: 00000001
SubType: 00000000
FileDate: 00000000:00000000
Module 2
ntdll.dll
Image Base: 0x7c900000 Image Size: 0x00000000
Checksum: 0x000bc674 Time Scamp: 0x49901d48
Version Information
Signature: feef04bd
StrucVer: 00010000
FileVer: (5.1:2600.5755)
ProdVer: (5.1:2600.5755)
FlagMask: 0000003f
Flags: 00000000
OS: 00040004
FileType: 00000002
SubType: 00000000
FileDate: 00000000:00000000
Module 3
kernel32.dll
Image Base: 0x7c800000 Image Size: 0x00000000

And so on. I stopped hand transcribing the information here. But I think the same info, in a less well formatted form, was placed in a file, which I will attach.

[old_death]

Try using one of the debug builds you can download on the debug builds page (link on the bottom of the Downloads page) (make sure you use one of the debug builds and not one of the release builds) and report back once you got an other crash (it will ask you to report the crash. Either you do this (including an error description (your operating system, system RAM etc. as well as description of what you did when it crashed - even if you did nothing when it crashed - as well as the networks you were using (gnutella, G2, ed2k, BT, IRC,...) etc.) or you save the crash report and post it here including the same description. It is important to note which revision of the debug builds you were using when it crashed.


mfg,
Old

[edgars777]

Can't install debug version. Curiouser and Curiouser.

I downloaded the latest debug version

Shareaza_2.4.0.4_Win32_Debug_r8180_2009-09-11.exe

But when I try to install it, I get an error message.

A malware has been detected on your system at C:\WINDOWS\system32\pxwma.dll, please remove it with a virus/malware scanner before Installing Shareaza. Do you want to exit now?

I scanned this system file with both Mcafee and Malwarebytes, but they didn't find a problem. I've RARed the file and attached it here. What should I do now?

[wiggindesigns]

I am submitting it to http://www.virustotal.com

Also, Mcaffee is one of the worst AVs, though Avira and AVG are just as bad with not detecting or detecting too many false positives. (Nod32, kapersky, etc are ok)



Information:
http://www.neuber.com/taskmanager/proce ... a.dll.html

http://www.virustotal.com/analisis/1566 ... 1252889805

http://www.bleepingcomputer.com/uninsta ... SONIC.html



It is part of the Kodak Easyshare software(Or Sonic/Roxio). It wasnt detected by any of the antivirus programs, and I am waiting for the result on cwsandbox. I wouldnt say its malware unless you dont have kodak easyshare or roxio installed.

[edgars777]

Thanks for the advice. I found a copy of Security Task Manager Version 1.7f. It does not even find pxwma.dll, much less say anything bad about it. I do have Kodak Easyshare installed, and Roxio EZ CD Creator 5. The date on the file is 4/4/07, so it's been there a long time. I'm interested in what you find out, but for now I think there isn't really a problem with this file. Can I force the Shareaza debug version to install anyway?

[old_death]

[wiggindesigns]

[collegiate]

I too am experiencing similar regular Shareaza crashes usually within say 1 hour of initiating a session. This has now been ongoing for several months.
Error screen says "A crash has been detected by Bugtrap" followed by "Exception Reason - Shareaza.exe caused ACCESS_VIOLATION at 001B:4EC674B2".
I am using Shareaza version 2.6.0.0 Release 32-bit (r9169 20120603).
PC OS is XP SP 3, Intel Core2 Quad CPU - 2.40GHz, 2 GB of 2.4 GHz RAM.
Appreciated any thoughts.

[edgars777]

I was surprised this thread is still active. I haven't used Shareaza for years. I'm now a Vuze user and I find it, along with torrent sites like PirateBay and KickAss to be a very reliable source of files I want, mainly movies and TV shows, but also PC applications and porn.

[old_death]

You might want to try v2.7.0.0 which has been released yesterday:
viewtopic.php?f=5&t=1571

[collegiate]

Thanks for the update Old_Death, I'll give it a try.

Old habits die slowly edgars_777, I've tried Vuze but still come back to Shareaza.