Starting FIrefox causes windows 10 to freeze with a DCP Watchdog Violation error
For the past several days, every time I try to start Firefox, my computer within seconds completely freezes and after about a minute I get a blue screen with the message that I have a DCP Watchdog Violation, after which the computer automatically reboots. I have made sure that all updates are installed in Windows 10 and have uninstalled and reinstalled Firefox. What are my options other than to stop using Firefox?
Isisombululo esikhethiwe
Sorry to hear about this problem. Some guesswork may be involved in tracking down what's happening.
My general understanding based on various web articles is that DPC WATCHDOG VIOLATION occurs when there is a problem with a "deferred procedure call" and can be caused by a device driver.
Firefox may exercise a number of device drivers, but the most notorious for causing issues are the display drivers (for built-in or added-on graphics hardware). This article describes safe ways to look for updates:
Upgrade your graphics drivers to use hardware acceleration and WebGL
You also could try starting Firefox in its Safe Mode. In its Safe Mode, Firefox temporarily deactivates hardware acceleration, which can bypass some issues caused by device driver incompatibilities.
If Firefox is not running: Hold down the Shift key when starting Firefox.
If Firefox is running: You can restart Firefox in Safe Mode using either:
- "3-bar" menu button > "?" button > Restart with Add-ons Disabled
- Help menu > Restart with Add-ons Disabled
and OK the restart.
Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).
Any improvement?
At startup, Firefox also may load other drivers. Users with older Logitech cameras have had issues with 64-bit Firefox 56-58 when Windows killed Firefox during startup due to issues with the camera driver software. Your situation is more severe, but if you have older audio/video, camera, or microphone device software, you might try updating it.
Beyond that, Windows creates some log files that you could get analyzed by Microsoft support. (Example threads from 2015 and 2017.)
Alternately, you could test whether 32-bit Firefox works better on your system for now until the cause(s) of the current issues are discovered. To make the switch:
(A) Download a fresh installer for Firefox to a convenient location:
https://www.mozilla.org/firefox/all/ -- chose from the non-64-bit column
(B) Exit out of Firefox (if applicable).
If you use Microsoft Office, please change your default browser to Internet Explorer before the next step.
(C) Using Windows Explorer/My Computer (hold down the Windows key and press E), right-click > rename the program folder as follows (you might have one or both):
C:\Program Files (x86)\Mozilla Firefox =to=> C:\Program Files (x86)\OldFirefox
C:\Program Files\Mozilla Firefox =to=> C:\Program Files\OldFirefox
(D) Run the installer you downloaded in step (A). It should automatically connect to your existing settings.
Any improvement?
Funda le mpendulo ngokuhambisana nalesi sihloko 👍 0All Replies (2)
Isisombululo Esikhethiwe
Sorry to hear about this problem. Some guesswork may be involved in tracking down what's happening.
My general understanding based on various web articles is that DPC WATCHDOG VIOLATION occurs when there is a problem with a "deferred procedure call" and can be caused by a device driver.
Firefox may exercise a number of device drivers, but the most notorious for causing issues are the display drivers (for built-in or added-on graphics hardware). This article describes safe ways to look for updates:
Upgrade your graphics drivers to use hardware acceleration and WebGL
You also could try starting Firefox in its Safe Mode. In its Safe Mode, Firefox temporarily deactivates hardware acceleration, which can bypass some issues caused by device driver incompatibilities.
If Firefox is not running: Hold down the Shift key when starting Firefox.
If Firefox is running: You can restart Firefox in Safe Mode using either:
- "3-bar" menu button > "?" button > Restart with Add-ons Disabled
- Help menu > Restart with Add-ons Disabled
and OK the restart.
Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).
Any improvement?
At startup, Firefox also may load other drivers. Users with older Logitech cameras have had issues with 64-bit Firefox 56-58 when Windows killed Firefox during startup due to issues with the camera driver software. Your situation is more severe, but if you have older audio/video, camera, or microphone device software, you might try updating it.
Beyond that, Windows creates some log files that you could get analyzed by Microsoft support. (Example threads from 2015 and 2017.)
Alternately, you could test whether 32-bit Firefox works better on your system for now until the cause(s) of the current issues are discovered. To make the switch:
(A) Download a fresh installer for Firefox to a convenient location:
https://www.mozilla.org/firefox/all/ -- chose from the non-64-bit column
(B) Exit out of Firefox (if applicable).
If you use Microsoft Office, please change your default browser to Internet Explorer before the next step.
(C) Using Windows Explorer/My Computer (hold down the Windows key and press E), right-click > rename the program folder as follows (you might have one or both):
C:\Program Files (x86)\Mozilla Firefox =to=> C:\Program Files (x86)\OldFirefox
C:\Program Files\Mozilla Firefox =to=> C:\Program Files\OldFirefox
(D) Run the installer you downloaded in step (A). It should automatically connect to your existing settings.
Any improvement?
Thanks. I was able to start Firefox in safe mode and then I refreshed my install. That has fixed the problem.