• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Anyone else experiencing massive system instability from WinMX?

I just installed the lastest WinMX. Previous to now, my computer has been rock stable. No problems of any kind. After I install it, I start getting horrible blue screens with the dreaded 'Driver IRQ not less than or equal" error.

This has happened 3 times now, all about 10 minutes after starting WinMX. I haven't started it yet, and my system seems stable once again. Is this experience familiar for anyone?
 
Sounds like a hardware problem. What do you have in your PCI slots? Driver IRQ problem usually means there is a confliction with your network card, sound card or something else. Try to move the cards around and that should fix it.
 
Originally posted by: cashman
Sounds like a hardware problem. What do you have in your PCI slots? Driver IRQ problem usually means there is a confliction with your network card, sound card or something else. Try to move the cards around and that should fix it.

I've had this same hardware configuration for 2 months now with NO problems up until I installed WinMX. How would an IRQ conflict suddenly rear its head after all this time???
 
Originally posted by: spazntwich1
I just installed the lastest WinMX. Previous to now, my computer has been rock stable. No problems of any kind. After I install it, I start getting horrible blue screens with the dreaded 'Driver IRQ not less than or equal" error.

This has happened 3 times now, all about 10 minutes after starting WinMX. I haven't started it yet, and my system seems stable once again. Is this experience familiar for anyone?

I've had the SAME EXACT PROBLEM! It's pissing me off. WinMX 3.2 worked fine, it wasn't until the dreaded 3.22 version came out!! So far it crashed 6/7 times i ran it.
 
Originally posted by: PSYWVic
Linksys NIC, I assume? Try making a secondary connection instead of primary.

It IS a Linksys NIC! Is there a documented problem? And if so, is it the NIC's fault, or the program's?
 
i'm using v.2.6 with no problems. on 3 diff comps 2 of which have linksys cards. i never have a problem running this program.
i understand later versions have spyware, maybe sothing going on there...
good luck
 
Originally posted by: chuck340
i'm using v.2.6 with no problems. on 3 diff comps 2 of which have linksys cards. i never have a problem running this program. i understand later versions have spyware, maybe sothing going on there...
good luck
According to the WinMX website there has never been and never will be any spyware in their program. Are they lying?

BTW, 3.22 works just fine on my WinXP Pro machine, using a Linksys LNE100TX v4 NIC set up as a secondary connection in WinMX.

 
According to the WinMX website there has never been and never will be any spyware in their program. Are they lying?
i understand later versions have spyware,...
was related to me by a friend that has a later version (not sure which) that adaware had found "spyware" running after he installed WINMX. he runs adaware after installing ANY type of program so i'm pretty sure something else didn't place ,whatever it was , on his system.
also v2.6 works just fine with XP
good luck
 
all versions, including 3.22 which i'm using now, have run rock solid on my system.

there's either something wrong with your hardware/software setup, or winmx is, for some odd reason, incompatible with your hardware/system configuration.
 
WinMX 3.22 does not have any spyware. Per Frontline Tech, the coders, it never has and never will. I update and run adaware at least twice a week and have never found any spyware related to WinMX.
There is a known but undocumentated problem (WinMX has ZERO support) regarding Linksys LNE100TX's. You have to establish a secondary connection, not primary, or it will BSOD during file transfers. A workaround for this is to use the generic drivers from the NIC chipset manufacturer (ADM something, honestly I forget, ask on the WinMX newsgroup if you really need to know). I can only assume that WinMX is at fault, as Linksys NICs tend to be very stable, but then again these workaround drivers work...

 
WinMX 3.22 does not have any spyware. Per Frontline Tech, the coders, it never has and never will. I update and run adaware at least twice a week and have never found any spyware related to WinMX.
thanks PSYWVic. i will pass on the info
 
Back
Top