flirc.exe crashes upon launching

[synthecypher]

flirc.exe crashes upon launching when the dongle is plugged in. If I leave it unplugged and launch flirc.exe it works, but as soon as I plug in the dongle flirc.exe crashes.

Any ideas?

I'm on Windows 8.1 using v1.2.4

 

:)

[TheRotag]

I'm seeing the same behavior, though I'm running version 1.2.6. Like the OP, I'm on Windows 8.1. I tried uninstalling the Flirc software, rebooting, reinstalling it, and then reconnecting the dongle. No change. I would try force upgrading the firmware on the dongle, but alas, can't do that without the software! What's the next step?

[rcketscientist]

The first time I connected 1.2.7 rc12 it mentioned a firmware upgrade.  I elected to install it.  The GUI immediately crashed.  Now any time I open the app it crashes immediately:

 

Problem signature:

  Problem Event Name: APPCRASH

  Application Name: Flirc.exe

  Application Version: 1.0.0.0

  Application Timestamp: 5417d5ea

  Fault Module Name: Flirc.exe

  Fault Module Version: 1.0.0.0

  Fault Module Timestamp: 5417d5ea

  Exception Code: c0000005

  Exception Offset: 000200ab

  OS Version: 6.3.9600.2.0.0.272.7

  Locale ID: 1033

  Additional Information 1: 39ff

  Additional Information 2: 39ff9f3dbae998697945453364708e3d

  Additional Information 3: d33f

  Additional Information 4: d33f9a336787301fff2d8076c353740c

 

Please let me know how to fix this.  I haven't even gotten a chance to try it out yet.

[rcketscientist]

Uninstalled and reinstalled, but still crashes immediately on open.  Uninstalled again and reinstalled the official release and crashes immediately upon open.  At this point I'm inclined to point to a bricked firmware.  Any way to manually patch the firmware?

[nickveldrin]

I'm also suffering from this problem, and am only running server2012r2 and windows 8.1 machines in my home and work.

 

I'll be happy to work with any developers to try to resolve the issue.

[nickveldrin]

Both the flirc.exe and the flirc_util.exe crash, the latter of which states 'Warning: cannot open usb device' and both create windows application log crash bundles that we can submit if it would help. Here's the text:

 

Fault bucket 73621029923, type 1

Event Name: APPCRASH

Response: Not available

Cab Id: 0

 

Problem signature:

P1: Flirc.exe

P2: 1.0.0.0

P3: 544db551

P4: Flirc.exe

P5: 1.0.0.0

P6: 544db551

P7: c0000005

P8: 0001fae0

P9: 

P10: 

 

Attached files:

C:\Users\xbmc\AppData\Local\Temp\WERDD7B.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Flirc.exe_27b6f8f9edf11f2e6dbd8636d897e896a863984_60561eeb_090a0111

 

Analysis symbol: 

Rechecking for solution: 0

Report Id: aaa1e1aa-5fd7-11e4-8266-dc85deb87652

Report Status: 0

Hashed bucket: 5345b14e590414e51d9d315b2ed863cb

 

------

Fault bucket 73621070462, type 1

Event Name: APPCRASH

Response: Not available

Cab Id: 0

 

Problem signature:

P1: flirc_util.exe

P2: 0.0.0.0

P3: 544db546

P4: flirc_util.exe

P5: 0.0.0.0

P6: 544db546

P7: c0000005

P8: 0000b214

P9: 

P10: 

 

Attached files:

C:\Users\xbmc\AppData\Local\Temp\WER1C21.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_flirc_util.exe_74771852a9d26f6a2be2d3b1ab45407d4f4d440_09afa46b_115722b8

 

Analysis symbol: 

Rechecking for solution: 0

Report Id: 84bba988-5fdb-11e4-8266-dc85deb87652

Report Status: 1

Hashed bucket: 44c229267f46d153fb26ae90a383e8be

[nickveldrin]

OK i actually made it through my issue by using that ZADIG utility https://flirc.zendesk.com/hc/en-us/articles/200712548-Using-the-ZADIG-Utility by reinstalling the driver in the instructions in the post, then plugging the FLIRC to a different port.

 

I originally had it in a USB2 port on my MB then when moving it to a USB3 after doing that ZADIG driver reinstall, it actually worked without crashing.

[crimper]

Have the same issue. Win7 64-bit. Had the utility installed for one day, barely had the device configured. Moved my USB keyboard to the Kodi box (to test Ctrl+F12 suspend) and then re-attached it to a different USB port. That triggered Windows keyboard driver installation process and I guess messed up something in the USB driver chain. Tried re-installing, removing the driver and re-installing, different compatibility options and tried the ZADIG utility. 

[Emmanuel]

Same problem with a flirc.se tried both methods of driver install and problem persists