Jump to content

Utorrent results in Windows Bluescreen Error


Recommended Posts

Ok, I have read through the forums, and I have seen where it is insisted that Utorrent doesn't result in these, nevertheless I am having it happen, caused only when Utorrent is running, and resulting in Utorrent's termination. It does not happen all the time, as Utorrent will start up fine, and run for random lengths of time (Usually 3 hours). Then I will get a Windows Blue Screen. It is a recoverable Blue Screen, with a very generic error. It states windows error, goes on about something not responding and pressing enter to return to windows, or ctrl+alt+delete to restart the computer, then at the bottom, gives this error message:

VSDATA95(01) + 00029A63 Error : 0E : 0028 : C00C54D7

I am running Windows ME, with IE 6.0.2800.1106, ZoneaAlarm Firewall Version 5.5.062, I do have Avast! installed, but disabled. I have tried the stable build of Utorrent, and the Beta. I have previously used Shadows Bittorrent Client, and Bittornado, with no difficulty other than tracker compatability issues (hence why I am trying to switch to U-Torrent). My machine is an AMD Athalon 700.

Here is the HijackThis log:

Logfile of HijackThis v1.99.1

Scan saved at 8:31:51 PM, on 6/23/2008

Platform: Windows ME (Win9x 4.90.3000)

MSIE: Internet Explorer v6.00 SP1 (6.00.2800.1106)

Running processes:




























O1 - Hosts: www.winmx.com err.winmx.com

O1 - Hosts: www.winmx.com err.winmx.com

O1 - Hosts: cache0.winmx.com test3201.winmx.com test3206.winmx.com

O1 - Hosts: cache1.winmx.com test3202.winmx.com test3207.winmx.com

O1 - Hosts: cache2.winmx.com test3203.winmx.com test3208.winmx.com

O1 - Hosts: cache3.winmx.com test3204.winmx.com

O1 - Hosts: cache4.winmx.com test3205.winmx.com

O1 - Hosts: c3310.z1301.winmx.com c3310.z1302.winmx.com c3310.z1303.winmx.com c3310.z1304.winmx.com c3310.z1305.winmx.com c3310.z1306.winmx.com

O1 - Hosts: c3311.z1301.winmx.com c3311.z1302.winmx.com c3311.z1303.winmx.com c3311.z1304.winmx.com c3311.z1305.winmx.com c3311.z1306.winmx.com

O1 - Hosts: c3312.z1301.winmx.com c3312.z1302.winmx.com c3312.z1303.winmx.com c3312.z1304.winmx.com c3312.z1305.winmx.com c3312.z1306.winmx.com

O1 - Hosts: c3313.z1301.winmx.com c3313.z1302.winmx.com c3313.z1303.winmx.com c3313.z1304.winmx.com c3313.z1305.winmx.com c3313.z1306.winmx.com

O1 - Hosts: c3314.z1301.winmx.com c3314.z1302.winmx.com c3314.z1303.winmx.com c3314.z1304.winmx.com c3314.z1305.winmx.com c3314.z1306.winmx.com

O1 - Hosts: c3315.z1301.winmx.com c3315.z1302.winmx.com c3315.z1303.winmx.com c3315.z1304.winmx.com c3315.z1305.winmx.com c3315.z1306.winmx.com

O1 - Hosts: c3316.z1301.winmx.com c3316.z1302.winmx.com c3316.z1303.winmx.com c3316.z1304.winmx.com c3316.z1305.winmx.com c3316.z1306.winmx.com

O1 - Hosts: c3317.z1301.winmx.com c3317.z1302.winmx.com c3317.z1303.winmx.com c3317.z1304.winmx.com c3317.z1305.winmx.com c3317.z1306.winmx.com

O1 - Hosts: c3318.z1301.winmx.com c3318.z1302.winmx.com c3318.z1303.winmx.com c3318.z1304.winmx.com c3318.z1305.winmx.com c3318.z1306.winmx.com

O1 - Hosts: c3319.z1301.winmx.com c3319.z1302.winmx.com c3319.z1303.winmx.com c3319.z1304.winmx.com c3319.z1305.winmx.com c3319.z1306.winmx.com

O1 - Hosts: c3520.z1301.winmx.com c3520.z1302.winmx.com c3520.z1303.winmx.com c3520.z1304.winmx.com c3520.z1305.winmx.com c3520.z1306.winmx.com

O1 - Hosts: c3521.z1301.winmx.com c3521.z1302.winmx.com c3521.z1303.winmx.com c3521.z1304.winmx.com c3521.z1305.winmx.com c3521.z1306.winmx.com

