125 posts in this topic

Sorry for my bad English.Bot started to summon BSOD (blue screen of death).

You need to block a Wrobot from accessing to the Internet. We have 3 methods (thanks

Please login or register to see this link.

), but you need to use only one of them:

Spoiler

 

1) 

Please login or register to see this link.

 I blocked Inbound and Outbound connections and now it's working.

2) If first method didn't work, you can try to use (thanks

Please login or register to see this link.

Please login or register to see this link.

3) And, I think, modifing "hosts" file (C:\Windows\System32\drivers\etc) with this:

Quote

127.0.0.1 wrobot.eu
127.0.0.1 download.wrobot.eu

also may help, but to be honest I don't want to try, because now my Windows fresh and clean. I will be really appreciated if someone check it and write result here in the comments.

 

First of all, for all who cares I want to outline my position. I am against the use of bots on the official World of wacraft servers. And for compliance with all the conditions prescribed in the Blizzard license agreement, but I am absolutely neutral about the use of these programs on private servers. Since these servers themselves violate EULA. 

TBC versions are unstable and have couple of bugs. 3.3.5a version that succeed with running in 2.4.3 works better in Grinding mode than original version for TBC, but Quester does’t work at all and possibly some other functions too.Links:

Wrobot for World of Warcraft 2.4.3:

Spoiler

 

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

 

Wrobot for World of Warcraft 3.3.5а:

Spoiler

 

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

 

Wrobot for World of Warcraft 5.4.8 (thanks

Please login or register to see this link.

):
(Some servers claim version 5.4.8, but in fact they have other versions)

Spoiler

 

With this version you need to run "WRobot Auth" before launch the program

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

 

Wrobot for World of Warcraft 7.2.5:
(Didn’t test it, possibly not working)

Spoiler

 

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

 

 

 

Wrobot for World of Warcraft 3.3.5a, that can work in 2.4.3:

Spoiler

 

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

 


VirusTotal:

Please login or register to see this link.

I’ve test all 4 versions (withought 5.4.8) in one archive withought meshes. Virustotal found: “Gen:Variant.Ursu.860805”, I’m not a programmer, so I don’t know what it is. But I was using a bot for a while and nothing extraordinary happened to my PC.
Old cracked version by Tumadre also have that “Ursu” thing:

Please login or register to see this link.


 

 

 

5 people like this

Share this post


Link to post
Share on other sites

hi thanks for sharing. Here for 5.4.8 add 

Please login or register to see this link.


key : B5EW4y1Q81H2uaLeLGxOZo-kIfo1PCZ12yMUxPr5yos

Please login or register to see this link.

Share this post


Link to post
Share on other sites

unfortunately, there is no release of this version

Share this post


Link to post
Share on other sites
15 hours ago, SND said:

have you done the cracking ?

Nope, it was Snub aka Sinister from nulled. He recracked 3.3.5a version, I just figured out which files was modified and move some of them from 3.3.5a to 2.4.3. Then I moved wManager.dll from 2.4.3 to 3.3.5a and this "new" version started to work in TBC. Also, I think, if someone can change dependencies in wManager.dll from 3.3.5 or 2.4.3 to 1.12.1 it can work in classic

1 person likes this

Share this post


Link to post
Share on other sites
17 minutes ago, Archwolf said:

Nope, it was Snub aka Sinister from nulled. He recracked 3.3.5a version, I just figured out which files was modified and move some of them from 3.3.5a to 2.4.3. Then I moved wManager.dll from 2.4.3 to 3.3.5a and this "new" version started to work in TBC. Also, I think, if someone can change dependencies in wManager.dll from 3.3.5 or 2.4.3 to 1.12.1 it can work in classic

Also Legion version possibly can work in 7.3.5/Draenor/Pandaria/Cata if change dependensies, but, like I said, Im not a programmer.

1 person likes this

Share this post


Link to post
Share on other sites

Was working fine for a few days, now when I try to start it my PC blue screens, even on a fresh extract. Kinda weird, I'll let you know if I come across a solution.

Share this post


Link to post
Share on other sites
6 hours ago, destroid said:

Was working fine for a few days, now when I try to start it my PC blue screens, even on a fresh extract. Kinda weird, I'll let you know if I come across a solution.

Something strange, I checked 2.4.3, 2.4.3>3.3.5, 3.3.5 and 5.4.8 versions. Everething works fine, I think, something in your system. Which OS and version of bot do you use?

1 person likes this

Share this post


Link to post
Share on other sites

Hi Archwolf, pandawow and taurrie wow the versions are not the same. 
Pandawow uses 5.4.7 or even less.
Taurus wow I don't know yet. but I think it's 5.4.8. just the client a little bit modified.
It's an old job, but I think it's still current :) 

