Opera 39 not opening

[A Former User]

A Former User last edited by

Hi, I've currently got some Win 7 issues, which I think are related to the DDR3; what happens is suddenly Windows will crash and try to reboot - it seems to happen when I have several browser windows open.

On one occasion, Windows recorded the error:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA8008ED5300
BCP3: FFFFFA8008ED55E0
BCP4: FFFFF80003791E40
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\090616-39873-01.dmp
C:\Users\XXXXXXX\AppData\Local\Temp\WER-55037-0.sysdata.xml

The latest crash happened last night. What usually happens is that I then try to reboot and Windows gives me the option to 'launch repair' or 'start windows'. After a crash, I usually click 'start repair' and it then crashes again. After an attempt at start repair, it seems to boot back into Windows again and seems to function OK.

Except, now when I try to launch Opera 39, Opera won't open and won't function at all! I thought to uninstall/reinstall but Win 7 won't allow me to uninstall Opera 39. Maybe I should just reinstall and hope for the best?

Given my problems I'm wondering if I should do a complete reinstall of Win 7.

[A Former User]

A Former User last edited by

When I try to open Opera, I look at processes in Task Mgr.

In addition to the usual processes there when there's no browser running, the following processes are listed when I attempt to open Opera 39:

launcher.exe *32
opera.exe *32
WerFault.exe *32

They then disappear when it fails to load.

[A Former User]

A Former User last edited by

Windows starting a repair and then rebooting seems to be normal behaviour in some circumstances, my Windows 8.1 does the same thing. I guess it needs to reboot to fully implement what it's done.
WerFault.exe is part of Windows Error Reporting.
I guess Opera is crashing and it's trying to send the information to Microsoft.
Try reinstalling Opera. Even if it is then still malfunctioning, it may get you the uninstall option back.
Failing that, I would rename the Opera folder in the Program Files folder so you can restore it easily if this doesn't work, and then reinstall using the offline installer.
If you want to keep all your profile information, bookmarks etc. don't delete the Opera folders in your Windows user profile AppData folders unless nothing works to get Opera running again.
It that's the case, you may need to disable your Opera profile by renaming those folders, in case it's something corrupted there which is casing the problem.

[alobpreis]

alobpreis last edited by

BSODs and reboots are often due to hardware issues, usually the RAM. I highly recommend you thoroughly test it with MemTest86 or any other software you trust. I would let the test run for several hours, so it completes at least 3 or 4 passes.

[A Former User]

A Former User last edited by

I went to update my media player and it opened an Opera 39 browser window, which confused me to say the least.

Post 'this issue', it seems the version of opera I was trying to open, pinned to the task bar, is the one in the C drive (which I'd thought I'd uninstalled?).

So, now the Opera 39 issue seems to be resolved.

It does seem to be a RAM issue. The BSODs and crashes seem to occur if I have too many windows open with videos, charts etc. I'll run that memory test when I get a chance. Cheers.