O1 - Hosts: c3522.z1301.winmx.com c3522.z1302.winmx.com c3522.z1303.winmx.com c3522.z1304.winmx.com c3522.z1305.winmx.com c3522.z1306.winmx.com

O1 - Hosts: c3523.z1301.winmx.com c3523.z1302.winmx.com c3523.z1303.winmx.com c3523.z1304.winmx.com c3523.z1305.winmx.com c3523.z1306.winmx.com

O1 - Hosts: c3524.z1301.winmx.com c3524.z1302.winmx.com c3524.z1303.winmx.com c3524.z1304.winmx.com c3524.z1305.winmx.com c3524.z1306.winmx.com

O1 - Hosts: c3525.z1301.winmx.com c3525.z1302.winmx.com c3525.z1303.winmx.com c3525.z1304.winmx.com c3525.z1305.winmx.com c3525.z1306.winmx.com

O1 - Hosts: c3526.z1301.winmx.com c3526.z1302.winmx.com c3526.z1303.winmx.com c3526.z1304.winmx.com c3526.z1305.winmx.com c3526.z1306.winmx.com

O1 - Hosts: c3527.z1301.winmx.com c3527.z1302.winmx.com c3527.z1303.winmx.com c3527.z1304.winmx.com c3527.z1305.winmx.com c3527.z1306.winmx.com

O1 - Hosts: c3528.z1301.winmx.com c3528.z1302.winmx.com c3528.z1303.winmx.com c3528.z1304.winmx.com c3528.z1305.winmx.com c3528.z1306.winmx.com

O1 - Hosts: c3529.z1301.winmx.com c3529.z1302.winmx.com c3529.z1303.winmx.com c3529.z1304.winmx.com c3529.z1305.winmx.com c3529.z1306.winmx.com

O1 - Hosts: winmx-com.winmxgroup.com winmx-com-v30.winmxgroup.com

O1 - Hosts: winmx-com.winmxgroup.com winmx-com-v30.winmxgroup.com

O1 - Hosts: test0.winmxgroup.net test5.winmxgroup.net

O1 - Hosts: test1.winmxgroup.net test6.winmxgroup.net

O1 - Hosts: test2.winmxgroup.net

O1 - Hosts: test3.winmxgroup.net

O1 - Hosts: test4.winmxgroup.net

O1 - Hosts: cache0.winmxgroup.com cache5.winmxgroup.com cache0.winmxgroup.net cache5.winmxgroup.net cache10.winmxgroup.net cache15.winmxgroup.net

O1 - Hosts: cache1.winmxgroup.com cache6.winmxgroup.com cache1.winmxgroup.net cache6.winmxgroup.net cache11.winmxgroup.net cache16.winmxgroup.net

O1 - Hosts: cache2.winmxgroup.com cache7.winmxgroup.com cache2.winmxgroup.net cache7.winmxgroup.net cache12.winmxgroup.net cache17.winmxgroup.net

O1 - Hosts: cache3.winmxgroup.com cache8.winmxgroup.com cache3.winmxgroup.net cache8.winmxgroup.net cache13.winmxgroup.net cache18.winmxgroup.net

O1 - Hosts: cache4.winmxgroup.com cache9.winmxgroup.com cache4.winmxgroup.net cache9.winmxgroup.net cache14.winmxgroup.net cache19.winmxgroup.net


O3 - Toolbar: @msdxmLC.dll,-1@1033,&Radio - {8E718888-423F-11D2-876E-00A0C9082467} - C:\WINDOWS\SYSTEM\MSDXM.OCX

O4 - HKLM\..\Run: [TaskMonitor] C:\WINDOWS\taskmon.exe

O4 - HKLM\..\Run: [systemTray] SysTray.Exe

O4 - HKLM\..\Run: [Zone Labs Client] "C:\Program Files\Zone Labs\ZoneAlarm\zlclient.exe"




O4 - HKLM\..\Run: [avast! Web Scanner] C:\PROGRA~1\ALWILS~1\AVAST4\ASHWEBSV.EXE

O4 - HKLM\..\Run: [ashMaiSv] C:\PROGRA~1\ALWILS~1\AVAST4\ashmaisv.exe

O4 - HKLM\..\RunServices: [schedulingAgent] mstask.exe

O4 - HKLM\..\RunServices: [KB891711] C:\WINDOWS\SYSTEM\KB891711\KB891711.EXE

O4 - HKLM\..\RunServices: [KB918547] C:\WINDOWS\SYSTEM\KB918547\KB918547.EXE

O4 - HKLM\..\RunServices: [avast!] C:\Program Files\Alwil Software\Avast4\ashServ.exe

O4 - HKLM\..\RunServices: [*StateMgr] C:\WINDOWS\System\Restore\StateMgr.exe

