PDA

View Full Version : ROG SPATHA Does Not Work in Wired mode [Resolved]



MLGbr
01-26-2018, 01:34 AM
My system: Win7 sp1 64 bits (updates disable since november 2017) + ROG Armoury v10226 (last version)

I've always used the mouse in WIRED mode, but...


=== THE EVENT

In 01/19/2018 00:51 (UTC -3) the mouse started to fail, I thought it was cable problem.
15 seconds later, it stopped working in wired mode.


=== SYMPTOMS

With the SAME CABLE in the wireless base, the mouse works in wireless mode.

In cable mode:
a) Irresponsible mouse
b) ROG ARMORY does not detect anything
c) Windows detect 2 hardware items 'Mouse compatible with HID'
d) Uninstalling and Installing ultimate version of ROG Armory did not provide any change in the outcome symptoms.

The SAME CABLE, removing of mouse and putting it in the WIRELESS BASE, and...
a) Windows detect 4 hardware items 'Mouse compatible with HID'
b) Sometimes the ROG armory detects the mouse, sometimes not.

--Behavior Ambiguous / Unpredictable--

Test 1
ROG ARMORY show message: "You also need to update the mouse firmware. Switch to THE WIRED connection mode to update the mouse firmware." I NOT update and not detect mouse in "mouse" tab, BUT in the settings says: Version Software 1.02.26 | base firmware: 1.32 | mouse firmware: 1.49

Test 2
ROG ARMORY detect Mouse, and show Mouse options in "Mouse" tab.
In the settings says: Version Software 1.02.26 | base firmware: 1.32 | mouse firmware: 0.00
Mouse is detected in Wireless mode, and I can reprogram the functionality of the mouse buttons.


I tested the sync buttons, or closed and reopened ROG ARMORY, but it did not change the symptoms.


CONCLUSION
a) If I am using the same cable, connected to the same USB port, it is clear that the cable is perfect.
b) The behavior of ROG ARMORY does not seem predictable, it can not be said why it detects the mouse, or why it in another test does not detect the mouse.
c) There may be a correct sequence of procedures, so that you can perfectly detect the mouse in ROG ARMORY, but there is no exact documentation.
d) ROG ARMORY software expects the user to have a specific update to Win7 and I do not have it?


MY OPINION:

I noticed that ROG ARMORY is automatic updates 'by default' . I'd never realized, if I did, I'd have disabled.
On 01/19/2018, when I turned on the computer, ROG ARMORY did an automatic update.

As Windows did kernel upgrade involving Meltdown / Specter, it is possible that 'The Peripheral Team of ASUS' has updated the ROG ARMORY,
assuming ALL users would upgrade Windows, which is not true, and problems are happening.

If you have any procedures, or any updates that solve the problem - Show now

MLGbr
01-27-2018, 10:10 PM
I have tried a new procedure

1) Uninstall the current ROG ARMORY (v10226)
2) Instal ROG ARMORY v10224
3) Restart, leaving the wireless base connected

4) Leaving the ROG ARMORY program open in the steps below
4a) Reset Mouse - Hold Left, right and wheel, Connect the mouse to the cable, and and keep holding for 10 seconds - If done correctly, mouse lights go off. It is difficult to achieve the first time, it is necessary several times to succeed.
4b) Remove the mouse cable and put it in the wireless base
4c) Turn off and power on the button under the mouse
4d) Press the sync button in wireless base
4e) The ROG ARMORY recognizes the mouse, and allows you to reprogram the buttons.

After restarting the computer, ROG ARMORY no longer recognizes the mouse, and lets not reprogram the buttons.

--Restarting, all problems return.
--In all this procedure, the MOUSE NOT worked in the cable mode, only wireless, all the symptoms are of a firmware corrupted in the mouse.


AND TELL THE ENTIRE 'THE PERIPHERAL TEAM OF ASUS' TEAM:
NEVER MAKE A PROGRAM THAT AUTOMATICALLY UPDATES FIRMWARE - IT IS THE SOURCE OF ALL SPATHA MOUSE PROBLEMS!!!
Just read the stories from this forum, to see what the issue is.


Will administrators not answer the topic?

Do you have any solutions?

MLGbr
01-31-2018, 12:54 AM
Something abnormal has happened today, I would like to report.

Initial conditions

Hardware:
a) The computer was off.
b) The wireless base was connected to the computer.
c) The mouse was in wireless mode, off, loading on the base.

Software:
a) Windows 7 sp 1
b) NetFramework 4.6.01055 + NetFramework 4.6.01055 pt-br
c) ROG ARMORY v10224 (and using default auto start setting)


