Opera stopped working
-
ronnieb45 last edited by
I was online this morning and everything was fine until about noon. Web pages then stopped loading. I had to go out so I shut everything down and when I returned Opera wasn't opening at all. I deleted it and re-installed it but still nothing. I checked my firewall and it was listed as OK. Win7 64 bit OS. IE and Chrome work fine, but I like Opera better. What could be wrong?
-
lando242 last edited by
A whole bunch of things. Which version of Opera are you using? That might help us narrow is down. Also, whats the exact error message you receive? Do you have any toolbars or extensions installed? Any weird apps running in the background (RocketTab, ShopOp, PennyBee, etc)?
-
ronnieb45 last edited by
You're comment made me realize what happened. I was activating some software that I use and the program froze when I clicked the activation link. I'm pretty sure I had the latest version of Opera installed and I have the latest version installed now. No toolbars or extensions are installed and I only have a digital clock app running on screen. There is no error message, just an hourglass appears for a few seconds. I just thought of something, I'm haven't shut the pc down. I'm going to reboot now and see what happens. Thanks.
-
blackbird71 last edited by
Glad to hear it! I've had something similar happen a time or two with IE, Firefox, and Presto Opera, all on this Win7-64 system. And like you, in each case it took a machine restart to ultimately clear it... so perhaps it has something to do with hangups in the general browser interfacing methodology with the OS or something of that sort.
-
pumpf last edited by
I'm having the same problem... and I'm not doing anything different. Actually, the last time opera worked was before my last shut down. Now it won't open. I tried installing the latest- but no good. Thoughts?
I'm using Windows 7, if that helps. -
blackbird71 last edited by
Have you tried opening Opera, then immediately checking in the Windows Event Viewer for both the System and Application sections to see what, if any, error messages may be present. Also, check back through the logs to around the times of that shutdown after the last time Opera worked and then when the system was later first restarted. Check each of any yellow warning symbols, but especially any red "critical" error symbols.
-
linuxmint7 last edited by
Have you tried opening Opera, then immediately checking in the Windows Event Viewer for both the System and Application sections to see what, if any, error messages may be present. Also, check back through the logs to around the times of that shutdown after the last time Opera worked and then when the system was later first restarted. Check each of any yellow warning symbols, but especially any red "critical" error symbols.
I did. It shows an error in ntdll.dll
Looks like I have the same effect like the post author. That occurred right after a windows update.
Both my old Opera and the newest one behave the same, do not start at all.
Have reported a bug at https://bugs.opera.com/wizarddesktop/ -
blackbird71 last edited by
Suddenly-appearing problems in a previously-working program where malware is known not to have just been downloaded often involve either: a hardware failure (in this case, not so likely), a sudden power interruption, or the installation/activation of new software (either updates for the program itself or installing/updating other programs). When or if the original problem can somehow be solidly linked to an 'error' involving ntdll.dll, it often stems from some kind of installation conflict with a driver, an OS update, or new software. This latter is not a hard-and-fast rule, but it is a fairly commonly-experienced troubleshooting pattern.
It is also one of the deadly surprises that occasionally accompany the increasing practice of silent "automatic updating" of computer software, particularly when those updates occur either randomly or at different times. That is, the user quite often cannot make an immediate knowledgeable connection between a particular update and the sudden appearance of problems, often in unrelated software. With anti-malware, operating systems, and installed apps all auto-updating at their own particular rhythms, recognizing and tracking down the cause of an update-related problem is made all the more difficult - if it can even be recognized that an update occurred just prior to the problem onset.
I cannot prove it's the same situation, but this is very reminiscent of a Microsoft 'update to Windows' involving an MS-pushed Nvidia driver update about 2-3 years ago. Certain apps programs (but not all) lost certain functionality (but not all), while some other programs refused to start. In that case, the Nvidia driver was the cause, ntdll.dll was the intermediate software, and removing the update and reverting the driver solved the problem for affected users. I do know that the recent Microsoft update batches (Dec 9) contained at least 3 separate updates that have thus far been reported by different users as causing various problems on different systems... though none seem to fully fit your description, unfortunately (3008923, 3004394 (since "pulled" by MS), and 2553154).