Opera auto-updater has stopped working

[robervin1]

robervin1 last edited by

I get this error message from Opera constantly now. "Opera auto-updater has stopped working."
Here are the error details:
Problem Event Name: BEX
Application Name: opera_autoupdate.exe
Application Version: 44.0.2510.857
Application Timestamp: 58d01e54
Fault Module Name: StackHash_0a9e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 2a000000
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

[leocg]

leocg Moderator Volunteer last edited by

Try download and run the installer to see if it fix the issue.

[robervin1]

robervin1 last edited by

I did just that, downloaded the installer and ran it. It seemed to work for a couple of days. Now I get the same error message again.

[zalex108]

zalex108 last edited by

Is your system working fine?

Since when do you receive that error?
What happened the same day or few days before the problem appeared?

Maybe your antivirus is blocking the task?

"You cannot know the meaning of your life until you are connected to the power that created you". · Shri Mataji Nirmala Devi

[malcolm569]

malcolm569 last edited by

I have the same problem,auto updater not working.

[malcolm569]

malcolm569 last edited by

This is a copy of the updater fault on my PC.
Description
Faulting Application Path: C:\Program Files (x86)\Opera\44.0.2510.1218\opera_autoupdate.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: opera_autoupdate.exe
Application Version: 44.0.2510.1218
Application Timestamp: 58ed11a0
Fault Module Name: opera_autoupdate.exe
Fault Module Version: 44.0.2510.1218
Fault Module Timestamp: 58ed11a0
Exception Code: c0000005
Exception Offset: 000000000034be04
OS Version: 10.0.14393.2.0.0.768.101
Locale ID: 2057
Additional Information 1: 4cba
Additional Information 2: 4cbaecd1903e4a805e33512a7be3c36d
Additional Information 3: f569
Additional Information 4: f569d627d8bc0598987dbe86348a300e

Extra information about the problem
Bucket ID: 25ce02eb35f6ab44e892d7447b905b2c (120739393754)

[robervin1]

robervin1 last edited by

My system is working fine. I did have a problem with a video driver recently, but that has been resolved. Other than that, it's just Opera that seems bugged.

I get the auto-updater error every time I run Opera now.

[robervin1]

robervin1 last edited by

Here are the program crash details.

Problem signature:
Problem Event Name: APPCRASH
Application Name: opera_autoupdate.exe
Application Version: 44.0.2510.1218
Application Timestamp: 58ed11a0
Fault Module Name: opera_autoupdate.exe
Fault Module Version: 44.0.2510.1218
Fault Module Timestamp: 58ed11a0
Exception Code: c0000005
Exception Offset: 000000000034be04
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: d274
Additional Information 2: d27450c38dce2934b287b336a30b8098
Additional Information 3: 175b
Additional Information 4: 175b2eed3af8a1bded503731f096829a

[blackbird71]

blackbird71 last edited by

A C0000005 error results when a program incorrectly or improperly attempts to access an area of the system's 'protected memory'. This can be caused by anything from a program coding error occuring under some particular condition to a conflict/interference with another piece of software during an attempted execution.

Typically, the most effective method of finding the exact cause is to track down the Windows mini-dump file on the problem system (typically at a location like C:\Windows\Minidump\Minidump.dmp) and get analysis assistance from one of the websites that help users identify specific crash causes from a minidump file. Note, however, that the system must be set up to allow creation of a minidump file in the Control Panel > Systems > Advanced System Settings > Startup and Recovery > Settings > System failure: Write debugging information > Small memory dump (256 KB) > OK. If the system hasn't been set to write a minidump file, set it to do so and then recreate the problem/error.

[robervin1]

robervin1 last edited by

I went to Control Panel > Systems > Advanced System Settings > Startup and Recovery > Settings > System failure: Write debugging information > Small memory dump (256 KB) and did this. I recreated the error but no file is created in C:\Windows\Minidump

Problem signature:
Problem Event Name: APPCRASH
Application Name: opera_autoupdate.exe
Application Version: 44.0.2510.1218
Application Timestamp: 58ed11a0
Fault Module Name: opera_autoupdate.exe
Fault Module Version: 44.0.2510.1218
Fault Module Timestamp: 58ed11a0
Exception Code: c0000005
Exception Offset: 000000000034be04
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: d274
Additional Information 2: d27450c38dce2934b287b336a30b8098
Additional Information 3: b43c
Additional Information 4: b43c5092e71870d1576a9cd066c3c082

[blackbird71]

blackbird71 last edited by

Unfortunately, unless you experience a system crash (not just an apps crash), Windows doesn't write a mini-dump file. In re-reading your original post, it appears only the auto-updater is crashing, so it probably isn't rising to a level sufficient to trigger Windows to create a mini-dump. I apologize for not discerning that from your original post.

Unfortunately, the lack of a mini-dump reduces the information available to track down the exact cause. The most fruitful approach then becomes something along the lines of what @zalex108 noted earlier: 'What happened the same day or few days before the problem appeared?' That would include new software installations, updates of existing software (especially video or printer drivers), power failures or other abnormal shutdowns of Windows and/or with apps open, etc. The system's Event Logs can be useful in looking back for errors or warnings that occur just prior to when the problem first appeared.

The most typical causes of a c0000005 access violation include corruption of the registry, Windows security and access settings, malware, failing/faulty RAM, as well as defective apps program code. As you can see, the list is broad which can make suggesting a solution path difficult.

[robervin1]

robervin1 last edited by

I did have a video driver problem that caused a BSOD recently. I had to boot to safe mode, roll back to an earlier driver, and then restart. I went a few rounds with AMD about this, and they did another driver update within a several days after that, which I used to upgrade the driver without a problem.

I have had no other problems with either the video, nor any more BSOD's. I rolled back the driver, then upgraded past the one that hung my system less than a week later. My system is is not hanging, it's just reporting the Opera error every time I run it.