Procedure:
1) I turned on the computer
2) Windows showed the desktop ( I do not know if ROG ARMORY was loading or if it had already loaded)
3) I took the mouse from the wireless base, and I turned it on (Power button underneath)
4) ROG ARMORY will report an error and stop working.


TECHNICAL REPORT:

------------------------------------------------------------------


Transmission in Windows Relatory (in pt-BR idiom):


------------------------------------------------------------------
Fonte
ROG Armoury

Resumo
Parou de funcionar

Data
‎30/‎01/‎2018 21:54

Status
Relatório enviado

Descrição
Caminho do Aplicativo com Falha: C:\Program Files (x86)\ASUS\ROG Armoury\ROG Armoury.exe

Assinatura do problema
Nome de Evento de Problema: CLR20r3
Assinatura do Problema 01: ROG Armoury.exe
Assinatura do Problema 02: 1.2.0.24
Assinatura do Problema 03: 5a1bb09d
Assinatura do Problema 04: System
Assinatura do Problema 05: 4.6.1085.0
Assinatura do Problema 06: 57a4fd23
Assinatura do Problema 07: 307c
Assinatura do Problema 08: 17
Assinatura do Problema 09: System.InvalidOperationException
Versão do sistema operacional: 6.1.7601.2.1.0.256.1
Identificação da Localidade: 1046
Informações Adicionais 1: 0a9e
Informações Adicionais 2: 0a9e372d3b4ad19135b953a78882e789
Informações Adicionais 3: 0a9e
Informações Adicionais 4: 0a9e372d3b4ad19135b953a78882e789

Informações adicionais sobre o problema
Id de Compartimento de Memória: 1399504513
------------------------------------------------------------------


In EventViewer - Event 1026 (XML in pt-BR idiom)


------------------------------------------------------------------
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-01-30T23:54:18.000000000Z" />
<EventRecordID>735226</EventRecordID>
<Channel>Application</Channel>
<Computer>user-PC</Computer>
<Security />
</System>
- <EventData>
<Data>Aplicativo: ROG Armoury.exe Versão do Framework: v4.0.30319 Descrição: O processo foi terminado devido a uma exceção sem tratamento. Informações da Exceção: System.InvalidOperationException em System.ComponentModel.BackgroundWorker.CancelAsync () em SPATHA.MainWindow.WirelessLink_Tick(System.Object, System.EventArgs) em System.Windows.Threading.DispatcherTimer.FireTick( System.Object) em System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32) em System.Windows.Threading.ExceptionWrapper.TryCatch When(System.Object, System.Delegate, System.Object, Int32, System.Delegate) em System.Windows.Threading.DispatcherOperation.Invok eImpl() em System.Windows.Threading.DispatcherOperation.Invok eInSecurityContext(System.Object) em System.Threading.ExecutionContext.RunInternal(Syst em.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) em System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) em System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object) em MS.Internal.CulturePreservingExecutionContext.Run( MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) em System.Windows.Threading.DispatcherOperation.Invok e() em System.Windows.Threading.Dispatcher.ProcessQueue() em System.Windows.Threading.Dispatcher.WndProcHook(In tPtr, Int32, IntPtr, IntPtr, Boolean ByRef) em MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) em MS.Win32.HwndSubclass.DispatcherCallbackOperation( System.Object) em System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32) em System.Windows.Threading.ExceptionWrapper.TryCatch When(System.Object, System.Delegate, System.Object, Int32, System.Delegate) em System.Windows.Threading.Dispatcher.LegacyInvokeIm pl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) em MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) em MS.Win32.UnsafeNativeMethods.DispatchMessage(Syste m.Windows.Interop.MSG ByRef) em System.Windows.Threading.Dispatcher.PushFrameImpl( System.Windows.Threading.DispatcherFrame) em System.Windows.Threading.Dispatcher.PushFrame(Syst em.Windows.Threading.DispatcherFrame) em System.Windows.Application.RunDispatcher(System.Ob ject) em System.Windows.Application.RunInternal(System.Wind ows.Window) em System.Windows.Application.Run(System.Windows.Wind ow) em ROG_ARMOURY.App.Main()</Data>
</EventData>
</Event>
------------------------------------------------------------------


In EventViewer - Event 1000 (XML in pt-BR idiom)


------------------------------------------------------------------
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-01-30T23:54:20.000000000Z" />
<EventRecordID>735227</EventRecordID>
<Channel>Application</Channel>
<Computer>user-PC</Computer>
<Security />
</System>
- <EventData>
<Data>ROG Armoury.exe</Data>
<Data>1.2.0.24</Data>
<Data>5a1bb09d</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.23915</Data>
<Data>59b94abb</Data>
<Data>e0434352</Data>
<Data>0000c54f</Data>
<Data>a64</Data>
<Data>01d39a25510df1f0</Data>
<Data>C:\Program Files (x86)\ASUS\ROG Armoury\ROG Armoury.exe</Data>
<Data>C:\Windows\syswow64\KERNELBASE.dll</Data>
<Data>e310d16e-0618-11e8-aeca-448a5b9bb104</Data>
</EventData>
</Event>
------------------------------------------------------------------


