I had no problem with the link you posted. ++++++++++++++++++++++++++++++++++ Some of your crash reports weren’t sent to the Mozilla Servers.

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.

The crash report is several pages of data. We need the report numbers to see the whole report.

Using your mouse, mark the most recent 7 - 10 crash reports, and copy them. Press the Reply button. Now go to the reply box and paste them in.

For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

Hello, Thanks for your reply. Here are the requested information: Report ID Date Crashed 59dc8e24-cffb-4a20-803d-5ec256552f7d 6/26/2017 10:46 AM dbdc4276-b023-48c9-8adb-3c7117ce08c7 6/26/2017 10:33 AM 44281a33-a430-4237-a89d-68d0b34940bf 6/26/2017 10:26 AM c77947ee-85ff-45a5-936a-65021f48669a 6/26/2017 10:24 AM f956802a-2091-44de-ab8e-7302d4df2629 6/26/2017 10:22 AM ef7d6ece-4772-4661-8672-d00b9140e58e 6/26/2017 9:52 AM ac998db7-b15f-42b3-9a6a-96774f3fa62f 6/5/2017 3:39 AM

Also, immediately after this Firefox error message, I also received a BDOD in Windows 7 as well. After restarting the PC, in the Windows Event Viewer, the corresponding error report was as follows: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff800030eaaf1, 0xfffff88007973628, 0xfffff88007972e80). A dump was saved in: C:\Windows\MEMORY.DMP. And then Firefox started to work again and I didn’t receive any BSOD until this moment. As said the strange behavior was started suddenly and was accompanied with the mentioned BSOD, then after restart everything else started to work again. I don’t understand the meaning of this Firefox error message nor the meaning of the BSOD error message but I thought maybe there is a connection between them while I have never had such issue in the past. I just don’t know suddenly what happened! Regards.

At the end of the link I have posted there is a bracket! That is why! I have noticed the only way you can see the link is to copy it into the clipboard and then paste it into the address bar… Even highlighting it and clicking on “Open Link in New Tab” won’t work!

firefoxusergermany said

Hello, Thanks for your reply. Here are the requested information:

Report ID Date Crashed
59dc8e24-cffb-4a20-803d-5ec256552f7d 6/26/2017 10:46 AM
dbdc4276-b023-48c9-8adb-3c7117ce08c7 6/26/2017 10:33 AM
44281a33-a430-4237-a89d-68d0b34940bf 6/26/2017 10:26 AM

Some of your crash reports weren’t sent to the Mozilla Servers.

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.

The crash report is several pages of data. We need the report numbers to see the whole report.

Using your mouse, mark the most recent 7 - 10 crash reports, and copy them. Press the Reply button. Now go to the reply box and paste them in.

For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support </blockquote>

Hello. For a user as me, it was not the most user-friendly process in the world to submit crash reports to Mozilla. I mean it could be designed much better. You could place a button there so all crash reports would be submitted at once but more importantly when I clicked on each report, another page would open and it took me a while (2 days) before I found out albeit I never receive any message saying the crash report was submitted or not but simply opening that page included it too (even though it would never inform the user about it). Anyway. Now all the reports are submitted to Mozilla as instructed :) Regards.

Good. Now please post the bp- numbers.

According to this: “Copy and paste the Report ID number for the latest crash (looks like bp-…) and into the "Details" section and submit your question.” Here is my latest report ID and what you want then:

bp-a7d72c21-cce8-422b-88e8-65cbb0170627

Also to be on the safe side, here is a copy of all of the “about:crashes” page:

Unsubmitted Crash Reports Report ID Date Crashed Submitted Crash Reports Report ID Date Submitted bp-a7d72c21-cce8-422b-88e8-65cbb0170627 6/27/17 5:22 PM bp-683d9a4d-8dad-41f2-8a6e-185310170627 6/27/17 5:22 PM bp-d2502358-df50-4cd5-a267-9dd7a0170627 6/27/17 5:22 PM bp-f0815ac8-8c27-41c6-beb0-5f2ee0170627 6/27/17 5:21 PM bp-7edfc551-e06c-4ef1-9ad0-bc3e70170627 6/27/17 2:49 AM bp-b03117c1-ed78-491b-a297-01a2f0170627 6/27/17 2:48 AM bp-e3dc47f0-55bf-416c-ab16-462090170626 6/26/17 8:38 PM bp-fe3a4f0a-47d5-4f13-b85b-df01e0170626 6/26/17 10:38 AM bp-2f482fe0-dbae-46a7-a685-abc9b0170626 6/26/17 10:29 AM bp-0dadbad0-19a6-48cf-a3bf-101a61170626 6/26/17 10:23 AM bp-a1b719aa-0f4a-4938-9a3b-fb7661170626 6/26/17 10:23 AM bp-3ade66ed-855b-41ef-8d9d-ec41a1170626 6/26/17 10:22 AM

Very good. This is what we need.

bp-a7d72c21-cce8-422b-88e8-65cbb0170627 Signature: IPCError-browser | ShutDownKill

Attention Sumo's there are 20 related bug reports

atidxx32.dll = Advanced Micro Devices = Check this link; http://support.amd.com/en-us/download/desktop?os=Windows+7+-+64 +++++++++++++++++++++++++++++++++++++++++ bp-683d9a4d-8dad-41f2-8a6e-185310170627 Signature: js::GCMarker::eagerlyMarkChildren

Attention Sumo's there are 3 related bug reports

atidxx32.dll = Advanced Micro Devices = Check this link; http://support.amd.com/en-us/download/desktop?os=Windows+7+-+64 ++++++++++++++++++++++++++++++++++++++++ bp-d2502358-df50-4cd5-a267-9dd7a0170627 bp-f0815ac8-8c27-41c6-beb0-5f2ee0170627 bp-7edfc551-e06c-4ef1-9ad0-bc3e70170627

Signature: CProgram::OptimizeCondition

atidxx32.dll = Advanced Micro Devices = Check this link; http://support.amd.com/en-us/download/desktop?os=Windows+7+-+64

See if the above link helps.

Thanks for your effort! I basically had a feeling maybe this is due to some issues with my graphic card driver too. It seems all of the links you have posted above as a solution are nothing but a link to my graphic card driver. So if I install “Crimson ReLive Edition 17.6.2 Optional” all my problems would be solved? Also, recently I see other strange behaviors too such “Windows 7 black screen with cursor after login” problem which is resolved by terminating and restarting the “explorer.exe” process inside the Windows “Task Manager”.

That's above me. I called for more help.

Run the Windows updater program. After, Perform a System File Check to fix corrupted system files

Win 7, 8, 10, Vista: https://support.microsoft.com/en-us/kb/929833 Win XP: https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/system_file_checker.mspx?mfr=true

Wiki - Windows 10 System File Check http://answers.microsoft.com/en-us/windows/wiki/windows_10-update/system-file-check-sfc-scan-and-repair-system-files/bc609315-da1f-4775-812c-695b60477a93

What happens if you disable multi-process?

Try to disable multi-process windows in Firefox to see if that has effect.

You can disable multi-process windows in Firefox by setting these prefs to false on the about:config page.

• browser.tabs.remote.autostart = false
• browser.tabs.remote.autostart.2 = false

You can open the about:config page: via the location/address bar. You can accept the warning and click "I'll be careful" to continue.

• http://kb.mozillazine.org/about:config

• http://www.ghacks.net/2016/07/22/multi-process-firefox/