Please login or register to see this link.

Share this post


Link to post
Share on other sites

Same thing happend to me, blue screen on Win10 says "CRITICAL PROCESS DIED", its been working fine for a month more or less and since yesterday I get that error in WOW 3.5.5a, but u can get that error just opening WROBOT.

Share this post


Link to post
Share on other sites

you must be missing something in the system. Do an update. It's working fine :3

Share this post


Link to post
Share on other sites
16 minutes ago, likon69 said:

you must be missing something in the system. Do an update. It's working fine :3

I did an update with my graphic card Ati Radeon drivers but Im not sure that it was before it started to fail, i will try to install previous drivers.

Share this post


Link to post
Share on other sites
16 hours ago, destroid said:

Was working fine for a few days, now when I try to start it my PC blue screens, even on a fresh extract. Kinda weird, I'll let you know if I come across a solution.

I made a semisolution, in my PC if you turn your conexion off (ethernet or wifi), open wow (you cant log now), open WROBOT -> then turn on conexion and it works, if I open WROBOT with internet conexion on it crash. O_o

2 people like this

Share this post


Link to post
Share on other sites
1 hour ago, gamusin0 said:

I made a semisolution, in my PC if you turn your conexion off (ethernet or wifi), open wow (you cant log now), open WROBOT -> then turn on conexion and it works, if I open WROBOT with internet conexion on it crash. O_o

Microsoft could broke something with a Windows update... again... Did you install something like VPN or local nerwork emulators like Hamachi, Tunngle or Zerotier? Something that creates virtual network adapter. Did you change "hosts" file before BSOD appear?

1 person likes this

Share this post


Link to post
Share on other sites
4 hours ago, Archwolf said:

 

It's Microsoft...

I think this shit happened 

Please login or register to see this link.

My Windows updated and started to BSOD too... Will add information to header after recover my PC

Share this post


Link to post
Share on other sites
4 hours ago, Archwolf said:

Microsoft could broke something with a Windows update... again... Did you install something like VPN or local nerwork emulators like Hamachi, Tunngle or Zerotier? Something that creates virtual network adapter. Did you change "hosts" file before BSOD appear?

No, didnt install anything voluntary, just now I have tryed to connect with a wifi usb and disable ethernet connection and I get same blue screen, maybe the issue is that new patch from WIN10. I will wait your news :)

1 person likes this

Share this post


Link to post
Share on other sites
1 hour ago, Archwolf said:

It's Microsoft...

I think this shit happened 

Please login or register to see this link.

My Windows updated and started to BSOD too... Will add information to header after recover my PC

Any workaround?

Share this post


Link to post
Share on other sites
53 minutes ago, destroid said:

Any workaround?

I think I hurried to conclusions. Because now I have Windows with 1909 update and BSOD appears. I'm trying to feagure out whats wrong.

Share this post


Link to post
Share on other sites
2 hours ago, destroid said:

Any workaround?

I think I found a solution, check the title.

 

 

A bit of conspiracy xD. May be if the bot still sent some data to the network and receiving something back, then Droidz (creator of Wrobot) is behind this problem? But I'm not a programmer, and possibly this is the dumbest thing you probably ever read :)

2 people like this

Share this post


Link to post
Share on other sites
On 5/9/2020 at 10:07 AM, Archwolf said:

You need to block a Wrobot from accessing to the Internet.

 

 

Tried this, still get BSOD...

1 person likes this

Share this post


Link to post
Share on other sites
9 minutes ago, destroid said:

 

Tried this, still get BSOD...

You must have unwittingly changed something. 
Do a restoration system on the date it works.
I know it's radical :/

1 person likes this

Share this post


Link to post
Share on other sites
34 minutes ago, destroid said:

 

Tried this, still get BSOD...

Did you block both inbound and outbound connections? If so, try to do like gamusin0 wrote

"I made a semisolution, in my PC if you turn your conexion off (ethernet or wifi), open wow (you cant log now), open WROBOT -> then turn on conexion and it works, if I open WROBOT with internet conexion on it crash. "

Share this post


Link to post
Share on other sites
29 minutes ago, destroid said:

 

Tried this, still get BSOD...

Just now I disabled my solution and Wrobot BSOD my PC. Then I enabled it and everething fine again. Btw I have Windows 1909 build, which build do you have?

Share this post


Link to post
Share on other sites
12 minutes ago, Archwolf said:

Just now I disabled my solution and Wrobot BSOD my PC. Then I enabled it and everething fine again. Btw I have Windows 1909 build, which build do you have?

I have build 1903.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now