O4 - HKCU\..\Run: [Taskbar Display Controls] RunDLL deskcp16.dll,QUICKRES_RUNDLLENTRY

O4 - Startup: Adobe Gamma Loader.lnk = C:\Program Files\Common Files\Adobe\Calibration\Adobe Gamma Loader.exe

O4 - Startup: IomegaWare.lnk = C:\Program Files\Iomega\IomegaWare\Commander.exe

O4 - Startup: Iomega Icons.lnk = C:\Program Files\Iomega\Tools\imgicon.exe

O4 - Startup: Iomega Startup Options.lnk = C:\Program Files\Iomega\Tools\imgstart.exe

O4 - Startup: Microsoft Office.lnk = C:\Program Files\Microsoft Office\Office\OSA9.EXE

O16 - DPF: {0A5FD7C5-A45C-49FC-ADB5-9952547D5715} (Creative Software AutoUpdate) - http://www.creative.com/su/ocx/15015/CTSUEng.cab

O16 - DPF: {F6ACF75C-C32C-447B-9BEF-46B766368D29} (Creative Software AutoUpdate Support Package) - http://www.creative.com/su/ocx/15023/CTPID.cab

In my research I have seen numerous errors regarding VSDATA95 linked to Zonealarm, usually involving incomplete removal. Most of those report either preventing the computer from booting, or preventing all internet access altogether. Neither is the case, as this seems to be an issue between Zonealarm and Utorrent, resulting in a windows error that terminates the Utorrent Process. I checked the faq, but saw no mention of ZoneAlarm causing such behavior, so I believe this may be an undiscovered, unreported, or newer situation.

Help is appreciated.

Link to comment
Share on other sites

Nope, I never had a problem with Zonealarm prior to Utorrent, and no other programs are having this problem, or conflicting with ZoneAlarm. I have Used ZoneAlarm for about 9 years now, and this is the first major program conflict I have seen. I do know others who use ZoneAlarm and Utorrent without these problems, which is why I posted, so as to get ideas of workarounds.

If there is a way to get ZoneAlarm and Utorrent to play nice together, I would appreciate help.

If not, then perhaps adding a note about compatibility issues between ZoneAlarm and Utorrent in the faq?

Link to comment
Share on other sites

