Skip to main content
July 25, 2017
Question

Adobe Flash hard freezes computer in all browsers!

  • July 25, 2017
  • 2 replies
  • 5946 views

I have Windows 7 and I'm using Firefox. Everything is up to date. Adobe hard freezes my computer, but only certain videos do it. I found out that it's the non-HTML5 videos that do it, and other videos are fine. YouTube videos always work for me just fine, but most of the videos shown they post on MSN completely locks up my computer. I have tried manually uninstalling and reinstalling Flash, deleting files related to Flash that a normal uninstallation does not remove. No luck. Internet Explorer and Google Chrome do the same thing.

This all started after I made the stupid decision to use ComboFIX in order to try and fix a certain issue I was having. Flash was working fine before that. I've reinstalled Windows since then, but it wasn't a clean reinstall(I really don't want to do that), and it didn't really help too much. I'm thinking maybe this is a registry issue?

This topic has been closed for replies.

2 replies

jeromiec83223024
Inspiring
August 11, 2017

At this point, if it's actually crashing, I really need a crash dump to tell you what's going on.  Your symptoms are super weird, and I'm out of good guesses.  I'm pretty sure it's crashing below us, but I need concrete data to give you a real answer.

Please see the following guide on how to report a crash or error:

https://helpx.adobe.com/flash-player/kb/report-flash-player-crash.html

jeromiec83223024
Inspiring
July 25, 2017

Please work through the video troubleshooting guide.

https://helpx.adobe.com/flash-player/kb/video-playback-issues.html

In particular, check out the part about disabling hardware acceleration.  Does the problem go away?

July 27, 2017

No. That's one of the first things I tried.

jeromiec83223024
Inspiring
July 27, 2017

Yeah, registry cleaners can definitely leave the machine in a bad state.  Microsoft has a lot to say about them, all of which basically comes down to "don't".

I'm definitely not aware of a widespread issue where we're taking down machines.

We don't have direct access to the hardware, so it's pretty difficult to take the whole machine down ourselves.  What's much more likely, is that we're calling into an intermediary Windows API in a totally reasonable way, but in the context of your system, it tickles the thing that ultimately brings the system down. 

In most cases, this is usually a case of ticking a video driver bug.  The driver *does* have direct hardware access, and can definitely bring the whole machine down.  This is why I was asking about disabling hardware acceleration.

In your case, it sounds like Windows might not be in a great state.  Instead of a driver issue, it might be a privileged system call (windows kernel, etc.), which ultimately leads to the crash.  A scenario where a privileged system call gets some garbage (or nonexistent) registry data and then operates on it would be a pretty reasonable guess. 

Analyzing the crash dump and tracking it back to some discrete action that you could take to "fix" the issue would be far more painful and time consuming than doing a clean install, and would likely have a much, much lower chance of success.  It sounds like you've already explored the reasonable things.