MY OPINION

I turned on the mouse, when ROG ARMORY was not fully charged, and created a situation that was not foreseen in the programming.

MLGbr
02-02-2018, 02:15 AM
There have been reports that since November 2017 a Windows update has caused problems in the mouse APIs - and this is Feb / 2018, and the problem has not been resolved yet.

I do not know if someone from ASUS is aware of the problem - may be impacting ROG ARMORY, in an unknown way, even in other versions of Windows.

https://answers.microsoft.com/en-us/windows/forum/windows_10-security/important-syslistview32-bug-with-multiple-items/9e6198f7-a38a-4614-bc89-4781a9bde748?tm=1509985739913&auth=1


The bug would be located in mscomctl.dll

https://social.msdn.microsoft.com/Forums/azure/en-US/bb920579-bad8-4956-9363-74336735bdcc/syslistview32-mouse-selecting-bug-after-windows-10-fall-update?forum=vcgeneral

MLGbr
02-03-2018, 12:27 AM
I tested the mouse on another computer, and it does not work.

My problem is 100% corrupted mouse firmware - confirmed.

The wireless base still works, but as the mouse is not detected, it is not possible to reprogram the buttons - which makes this mouse full of buttons useless.


I'll check if Asus accepts RMA in Brazil.


But it was a good lesson:
BY INSTALLING THE APPLICATION OF THE MANUFACTURER,MAKE SURE THAT THE "DEFAULT OPTION" IS NEVER "AUTO UPDATE".
IF IT IS, DISABLE - BEFORE ANY STUPID UPDATE DESTROY YOUR COMPUTER WITHOUT YOUR PERMISSION.


If you followed this forum, you should have seen that I stayed for 1 week reporting my problem in this forum, in different postings, and no administrator appeared, to give any support or to respond. I needed to find out all by myself.


They may be accustomed to users who write profanity and have no technical knowledge. When technical information is displayed on the post, they disappear.

MasterC@ROG
02-05-2018, 03:09 AM
You can check if the MCU is causing the mouse to crash.
1. Remove the four screw covers.
2. Open up the Spatha by using the supplied screwdriver to remove the four screws. This will not void the warranty since the same procedure applies when swapping switches.
3. Disconnect then reconnect the battery connector (see below).
71336
4. Reassemble the Spatha.
5. Test the mouse and update the firmware to 1.69.
71337

MLGbr
02-07-2018, 11:16 PM
1) I updated the ROG ARMORY to 2.04.04 version

2) I opened the mouse, disconnected the battery, closed the mouse, and connected the USB cable (Wired Mode)

3) I run ROG ARMORY, open "configurations", and click on "Live Update", and ROG ARMORY crash every time.


71402

71403

71404


Produced 2 error events: 1026 and 1000

==================================

EventView 1026 (XML in Portuguese Windows)

