softxpand and windower "Windower Launcher has stopped working"

Started by Zeal , Oct 27 2017 12:36 AM

softxpand miniframe multiseat windower launcher

1 reply to this topic

#1 Zeal

Newbie

Members
1 posts

Posted 27 October 2017 - 12:36 AM

Hello,

I've managed to break windower in a strange way, and i understand if support is difficult since I have what could be qualified as an unsupported setup. This started occurring yesterday the 25th, I run the windower.exe i get the "windower" splash screen and it proceeds no further and crashes. I've narrowed the problem down to the using of softxpand. turn it off, windower works, turn it on, crash. I have not rebuilt the machine yet nor uninstalled/reinstalled windower, it's on my to test list. Softxpand allows for a multiseat session on a windows 7 machine one of it's quirks maybe compounding the windower.exe. Any suggestions are welcomed, I will let you know my results on the softxpand re-install when i get to it. Thank you for your time reviewing this post.

-Zeal

Configuration

window 7 up to date on patching

Norton AV up to date (also tried uninstalled)

softxpand 2011 v1.2.4

My crash.log file contains the following.

`````````````````````````````````````````````````````````````````````

[ 4.3.6504.11447 ] 2017-10-26 23:47:13.6838729 UTC

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

System.ComponentModel.Win32Exception (0x80004005): The operation completed successfully

at Launcher.Display.GetCurrentDisplayMode()

at Launcher.Core.SendInitializationReport()

at Launcher.Core..ctor()

at Launcher.LauncherApplication..ctor(SplashScreen splashinit, LauncherOptions options)

at Launcher.Bootstrap.Main(String[] args)

`````````````````````````````````````````````````````````````````````

Windows event contains the following

Log Name: Application

Source: Windows Error Reporting

Date: 10/26/2017 7:04:34 PM

Event ID: 1001

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Computer: Bahamut

Description:

Fault bucket 750494069, type 30

Event Name: CLR20r3

Response: Not available

Cab Id: 0

Problem signature:

P1: Windower.exe

P2: 4.3.6504.11447

P3: 59ec712e

P4: Windower

P5: 4.3.6504.11447

P6: 59ec712e

P7: d7

P8: 37

P9: System.ComponentModel.Win32

P10:

Attached files:

C:\Users\Zeal\AppData\Local\Temp\WER24C8.tmp.WERInternalMetadata.xml

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Windower.exe_aa32655fa2325caffa63b9f59b6f6b143771c77_1a552a16

Analysis symbol:

Rechecking for solution: 0

Report Id: 68be2207-baaa-11e7-b211-005056c00008

Report Status: 1

Event Xml:

<Channel>Application</Channel>

<Computer>Bahamut</Computer>

</System>

<Data>Not available</Data>

<Data>Windower.exe</Data>

<Data>Windower</Data>

<Data>System.ComponentModel.Win32</Data>

<Data>

</Data>

<Data>

C:\Users\Zeal\AppData\Local\Temp\WER24C8.tmp.WERInternalMetadata.xml</Data>

<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Windower.exe_aa32655fa2325caffa63b9f59b6f6b143771c77_1a552a16</Data>

<Data>

</Data>

</EventData>

</Event>

Log Name: Application

Source: Application Error

Date: 10/26/2017 7:04:33 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: Bahamut

Description:

Faulting application name: Windower.exe, version: 4.3.6504.11447, time stamp: 0x59ec712e

Faulting module name: KERNELBASE.dll, version: 6.1.7601.23915, time stamp: 0x59b94abb

Exception code: 0xe0434352

Fault offset: 0x0000c54f

Faulting process id: 0x1c80

Faulting application start time: 0x01d34eb7298eb264

Faulting application path: D:\FFXI\Windower4\Windower.exe

Faulting module path: C:\Windows\syswow64\KERNELBASE.dll

Report Id: 68be2207-baaa-11e7-b211-005056c00008

Event Xml:

<Channel>Application</Channel>

<Computer>Bahamut</Computer>

</System>

<Data>Windower.exe</Data>

<Data>KERNELBASE.dll</Data>

<Data>D:\FFXI\Windower4\Windower.exe</Data>

<Data>C:\Windows\syswow64\KERNELBASE.dll</Data>

</EventData>

</Event>

Log Name: Application

Source: .NET Runtime

Date: 10/26/2017 7:04:31 PM

Event ID: 1026

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: Bahamut

Description:

Application: Windower.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.ComponentModel.Win32Exception

at Launcher.Display.GetCurrentDisplayMode()

at Launcher.Core.SendInitializationReport()

at Launcher.Core..ctor()

at Launcher.LauncherApplication..ctor(System.Windows.SplashScreen, Launcher.LauncherOptions)

at Launcher.Bootstrap.Main(System.String[])

Event Xml:

<Channel>Application</Channel>

<Computer>Bahamut</Computer>

</System>

<Data>Application: Windower.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.ComponentModel.Win32Exception

at Launcher.Display.GetCurrentDisplayMode()

at Launcher.Core.SendInitializationReport()

at Launcher.Core..ctor()

at Launcher.LauncherApplication..ctor(System.Windows.SplashScreen, Launcher.LauncherOptions)

at Launcher.Bootstrap.Main(System.String[])

</Data>

</EventData>

</Event>

Attached Files

windower_error.JPG 45.25K 3 downloads

Back to top

#2 taff51

Newbie

Members
3 posts

Posted 09 December 2017 - 09:24 PM

I've just started to get this problem as well after doing some major cleanups on my laptop.

Did you work out a solution to the problems at all?

Back to top

Back to Support

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users