GµårÐïåñ said

[..]

So, long story short, what would you like me to do?

(I don't remember any other drivers updates, as of they all require my actual will to do it (visiging the website, restarts etc)., so unless Windows did something on it's own - no other driver updates were present).

Actually while some drivers are vendor specific and require manual installs; Windows 10 DOES update drivers/firmwares during Windows Update. In fact, since they prefer the more broad driver versions, it can cause an issue at times when they replace the vendor specific drivers with their own generalized drivers. So, that can also impact it too, and if you find something that was updated that way you might want to roll it back and see if it resolves the issue.

Take a look under the update history and see if any of them were installed there. Alternatively, it can be that a driver is outdated and so why it is not properly handling memory allocation anymore, so you might actually want to check your drivers to see if there are any that are outdated or have not update it for at least a year or more.

There are some tools that will do this for you, unfortunately I don't feel comfortable or think it would be appropriate to mention them here as they are third party but a quick search should reveal them. Just make sure you pick something that is trustworthy, reputable and vetted.

I've checked my MOBO driver download list (and bios updates), nothing has changed there. All drivers are up-to-date.

I know that Windows likes to be a sneaky b!tch, so I've blocked Windows Update so it's not updating unless I want it. Perhaps some cumulative update has updated some strange drivers and we can see the effect.

Too bad we don't know what driver.

If only it crashed in any other application, but it does ONLY in Firefox and ONLY on MOUSE_DRAG event.

I've checked my mouse drivers and they are not touched, however, USB drivers have been updated at the FF57 update time.

Do you think that USB 3.0 can affect this crash? Should I try with mouse connected to USB 2.0 port?

///

Firefox 57 beta branch relase date: 2017-09-28

GµårÐïåñ said

Actually while some drivers are vendor specific and require manual installs; Windows 10 DOES update drivers/firmwares during Windows Update. In fact, since they prefer the more broad driver versions, it can cause an issue at times when they replace the vendor specific drivers with their own generalized drivers. So, that can also impact it too, and if you find something that was updated that way you might want to roll it back and see if it resolves the issue. Take a look under the update history and see if any of them were installed there. Alternatively, it can be that a driver is outdated and so why it is not properly handling memory allocation anymore, so you might actually want to check your drivers to see if there are any that are outdated or have not update it for at least a year or more. There are some tools that will do this for you, unfortunately I don't feel comfortable or think it would be appropriate to mention them here as they are third party but a quick search should reveal them. Just make sure you pick something that is trustworthy, reputable and vetted.

https://www.howtogeek.com/302595/how-to-stop-windows-10-from-automatically-updating-hardware-drivers/

Acrivec said

Firefox 57 beta branch relase date: 2017-09-28

So you are using a old Beta build (either 57.0b3 or 57.0b4 based on date?) of Firefox 57.0 instead of the Release that came out on Nov 14 ?. There were fourteen builds of 57.0 on Beta channel before Release.

www.mozilla.org/firefox/all/

If you have a USB mouse, then yet any updates to the USB hardware can affect anything connected to it as well.

Problem stopped appearing for a while. Right now it's second bluescreen caused by dragging something in Firefox (image, tab, text, link...) today. Both times it interrupted my rendering in Blender which drove me crazy, escpecially that I can't use computer when rendering on GPU.

Some update fixed it (or I think it did), and it's back now.

To reproduce simply drag something and move around, stopping sometimes for a couple of seconds. Boom.

58.0b12 (64 bit)

To be expected when running a Beta. This is going on to long for what is needed as the beta changes all the time. If you have a bug, file a bug report. https://bugzilla.mozilla.org/ Bug Writing Guidelines : https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines

This now a none issue. Go to the stable release.

uninstall Firefox. Then Delete the Mozilla Firefox Folders in C:\Program Files and C:\Program Files(x86) Then restart system. Then run Windows Disk Cleanup. (Note: This should be Pinned and run Weekly, If never done below expect 10's of gig's) Then run it again and click the button that says Cleanup System Files. Note: your Firefox Profile is saved. But you should make a back up before you do :

• https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles
• https://support.mozilla.org/en-US/kb/export-firefox-bookmarks-to-backup-or-transfer

Reinstall with Current Release Firefox 57.0.2 with a Full Version Installer

• https://www.mozilla.org/firefox/all/

Windows 10 To run the DISM command use the Windows key + X keyboard shortcut to open the Power User menu, then select Command Prompt (Admin). Type "DISM /Online /Cleanup-Image /RestoreHealth" (without quotes or copy/paste) and press Enter. Reboot After.

Note : SFC /scannow fixes files locally using files found on your system. Note : DISM goes up to Microsoft for new ones.

Please let us know if this solved your issue or if need further assistance.