==================================

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-02-07T21:23:54.000000000Z" />
<EventRecordID>735725</EventRecordID>
<Channel>Application</Channel>
<Computer>user-PC</Computer>
<Security />
</System>
- <EventData>
<Data>Aplicativo: ROG Armoury.exe Versão do Framework: v4.0.30319 Descrição: O processo foi terminado devido a uma exceção sem tratamento. Informações da Exceção: System.ArgumentOutOfRangeException em System.Collections.ArrayList.get_Item(Int32) em ROG_ARMOURY.VerCheck.Button_Click(System.Object, System.Windows.RoutedEventArgs) em System.Windows.RoutedEventHandlerInfo.InvokeHandle r(System.Object, System.Windows.RoutedEventArgs) em System.Windows.EventRoute.InvokeHandlersImpl(Syste m.Object, System.Windows.RoutedEventArgs, Boolean) em System.Windows.UIElement.RaiseEventImpl(System.Win dows.DependencyObject, System.Windows.RoutedEventArgs) em System.Windows.UIElement.RaiseEvent(System.Windows .RoutedEventArgs) em System.Windows.Controls.Primitives.ButtonBase.OnCl ick() em System.Windows.Controls.Button.OnClick() em System.Windows.Controls.Primitives.ButtonBase.OnMo useLeftButtonUp(System.Windows.Input.MouseButtonEv entArgs) em System.Windows.UIElement.OnMouseLeftButtonUpThunk( System.Object, System.Windows.Input.MouseButtonEventArgs) em System.Windows.Input.MouseButtonEventArgs.InvokeEv entHandler(System.Delegate, System.Object) em System.Windows.RoutedEventArgs.InvokeHandler(Syste m.Delegate, System.Object) em System.Windows.RoutedEventHandlerInfo.InvokeHandle r(System.Object, System.Windows.RoutedEventArgs) em System.Windows.EventRoute.InvokeHandlersImpl(Syste m.Object, System.Windows.RoutedEventArgs, Boolean) em System.Windows.UIElement.ReRaiseEventAs(System.Win dows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent) em System.Windows.UIElement.OnMouseUpThunk(System.Obj ect, System.Windows.Input.MouseButtonEventArgs) em System.Windows.Input.MouseButtonEventArgs.InvokeEv entHandler(System.Delegate, System.Object) em System.Windows.RoutedEventArgs.InvokeHandler(Syste m.Delegate, System.Object) em System.Windows.RoutedEventHandlerInfo.InvokeHandle r(System.Object, System.Windows.RoutedEventArgs) em System.Windows.EventRoute.InvokeHandlersImpl(Syste m.Object, System.Windows.RoutedEventArgs, Boolean) em System.Windows.UIElement.RaiseEventImpl(System.Win dows.DependencyObject, System.Windows.RoutedEventArgs) em System.Windows.UIElement.RaiseTrustedEvent(System. Windows.RoutedEventArgs) em System.Windows.UIElement.RaiseEvent(System.Windows .RoutedEventArgs, Boolean) em System.Windows.Input.InputManager.ProcessStagingAr ea() em System.Windows.Input.InputManager.ProcessInput(Sys tem.Windows.Input.InputEventArgs) em System.Windows.Input.InputProviderSite.ReportInput (System.Windows.Input.InputReport) em System.Windows.Interop.HwndMouseInputProvider.Repo rtInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32) em System.Windows.Interop.HwndMouseInputProvider.Filt erMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef) em System.Windows.Interop.HwndSource.InputFilterMessa ge(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) em MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) em MS.Win32.HwndSubclass.DispatcherCallbackOperation( System.Object) em System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32) em System.Windows.Threading.ExceptionWrapper.TryCatch When(System.Object, System.Delegate, System.Object, Int32, System.Delegate) em System.Windows.Threading.Dispatcher.LegacyInvokeIm pl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) em MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) em MS.Win32.UnsafeNativeMethods.DispatchMessage(Syste m.Windows.Interop.MSG ByRef) em System.Windows.Threading.Dispatcher.PushFrameImpl( System.Windows.Threading.DispatcherFrame) em System.Windows.Threading.Dispatcher.PushFrame(Syst em.Windows.Threading.DispatcherFrame) em System.Windows.Window.ShowHelper(System.Object) em System.Windows.Window.Show() em System.Windows.Window.ShowDialog() em ROG_ARMOURY.MainWindow.Button_Click(System.Object, System.Windows.RoutedEventArgs) em System.Windows.RoutedEventHandlerInfo.InvokeHandle r(System.Object, System.Windows.RoutedEventArgs) em System.Windows.EventRoute.InvokeHandlersImpl(Syste m.Object, System.Windows.RoutedEventArgs, Boolean) em System.Windows.UIElement.RaiseEventImpl(System.Win dows.DependencyObject, System.Windows.RoutedEventArgs) em System.Windows.UIElement.RaiseEvent(System.Windows .RoutedEventArgs) em System.Windows.Controls.Primitives.ButtonBase.OnCl ick() em System.Windows.Controls.Button.OnClick() em System.Windows.Controls.Primitives.ButtonBase.OnMo useLeftButtonUp(System.Windows.Input.MouseButtonEv entArgs) em System.Windows.UIElement.OnMouseLeftButtonUpThunk( System.Object, System.Windows.Input.MouseButtonEventArgs) em System.Windows.Input.MouseButtonEventArgs.InvokeEv entHandler(System.Delegate, System.Object) em System.Windows.RoutedEventArgs.InvokeHandler(Syste m.Delegate, System.Object) em System.Windows.RoutedEventHandlerInfo.InvokeHandle r(System.Object, System.Windows.RoutedEventArgs) em System.Windows.EventRoute.InvokeHandlersImpl(Syste m.Object, System.Windows.RoutedEventArgs, Boolean) em System.Windows.UIElement.ReRaiseEventAs(System.Win dows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent) em System.Windows.UIElement.OnMouseUpThunk(System.Obj ect, System.Windows.Input.MouseButtonEventArgs) em System.Windows.Input.MouseButtonEventArgs.InvokeEv entHandler(System.Delegate, System.Object) em System.Windows.RoutedEventArgs.InvokeHandler(Syste m.Delegate, System.Object) em System.Windows.RoutedEventHandlerInfo.InvokeHandle r(System.Object, System.Windows.RoutedEventArgs) em System.Windows.EventRoute.InvokeHandlersImpl(Syste m.Object, System.Windows.RoutedEventArgs, Boolean) em System.Windows.UIElement.RaiseEventImpl(System.Win dows.DependencyObject, System.Windows.RoutedEventArgs) em System.Windows.UIElement.RaiseTrustedEvent(System. Windows.RoutedEventArgs) em System.Windows.UIElement.RaiseEvent(System.Windows .RoutedEventArgs, Boolean) em System.Windows.Input.InputManager.ProcessStagingAr ea() em System.Windows.Input.InputManager.ProcessInput(Sys tem.Windows.Input.InputEventArgs) em System.Windows.Input.InputProviderSite.ReportInput (System.Windows.Input.InputReport) em System.Windows.Interop.HwndMouseInputProvider.Repo rtInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32) em System.Windows.Interop.HwndMouseInputProvider.Filt erMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef) em System.Windows.Interop.HwndSource.InputFilterMessa ge(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) em MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) em MS.Win32.HwndSubclass.DispatcherCallbackOperation( System.Object) em System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32) em System.Windows.Threading.ExceptionWrapper.TryCatch When(System.Object, System.Delegate, System.Object, Int32, System.Delegate) em System.Windows.Threading.Dispatcher.LegacyInvokeIm pl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) em MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) em MS.Win32.UnsafeNativeMethods.DispatchMessage(Syste m.Windows.Interop.MSG ByRef) em System.Windows.Threading.Dispatcher.PushFrameImpl( System.Windows.Threading.DispatcherFrame) em System.Windows.Threading.Dispatcher.PushFrame(Syst em.Windows.Threading.DispatcherFrame) em System.Windows.Application.RunDispatcher(System.Ob ject) em System.Windows.Application.RunInternal(System.Wind ows.Window) em System.Windows.Application.Run(System.Windows.Wind ow) em ROG_ARMOURY.App.Main()</Data>
</EventData>
</Event>

