X
Tap here to go to the mobile version of the site.

Support Forum

Firefox crashes on start up

Posted

Hello,

From today in the morning I cannot start the Firefox browser. It crashes on start up - I got directly a pop-up window with Mozilla Crash Report. Clicking on Restart option would open another Crash Report Window and so on.... Same in safety mode I have tried so far: 1. Clean de-installation (removing all the folders & mozilla files) 2. Downgrading until 38.0 version 3. Upgrading to 41.0.1 version 4. Restoring my Windows to an earlier time Nothing helps. Just after clean installation the Firefox opens, stays opened for about 2 seconds and closes without pushing any buttons. And than I got the Crash Report window, and another, another... I can only click on Close Firefox option. Summarising, I cannot open at all in any condition

Example: Crash ID: bp-85eaf576-3aff-46d9-8e38-837be2151006

                bp-257cfaf2-c32c-45ab-93ee-586d12151006
                bp-861ec698-82bb-421e-8c49-6fe9c2151006
Hello, From today in the morning I cannot start the Firefox browser. It crashes on start up - I got directly a pop-up window with Mozilla Crash Report. Clicking on Restart option would open another Crash Report Window and so on.... Same in safety mode I have tried so far: 1. Clean de-installation (removing all the folders & mozilla files) 2. Downgrading until 38.0 version 3. Upgrading to 41.0.1 version 4. Restoring my Windows to an earlier time Nothing helps. Just after clean installation the Firefox opens, stays opened for about 2 seconds and closes without pushing any buttons. And than I got the Crash Report window, and another, another... I can only click on Close Firefox option. Summarising, I cannot open at all in any condition Example: Crash ID: bp-85eaf576-3aff-46d9-8e38-837be2151006 bp-257cfaf2-c32c-45ab-93ee-586d12151006 bp-861ec698-82bb-421e-8c49-6fe9c2151006

Additional System Details

Installed Plug-ins

None - clean installation

Application

  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36

More Information

AvailablePageFile: 4032966656
AvailablePhysicalMemory: 1131622400
AvailableVirtualMemory: 4030705664
BIOS_Manufacturer: Hewlett-Packard
BlockedDllList:
BreakpadReserveAddress: 98566144
BreakpadReserveSize: 67108864
BuildID: 20150929144111
CrashTime: 1444129464
FramePoisonBase: 00000000f0de0000
FramePoisonSize: 65536
InstallTime: 1444124200
ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
ProductName: Firefox
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 861
StartupTime: 1444129462
SystemMemoryUsePercentage: 72
Throttleable: 1
TotalPageFile: 8167129088
TotalPhysicalMemory: 4084506624
TotalVirtualMemory: 4294836224
URL:
User32BeforeBlocklist: 1
Vendor: Mozilla
Version: 41.0.1
This report also contains technical information about the state of the application when it crashed.
AvailablePageFile: 3990478848
AvailablePhysicalMemory: 1067982848
AvailableVirtualMemory: 4031762432
BIOS_Manufacturer: Hewlett-Packard
BlockedDllList:
BreakpadReserveAddress: 112590848
BreakpadReserveSize: 67108864
BuildID: 20150929144111
CrashTime: 1444129564
FramePoisonBase: 00000000f0de0000
FramePoisonSize: 65536
InstallTime: 1444124200
ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
ProductName: Firefox
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 100
StartupTime: 1444129563
SystemMemoryUsePercentage: 73
Throttleable: 1
TotalPageFile: 8167129088
TotalPhysicalMemory: 4084506624
TotalVirtualMemory: 4294836224
URL:
User32BeforeBlocklist: 1
Vendor: Mozilla
Version: 41.0.1
This report also contains technical information about the state of the application when it crashed.
AvailablePageFile: 3990478848
AvailablePhysicalMemory: 1067982848
AvailableVirtualMemory: 4031762432
BIOS_Manufacturer: Hewlett-Packard
BlockedDllList:
BreakpadReserveAddress: 112590848
BreakpadReserveSize: 67108864
BuildID: 20150929144111
CrashTime: 1444129564
FramePoisonBase: 00000000f0de0000
FramePoisonSize: 65536
InstallTime: 1444124200
ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
ProductName: Firefox
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 100
StartupTime: 1444129563
SystemMemoryUsePercentage: 73
Throttleable: 1
TotalPageFile: 8167129088
TotalPhysicalMemory: 4084506624
TotalVirtualMemory: 4294836224
URL:
User32BeforeBlocklist: 1
Vendor: Mozilla
Version: 41.0.1
This report also contains technical information about the state of the application when it crashed.

philipp
  • Top 25 Contributor
  • Moderator
5315 solutions 23462 answers

Helpful Reply

hi, this appears to be caused by a security/monitoring software by a company called SoftCamp, that is running on your device. please try to see if there are any updates available for it that might solve this crash or else uninstall it for the moment. if the computer is part of a corporate network please get in touch with your it department about this issue...

hi, this appears to be caused by a security/monitoring software by a company called SoftCamp, that is running on your device. please try to see if there are any updates available for it that might solve this crash or else uninstall it for the moment. if the computer is part of a corporate network please get in touch with your it department about this issue...

Question owner

Hi, that must be it. Yes, indeed - my PC is a part of corporate network. I cannot do anything about it - I need to contact the IT.

Cheers

Hi, that must be it. Yes, indeed - my PC is a part of corporate network. I cannot do anything about it - I need to contact the IT. Cheers

Question owner

Hi again, Sorry for spliting my answer in two, but I gave a second thought about the situation. The SoftCamp software has not been updated recently, I still have the version from Jan 2015 & there has been no conflicts ever since. The only thing that changed recently, was the Firefox... I got an update to version 41.0.1 today (or recently - I am not sure when exactly) & after that it crashed totally. My point here is, that the suspicious is the Firefox's update, not SoftCamp soft. The potential conflict has occurred after the Firefox update to newer version. This makes sense I think, doesn't it....?

Cheers

Hi again, Sorry for spliting my answer in two, but I gave a second thought about the situation. The SoftCamp software has not been updated recently, I still have the version from Jan 2015 & there has been no conflicts ever since. The only thing that changed recently, was the Firefox... I got an update to version 41.0.1 today (or recently - I am not sure when exactly) & after that it crashed totally. My point here is, that the suspicious is the Firefox's update, not SoftCamp soft. The potential conflict has occurred after the Firefox update to newer version. This makes sense I think, doesn't it....? Cheers
philipp
  • Top 25 Contributor
  • Moderator
5315 solutions 23462 answers

looking at the over all crash stats for this signature this seems unlikely that the firefox update played a part, since it happened with version 40 and earlier as well. according to your particular report not only does a library by softcamp (dstermpr.dll) play a role, as does your norton product (ipseng32.dll) - so maybe it's some form of two-way interference triggered by a recent signature update... sorry for being a bit general/vague on the subject, but i don't know how the softcamp software is functioning and the overall numbers of those crashes (~70 over the last month) is probably too insignificant to get firefox developers interested in this issue.

looking at the over all crash stats for this signature this seems unlikely that the firefox update played a part, since it happened with version 40 and earlier as well. according to your particular report not only does a library by softcamp (dstermpr.dll) play a role, as does your norton product (ipseng32.dll) - so maybe it's some form of two-way interference triggered by a recent signature update... sorry for being a bit general/vague on the subject, but i don't know how the softcamp software is functioning and the overall numbers of those crashes (~70 over the last month) is probably too insignificant to get firefox developers interested in this issue.