[Solved] BSOD from Adobe Flash Player Updater
As I have seen several BSOD threads over time, I wanted to throw this out for folks who are trying to track BSODs while "using SONAR" and blaming SONAR for them.
In the past three years, I have gotten BSODs from primariy two sources - Adobe updating utilities, and Realtek crapping out. Realtek is predicable and avoidable, but the Adobe crash (although can be mitigated) is not so much. Adobe is the one that "gets my goat" and I wanted to at least throw out what is repeatable about this -
This morning I was using X3 and a short way into the work, a BSOD pops up. Is often a 00000F4 error, but not always (and the process is always something off the wall).
What is 100% consistent after these is the "Adobe Flash Player" updater window pops up on reboot (and I already have the latest version each time). There is always a "Adobe Flash Player Installer" "FlashUtil64_14_0_0_145_ActiveX.exe" (long gross name) running in the task manager after reboot (and was somehow triggered prior to the BSOD.
Mitigation (with Acrobat) can be done through msconfig and disabling Adobe Acrobat Updater Service, however, launching Acrobat will re-enable that registry entry. The FlashUtil64_14_0_0_145_ActiveX.exe seems to pop off with anything that uses flash.
General gripe for info, sorry. The Acrobat issue requires remembering when Acrobat was launched last to disable the msconfig registry entry (which is cumbersome at best), but the Flash utility issue unto itself seems to account for 75% of the BSODs I have experienced in the past 3.5 years.
LOL... since I
was using X3 during the BSOD, I guess I "could" have titled the thread "X3 BSOD, SONAR stinks!!!"

But on a serious note, I wanted to share that this is incredibly consistent, yet I have not been able to eliminate it... so if anyone has a tip how to better manage this I am open to suggestions. Adobe has so many invasive anti-piracy hooks that it ticks a paying customer like myself off completely.
Edit: I just wanted to tack this link on here as it gives more information on this file (so I can track this more later): http://www.freefixer.com/library/file/FlashUtil64_14_0_0_145_ActiveX.exe-134014/ There are also a couple registry entries on this from this link that I will want to check later too:
http://www.bleepingcomputer.com/forums/t/540783/unable-to-detect-reason-for-bsod/(the link title says it all!!)
The most upsetting for me is if you choose "Never Remind Me" it doesn't take (seems to be identical to "Remind Me Later"), and "Remind Me Later" seems to trigger it at exactly the 7-day mark (or some such).
I will add to this thread when I get more info.
post edited by mettelus - 2015/01/04 16:00:08