==================================

EventView 1000 (XML in Portuguese Windows)

==================================
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-02-07T21:23:55.000000000Z" />
<EventRecordID>735726</EventRecordID>
<Channel>Application</Channel>
<Computer>user-PC</Computer>
<Security />
</System>
- <EventData>
<Data>ROG Armoury.exe</Data>
<Data>1.0.111.11111</Data>
<Data>5a712890</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.23915</Data>
<Data>59b94abb</Data>
<Data>e0434352</Data>
<Data>0000c54f</Data>
<Data>a3c</Data>
<Data>01d3a05935b03cce</Data>
<Data>C:\Program Files (x86)\ASUS\ROG Armoury\ROG Armoury.exe</Data>
<Data>C:\Windows\syswow64\KERNELBASE.dll</Data>
<Data>32fd0043-0c4d-11e8-b73d-448a5b9bb104</Data>
</EventData>
</Event>

=============================================

Crash Reports - I tried 3 times, got 3 identical crash reports (in Portuguese Windows)


=============================================

Descrição
Caminho do Aplicativo com Falha: C:\Program Files (x86)\ASUS\ROG Armoury\ROG Armoury.exe

Assinatura do problema
Nome de Evento de Problema: CLR20r3
Assinatura do Problema 01: ROG Armoury.exe
Assinatura do Problema 02: 1.0.111.11111
Assinatura do Problema 03: 5a712890
Assinatura do Problema 04: mscorlib
Assinatura do Problema 05: 4.6.1085.0
Assinatura do Problema 06: 57a4fbb5
Assinatura do Problema 07: 3526
Assinatura do Problema 08: 21
Assinatura do Problema 09: System.ArgumentOutOfRange
Versão do sistema operacional: 6.1.7601.2.1.0.256.1
Identificação da Localidade: 1046
Informações Adicionais 1: 0a9e
Informações Adicionais 2: 0a9e372d3b4ad19135b953a78882e789
Informações Adicionais 3: 0a9e
Informações Adicionais 4: 0a9e372d3b4ad19135b953a78882e789

Informações adicionais sobre o problema
Id de Compartimento de Memória: 3532824919

=============================================


The error is no longer random.

Now using the mouse in wired mode, and trying 'Live update', the same error occurs every time.

It seems to be a programming flaw - When a FOR loop attempts to iterate array, and it goes into an element outside the array.