Have you uninstalled ZA to see if the BSOD stops? If not you cannot say 'Nope.' Sure it works for some people. For just as many (it's not that easy to give numbers since many people who are happy with a program don't post to say 'It works for me.'

Remember you also must be conservative with any p2p application not based on NT... Searching using "vsdata95" gives various references to ZoneAlarm and ways to troubleshoot it... so I don't know how you couldn't find any information on it. Similarly, on this forum, searching for ZoneAlarm brings up the bad juju it exhibits each time it goes bad... it creates one of those Murphy-esque states. It can work fine... and then POW!

Link to comment
Share on other sites

jewelishaven -

It's not quite a BSOD, as it is recoverable...just a generic Windows Bluescreen error. I tried removing and reinstalling Zonealarm, and even just updated to a newer build of Zonealarm earlier, which only served to change the address string of the violation too this:

VSDATA95(01) + 002C4D4 Error : 0E 0028 : C00C7F4E

I do not want to terminate using a firewall, as it will seriously reduce the overall efficiency and usability of my internet connection.


No, that is complete crap, as I have used Zonealarm for 9 years without problems, and know many others who use it as well. THIS error is triggered by Utorrent, and is most certainly Utorrent specific. NO other program I have has had a conflict with Zonealarm, and the program windows terminates when the error is generated is Utorrent, which anyone who has half a clue could tell means that it is Utorrent doing something to trigger the error. Further, if "everyone" was experiencing trouble with ZoneAlarm I would see a lot more complaints than I do in the tech forums I am a regular member of. I realize, unlike you obviously, that not everyone can get every program to work with every setup, and am trying to troubleshoot to find fixes. Given how compatible that the Utorrent homepage claims it is, I figured you would be interested in trying to help troubleshoot the bug, I see that is not the case. Everyone who posts an error in these forums, it seems, you blame on some other software, or on hardware when all else fails. If it is your contention that the problem is ZoneAlarm, and that Utorrent is reacting with Zonealarm, then add ZoneAlarm to your long list of "Software Conflicts" on the FAQ, since you obviously have no useful information or any real clue as to waht the problem is (other than Utorrent being incompatible with seemingly everything).

Link to comment
Share on other sites

I'd like to try and cool this off a bit. If it was a problem with uT everyone would complain of it. Why do they not complain of it? Search for ZoneAlarm and it's like I said before. You will see a majority of users complaining about it. When ZA is uninstalled, the problems go away...(in your case because the module is PART of ZA. There are also posts and people who work just fine with ZA.

It is MY OPINION your situation simply cannot handle uT and ZA since ZA is known as a resource hog and likely does additional network strain to the already pathetic stack in the 9x line of Windows.... hence the switch to NT kernel after NT4.

If you want to use Process Explorer to pull up a call stack on the problem... if it's not internal to uT there's nothing anyone here can do about it. You'd need to point out that call stack to the Zone Alarm developers and say.. hey your software crashes, this is what's happening.... etc. What else do you need to help fix this. It's causing trouble with filesharing software on my Windows ME computer.

Link to comment
Share on other sites

ZA is kernel-mode software. µTorrent is user-mode. As a result, the BSOD can't actually be triggered by user-mode software (except due to a bug in the kernel-mode software).

ZA crashes itself due to poor coding. It happens on 9x, it happens on NT. It happens with more than just µTorrent.

Just because you were lucky enough to have it work until now doesn't mean the problem still doesn't lie with ZA.

I see complaints about ZA ALL the time. And not just here. It is the single worst firewall in existence, and if you don't want to admit that, fine. But don't blame µTorrent.




I'd like you to explain all those crash threads (most of which are not involving µTorrent). Explain it as something besides huge problems lying with ZA that they refuse to fix. Years pass, versions change, the problems only get worse with each release. Their support staff is useless. They won't admit to anything or try to fix the issues.

Link to comment
Share on other sites

From the OPs 2nd paragraph>>>I am running Windows ME,<<<Even I know that this is the worst POS that MS has ever cast out to the masses. You cannot build a house on a foundation of sand.

You can buy a brand new computer with a monitor and printer for less than you can purchase the OS separately. Go spend $250

Link to comment
Share on other sites

I was switching to Utorrent because I heard good things. Those were obviously mistaken. Just looking at the list of software that is already in the Faq that Utorrent has issues with is extensive. It is a Utorretn error, triggered by Utorrent, which results in Utorrents termination. Utorrents claims to be stable enough to run on any OS, Even Win95, posted all over your website are obviously grossly inaccurate, as when a user does have an error you will insist it is the OS or their Firewall, even when they are not using one of the firewalls or security programs that you post known issues with. I personally have run ZA on 5 computers, with multiple OSes ranging from 95 through XP, and have not had any other problems or program conflicts.

Obviously Utorrent is one big piece of shit.

So go ahead and stick your heads in the sand and ignore its problems. I'll find another BT client, one that WORKS without so many problems or program compatability issues. It's not like there is a shortage of them out there.

On a side not, the complete ass-hattery in this forum has restored my faith in internet forums.

I'd ask you to explain the other threads in these forums complaining about BSODs triggered by Utorrent not related to ZA, but you would just blames their OS or hardware as you did in those threads.

I can find plenty of search results that cast Utorrent in a bad light as well:








Link to comment
Share on other sites

And how many of those people are even bothering to post here for support?

We already know our software isn't perfect, but bluescreens when running ANY software that runs exclusively at user-level indicate other problems on the system at kernel or hardware level.

Oh, and the first and second hits in your "utorrent sucks" search don't even back up your point.

Link to comment
Share on other sites

uTorent tries to make lots of connections, often faster than Zone Alarm can handle them. Zone Alarm mishandles the connections...uTorrent expects the connections to be open and ready...ZA drops the ball, but uTorrent crashes before ZA does due to how Windows networking works. Parts of Windows networking support crashes with a bluescreen...uTorrent gets the blame.

PLEASE try uTorrent without Zone Alarm!

Link to comment
Share on other sites

Asshats don't plead with others to do something, Switeck. They tell them to do it or GTFO! Get with the program!

@KageRyu: Yeah, and I used to use ZA as well. I even wrote a whole setup guide for it from my own experience using it (which, at the time, had already spanned several years as well). I ended up turning away from it because it became utter trash. If there are any users here that have the right to speak badly of it here, I'm among them. It sucks.




There, from their own forums (that's just the tip of the iceberg). And the threads aren't even necessarily related directly to µTorrent. [facetious]Obviously, Azureus is as big a "piece of shit" as µTorrent is.[/facetious]

Heck, even our forums are littered with tons of troubleshooting threads for ZA, and people have reported success in switching firewalls (yes, to higher quality firewalls). One in particular that I managed to remember is this thread. Do take care to look at this particular post as well. The firewall can't handle large amounts of simultaneous connections, which BitTorrent inherently causes. Its TrueVector service often fails due to this. Who knows what happens on older OSes that don't have any concept of services (like Windows 9x/ME)? BSOD isn't out of the question.

I'd ask you to explain why ZoneAlarm is having so many issues with P2P in general, but you'll probably just blame it on µTorrent as you're doing here.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...