Please supply information on WInMX Crashing Here

[wavoka]

Over Christmas I noticed a lot fewer transfers. I thought it was just the holidays. Today I was getting a DL and had folk DLing from me when I got the dreaded error message. I'm running 1.9 patch with IE 6.0 on XP Pro with Stopsign. Yesterday my Stopsign download guard errored out. I restared it and ran a scan. It found nothing.

I suspect it is the enemy.

[wavoka]

Can't cut error message details and paste. It says error was in the temporary files and mentions appcompatt.txt.

Doe this help:
szApp Name winmx.exe
szApp Ver 3.5.4.0
szMod Name hung.app
szMod Ver 0.0.0.0
Offset 00000000

Checking peer caches as of time of post (3.48 CDT):

Cache 9 67.18.233.36 offline across the board.  Other primaries okay.

Anyone tried the open nap feature to see if it still works?

[wavoka]

Just before WinMx crashes I see multiple WinMx icons in my systray. This happened with all or the first WinMx patches.

[dlc247]

An Update: I was able to overcome WinMX crashes by completely stripping WinMX from my PC. The app seemed to be corrupted. I re-installed 3.5.4 from the winzip file and so far its ok.

[FasterThanLightSpeed]

Same crap as all of you. I just started having the crashes last night.

I run WinMX 3.54 Beta
Install 1.9 Patch
Secondary Conn.
Aol ISP  (Dial Up )
Mozilla & IE 6 Browsers
Havnt checked modem make
Microsoft Windows XP SP2
No PeerGuardian
No major program changes, iTunes for my ipod, thats it.

I hope it aint the F'n RIAA, cheap whores.

Hope you guys put a knack on this one, I dont want to switch over to LimeWire, They have a lot of sueing cases.




AARGGGGGGGGGGGGGHHHHHHHHHHHH!!!!!

Oh, by the way im running that sfc scan right now, and Im going to take Winmx completely off my pc and install it again.

[jfoc567723]

I just tried to connect to MX this morning, and it connected, but within a minute i got the dreaded error.  this is what it said at the top.

Error Signature
AppName: winmx.exe    AppVer: 3.5.4.0    ModName: ntdll.dll
ModVer: 5.1.2600.2180    Offset: 00011e58

then when you click on technical info it has a very long list of things.  too long to put in one of these messages.

 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\5bcc_appcompat.txt

I don't know if any of  this helps, but thought i would post it for you.

[i share if u share]

Just an extra observation in case its relevant or of help. My WinMX 3.53 with the .dll from 1.9 installer crashes when I use Opennap without being connected to the WinMX network. Never done this before.

[tatman]

Win mx is repeatedly crashing as soon as a transfer is initiated. this occured after a break in internet access and a reboot of my PC

System: Windows XP SP2
Intenet: ADSL
Vers: 3.54
Primary user

using windows firewall and peer guardian
MX monitor installed
no new software installed, scan of PC performed at 5 am this morning log shows no action required and no infected items