MasterC@ROG
02-08-2018, 06:47 AM
So the mouse is working now? In wireless mode too?
Is the only issue now the Live Update function in Armoury 2.04.04 preventing you from updating the firmware?

MLGbr
02-08-2018, 08:59 PM
1) So the mouse is working now? In wireless mode too?

Now I have a "wireless only" mouse - but I'm very happy to be working

The resolution of the intermittent Wireless problem occurred hours before I read your forum post (asking to unmount the mouse), and it was caused by updating the ROG ARMORY.




2) The only problem now is the Live Update function in Armory 2.04.04 that prevents the firmware update?

2 Problems, ONLY em wired Mode.

(A) Hardware Problem:
The mouse does not work in wired mode, with or without battery connected.

(B) Software Problem:
In wired mode, when I try to update ROG ARMORY, errors occurs.

My Spatha in wired mode + Update Rog Armory = Lots of errors

This is what was explained in my previous post.


I hope to have clarified your doubts.

MasterC@ROG
02-09-2018, 07:12 AM
1) So the mouse is working now? In wireless mode too?

Now I have a "wireless only" mouse - but I'm very happy to be working

The resolution of the intermittent Wireless problem occurred hours before I read your forum post (asking to unmount the mouse), and it was caused by updating the ROG ARMORY.


2) The only problem now is the Live Update function in Armory 2.04.04 that prevents the firmware update?

2 Problems, ONLY em wired Mode.

(A) Hardware Problem:
The mouse does not work in wired mode, with or without battery connected.

(B) Software Problem:
In wired mode, when I try to update ROG ARMORY, errors occurs.
My Spatha in wired mode + Update Rog Armory = Lots of errors
This is what was explained in my previous post.
I hope to have clarified your doubts.

Thanks for clarifying. Good to hear you can use your Spatha again.
We are currently investigating the Live Update function, it should be resolved very soon. When that is ready, try to see if updating the firmware resolves your wired mode issue (new version of Armoury not needed). Sorry for the inconvenience.

MLGbr
02-10-2018, 12:00 AM
Mr administrator: IT IS IMPOSSIBLE TO UPDATE MOUSE FIRMWARE IN CABLE MODE!


I will draw


Step 1 - Put Mouse on the cable
71463


Step 2 - Open ROG ARMORY
71464

Step 3 - Live Update
71465

Crash!!
71466

EVENTVIEWER
71467


STATUS:
Wireless - OK
Wired - Not Work



MASSIVE LOGS HERE - From the beginning of the problems

https://www.dropbox.com/s/f64euplin26dngv/MyLogs.7z

I hope to help the ASUS peripheral team, In particular, the ROG ARMORY developers team.


I will use the mouse in Wireless mode, until ASUS found a solution.

Mr administrator: Do you want me to open a post "Rog Spatha does not work in wired mode", or can we continue here in this post?

MLGbr
02-11-2018, 09:39 PM
HOW THE WIRELESS PROBLEM WAS RESOLVED

I bought a Corsair keyboard, and I installed the Corsair Utility Engine (CUE) version 2.20.72 on 12/18/2017.
A perfect month later (01/19) the problem occurred in the ROG SPATHA mouse.

Several times during these days, I suspected CUE, and disabled boot during tests and in my attempts to re-enable the Mouse.
But during the normal use of everyday life, I allowed CUE to be run in Windows start.

Between the dawn of 01/19/2018 and the afternoon of 01/07/2018, the wireless base was detected, but the mouse was not detected by ROG ARMORY, not being able to reprogram the mouse buttons in Wireless mode, although the simple operations of clicking and moving the cursor worked.

I do not have a screenshot, but in Wireless ROG Armory mode it did not display Mouse information, it only showed a reddish background.

