Flash crashes Windows App (using ActiveX Shockwave COM Flash-Object)

Question

Hi,
I developed a program via Visual Basic Express 2010 using a flashplayer COM ActiveX object to run some content.
It happens, that the App crashes telling me that flash32 is the initiator. I can't say when - it crashes at different times, sometimes after an hour, sometimes after 3 days. The program itself runs stable.
PC: Win7 professional 64, IE9, up to date, nothing else installed (except realVNC)
Error Report:
Problemsignatur:
  Problemereignisname:    APPCRASH
  Anwendungsname:    ***.exe
  Anwendungsversion:    1.0.0.0
  Anwendungszeitstempel:    511cc151
  Fehlermodulname:    Flash32_11_6_602_180.ocx
  Fehlermodulversion:    11.6.602.180
  Fehlermodulzeitstempel:    513013da
  Ausnahmecode:    c0000005
  Ausnahmeoffset:    004b1409
  Betriebsystemversion:    6.1.7601.2.1.0.256.48
  Gebietsschema-ID:    1031
  Zusatzinformation 1:    0a9e
  Zusatzinformation 2:    0a9e372d3b4ad19135b953a78882e789
  Zusatzinformation 3:    0a9e
  Zusatzinformation 4:    0a9e372d3b4ad19135b953a78882e789
Last week I updatet flash from 11.4 to 11.6 -> same problem.
Today I updatet it to 11.7 -> same problem.
Some weeks ago we had to replace the old machine completely using winXP 32bit, flash 9 or 10 (not sure, think it was 10).
1. should I try an older version of flash? found some similar problems using the IE, but I dont use the IE and these threads have no solution.
2. how to enable a flash error reporting in this VB-Flash solution?
Thanks and greetings!

Answer 1

1. "User-Agent Strings"
Microsoft "rewrote" the User-Agent Strings for the abomination they call their latest and greatest browser. User-Agent Strings are what websites use to identify the browser you're using and provide the proper content for it's browser engine, like ActiveX stuff, and Flash or HTML5 video. Thanks to the geniuses in Redmond, WA, the User-Agent Strings for IE11 (which has a Trident engine), ID it as either "Gecko" (Firefox) or "Webkit" (Chrome). Problem is: when the site the directs to the content for one of these two engines, the Trident engine in IE can't intepret it and the site then sees IE as an "unidentified" browser.Microsoft has no immediate plans to "fix" the mess they've created.
2. Chrome is a 32 bit browser, and will identify as such, including the plug-ins in it.
IE uses the plug-in from the SyWOW64 folder (WOW=Windows On WIndows - which runs 32 bit apps in the 64 bit environment)