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

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

FREQUENT FIREFOX CRASHES

more options

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)

more options

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.

問個問題

如果您還沒有帳號,您必須先登入帳號 來回覆文章。還沒有帳號的話,只能發問新問題