( It is not the real screen, it's just a similar drawing of SPATHA in wireless mode, without detection by ROG ARMORY )
71515


INVESTIGATION - RETURN OF WIRELESS OPERATION


-Computer was shut down on 02/07/2018 at 03:30:20 (UTC-2), still with all problems

-Computer was connected on 02/07/2018 at 18:27:57 (UTC-2)

-Corsair Utility Engine (CUE) version 2.20.72 if run at Windows startup, and displayed a black popup saying there were updates.

-I opened the CUE application, and I used its graphical interface, to cancel any kind of update, but there was no option to cancel, and I ended up making no changes.
I was completely involved with the problems of the mouse, and I did not want this application to disturb me.

-CUE may have carried out some procedure without my consent. I've never updated the CUE application.

The ROG SPATHA mouse was detected again in wireless mode, allowing button programming and light change, even using the old ROG ARMORY version 10224.

I made a printscreen - SPATHA is complete detected in Wireless mode
71516


-I updated the ROG ARMORY for version 2.04.04 on 02/07/2018 at 18:51:29 (UTC-2)

- After updating, the ROG SPATHA continued working perfectly in Wireless mode.

Then, I performed the procedure of opening the mouse and disconnecting the battery (as requested by the forum administrator), and I answered writing the post #7 in this thread.

The correction of the problem of the ROG SPATHA Wireless occurred on 02/07/2018, between 18:27:57 and 18:51:29 (UTC-2), AND I AM SURE THAT IT WAS CAUSED BY AN "unknown remote procedure" of Corsair Utility Engine version 2.20.72, which I did not order, and never allowed, and occurred when the application detected an online update (which I never asked to do).

- CUE is in version 2.20.72 in my PC, it is the same version that I installed on 12/18/2017, and officially no update occurred.

71517


MY ANALISIS

File changes at critical moment, between the 'mouse correction event' and the ROG ARMORY update

"user-PC" is my local user


PATH - Data - Hour (UTC-2) - Size - User - FileName

--18:34

C:\Users\user\AppData\Roaming\Corsair\CUE
07/02/2018 18:34 <DIR> user-PC\user Corsair

C:\Users\user\AppData\Roaming\Corsair\CUE\Corsair
07/02/2018 18:34 365 user-PC\user CUE.cuecfg
07/02/2018 18:34 <DIR> user-PC\user ..
07/02/2018 18:34 <DIR> user-PC\user .

Comment: Files produced by CUE, automatically or during my access, although I have not made any changes

Corsair modification files at 18:34
71518
There may have been changes in the Windows registry, I have no way of knowing.



--18:48

C:\Users\user\Pictures\2018-01-23
07/02/2018 18:48 67.565 user-PC\user TelaFuncionando.JPG

Comment: ROG SPATHA was working perfectly in wireless mode with ROG ARMORY v10224, and I did a screenshot using SnippingTool from Windows 7


C:\Users\user\AppData\Local\Microsoft\Windows\Hist ory\History.IE5
07/02/2018 18:48 <DIR> user-PC\user MSHist012018020720180208

C:\Users\user\AppData\Local\Microsoft\Windows\Hist ory\History.IE5\MSHist012018020720180208
07/02/2018 18:48 <DIR> user-PC\user ..
07/02/2018 18:48 0 user-PC\user container.dat
07/02/2018 18:48 <DIR> user-PC\user .


Comment: I never use Internet Explorer, it must have been opened as embeded by some other application, must have saved history when it was closed.


SOFTWARE ANALISIS


The application's XML may indicate an attempt to identify a Scimitar mouse.

Opening the configuration files, at the end of the file

C:\Users\user\AppData\Roaming\Corsair\CUE\profiles \"UNIQUE ID".cueprofiledata

71519

I have a Corsair keyboard, but I've never had a Scimitar.

Perhaps this is the source of the all problems: Attempting to execute "Demo" in other hardwares.

I removed CUE from the startup.



NOTE: The Wireless Problem has been solved, but the mouse continues to have problems in the wired mode.

MasterC@ROG
02-12-2018, 02:10 AM
As mentioned previously, please wait until the Live Update feature is ready. When it is, you should be able to update your firmware. From there we can we can determine what to do next. Version 2 of Armoury was actually not supposed to be available to the public last week.

MLGbr
02-17-2018, 02:17 AM
ROG SPATHA STATUS:
Wired: Intermittent detection (less than 2 seconds)
Wireless: Perfect Operation



Connecting the ROG Spatha to the computer in wired mode, with ROG ARMORY 2.04.04 opened - Every 30 seconds Windows seems to try to detect it, but can not,
as if the mouse was connected for 2 seconds and then disconnected.


Windows does not recognize
71690


Windows recognition only 2 seconds
71691


And return to 'not-recognize normal situation' for 30 seconds
71690


After some detection attempts, the behavior stops for a few minutes (leaving the mouse completely dead), and returns again.

Does the administrator have any ideas?

------------------------------------------------------------
What about the mysterious ASUS RMA in Brazil?

After a purchase, how many months does ASUS allow the user to do RMA, with a Brazilian shopping in a store in Brazil?
The manual of the Mouse says "1 month for the physical store", and supposed 6 months given by the Asus brand - It is possible that this guarantee should not be valid in Brazil, neither ASUS staff can answer that.

I tried to go from behind the RMA and had a brutally negative experience.
If the mouse problem is not solved, I'll be posting here what happened.

MasterC@ROG
02-17-2018, 03:12 AM
Sorry the Live Update has been delayed until next week. It is best to wait for that before trying RMA.

For more info about RMA:
https://rog.asus.com/forum/showthread.php?34832-ASUS-Worldwide-RMA-Guide

MasterC@ROG
02-23-2018, 09:51 AM
The new Armoury II (2.04.07) is now available, please try it by going to this thread to download:
https://rog.asus.com/forum/showthrea...ny-issues-here

MLGbr
03-02-2018, 01:06 AM
1) I downloaded Rog Armory 2.04.07 zip file and unzipped into a folder
2) I connected the mouse Rog Spatha on the cable
2b) I use another common mouse to operate the computer
3) Close all Rog Armory executables (ArmoryLiveUpdate.exe, ROG Armory.exe, Mutually Exclusive Aura Agent.exe, MacroAgent.exe) and taskeng.exe
4) Execute Setup.exe of installation
5) I confirmed the uninstallation of Rog Armory previous version.
6) The installation closed and nothing happened.
7) Execute Setup.exe again
8) Installation occurs normally, and prompts you to restart
9) Restart computer
10) Execute Rog Armory (from desktop Link) as administrator
11) Rog Armory detects Rog Spatha mouse.
11b) The mouse pointer slowly slides to the right and down.
12) I make the mouse firmware update
12b) During firmware installation, Windows emits USB connection and disconnection sound several times, but I watch it without interfering.
13) The mouse returned to normal operation

