Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

FREQUENT FIREFOX CRASHES

更多选项

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000030, 0x0000000000000002, 0x0000000000000000, 0xfffff80274225392) CAUSE WAS FIREFOX.EXE

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000030, 0x0000000000000002, 0x0000000000000000, 0xfffff80274225392) CAUSE WAS FIREFOX.EXE

所有回复 (1)

更多选项

Hi

Firefox cannot directly cause an IRQL_NOT_LESS_OR_EQUAL bugcheck What the debugger likely showed is that Firefox was the actively running application when the crash occurred. The true culprit is almost always a kernel-mode driver that was processing a request initiated by Firefox.

Bugcheck Code: 0x0000000a (IRQL_NOT_LESS_OR_EQUAL) It means that the operating system kernel, or a driver running in kernel mode, tried to access a memory address to which it did not have permission, often because it was executing at an elevated IRQL (like DISPATCH_LEVEL or higher) but attempted to use pageable memory.

Parameters: 0x0000000000000030: The memory address referenced. 0x0000000000000002: The IRQL at the time of the access (2 = DISPATCH_LEVEL). 0x0000000000000000: The type of access (0 = Read operation). 0xfffff80274225392: The instruction address that referenced the memory.

I recommend to update your Graphics Driver (GPU) and/or Network/Wi-Fi Driver.

For a definitive answer, you'd need to use a tool like WinDbg to analyze the minidump file created during the crash. This would pinpoint the specific driver file that contains the instruction address 0xfffff80274225392.

我要提问

您需要登录才能回复。如果您还没账号,可以提出新问题