Jump to content

bot crashing or closing on trial login


jackson2020
 Share

Recommended Posts

tried switching from dx9 to dx11 - dx9 crashes dx11 just closes

installed slimdx, no good

updated all of system, setup worked fine with honorbuddy running 5 instances

complete log DX9:

 

[D] 18:02:20 - [Info] Log file created: 16 Dec 2015 18H02.log.html
[D] 18:02:20 - [Info] WRobot Version: 1.5.5 (26656) for wow: 6.2.3_20726
[D] 18:02:20 - [Info] Offical website: http://wrobot.eu/
[D] 18:02:20 - [Info] Operating System Details: Microsoft Windows NT 6.1.7601 Service Pack 1
[D] 18:02:20 - [Info] Lang: English (United States)
[F] 18:02:21 - [Memory] D3D9 found: 55 8B EC 8B 45 8 8B 48 4 8B 
[F] 18:02:21 - [Memory] D3D11 found: 55 8B EC 51 C7 45 FC 0 0 0 
[D] 18:02:21 - [Memory] D3D9 used
[E] 18:02:31 - Error injection: Cannot launch it, skipped.

[E] 18:02:45 - [Memory] Error during hook test. If the program freeze or have problem I recommend to change in game your directx version.

[E] 18:02:45 - wManager > Pulstator > Pulse(int processId, string secretKey): System.ComponentModel.Win32Exception (0x80004005): A 32 bit processes cannot access modules of a 64 bit process.
at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
at System.Diagnostics.NtProcessManager.GetFirstModuleInfo(Int32 processId)
at System.Diagnostics.Process.get_MainModule()
at MemoryRobot.Memory.FindPattern(String szPattern, String szMask)
at MemoryRobot.Memory.FindPattern(String pattern)
at wManager.Wow.Memory.GetOffset(String pattern, Int32 position, Boolean isFunction, Boolean rebase, Memory memory)
at wManager.Wow.Patchables.RakuteafuruIdejeu.FunctionWow.Initialize()
at wManager.Pulsator.Pulse(Int32 processId, String secretKey)


18:02:45 - [Memory] Select game process: 3400 - Ska...

 

complete log DX11:

[D] 17:51:17 - [Info] Log file created: 16 Dec 2015 17H51.log.html
[D] 17:51:17 - [Info] WRobot Version: 1.5.5 (26656) for wow: 6.2.3_20726
[D] 17:51:17 - [Info] Offical website: http://wrobot.eu/
[D] 17:51:17 - [Info] Operating System Details: Microsoft Windows NT 6.1.7601 Service Pack 1
[D] 17:51:17 - [Info] Lang: English (United States)
[F] 17:51:17 - [Memory] D3D9 found: 55 8B EC 8B 45 8 8B 48 4 8B 
[F] 17:51:17 - [Memory] D3D11 found: 55 8B EC 51 C7 45 FC 0 0 0 
[D] 17:51:17 - [Memory] D3D11 used
[E] 17:51:34 - wManager > Pulstator > Pulse(int processId, string secretKey): System.ComponentModel.Win32Exception (0x80004005): Only part of a ReadProcessMemory or WriteProcessMemory request was completed
at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
at System.Diagnostics.NtProcessManager.GetFirstModuleInfo(Int32 processId)
at System.Diagnostics.Process.get_MainModule()
at MemoryRobot.Memory.FindPattern(String szPattern, String szMask)
at MemoryRobot.Memory.FindPattern(String pattern)
at wManager.Wow.Memory.GetOffset(String pattern, Int32 position, Boolean isFunction, Boolean rebase, Memory memory)
at wManager.Wow.Patchables.RakuteafuruIdejeu.FunctionWow.Initialize()
at wManager.Pulsator.Pulse(Int32 processId, String secretKey)


17:51:34 - [Memory] Select game process: 6332 - Ska...

 

any ideas? 

Link to comment
Share on other sites

mmm, yes, I am sure, i read every support topic in your forum and tried everything listed first. And i am well acquainted with keeping a system up to date. I dont use AV, and i have reinstalled it several times. All of this minus the reinstallations were listed in my steps of what i have already tested - i am sure that it is not something that will be "easily fixed" from your list of fixes on the forum. The only information that i was able to identify was another user who claimed that his issues were resolved after rolling back his HDD 2 days. Either way, 3 days to get one response was not quick enough for me - i have identified another solution besides wrobot, so thanks, hopefully my issue doesnt become some kind of pandemic for you in the future. 

 

 

Link to comment
Share on other sites

Yes sorry I can understand, I have delay on the WRobot support.


If you have time, if you can try with new WRobot update and tell me if problem is resolved (your directx version seem modified (by your driver or another program)).

Link to comment
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
 Share

×
×
  • Create New...