The recorded macro was lost, possibly because of the reinstallation process, but I'm very happy.

:rolleyes::cool::D;):o

MasterC@ROG
03-02-2018, 01:13 AM
Glad everything work out!

MLGbr
03-02-2018, 02:10 AM
I left the computer for 10 minutes.
When I came back,
Windows had a message that USB was not being recognized,
and Rog Spatha's mouse with the lights off.

Since surely the problem is caused by software - 100% by the ROG armory - I rebooted the computer, and the mouse returned to normal.

1) I closed all Rog Armory executables
2) Msconfig and removed "Armory live update" from startup.
3) Restart
4) I waited another 10 minutes, and everything continued normal.


The problem was solved by removing "Armory live update" from startup

It seems like a problem:
- Power management
- Some kind of TimeOut

This is a Rog Armory issue - 100% software;
The mouse working perfect without "Armory live update" from startup.

MLGbr
04-15-2018, 04:53 PM
I found the final solution for the Rog Spatha Mouse.

After

1) Updating Rog Armory
2) Remove Rog Armory from Windows start

I CHANGE THE USB PORT !!!

Windows detected the mouse, did the installation, and now it works perfectly.

Never again of problem of bad detection.

100% solved!!! :D

MasterC@ROG
04-16-2018, 01:35 AM
I found the final solution for the Rog Spatha Mouse.

After

1) Updating Rog Armory
2) Remove Rog Armory from Windows start

I CHANGE THE USB PORT !!!

Windows detected the mouse, did the installation, and now it works perfectly.

Never again of problem of bad detection.

100% solved!!! :D

Which USB port was giving you issues? Front-panel?
DId you update to Armoury 2.04.09?

MLGbr
04-16-2018, 11:19 PM
I'm still with Armory 2.04.07 (I have not updated it since).

Windows had already registered the mouse on that USB port, so it was necessary to change the USB port so WIndows installed the mouse "from scratch" on the computer.

It's a Windows 7 trick.
When a USB device is not properly installed in a USB port (and errors or failures occur), switching the USB port will force Windows to install the hardware "from scratch" on the other port, and the problem disappears.


I use two mouses.

Rog Spatha in the USB 2 front
Another vulgar mouse in rear USB ( was used, when Spatha presented problems )

Thus, complete solution went through 3 steps:

1) Upgrade Rog Armory ( resuscitate the mouse. Before that, it did not even work on another computer. )
2) Remove Rog Armory 2.04.07 from start (fixes the problem of stopping detecting the mouse every 5 minutes)
3) Replace the USB port installation (solve all random detection problems)

Now both mouse are working, in rear USBs ports.

MasterC@ROG
04-17-2018, 06:39 AM
Occasionally the front panel ports and hubs can cause problems, best to go with rear ports when troubleshooting.

Try 2.04.09 if you run into any more issues.

paul roperos
08-13-2020, 05:11 PM
can I post a review here?

CONS
-expensive
-not ergonomic
-too heavy to be a mouse
-crappy scroll wheel
-none stable connectivity (even at 1.5 meter)
-none replaceable battery
-only lazer censor
-not supported by AURA sink
-buggy software
-easy to be lowbat
-no ASUS Support if you have a problem

Pros
-design (looks cool on the desk)
-2 cables include
-2 sticker badge included

Overall a expensive and crappy mouse HAHAHA (dont buy this mouse)