Firefox BSOD
Hello, today i had weird FF behavior, for while i was browsing i have got BSOD. When i have analyzed the minidump file it says firefox.exe is a reason.
FF: 115.0.3 Here is WinDBG log:
Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\072923-8328-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff801`5f800000 PsLoadedModuleList = 0xfffff801`6042a2d0 Debug session time: Sat Jul 29 00:42:10.245 2023 (UTC + 3:00) System Uptime: 0 days 3:55:03.853 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................ Loading User Symbols Loading unloaded module list .............. For analysis of this file, run !analyze -v 9: kd> !analyze -v
- *
- Bugcheck Analysis *
- *
SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff8015fdf5f61, Address of the instruction which caused the bugcheck Arg3: ffffb20bb3347a20, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero.
Debugging Details:
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec Value: 3937
Key : Analysis.DebugAnalysisManager Value: Create
Key : Analysis.Elapsed.mSec Value: 19210
Key : Analysis.Init.CPU.mSec Value: 5155
Key : Analysis.Init.Elapsed.mSec Value: 33986
Key : Analysis.Memory.CommitPeak.Mb Value: 80
Key : WER.OS.Branch Value: vb_release
Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version Value: 10.0.19041.1
BUGCHECK_CODE: 3b
BUGCHECK_P1: c0000005
BUGCHECK_P2: fffff8015fdf5f61
BUGCHECK_P3: ffffb20bb3347a20
BUGCHECK_P4: 0
CONTEXT: ffffb20bb3347a20 -- (.cxr 0xffffb20bb3347a20) rax=ffffb20bb33484e0 rbx=000000000000000b rcx=ffff8001fb3cc080 rdx=0000000000000000 rsi=ffff8001fb3cc080 rdi=dfffa007000746c0 rip=fffff8015fdf5f61 rsp=ffffb20bb3348420 rbp=ffffb20bb3348609
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=ffffcd7f6d800000 r12=0000000000000000 r13=0000000000000000 r14=ffff8001dacbb6c0 r15=0000000000000001 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286 nt!SeDefaultObjectMethod+0xb1: fffff801`5fdf5f61 488b4708 mov rax,qword ptr [rdi+8] ds:002b:dfffa007`000746c8=???????????????? Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: firefox.exe
STACK_TEXT: ffffb20b`b3348420 fffff801`5fe11216 : ffff8001`fb3cc050 ffffb20b`b3348609 00000000`00000000 00000000`00000000 : nt!SeDefaultObjectMethod+0xb1 ffffb20b`b3348480 fffff801`5fa212d7 : 00000000`00000000 00000000`00000000 ffffb20b`b3348609 ffff8001`fb3cc080 : nt!ObpRemoveObjectRoutine+0xd6 ffffb20b`b33484e0 fffff801`5fe167a9 : ffff8001`fb3cc050 ffffa007`05affa90 00000000`00000000 ffffa007`05aff7d0 : nt!ObfDereferenceObjectWithTag+0xc7 ffffb20b`b3348520 fffff801`5fe31815 : ffff8001`fe2c0098 fffff801`5fa215c9 ffff8001`fe2c0060 00000000`00000000 : nt!ObCloseHandleTableEntry+0x6c9 ffffb20b`b3348660 fffff801`5fe3213d : ffff8001`fe2c0060 ffff8001`f83da080 ffffffff`ffffff01 ffff8001`fc4c2798 : nt!ExSweepHandleTable+0xd5 ffffb20b`b3348710 fffff801`5fe31548 : ffffffff`ffffffff ffff8001`fc4c2340 ffffb20b`b3348760 fffff801`5fe50fec : nt!ObKillProcess+0x35 ffffb20b`b3348740 fffff801`5fe83f02 : ffff8001`fc4c2340 ffffa007`04017060 ffffb20b`b3348990 00000000`00000000 : nt!PspRundownSingleProcess+0x204 ffffb20b`b33487d0 fffff801`5fec8578 : 00000001`00000001 00000000`00000001 ffffb20b`b33489e0 0000000c`eaad4000 : nt!PspExitThread+0x5f6 ffffb20b`b33488d0 fffff801`5faddf37 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0050d000 : nt!KiSchedulerApcTerminate+0x38 ffffb20b`b3348910 fffff801`5fc01060 : 00000000`00000000 ffffb20b`b33489c0 ffffb20b`b3348b80 00000200`00000000 : nt!KiDeliverApc+0x487 ffffb20b`b33489c0 fffff801`5fc0f49f : ffff8001`f83da080 ffff8001`fff64ee0 00000000`00000000 00000000`00000000 : nt!KiInitiateUserApc+0x70 ffffb20b`b3348b00 00007ffd`7960d0e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f 0000000c`ec46fba8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`7960d0e4
SYMBOL_NAME: nt!SeDefaultObjectMethod+b1
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.2846
STACK_COMMAND: .cxr 0xffffb20bb3347a20 ; kb
BUCKET_ID_FUNC_OFFSET: b1
FAILURE_BUCKET_ID: 0x3B_c0000005_nt!SeDefaultObjectMethod
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {0efa101b-e9d0-1362-a826-cbc49be172a8}
Followup: MachineOwner
Todas as respostas (1)
See if it still happens with hardware acceleration disabled. You might need to update your graphics drivers to the latest stable version.