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

BSOD caused by Firefox

  • 28 பதிலளிப்புகள்
  • 9 இந்த பிரச்னைகள் உள்ளது
  • 2 views
  • Last reply by Shadow110

Hello, I've got like 6th BSOD while using Firefox. The problem started after updating to Firefox 57 beta. The common thing that I've found with those bluescreens is: - media - selection.

I'm almost sure that it happens after trying to drag anything. You know what I'm talking about: if we have an image we can 'drag' it and it becomes semi-transparent. This doesn't happen every time - firefox needs to be opened for some time. It's connected with YouTube, static images and - I think - selected text.

I wanted to attach minidump files, but I forgot I've cleaned them up, and the ones from last 3 BSODs were not created (I didn't want to wait, the code was the same, the file was the same).

SYSTEM_SERVICE_EXCEPTION (win32kfull.sys) or SYSTEM_SERVICE_EXCEPTION (win32k.sys)

Both connected with ntoskrnl.exe

I've reinstalled my graphic drivers, thinking it was them, but BSOD happens every time in firefox, never in anything else, and it didn't occur before 57 I'd like not to surf in safe mode; this BSOD doesn't happen regularly. I fear the internet without adblock. ( ͡° ͜ʖ ͡°)

Hello, I've got like 6th BSOD while using Firefox. The problem started after updating to Firefox 57 beta. The common thing that I've found with those bluescreens is: - media - selection. I'm almost sure that it happens after trying to drag anything. You know what I'm talking about: if we have an image we can 'drag' it and it becomes semi-transparent. This doesn't happen every time - firefox needs to be opened for some time. It's connected with YouTube, static images and - I think - selected text. I wanted to attach minidump files, but I forgot I've cleaned them up, and the ones from last 3 BSODs were not created (I didn't want to wait, the code was the same, the file was the same). SYSTEM_SERVICE_EXCEPTION (win32kfull.sys) or SYSTEM_SERVICE_EXCEPTION (win32k.sys) Both connected with ntoskrnl.exe I've reinstalled my graphic drivers, thinking it was them, but BSOD happens every time in firefox, never in anything else, and it didn't occur before 57 I'd like not to surf in safe mode; this BSOD doesn't happen regularly. I fear the internet without adblock. ( ͡° ͜ʖ ͡°)

All Replies (20)

It might have to do with the GPU and the use of hardware acceleration being somehow incompatible with yours. Can you try and disable hardware acceleration and see if it still happens.

GµårÐïåñ said

It might have to do with the GPU and the use of hardware acceleration being somehow incompatible with yours. Can you try and disable hardware acceleration and see if it still happens.

Didn't help. I've been finishing stuff to go to work, paused youtube video and decided to do a quick test - selected some text and dragged it. Instant BSOD. I have the minidump file if needed.