error report as follows:

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="WinMX.exe" FILTER="GRABMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="errcatch.exe" SIZE="32768" CHECKSUM="0x8EF0BD46" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="08/28/2002 21:54:26" UPTO_LINK_DATE="08/28/2002 21:54:26" />
    <MATCHING_FILE NAME="Install-1.9.exe" SIZE="103180" CHECKSUM="0x7A8DA4FC" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="10/04/2005 14:26:31" UPTO_LINK_DATE="10/04/2005 14:26:31" />
    <MATCHING_FILE NAME="uninstall.exe" SIZE="94208" CHECKSUM="0x2F13DF12" BIN_FILE_VERSION="1.0.0.1" BIN_PRODUCT_VERSION="1.0.0.1" PRODUCT_VERSION="1, 0, 0, 1" FILE_DESCRIPTION="WinMX Uninstaller" COMPANY_NAME="Frontcode Technologies" PRODUCT_NAME="WinMX Uninstaller" FILE_VERSION="1, 0, 0, 1" ORIGINAL_FILENAME="Uninstaller.EXE" INTERNAL_NAME="Uninstaller" LEGAL_COPYRIGHT="Copyright (C) 2001 Frontcode Technologies" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1CDDE" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.1" UPTO_BIN_PRODUCT_VERSION="1.0.0.1" LINK_DATE="09/06/2002 09:46:31" UPTO_LINK_DATE="09/06/2002 09:46:31" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="uninstallmx.exe" SIZE="33948" CHECKSUM="0x7A8DA4FC" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="10/04/2005 14:26:31" UPTO_LINK_DATE="10/04/2005 14:26:31" />
    <MATCHING_FILE NAME="WinMX.exe" SIZE="1069056" CHECKSUM="0x882DBE43" BIN_FILE_VERSION="3.5.4.0" BIN_PRODUCT_VERSION="3.5.4.0" PRODUCT_VERSION="3.54" FILE_DESCRIPTION="WinMX Application" COMPANY_NAME="Frontcode Technologies" PRODUCT_NAME="WinMX" FILE_VERSION="3.54" ORIGINAL_FILENAME="winmx.exe" INTERNAL_NAME="WinMX" LEGAL_COPYRIGHT="Copyright (C) 2004 Frontcode Technologies, ALL RIGHTS RESERVED." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x113548" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="3.5.4.0" UPTO_BIN_PRODUCT_VERSION="3.5.4.0" LINK_DATE="12/13/2004 03:58:48" UPTO_LINK_DATE="12/13/2004 03:58:48" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="ws2_32.dll" SIZE="32768" CHECKSUM="0xE30BF3B6" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="10/11/2005 17:18:48" UPTO_LINK_DATE="10/11/2005 17:18:48" />
    <MATCHING_FILE NAME="patches\Install-1.9.exe" SIZE="103180" CHECKSUM="0x7A8DA4FC" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="10/04/2005 14:26:31" UPTO_LINK_DATE="10/04/2005 14:26:31" />
</EXE>
<EXE NAME="ntdll.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="ntdll.dll" SIZE="708096" CHECKSUM="0x9D20568" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="NT Layer DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="ntdll.dll" INTERNAL_NAME="ntdll.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xAF2F7" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:56:36" UPTO_LINK_DATE="08/04/2004 07:56:36" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="983552" CHECKSUM="0x4CE79457" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFF848" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:56:36" UPTO_LINK_DATE="08/04/2004 07:56:36" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

Exception info:  code:0xc0000005    Flags 0x00000000
record 0x00000000000000000 adress: 0x000000007c93426d

system info

Windows NT 5.1 build 2600
CPU vendoe code 756E6547 - 49656E9 - 6C65746E
CPU version 00000F29 CPU Feature code BFEBFBFF
CPU AMD Feature code: 00D2E824

Module 1

WinMX.exe
image base 0x00400000 image size 0x00000000
checksum 0x00113548  Timestamp: 0x41bd1378

note sure if that helps

[passer]

Version 3.5.4; XP Pro, sp2; McAfee, SpywareGuard, etc. etc.
I was OK up till the 28th Dec, but started up yesterday 29th and crashed with the error. Tried many times and gave up - assumed the cache server was offline. Today I tried again, same problems. I stripped it right out of the PC, and reinstalled - no joy. Stripped it out again and installed 3.53 - same result. Primary or Secondary - no difference. Restored the PC back to the 28th - no joy.
When I connect as a Primary, if I don't touch anything, I get 4 Primaries and a huge flood of Secondaries before it crashes (that old problem...).
On one occasion, firing up as a Primary, I got 3 secondaries attached before getting a Primary -at which point it crashed again.
I have also noticed the multiple iterations of the icon on the taskbar before it terminates.
If I go into Chat, it usually crashes immediately, though as a Secondary, I managed to get a partial room-list, and get into one...before crashing.
On one occasion I managed to put in a search. I chose Rolling Stones, and got an immediate flood of fake files. Haven't seen any fake files for ages, so I assume that the DLL file has been compromised in some way.

