Jump to content


Photo

Error CLR20r3 After Windower Update Today


    7 replies to this topic

    #1 Lokimaru

    Lokimaru

      Newbie

    • Members
    • Pip
    • 4 posts

      Posted 28 April 2017 - 03:16 AM

      Hello, Windower had an update today that seems to have caused the hook to think I'm running 32-bit processes?

       

      I have been able to play through Windower for over two weeks now and today's update appears to have broken that.

       

      Here is the crash log:

       

      [ 4.3.6326.35073 ] 2017-04-28 03:13:49.7994537 UTC
      ---------------------------------------------------------------------
      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.ProcessManager.GetModuleInfos(Int32 processId)
         at System.Diagnostics.Process.get_Modules()
         at Windower.Core.Injector.GetRemoteFunctionAddress(String module, String function)
         at Windower.Core.Injector.Inject(String dllPath)
         at Launcher.PlayOnlineLauncher.Launch(String hook, Profile profile, Boolean debug, TimeSpan timeout)
         at Launcher.Tasks.LaunchTask.Run()
         at Launcher.Tasks.Task.Run(Core core)
         at Launcher.Core.Run()
         at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
         at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
         at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
         at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
         at System.Threading.ThreadHelper.ThreadStart()
      `````````````````````````````````````````````````````````````````````
       
      As far as I know, both FFXI and Windower are 64-bit processes on my system.
       
      Edit: FFXI does run without Windower
       
      Thanks!


      #2 Cloudstrafie

      Cloudstrafie

        Newbie

      • Members
      • Pip
      • 9 posts

        Posted 28 April 2017 - 03:59 AM

        Hello, Windower had an update today that seems to have caused the hook to think I'm running 32-bit processes?

         

        I have been able to play through Windower for over two weeks now and today's update appears to have broken that.

         

        Here is the crash log:

         

        [ 4.3.6326.35073 ] 2017-04-28 03:13:49.7994537 UTC
        ---------------------------------------------------------------------
        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.ProcessManager.GetModuleInfos(Int32 processId)
           at System.Diagnostics.Process.get_Modules()
           at Windower.Core.Injector.GetRemoteFunctionAddress(String module, String function)
           at Windower.Core.Injector.Inject(String dllPath)
           at Launcher.PlayOnlineLauncher.Launch(String hook, Profile profile, Boolean debug, TimeSpan timeout)
           at Launcher.Tasks.LaunchTask.Run()
           at Launcher.Tasks.Task.Run(Core core)
           at Launcher.Core.Run()
           at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
           at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
           at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
           at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
           at System.Threading.ThreadHelper.ThreadStart()
        `````````````````````````````````````````````````````````````````````
         
        As far as I know, both FFXI and Windower are 64-bit processes on my system.
         
        Edit: FFXI does run without Windower
         
        Thanks!

        Are you using windower 4.3 or the new Dev release? im having issues with random crashes from 4.3



        #3 Lokimaru

        Lokimaru

          Newbie

        • Members
        • Pip
        • 4 posts

          Posted 28 April 2017 - 04:06 AM

          It is the automatic update and not the dev release.



          #4 mckeyd276

          mckeyd276

            Newbie

          • Members
          • Pip
          • 3 posts

            Posted 28 April 2017 - 06:44 PM

            Has this issue been addressed and how to overcome it??



            #5 Lokimaru

            Lokimaru

              Newbie

            • Members
            • Pip
            • 4 posts

              Posted 28 April 2017 - 07:04 PM

              As of this morning and what appeared to be another small update, the issue is still not fixed.



              #6 mckeyd276

              mckeyd276

                Newbie

              • Members
              • Pip
              • 3 posts

                Posted 28 April 2017 - 07:14 PM

                As of this morning and what appeared to be another small update, the issue is still not fixed.

                i agree - what irritates me the most is that i cant stop it from auto updating, Please reply if im mistaken 


                • Lokimaru likes this

                #7 Lokimaru

                Lokimaru

                  Newbie

                • Members
                • Pip
                • 4 posts

                  Posted 29 April 2017 - 07:25 PM

                  The issue appears to have been resolved in a patch today! If you had the same problem, try logging in through Windower. 



                  #8 Manaroth

                  Manaroth

                    Member

                  • Members
                  • PipPip
                  • 11 posts

                    Posted 30 April 2017 - 01:37 AM

                    Moved to new post think this may have been wrong spot






                    1 user(s) are reading this topic

                    0 members, 1 guests, 0 anonymous users