Mouse movement or mouse scolling in Firefox crashes my computer (BSOD) daily.
Firefox is crashing (BSOD) my computer (PC with Win7x64) daily, during mouse movement or during auto-scrolling after clicking the middle mouse button. It usually happens at least once per day, and has been happening for weeks. FF, Windows and my mouse driver are up to date. I have tested memory many times (using Memtest86) and my hard drive. I have no crashes except in Firefox during mouse activity.
The BSOD reports vary. Recent ones: Bad Pool Caller (019 and 0C2), PFN List Corrupt (04E), Memory Management Error (01A), ??? (07E), System Service Exception (033). The only consistent thing is using the mouse within Firefox.
Wšě wotmołwy (5)
We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
The crash report is several pages of data. We need the report numbers to see the whole report.
- Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted/Unsubmitted Crash Reports will appear, similar to the one shown below.
- Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.
Note: If a recent Report ID does not start with bp- click on it to submit the report.
(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)
Thank you for your help!
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
Here are the five most recent crash IDs. However, the latest ones are for December 4, and I have also had BSOD crashes in Firefox on December 5, 6 and 7 (and probably earlier ones that aren't listed in the About:Crash reports).
ff2b3758-be99-4824-8ba5-89623c89c775 12/4/2019, 11:26 PM 4c03c125-3799-4583-ab8e-c2be3293f4b9 12/4/2019, 11:24 PM c66ef7ea-d0b2-4b5f-8316-54fff453ce4d 12/4/2019, 1:40 PM ddddb586-bd82-4d26-9acd-476c3954c5b0 12/4/2019, 9:38 AM 6dd11694-51fe-44d2-be6e-324533531b22 12/2/2019, 3:25 PM
Today FireFox crashed (again while using the mouse), but without crashing the computer -- so for the first time I was able to capture a FF crash report that is relevant to the problem in this thread:
339e6dd3-a4bc-4d0f-8d85-8e2957c5d18e 12/13/2019, 9:42 AM.
During this crash I was auto-scrolling (activated with middle mouse button, and mouse pulled toward me) toward the bottom of a personal list (feed) on Twitter. The list has >300 twitter members on it, and on a fresh morning read it takes 40 spurts of 20 tweets each before it bottoms-out. (I then read the list from bottom - oldest post - to top). When the crash occurred I was perhaps halfway through such a download (to memory) of the list.
The crash report IDs you posted haven't been submitted to the Socorro Crash server.
If a line on the about:crashes page doesn't start with "bp-" then you can click this line to submit the crash report. The link will be updated and gets a "bp-" prefix if the report is submitted successfully.
- please do not add the "bp-" prefix yourself
If you have submitted crash reports then please post the IDs of one or more (5-10) recent crash reports that start with "bp-".
- bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
See also:
I just now clicked the "submit" button for six of them, but the "bp-" doesn't appear. (Nor does the "view" button, which is shown in the online instructions" appear). It seems all these should have been submitted automatically already, according to what the Mozilla Crash Reporter dialog box says.
I don't know what I am doing wrong on this.