winmx has to close error

[dabud]

winmx 3.54  winmxworld 3.o patch   win xp sp2  P4 2.4 ghz  1.0 mb ram


i keep getting an error window  that states "Winmx has to close"    when this occurs  winmx freezes and i have to reboot
this happens fairly often  and usually when i am getting a dld that i really want.

On the advice of someone from winmxworld help room I ran   "%SystemRoot%\system32\eventvwr.msc /s" and checked when and what error was occuring and got this info:

Event Type:   Error
Event Source:   Application Error
Event Category:   None
Event ID:   1000
Date:      6.9.2007
Time:      8:21:31 PM
User:      N/A
Computer:   DABUD
Description:
Faulting application winmx.exe, version 3.5.4.0, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00011e58.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 77 69 6e   ure  win
0018: 6d 78 2e 65 78 65 20 33   mx.exe 3
0020: 2e 35 2e 34 2e 30 20 69   .5.4.0 i
0028: 6e 20 6e 74 64 6c 6c 2e   n ntdll.
0030: 64 6c 6c 20 35 2e 31 2e   dll 5.1.
0038: 32 36 30 30 2e 32 31 38   2600.218
0040: 30 20 61 74 20 6f 66 66   0 at off
0048: 73 65 74 20 30 30 30 31   set 0001
0050: 31 65 35 38 0d 0a         1e58.. 


Is there anything in the above that may tell me what the problem is [sorry don't know how to interpret]

After that I ran   sfc/scannow  from command prompt  but  no errors were found .

I would like to finally get rid of this  problem   can anyone help?    The peeps in the winmxworld help room suggested I should talk to KM  that maybe he would have a solution.
thank you.

[GhostShip]

It doesnt look like there is anything in that report that can be used to deduce the problem 

Can you try something for me please ?

In your Program Files folder can you make a new folder for winmx called Winmx1 and reinstall your winmx to there using fresh copies of the install files , then remove the old winmx folder and see if that makes a difference.

I have had this problem myself and doing the above seemed to resolve it, the important part is making sure you dont re-use the old folder.

[dabud]

i'll try anything at this point.
If it is important to not reuse the old winmx folder would uninstalling winmx, doing a search on winmx, deleting any reference and clearing all registry references to winmx help?

I will follow your suggestion and try that  but would like to know if doing the above is the same or better?
thank you for speedy reply.

[Me Here]

Dabud actually WinMX doesnt usually have any regestry issues or entries so its best to just either uninstall using the Control Panel > Add/Remove Programs or its also safe to just delete the folder in C:\Program Files\WinMX  because its  basicaly all located right there.

[dabud]

thank you Me Here

I followed Ghostship's instructions and am now running a entirely new winmx. [ty Ghostship]

Here's hoping!!

I know I am not the only one having this problem, I am trying to encourage more peeps to post here regarding this issue.
Hopefully, one day, it will be solved.

[dabud]

Well so much for here's hoping!!
Not 10 minutes after I posted, I got the "Winmx has to close" message again!

Here is the event info, don't know if it will help tho'.  UNforntuneatly it means nothing to me.
Would it help to post the info, say, from the last five times Winmx dumped?  [As a comparison?]
The new Winmx I installed was downloaded from WinmxWorld link and it came with patch 3.0 included.
Would it make any difference if I reinstalled Winmx 3.54 by itself and then installed the patch separately?
I wish there was a way to determine if this is a Winmx problem  or a patch problem or a Microsoft problem.
Of course, I am Leaning towards Microsoft problem, cos the only time Microsoft made something that didn't suck,
 it was a vaccum cleaner!!  LOL   [Has to be some humour inserted here, I think]
I am certainly willing to try any suggestions.
Thanks

Event Type:   Error
Event Source:   Application Error
Event Category:   None
Event ID:   1000
Date:      6.10.2007
Time:      6:41:56 PM
User:      N/A
Computer:   DABUD
Description:
Faulting application winmx.exe, version 3.5.4.0, faulting module unknown, version 0.0.0.0, fault address 0x41746e65.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 77 69 6e   ure  win
0018: 6d 78 2e 65 78 65 20 33   mx.exe 3
0020: 2e 35 2e 34 2e 30 20 69   .5.4.0 i
0028: 6e 20 75 6e 6b 6e 6f 77   n unknow
0030: 6e 20 30 2e 30 2e 30 2e   n 0.0.0.
0038: 30 20 61 74 20 6f 66 66   0 at off
0040: 73 65 74 20 34 31 37 34   set 4174
0048: 36 65 36 35 0d 0a         6e65.. 

[Me Here]

Dabud do you have any incompletes listed in your transfers screen?

If yes, I want you to remove them all.  (not delete just move them off the transfers screen 'Clear Incompletes' ) You may have to go in and change the Find Sources to Never for them to be removed.  Then restart WinMX for me and see what happens..


**EDIT**

If you do still have the crash or have not had any incompletes then are you running in primary mode?  If so please switch to secondary for me and try that..

[dabud]

I am removing my incompletes from winmx and will reboot.

will keep you posted

ty

[dabud]

Well we ran without this error for about 3 weeks, but now it is occurring, with increasing frequency, again.There has been nothing new re: computer since then, so I cannot even suggest or tell you anything new there.  I have kept my download file clear and did not re enter my old incompletes.


The following is the error file that was generated by this last error.

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="WinMX.exe" FILTER="GRABMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="OLEDLG.DLL" SIZE="61440" CHECKSUM="0xE711868" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="06/07/2006 16:49:20" UPTO_LINK_DATE="06/07/2006 16:49:20" />
    <MATCHING_FILE NAME="uninstallmx.exe" SIZE="48033" CHECKSUM="0x5E707DE4" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="05/19/2006 18:29:25" UPTO_LINK_DATE="05/19/2006 18:29:25" />
    <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="WMW XP\Vista WinMX Patch\OLEDLG.DLL" SIZE="61440" CHECKSUM="0xE711868" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="06/07/2006 16:49:20" UPTO_LINK_DATE="06/07/2006 16:49:20" />
</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>



I don't know if it will help, for I don't know how to interpret it.


please take a look and again,  any suggestions you have I will try.

thank You

[dabud]

Sorry, there is something new about the computer, I did install the new winmxworld xp_vista patch.

[dabud]

Again SORRY

 the occurrence of the Winmx has to close error existed before and after this new patch was installed so I really dont think the new patch is an issue

[bughunter]

http://www.microsoft.com/technet/support/ee/SearchResults.aspx?Type=0&Product=Windows%20Operating%20System&Message=event%20id%201000

seems to be related to ip addresses  try flushing the dns cache   go to a command prompt type ipconfig /flushdns   hit enter  then reboot, also see if setting a static ip on the vista powered puter doesnt help also
https://www.winmxworld.com/tutorials/static_ip.html                is a tutorial on how to do that..........

these are a bit of a long shot but wont hurt either way...............

let us know how you get on

[dabud]

ok   I'll try that dns flush
don't have vista tho'  so the static ip is out for now

                            ty

[lovejoy291]

i have had this in the past and the only way to i found to solve it is a total reinstall of winmx delete all winmx on ur computer and stat a fresh i have a copy of winmx running with a host file had it a yr now ur welcome to try a copy of that 

Tv and film lounge _58442E5022C3      : )

[SamSeeSam]

The blockign dll patch is there now, you can download it from the links in m,y signature below this post
Choose your os.

Cheers