111617-7125-01.dmp 16.11.2017 19:37:56 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 ffffab1a`ae150edf ffff800d`194560c0 00000000`00000000 win32kfull.sys win32kfull.sys+150edf Full/Desktop Win32k Kernel Driver Microsoft® Windows® Operating System Microsoft Corporation 10.0.16299.19 (WinBuild.160101.0800) x64 ntoskrnl.exe+163960 C:\WINDOWS\Minidump\111617-7125-01.dmp 8 15 16299 1 024 180 16.11.2017 22:36:28

Acrivec மூலமாக திருத்தப்பட்டது

Nope need the bp- files sent back in a message as per the instructions here please : https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

Video Card drivers look good. A update was released 2 days ago for you Video Card though. https://www.techspot.com/drivers/driver/file/information/18125/ Should always keep updated as old & corrupted drivers can cause a wide range of issues. Also never know when support will end, so always keep the installer.

Shadow110 மூலமாக திருத்தப்பட்டது

Pkshadow said

Nope need the bp- files sent back in a message as per the instructions here please : https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

I have no crash reports from firefox as of BSOD interrupts all processes, so nothing can be saved on the disc by Firefox. The last crash report is from 26.09.2017, so I don't think it will help.

Repair System Registry and Files

(FOR DOING Above & Below - WINDOWS All OTHER VERSIONS - Use Search To Find Command Prompt ** Enter CMD.exe to Find COMMAND PROMPT Then Right Click & RUN AS ADMIN)

To run the SFC command use the Windows key + X keyboard shortcut to open the Power User menu and select Command Prompt (Admin). Type "SFC /SCANNOW" (without quotes or copy/paste) and press Enter. For more information on using SFC, please refer to the Microsoft KB: Use the System File Checker tool to repair missing or corrupted system files

Run the Windows Deployment Image Servicing and Management (DISM) and System File Checker (SFC) tools as Administrator. The DISM and SFC tools scan the integrity of the Windows image and all protected system files replaces corrupted, damaged and incorrect versions. (FOR DOING Above & Below - WINDOWS All OTHER VERSIONS - Use Search To Find Command Prompt ** Enter CMD.exe to Find COMMAND PROMPT Then Right Click & RUN AS ADMIN) Type "DISM /Online /Cleanup-Image /RestoreHealth" (without quotes or copy/paste) and press Enter.

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. While running DISM you may notice the process will appear to pause at 20%. After a few minutes the operation will continue.

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

Pkshadow said [...] </blockquote> My system is basically freshly installed, but okay, I'll run DISM and wait for next BSOD.

Pkshadow said

Video Card drivers look good. A update was released 2 days ago for you Video Card though. https://www.techspot.com/drivers/driver/file/information/18125/ Should always keep updated as old & corrupted drivers can cause a wide range of issues. Also never know when support will end, so always keep the installer.

I have this version installed, I've sort of mentioned it in first post.

Pkshadow said

Note : DISM goes up to Microsoft for new ones.

DISM was completed successfully. Then I've turned on camera and... here you go! ;)

https://gfycat.com/GroundedFaroffKangaroo

I am sorry I wasn't able to respond sooner but while the suggestions are often a fix, they are not a cure all and did not seem to be your issue that's why I didn't ask you to do it and had you check your hardware acceleration and the GPU instead.

It seems that the render engine is the problem and somehow has a memory access violation which would qualify as a bug. It may have to do with direct write and that is just a bad hook and resource mismanagement, nothing to do with actual problems with your install.

However, before I ask you to open a bug report, can you do me ONE more favor please and let me know your results. IIRC you said you had a driver update 2 days ago, correct? If so, can you please do me a favor and roll back the driver to the previous one and see if you can still make it happen.

One of two things.

  1. it still happens, then it is the browser having a bug and we can report it and have them look into it. At that point your mini dumps will help them figure out what happened.
  2. it stops happening in which case it would point to a bad driver update and you may need to report it to them to take a look. Either way you'll know for sure.

GµårÐïåñ said

I am sorry I wasn't able to respond sooner but while the suggestions are

I've updated the driver thinking it was it's fault. The blue screens happened before updating the driver.

Ok, let me ask you a couple of questions to better have a grip on the timeline of events.

  1. What version of Firefox were you running BEFORE the driver upgrade (when the issue you said was still happening) - this would all the more confirm issues with the way the driver is interacting with the browser, specially if it is going across multiple versions.
  2. Did you update the driver BEFORE or AFTER you upgraded to the latest Firefox 57?

The reason I ask is because it seems a couple of things happened at the same time, we need to figure out what happened when and try and see who might be causing it. Now I know you said you disabled hardware acceleration, can you confirm that is still the case please?

GµårÐïåñ மூலமாக திருத்தப்பட்டது

GµårÐïåñ said

Ok, let me ask you a couple of questions to better have a grip on the timeline of events.
  1. What version of Firefox were you running BEFORE the driver upgrade (when the issue you said was still happening) - this would all the more confirm issues with the way the driver is interacting with the browser, specially if it is going across multiple versions.
  2. Did you update the driver BEFORE or AFTER you upgraded to the latest Firefox 57?
The reason I ask is because it seems a couple of things happened at the same time, we need to figure out what happened when and try and see who might be causing it. Now I know you said you disabled hardware acceleration, can you confirm that is still the case please?

Timeline:



FF57update---BSODS----driverupdate---BSODS----DISM---BSODS-->


So:

I've updated to FF57, BSODS started, then I've updated graphic drivers, didn't help, posted here, disabled hardware acceleration, run DISM, nothing helped. Right now I'm avoiding to drag anything.

Acrivec மூலமாக திருத்தப்பட்டது

Got it, thank you for that. So it seems it began with the introduction of 57 on the system, and driver updates didn't resolve it either.

There are a couple of bugs that were fixed in 56 that mimic what you are experiencing, I would wonder if there was some kind of regression in 57 or they were not fully resolved. You can take a peek here, though you won't be able to access a few of concern. Security vulnerabilities fixed in Firefox 56

Since predominantly it seems to affect WebGL, can you do the following and then try again to see if the problem persists.

  1. Goto about:addons
  2. Temporarily disable all addons (after all are done, if any required restart of the browser, do it first before continuing)
  3. Go to about:config
  4. Search for webgl.disabled and set the value to true
  5. Search for webgl.dxgl.enabled and set the value to false
  6. Search for webgl.enable-webgl2 and set the value to false
  7. Check for gl.require-hardware and make sure it is false
  8. Check for media.hardware-video-decoding.enabled and make sure it is false
  9. Confirm that media.hardware-video-decoding.force-enabled is NOT true
  10. Confirm that webgl.force-enabled is NOT true
  11. Restart the browser
  12. Try to replicate the issue as before, does it happen still?

If this resolves it, then you have a temporary workaround and we can file a bug for regression of the WebGL issue and have them look into it, but if it keeps happening then we need to still file a bug but they might need more diagnostic data from you to see if it is new or a regression.

9 false 10 false changed 4, 5, 6, 8 7 was already false opened in save mode (addons disabled), let's bsod!

GµårÐïåñ said

but if it keeps happening then we need to still file a bug but they might need more diagnostic data from you to see if it is new or a regression.

111917-7046-01.dmp 19.11.2017 13:48:35 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 ffff800d`41d50edf fffff485`401b60c0 00000000`00000000 win32kfull.sys win32kfull.sys+150edf Full/Desktop Win32k Kernel Driver Microsoft® Windows® Operating System Microsoft Corporation 10.0.16299.19 (WinBuild.160101.0800) x64 ntoskrnl.exe+163960 C:\WINDOWS\Minidump\111917-7046-01.dmp 8 15 16299 1 453 116 19.11.2017 13:50:42

