Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

FF caused BSOD

  • No replies
  • 1 has this problem
  • 29 views
SirCobalt
SirCobalt
more options

I was recently watching a Twitch livestream when I stepped away from my PC for a moment and upon returning found it sitting at the login screen. Checking eventvwr it showed a BSOD event had occurred. The only thing actively running on my PC was FireFox with a single tab for Twitch.

Level: Critical Source: Kernal-Power Event ID: 41 BugCheckCode: 307 decimal, 0x133 hex

Windows documentation lists hex 0x133 as a DPC_WATCHDOG_VIOLATION error, and since Parameter 1 was a '0', it states, "A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace." https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x133-dpc-watchdog-violation

From Windows Debugging Tools I loaded up the DMP file and ran !analyze to see the process name listed as FF (there's more information listed, just not sure it's really useful).

PROCESS_NAME: firefox.exe MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe STACK_COMMAND: .thread ; .cxr ; kb STACK_TEXT: ffffa681`de892c88 fffff804`7581f5fa  : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffa681`de892c90 fffff804`7561c3cd  : 0000de92`ad226167 ffffa681`de840180 00000000`00000246 00000000`008d0193 : nt!KeAccumulateTicks+0x20644a ffffa681`de892cf0 fffff804`7561c971  : 00000000`008d0192 00000000`00540bd4 ffffa681`de840180 00000000`00000001 : nt!KiUpdateRunTime+0x5d ffffa681`de892d40 fffff804`756167e3  : ffffa681`de840180 00000000`00000000 fffff804`76031630 00000000`00000000 : nt!KiUpdateTime+0x4a1 ffffa681`de892e80 fffff804`7561f1a2  : ffff8a08`cf6e79c0 ffff8a08`cf6e7a40 ffff8a08`cf6e7a00 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3 ffffa681`de892f30 fffff804`756de055  : 00000150`3043798c ffffcb8c`9850adc0 ffffcb8c`9850ae70 ffff2a97`b5c65417 : nt!HalpTimerClockInterrupt+0xe2 ffffa681`de892f60 fffff804`757f8d4a  : ffff8a08`cf6e7a40 ffffcb8c`9850adc0 0000de80`ffc7236f 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5 ffffa681`de892fb0 fffff804`757f92b7  : 00000000`00000000 00001f80`007f02c4 00000000`4af4ce39 ffff8a08`cf6e7bb8 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffff8a08`cf6e79c0 fffff804`75680c6b  : 00000000`80000000 fffff804`75729a99 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffff8a08`cf6e7b50 fffff804`75729a99  : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x1b ffff8a08`cf6e7b60 fffff804`7569a24e  : ffffa681`de843240 ffffa681`4afc988a ffffcb8c`b0c73480 ffffcb8c`ac2e3040 : nt!ExpGetPoolTagInfoTarget+0x149 ffff8a08`cf6e7bb0 fffff804`75699534  : ffffa681`de840180 00000000`00000000 00000000`00000008 00000000`005408f1 : nt!KiExecuteAllDpcs+0x30e ffff8a08`cf6e7d20 fffff804`757fe2e5  : 00000000`00000000 ffffa681`de840180 00000000`00000000 000001d3`21056910 : nt!KiRetireDpcList+0x1f4 ffff8a08`cf6e7fb0 fffff804`757fe0d0  : 00000081`e2df8c90 00000000`00000000 000001d3`18d58b28 00000081`e2df8b90 : nt!KxRetireDpcList+0x5 ffff8a08`d1eefa90 fffff804`757fd79e  : 000001d3`00000000 00000000`00000001 000001d3`2105a4e0 ffff8a08`d1eefb40 : nt!KiDispatchInterruptContinue ffff8a08`d1eefac0 00007ff8`acdd7bd7  : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2ee 00000081`e2def0b0 00000000`00000000  : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`acdd7bd7

I checked FF `about:crashes` and it doesn't show any crash report there (presumably because the system BSOD and it did not have a chance to do anything).

Just wondering if anyone else has seen this issue and how/if they resolved it. In searching around it seemed like some folks suggested disabling hardware acceleration as there may be incompatibility issues with FF and GPU drivers. I checked under FF settings and it has "Use recommended performance settings" enabled, but there are no sub-options specific for hardware acceleration.

Some basic system specs: MoBo: Gigabyte B550 Vision D-P (BIOS F13e, latest available) CPU: AMX Ryzen 7 5800X GPU: Gigabyte GeForce 3060Ti (driver 30.0.14.7141, latest one available)

Running on FF 94.0.2 (64-bit), the latest update.

I was recently watching a Twitch livestream when I stepped away from my PC for a moment and upon returning found it sitting at the login screen. Checking eventvwr it showed a BSOD event had occurred. The only thing actively running on my PC was FireFox with a single tab for Twitch. Level: Critical Source: Kernal-Power Event ID: 41 BugCheckCode: 307 decimal, 0x133 hex Windows documentation lists hex 0x133 as a DPC_WATCHDOG_VIOLATION error, and since Parameter 1 was a '0', it states, "A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace." https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x133-dpc-watchdog-violation From Windows Debugging Tools I loaded up the DMP file and ran !analyze to see the process name listed as FF (there's more information listed, just not sure it's really useful). PROCESS_NAME: firefox.exe MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe STACK_COMMAND: .thread ; .cxr ; kb STACK_TEXT: ffffa681`de892c88 fffff804`7581f5fa : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffa681`de892c90 fffff804`7561c3cd : 0000de92`ad226167 ffffa681`de840180 00000000`00000246 00000000`008d0193 : nt!KeAccumulateTicks+0x20644a ffffa681`de892cf0 fffff804`7561c971 : 00000000`008d0192 00000000`00540bd4 ffffa681`de840180 00000000`00000001 : nt!KiUpdateRunTime+0x5d ffffa681`de892d40 fffff804`756167e3 : ffffa681`de840180 00000000`00000000 fffff804`76031630 00000000`00000000 : nt!KiUpdateTime+0x4a1 ffffa681`de892e80 fffff804`7561f1a2 : ffff8a08`cf6e79c0 ffff8a08`cf6e7a40 ffff8a08`cf6e7a00 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3 ffffa681`de892f30 fffff804`756de055 : 00000150`3043798c ffffcb8c`9850adc0 ffffcb8c`9850ae70 ffff2a97`b5c65417 : nt!HalpTimerClockInterrupt+0xe2 ffffa681`de892f60 fffff804`757f8d4a : ffff8a08`cf6e7a40 ffffcb8c`9850adc0 0000de80`ffc7236f 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5 ffffa681`de892fb0 fffff804`757f92b7 : 00000000`00000000 00001f80`007f02c4 00000000`4af4ce39 ffff8a08`cf6e7bb8 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffff8a08`cf6e79c0 fffff804`75680c6b : 00000000`80000000 fffff804`75729a99 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffff8a08`cf6e7b50 fffff804`75729a99 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x1b ffff8a08`cf6e7b60 fffff804`7569a24e : ffffa681`de843240 ffffa681`4afc988a ffffcb8c`b0c73480 ffffcb8c`ac2e3040 : nt!ExpGetPoolTagInfoTarget+0x149 ffff8a08`cf6e7bb0 fffff804`75699534 : ffffa681`de840180 00000000`00000000 00000000`00000008 00000000`005408f1 : nt!KiExecuteAllDpcs+0x30e ffff8a08`cf6e7d20 fffff804`757fe2e5 : 00000000`00000000 ffffa681`de840180 00000000`00000000 000001d3`21056910 : nt!KiRetireDpcList+0x1f4 ffff8a08`cf6e7fb0 fffff804`757fe0d0 : 00000081`e2df8c90 00000000`00000000 000001d3`18d58b28 00000081`e2df8b90 : nt!KxRetireDpcList+0x5 ffff8a08`d1eefa90 fffff804`757fd79e : 000001d3`00000000 00000000`00000001 000001d3`2105a4e0 ffff8a08`d1eefb40 : nt!KiDispatchInterruptContinue ffff8a08`d1eefac0 00007ff8`acdd7bd7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2ee 00000081`e2def0b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`acdd7bd7 I checked FF `about:crashes` and it doesn't show any crash report there (presumably because the system BSOD and it did not have a chance to do anything). Just wondering if anyone else has seen this issue and how/if they resolved it. In searching around it seemed like some folks suggested disabling hardware acceleration as there may be incompatibility issues with FF and GPU drivers. I checked under FF settings and it has "Use recommended performance settings" enabled, but there are no sub-options specific for hardware acceleration. Some basic system specs: MoBo: Gigabyte B550 Vision D-P (BIOS F13e, latest available) CPU: AMX Ryzen 7 5800X GPU: Gigabyte GeForce 3060Ti (driver 30.0.14.7141, latest one available) Running on FF 94.0.2 (64-bit), the latest update.