Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Always crash

  • 27 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 14 views
  • Last reply by ·´¯`·...¸>-)))º> ~dbben

I did everything that was recommended to solve this problem. BUT THIS DONT WORK

I did everything that was recommended to solve this problem. BUT THIS DONT WORK

All Replies (20)

dennispain said

I did everything that was recommended to solve this problem. BUT THIS DONT WORK

Look at this.....

ok.

can you briefly list what all was recommended?

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 Submitted crash reports, and copy them. Now go to the reply box and paste them in.

Please, Do not post a screenshot ! !

aboutcrashesFx57

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

~dbben сказал(а)

ok. can you briefly list what all was recommended?

Update Firefox Update Windows Update your drivers Update your internet security software Check for viruses or spyware Check if a crash occurs in Safe Mode (The crash is still happening in Safe Mode)

Thanks for the additional info !

btw:

what windows version and bit are you using? what is size of your ram memory and also the page file?

FredMcD сказал(а)

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 Submitted crash reports, and copy them. Now go to the reply box and paste them in. Please, Do not post a screenshot ! !
aboutcrashesFx57
For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

bp-fca58e73-aa9b-42fe-8543-3a9540210403 03.04.2021, 19:05 Просмотреть bp-9765aa73-260a-4f7a-a65b-7bdb90210403 03.04.2021, 19:04 Просмотреть bp-92591ea9-84cf-4883-9649-068290210403 03.04.2021, 16:17 Просмотреть bp-bb1c1b9c-f5f8-47da-b67e-b1fe40210403 03.04.2021, 16:16 Просмотреть bp-a0c6dd14-de06-4128-9fb6-c2bf40210403 03.04.2021, 16:16 Просмотреть bp-8a96186e-776c-44d6-a3fe-5e3180210403 03.04.2021, 16:16 Просмотреть bp-93794736-1c47-4e24-b9c0-15e9d0210403 03.04.2021, 15:07 Просмотреть bp-34440bdc-b809-4327-8972-3cac00210403 03.04.2021, 15:07 Просмотреть bp-1cae48d4-d964-45ff-8afa-110e00210403 03.04.2021, 15:07 Просмотреть bp-dde6a717-960a-4e7e-8b2f-623430210403 03.04.2021, 15:07 Просмотреть bp-abbfdc28-4707-498d-a9a6-bfa6d0210403 03.04.2021, 15:07 Просмотреть bp-40482976-47a5-4032-8cce-6d8210210403 03.04.2021, 15:07 Просмотреть bp-21d1e7c8-dd9a-4159-ab6b-fe9400210403 03.04.2021, 15:07 Просмотреть bp-18a86a2b-3c08-4960-a703-ea1ba0210403 03.04.2021, 15:07 Просмотреть bp-84a60e39-f4e3-4860-8716-9692d0210403 03.04.2021, 14:25 Просмотреть bp-7731bf4b-2cee-4d3c-a7d4-f67dd0210315 15.03.2021, 18:03 Просмотреть bp-f2a5f1ea-a8d9-4c54-b1cb-a8e080190515 15.05.2019, 17:05 Просмотреть bp-98abd3ac-0db5-4167-bb73-557c91180225 25.02.2018, 13:30 Просмотреть bp-d284c326-1108-417e-abf9-7ec781170609 09.06.2017, 17:49 Просмотреть bp-c028e4b1-a0e1-4f6a-b163-33a850210404 04.04.2021, 21:17 Просмотреть bp-ed6fa917-0247-4c02-bb9b-19be50210404 04.04.2021, 21:17 Просмотреть bp-fdf9fee3-e5ca-475b-b11c-394c80210404 04.04.2021, 21:17 Просмотреть bp-053be95e-7fe5-4762-af0b-b14d90210404 04.04.2021, 21:17 Просмотреть bp-59952090-f924-42c1-9927-fbca40210404

hello dennis, thanks for the additional info.

while i am notan expert in crash reports, i did see something in one of your crash reports that doesnt parallel what you cited in the above.

take a look at the pagefile cited in the attached pic:

really weird, what do you suggest doing?

I basically have the same setup as you do, but with 16 gigs of ram. but i limit my pagefile to be approx 2400. and my system functions very well even when i run microsoft office and photoshop at the same time.

Assuming that the page file is going coo coo on you, there are some old fashion methods to deal with the page file.

For example, sometimes it can be deleted by simply disabling the pagefile.

Then when you reboot, it will be very slow to start up. But when it does, the pagefile will be seen as none existent while windows uses a back up pagefile in the interim. Once you can access the virtual memory window, you can then enable the pagefile to "auto" and reboot to see if this helps.

Another option is to take it off "auto" and then enter the same size for the "min" and the "max" in the virtual memory window.

Another option is to go into the registry and set the size

Afterwards, lets take a look at a crash report to see if the numbers look more logical.

Thank you for sharing the report links. Here are some thoughts:

(1) Did you already restart Windows at some point in your troubleshooting?

(2) 9 of the first 10 crash reports all have the same "signature" and on the Bugzilla tab, there is a link to an old bug where people don't have enough data to solve it but speculate that possibly it could be caused by a corrupted font file. Does your Windows have any option to repair font files?

(3) Since you have dual Intel/Nvidia graphics, I wonder whether there is a way to disable the Intel graphics -- mentioned in the crash reports -- to test whether Firefox runs normally with Nvidia graphics. Not sure this is relevant.

(4) Do you want to test a new profile? To create a new profile without being able to run Firefox, you need to use a startup / command line switch. You can modify your desktop shortcut. Let's say you right-click it and choose Properties, then on the Shortcut tab, the Target line usually is:

"C:\Program Files\Mozilla Firefox\firefox.exe"

after the last " add a space and then -P so it reads

"C:\Program Files\Mozilla Firefox\firefox.exe" -P

After you OK that, when you use the shortcut, it will show a small dialog. Here you can create a new profile and test whether it is more stable. To get the "new install" experience, don't connect the new profile to your Firefox Account at first, test it through a few sessions, so you can allow Firefox time to discover your system features and adapt its settings. Is it stable?

bp-fca58e73-aa9b-42fe-8543-3a9540210403 bp-9765aa73-260a-4f7a-a65b-7bdb90210403 bp-92591ea9-84cf-4883-9649-068290210403

Signature: GetMBDefault

Uptime 12 seconds - Uptime 77 seconds - Uptime 9 seconds

Crash Reason EXCEPTION_IN_PAGE_ERROR_READ / STATUS_DEVICE_DATA_ERROR

This is for Sumo's Related Bugs 1485425 NEW --- Crash in ComputeCrc32 in dwrite.dll via gfxDWriteFontEntry::CreateFontFace

DWrite.dll = Microsoft DirectX Typography Services


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

Hello Dennis, Thanks for the update.

Did a new crash report cite different numbers for the pagefile?

Incidentally, is there a reason why you chose 1900 for the page file size? Also, did you happen to wipe it clean too?

There was a time when older malware would hide themselves inside the pagefile. I think specialty "fonts" from some font were also used to contaminate systems.

In any case, it looks like you have some more suggestions for you to look into. I will be eagerly watching your results.

I restored the fonts, it didn't help Tomorrow I will reinstall Windows again, but if this does not work,I will just switch to another browser

Hello Dennis,

I would not do a reinstall just to restore a browser. And who knows? Reinstalling windows may not fix the issue. So you may end up using another browser anyways.

And again who knows? Maybe after a while the other browser will stop functioning too.

Instead leave everything as is. And be patient.

In meantime do an SFC and disk optimization provided as features in windows.

Incidentally, while i have not used it, I think win10 has the ability to repair its system files while not losing the apps. I think it is a similar to a repair install. So you might look into this other feature.

·´¯`·...¸>-)))º> ~dbben மூலமாக திருத்தப்பட்டது

Yes, but I just looked and I don't have any system restore points. Mb you know how to create it a few days ago or something

Hello Dennis,

Win10 has a system restore feature under the Pc Settings > System > About section. You can always make a restore point.

Also, a repair install, aka in-place install, is not the same as a restore point. The repaif feature is under PC settings > Update Security > Recovery

But again, I would suggest to leave everything as is; other than executing an SFC. You may be wasting your time repairing your o.s. when it may not need repairing.

Also, I am highly curious with the out of control page file. Lock the size to 2500.

Hello again I checked the system through the SFC and was unpleasantly surprised " Windows Resource Protection program has detected corrupted files, but cannot restore some of them. For more information, see the CBS.Log file, which is located at the following path: windir\Logs\CBS\CBS. log. For example, C:\Windows\Logs\CBS\CBS.log. The details are included in the log file provided by the /OFFLOGFILE flag. " I looked through the notebook what exactly are the errors. "[SR] Cannot repair member file [l:9]'C_932.NLS' of Microsoft-Windows-International-CodePage-Core, version 10.0.18362.1440, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch" There are several such errors and they are all the same Although a couple of days before the browser crash, I checked and everything was fine

  1. 1
  2. 2