Ok so with all graphic accelerators disabled and no addons (just to review and confirm) it still crashed.

Clearly there is something we are not seeing and thank you for the message you posted above but that is a generic top branch, the useful information is unfortunately buried a bit deeper, so 1) how big is the dump file? 2) can you make it available to me to download so I can take a look inside and see what exactly is causing the crash to see how it ties in with the browser. Believe it or not, it could still be related to anything like a BIOS, firmware, memory corruption or any host of drive issues, but I want to be sure. I don't want us to file a bug and find out it was something else and end up wasting everyone's time.

In for an ounce, in for a pound I guess, so we are deep into it, so let's do more digging before passing it off to the dev team so at least most of the research and probing is done for them, and they can more quickly get to a resolution should it be something they need to handle.

GµårÐïåñ said

[...]

It's 1.38MB. I can send you it by email.

Please check my reply in PM.

It would be best to have a link to an upload so when needing more eyes on it later on, we don't have to keep forwarding the file around through email.

I got your link from the PM, give me tonight at least to dig through it and if necessary consult others and I will get back to you on what/where to do/go next. Thanks.

Sorry for the delay in getting back to you, I was trying to be as thorough as possible analyzing the dump file.

I can confirmed that it does not contain any hardware issues, so that's good news. It is indeed a software issue (though not particularly Firefox) which is resulting from transition from unprivilaged to privilaged memory space which is causing it.

Specifically it is caused by the presence of multiple drivers reserving and accessing the same memory space, which means that some other driver/firmware is conflicting with the system as a whole. This suggests that at least one or more other drivers got updated in the same timespan and they are now causing memory access conflicts.

The bad news, there is no indication of which drivers which I suspect would not be included in the mini dump but would be in the full dump logs. You can try and check under event viewer to look for hardware and system recorded alerts and they might shine more light on what is causing it, assuming it had a chance to record the event before it terminated.

While you are welcome to file a bug with us to have them take a look, I can all but assure it won't be related and you will still be facing the issue after they are done and it will just waste your effort. If you can do a through check of all your drivers that have updated recently (as far back as when the issue was first noticed) and check to see if they have any known issues or workarounds for the issue you are experiencing or better yet an update to the driver you can install yourself.

  1. 1
  2. 2