Lemmy Posted September 1, 2016 Report Share Posted September 1, 2016 (edited) 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: 0x56f398baFaulting module name: Flirc.exe, version: 1.0.0.0, time stamp: 0x56f398baException code: 0xc0000005Fault offset: 0x0001ff94Faulting process id: 0x1994Faulting application start time: 0x01d2049f0af0fd6aFaulting application path: C:\Program Files (x86)\Flirc\Flirc.exeFaulting module path: C:\Program Files (x86)\Flirc\Flirc.exeReport Id: b6c1dd72-5956-4c80-a8f2-eb2893319591Faulting 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=1EventType=APPCRASHEventTime=131172420282535707ReportType=2Consent=1UploadTime=131172420283160532ReportIdentifier=48ebb5db-7092-11e6-a938-408d5cc29c97IntegratorReportIdentifier=b6c1dd72-5956-4c80-a8f2-eb2893319591WOW64=1NsAppName=Flirc.exeResponse.BucketId=7567d99cd518808e0a897819e88a697eResponse.BucketTable=1Response.LegacyBucketId=108049589966Response.type=4Sig[0].Name=Application NameSig[0].Value=Flirc.exeSig[1].Name=Application VersionSig[1].Value=1.0.0.0Sig[2].Name=Application TimestampSig[2].Value=56f398baSig[3].Name=Fault Module NameSig[3].Value=Flirc.exeSig[4].Name=Fault Module VersionSig[4].Value=1.0.0.0Sig[5].Name=Fault Module TimestampSig[5].Value=56f398baSig[6].Name=Exception CodeSig[6].Value=c0000005Sig[7].Name=Exception OffsetSig[7].Value=0001ff94DynamicSig[1].Name=OS VersionDynamicSig[1].Value=10.0.10586.2.0.0.256.48DynamicSig[2].Name=Locale IDDynamicSig[2].Value=1043DynamicSig[22].Name=Additional Information 1DynamicSig[22].Value=1eccDynamicSig[23].Name=Additional Information 2DynamicSig[23].Value=1ecc43bbf5e7873ebf6fec7da93f19acDynamicSig[24].Name=Additional Information 3DynamicSig[24].Value=22daDynamicSig[25].Name=Additional Information 4DynamicSig[25].Value=22dac85fa4092451508d6593f9987781UI[2]=C:\Program Files (x86)\Flirc\Flirc.exeUI[3]=Flirc.exe has stopped workingUI[4]=Windows can check online for a solution to the problem.UI[5]=Check online for a solution and close the programUI[6]=Check online for a solution later and close the programUI[7]=Close the programLoadedModule[0]=C:\Program Files (x86)\Flirc\Flirc.exeLoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dllLoadedModule[2]=C:\Windows\SYSTEM32\KERNEL32.DLLLoadedModule[3]=C:\Windows\SYSTEM32\KERNELBASE.dllLoadedModule[4]=C:\Windows\SYSTEM32\ADVAPI32.DLLLoadedModule[5]=C:\Windows\SYSTEM32\msvcrt.dllLoadedModule[6]=C:\Windows\SYSTEM32\sechost.dllLoadedModule[7]=C:\Windows\SYSTEM32\RPCRT4.dllLoadedModule[8]=C:\Windows\SYSTEM32\SspiCli.dllLoadedModule[9]=C:\Windows\SYSTEM32\CRYPTBASE.dllLoadedModule[10]=C:\Windows\SYSTEM32\bcryptPrimitives.dllLoadedModule[11]=C:\Windows\SYSTEM32\COMDLG32.DLLLoadedModule[12]=C:\Windows\SYSTEM32\combase.dllLoadedModule[13]=C:\Windows\SYSTEM32\shcore.dllLoadedModule[14]=C:\Windows\SYSTEM32\USER32.dllLoadedModule[15]=C:\Windows\SYSTEM32\GDI32.dllLoadedModule[16]=C:\Windows\SYSTEM32\SHLWAPI.dllLoadedModule[17]=C:\Windows\SYSTEM32\SHELL32.dllLoadedModule[18]=C:\Windows\SYSTEM32\cfgmgr32.dllLoadedModule[19]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.10586.0_none_811bc0006c44242b\COMCTL32.dllLoadedModule[20]=C:\Windows\SYSTEM32\windows.storage.dllLoadedModule[21]=C:\Windows\SYSTEM32\kernel.appcore.dllLoadedModule[22]=C:\Windows\SYSTEM32\powrprof.dllLoadedModule[23]=C:\Windows\SYSTEM32\profapi.dllLoadedModule[24]=C:\Windows\SYSTEM32\FirewallAPI.dllLoadedModule[25]=C:\Windows\SYSTEM32\NETAPI32.dllLoadedModule[26]=C:\Windows\SYSTEM32\IMM32.DLLLoadedModule[27]=C:\Windows\SYSTEM32\OLE32.dllLoadedModule[28]=C:\Windows\SYSTEM32\OLEAUT32.DLLLoadedModule[29]=C:\Windows\SYSTEM32\WS2_32.dllLoadedModule[30]=C:\Windows\SYSTEM32\DAVHLPR.DLLLoadedModule[31]=C:\Windows\SYSTEM32\WINSPOOL.DRVLoadedModule[32]=C:\Windows\SYSTEM32\WINMM.DLLLoadedModule[33]=C:\Windows\SYSTEM32\bcrypt.dllLoadedModule[34]=C:\Windows\SYSTEM32\WINMMBASE.dllLoadedModule[35]=C:\Windows\SYSTEM32\fwbase.dllLoadedModule[36]=C:\Windows\system32\uxtheme.dllLoadedModule[37]=C:\Windows\SYSTEM32\MSCTF.dllLoadedModule[38]=C:\Windows\system32\dwmapi.dllLoadedModule[39]=C:\Windows\SYSTEM32\clbcatq.dllLoadedModule[40]=C:\Windows\system32\dataexchange.dllLoadedModule[41]=C:\Windows\system32\d3d11.dllLoadedModule[42]=C:\Windows\system32\dcomp.dllLoadedModule[43]=C:\Windows\system32\dxgi.dllLoadedModule[44]=C:\Windows\system32\twinapi.appcore.dllLoadedModule[45]=C:\Windows\SYSTEM32\SetupAPI.dllLoadedModule[46]=C:\Windows\SYSTEM32\libusbK.DLLLoadedModule[47]=C:\Windows\SYSTEM32\wintrust.DLLLoadedModule[48]=C:\Windows\SYSTEM32\MSASN1.dllLoadedModule[49]=C:\Windows\SYSTEM32\CRYPT32.dllLoadedModule[50]=C:\Windows\SYSTEM32\winusb.dllLoadedModule[51]=C:\Windows\SYSTEM32\hid.dllLoadedModule[52]=C:\Windows\SYSTEM32\DEVOBJ.dllState[0].Key=Transport.DoneStage1State[0].Value=1FriendlyEventName=Stopped workingConsentKey=APPCRASHAppName=Flirc.exeAppPath=C:\Program Files (x86)\Flirc\Flirc.exeNsPartner=windowsNsGroup=windows8ApplicationIdentity=41599A98A01D088430356291B20435[End of WER file content]The question remains the same, how can I get the GUI running? Edited September 2, 2016 by Lemmy Update after some research Quote Link to comment Share on other sites More sharing options...
houndie Posted October 28, 2016 Report Share Posted October 28, 2016 (edited) Having same issue, did you fix this somehow? Edit: nm turns out the usb port i was using didnt like the dongle. Edited October 28, 2016 by houndie Quote Link to comment Share on other sites More sharing options...
Lemmy Posted October 29, 2016 Author Report Share Posted October 29, 2016 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! Quote Link to comment Share on other sites More sharing options...
Florarctus Posted December 8, 2016 Report Share Posted December 8, 2016 (edited) 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! Hello I have the same problem with windows 10 how you solved? Edited December 8, 2016 by Florarctus Quote Link to comment Share on other sites More sharing options...
PolloLoco Posted December 8, 2016 Report Share Posted December 8, 2016 (edited) I have had this problem since yesterday, for a flirc that has been working for over a year. I recently got a 2016 Fire TV Stick and wanted to map the home button correctly for my Harmony remote. I installed the new flirc software, plugged in the flirc and it immediately crashed with "flirc exe has stopped working". I then tried to install the software on 3 different Windows 10 Pc's. The same crash, but my flirc still worked on the HTPC with the previous button settings - so I disagreed that it could be defective as with the above comments. I then dug an ancient Viliv S5 slate out of my drawer, charged it up - and since it was running Windows 7 - it worked fine. I was able to set up the flirc to work perfectly with my Fire TV Stick. In the short term, a fix is to use a non Windows 10 pc. Long term, the software should be fixed for Windows 10. Edited December 8, 2016 by PolloLoco Quote Link to comment Share on other sites More sharing options...
Ryan Breeze Posted December 8, 2016 Report Share Posted December 8, 2016 I'm experiencing the same issue. This should REALLY be stressed to potential customers BEFORE we buy the product. Instead of it working out of the box, I'm having to set up a Linux virtual machine to get something working because I don't want to have to go through the trouble of sending it back. If it works after, I'll be satisfied, but this is not how I envisioned spending my time after a hard day at work. Quote Link to comment Share on other sites More sharing options...
yawor Posted December 9, 2016 Report Share Posted December 9, 2016 (edited) Windows 10 is a moving target. Current crashes may be caused by some recent system updates. It's hard to test on every single hardware and software configuration. For example some fix that makes the app work on latest version of Windows may cause it not to work on previous or vice versa.Which software version do you use? Have you already tried the latest 2.0.0? Edited December 9, 2016 by yawor Quote Link to comment Share on other sites More sharing options...
Florarctus Posted December 9, 2016 Report Share Posted December 9, 2016 Windows 10 è un bersaglio in movimento. crash correnti possono essere causate da alcuni recenti aggiornamenti del sistema. E 'difficile da testare su ogni singola configurazione hardware e software. Per esempio qualche correzione che rende il lavoro app ultima versione di Windows può causare non lavorare su precedente o viceversa.Quale versione del software utilizzate? Avete già provato l'ultima 2.0.0?2.0.0 Quote Link to comment Share on other sites More sharing options...
benjamin Posted December 10, 2016 Report Share Posted December 10, 2016 (edited) same problem here win10 64bits flirc 2.0.0does not work either if I run flirc.exe as administrator Does someone can give the previous version (1.4.4 I think) thank you very much Edited December 10, 2016 by ben Quote Link to comment Share on other sites More sharing options...
Florarctus Posted December 12, 2016 Report Share Posted December 12, 2016 (edited) I solved programming flirc-se in Windows 7, and after installation Windows 10.I have not installed the driver in Windows 10. I left unknown device.In this way, it works.I'm hoping for an update. Edited December 12, 2016 by Florarctus Quote Link to comment Share on other sites More sharing options...
deck Posted December 13, 2016 Report Share Posted December 13, 2016 Same issue with 2.0.1. Win 10 x64. If dongle is plugged in, flirc.exe crashes. Quote Link to comment Share on other sites More sharing options...
estephano Posted December 14, 2016 Report Share Posted December 14, 2016 Hello! Same problem here. Worked before, now flirc.exe crashed as soon as dongle is plugged in on 2 different devices running Windows 10. When will this be fixed? Quote Link to comment Share on other sites More sharing options...
Florarctus Posted December 15, 2016 Report Share Posted December 15, 2016 2.0.2 Windows 10 OK Quote Link to comment Share on other sites More sharing options...
mr_black Posted December 20, 2016 Report Share Posted December 20, 2016 Decided to try the new Flirc, plugged the old one in first, upgraded fw, saved config then swapped for the new one. Unfortunately I've had the same error msg which only happens with the new dongle?Windows 8.1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.