[tatman]

OK having de installed and re installed still kept crashing

then did another reboot and now everything is working fine again

any ideas?

steve

[Anonymous]

OK having de installed and re installed still kept crashing

then did another reboot and now everything is working fine again

any ideas?

steve

for get that I'm back to crashingconstantly as soon as a connection is made irrespective of whether i have a priomary or secondary connection... we need this sorted fast as I know friends who are leaving WinMx in droves as they cant keep up with all the problems and I must admit I'm ready to agree that is more of a constant problem than its worth anybody with any ideas?

steve

[dlc247]

Another Update: As I said before after stripping WinMX completely and re-installing it everything ran fine. Fine, that is until this a.m. I brought up X-Netstat and BAM! the dreaded error message, "WinMX has encountered a problem and has to shut down", came on screen. This time not only did it shut down but the app actually was uninstalled. That's right, the desktop icon was gone, the WinMX folder in Programs was gone, too. I still have a copy of the app so I can reinstall but, what in hell happened? I don't have a clue.

I will go through the drawn out reinstall procedure again but, at this point things look gloomy .

However, I'm not surrendering, that's what the darkside  :twisted:  wants us all to do.

WinMX now and forever!

[tatman]

I wonder whether some prog is being downloaded and inititiatuing on start up replacing the trouble free win mx and trying to delete itself... is this feasible or am I just getting totally paranoid about conspiracies.

Keep up the good work guys and thanx for trying to sort the problem, hope there's a fix soon

steve

[Anonymous]

OK having de installed and re installed still kept crashing

then did another reboot and now everything is working fine again

any ideas?

steve

for get that I'm back to crashingconstantly as soon as a connection is made irrespective of whether i have a priomary or secondary connection... we need this sorted fast as I know friends who are leaving WinMx in droves as they cant keep up with all the problems and I must admit I'm ready to agree that is more of a constant problem than its worth anybody with any ideas?

steve

OK have cracked the problem (at least in my case) its MXMonitor that is causing winmx to crash have de-installed and re-installed monitor but the problem persists). disable monitor and win mx runs smoothly.; OK now the monitor issue to sort if you could think 0of a solution ;@)

[Anonymous]

ok spoke to soon (wont post again until you find the problem) it works fine as long as i dont attempt to do anything in the program eg. search browse etc.

[fEEt]

Its not mx monitor cos I don't have it.

Heres a screenshot of the error...

[Me Here]

As of right now the best Advise I can give everyone experiencing the crashes is to do this

Rename your current C:\Program Files\WinMx folder to WinMx2

Now install the Install 1.9 for the 98/ME system onto your xp.  This will give you the olepro32.dll patch and WinMx Version 3.53.

Restart your WinMx and let me know how you do.. please

[fEEt]

Rename your current C:\Program Files\WinMx folder to WinMx2

Now install the Install 1.9 for the 98/ME system onto your xp. This will give you the olepro32.dll patch and WinMx Version 3.53.

Yeps...that worked for me. Thanx lots!  

[Me Here]

Good.. keep me posted on this.. and bear in mind this patch does NOT block the flooders.. although thanks to the pie patch users its almost impossible to actually stop the riaa now.. i still recommend you use the peer guardian if your on a primary connection with our block list..

https://www.winmxworld.com/tutorials/block_the_riaa.html

[Eddy Belly]

i got no probs here ME

OS: winxp pro corporal with sp2
Connection type: Cable
Winmx version: 3.54 beta 4
patch: https://www.winmxgroup.com/Install-1.9.exe (deleted old winmx, made a fresh install when it came out)
Primary user ( P=7 S=8 )
Firewall: Xp
Router: None
Bot: MxConrtol 1.3  ( unpatched ( copy and paste room for entry))
also running: AVG PG2 ( fully updated lists ), Filetopia, MSN,

as i said i have not had any probs at all been online for 77.5 hrs