Jump to content
Flirc Forums

Lemmy

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by Lemmy

  1. Houndie, I suppose your problem is solved now?

    For the record: my problem is solved to. I've got a reply from Jason from Flirq that he had seen this problem only once or twice before. The only solution according to Jason was to replace the unit for a new one.

    I told this to the supplier and I returned the unit to them. Strange enough the unit worked perfectly when they tested it, so it took some time to convince them to send me a new one. The new unit works fine, my problem is solved!

  2. Just installed de Flirc SE edition in my HTPC running Windows 10. I downloaded and installed the latest installation software. In the Devicemanager under "libusbK USB Devices" there is a "flirc bootloader" visible, so the installation looks OK. 

    However when starting the Flirc GUI the application appears, immediately followed by the message "Flirc.exe has stopped working. Windows is checking for a solution of the problem", and again immediately followed by a message "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available". The only button showing is "Close program", and when pressing this button both the error massage and the mainscreen of the Flirc GUI dissappear....

    Any idea how to get the GUI working?

    Update: I did some research, maybe this will help:
    In "Computer Management (Local) / System Tools / Event Viewer / Windows Logs / Application" I found the error message:

    [Begin of error message]

    Faulting application name: Flirc.exe, version: 1.0.0.0, time stamp: 0x56f398ba
    Faulting module name: Flirc.exe, version: 1.0.0.0, time stamp: 0x56f398ba
    Exception code: 0xc0000005
    Fault offset: 0x0001ff94
    Faulting process id: 0x1994
    Faulting application start time: 0x01d2049f0af0fd6a
    Faulting application path: C:\Program Files (x86)\Flirc\Flirc.exe
    Faulting module path: C:\Program Files (x86)\Flirc\Flirc.exe
    Report Id: b6c1dd72-5956-4c80-a8f2-eb2893319591
    Faulting package full name: 
    Faulting package-relative application ID: 

    [End of error message]

    In the Registry I searched for "Flirc"  and there was a link to "C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Flirc.exe_d0fe6a7a891226f04a80b6257c6fa098e7b2e1a3_a6c57563_16bd12f6"

    The content of this WER file is as follows:

    [Begin of WER file content]

    Version=1
    EventType=APPCRASH
    EventTime=131172420282535707
    ReportType=2
    Consent=1
    UploadTime=131172420283160532
    ReportIdentifier=48ebb5db-7092-11e6-a938-408d5cc29c97
    IntegratorReportIdentifier=b6c1dd72-5956-4c80-a8f2-eb2893319591
    WOW64=1
    NsAppName=Flirc.exe
    Response.BucketId=7567d99cd518808e0a897819e88a697e
    Response.BucketTable=1
    Response.LegacyBucketId=108049589966
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=Flirc.exe
    Sig[1].Name=Application Version
    Sig[1].Value=1.0.0.0
    Sig[2].Name=Application Timestamp
    Sig[2].Value=56f398ba
    Sig[3].Name=Fault Module Name
    Sig[3].Value=Flirc.exe
    Sig[4].Name=Fault Module Version
    Sig[4].Value=1.0.0.0
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=56f398ba
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000005
    Sig[7].Name=Exception Offset
    Sig[7].Value=0001ff94
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.10586.2.0.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1043
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=1ecc
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=1ecc43bbf5e7873ebf6fec7da93f19ac
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=22da
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=22dac85fa4092451508d6593f9987781
    UI[2]=C:\Program Files (x86)\Flirc\Flirc.exe
    UI[3]=Flirc.exe has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution and close the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    LoadedModule[0]=C:\Program Files (x86)\Flirc\Flirc.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\SYSTEM32\KERNEL32.DLL
    LoadedModule[3]=C:\Windows\SYSTEM32\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\SYSTEM32\ADVAPI32.DLL
    LoadedModule[5]=C:\Windows\SYSTEM32\msvcrt.dll
    LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
    LoadedModule[7]=C:\Windows\SYSTEM32\RPCRT4.dll
    LoadedModule[8]=C:\Windows\SYSTEM32\SspiCli.dll
    LoadedModule[9]=C:\Windows\SYSTEM32\CRYPTBASE.dll
    LoadedModule[10]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
    LoadedModule[11]=C:\Windows\SYSTEM32\COMDLG32.DLL
    LoadedModule[12]=C:\Windows\SYSTEM32\combase.dll
    LoadedModule[13]=C:\Windows\SYSTEM32\shcore.dll
    LoadedModule[14]=C:\Windows\SYSTEM32\USER32.dll
    LoadedModule[15]=C:\Windows\SYSTEM32\GDI32.dll
    LoadedModule[16]=C:\Windows\SYSTEM32\SHLWAPI.dll
    LoadedModule[17]=C:\Windows\SYSTEM32\SHELL32.dll
    LoadedModule[18]=C:\Windows\SYSTEM32\cfgmgr32.dll
    LoadedModule[19]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.10586.0_none_811bc0006c44242b\COMCTL32.dll
    LoadedModule[20]=C:\Windows\SYSTEM32\windows.storage.dll
    LoadedModule[21]=C:\Windows\SYSTEM32\kernel.appcore.dll
    LoadedModule[22]=C:\Windows\SYSTEM32\powrprof.dll
    LoadedModule[23]=C:\Windows\SYSTEM32\profapi.dll
    LoadedModule[24]=C:\Windows\SYSTEM32\FirewallAPI.dll
    LoadedModule[25]=C:\Windows\SYSTEM32\NETAPI32.dll
    LoadedModule[26]=C:\Windows\SYSTEM32\IMM32.DLL
    LoadedModule[27]=C:\Windows\SYSTEM32\OLE32.dll
    LoadedModule[28]=C:\Windows\SYSTEM32\OLEAUT32.DLL
    LoadedModule[29]=C:\Windows\SYSTEM32\WS2_32.dll
    LoadedModule[30]=C:\Windows\SYSTEM32\DAVHLPR.DLL
    LoadedModule[31]=C:\Windows\SYSTEM32\WINSPOOL.DRV
    LoadedModule[32]=C:\Windows\SYSTEM32\WINMM.DLL
    LoadedModule[33]=C:\Windows\SYSTEM32\bcrypt.dll
    LoadedModule[34]=C:\Windows\SYSTEM32\WINMMBASE.dll
    LoadedModule[35]=C:\Windows\SYSTEM32\fwbase.dll
    LoadedModule[36]=C:\Windows\system32\uxtheme.dll
    LoadedModule[37]=C:\Windows\SYSTEM32\MSCTF.dll
    LoadedModule[38]=C:\Windows\system32\dwmapi.dll
    LoadedModule[39]=C:\Windows\SYSTEM32\clbcatq.dll
    LoadedModule[40]=C:\Windows\system32\dataexchange.dll
    LoadedModule[41]=C:\Windows\system32\d3d11.dll
    LoadedModule[42]=C:\Windows\system32\dcomp.dll
    LoadedModule[43]=C:\Windows\system32\dxgi.dll
    LoadedModule[44]=C:\Windows\system32\twinapi.appcore.dll
    LoadedModule[45]=C:\Windows\SYSTEM32\SetupAPI.dll
    LoadedModule[46]=C:\Windows\SYSTEM32\libusbK.DLL
    LoadedModule[47]=C:\Windows\SYSTEM32\wintrust.DLL
    LoadedModule[48]=C:\Windows\SYSTEM32\MSASN1.dll
    LoadedModule[49]=C:\Windows\SYSTEM32\CRYPT32.dll
    LoadedModule[50]=C:\Windows\SYSTEM32\winusb.dll
    LoadedModule[51]=C:\Windows\SYSTEM32\hid.dll
    LoadedModule[52]=C:\Windows\SYSTEM32\DEVOBJ.dll
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=Flirc.exe
    AppPath=C:\Program Files (x86)\Flirc\Flirc.exe
    NsPartner=windows
    NsGroup=windows8
    ApplicationIdentity=41599A98A01D088430356291B20435

    [End of WER file content]

    The question remains the same, how can I get the GUI running?

     

×
×
  • Create New...