打游戏总会反复蓝屏,已经尝试检查内存无问题,电脑正常使用无问题,就是打游戏打到一半蓝屏

匿名
2024-11-12T17:33:52+00:00

************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\32084\Desktop\111124-7781-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff801`22a00000 PsLoadedModuleList = 0xfffff801`23613510
Debug session time: Mon Nov 11 20:38:53.643 2024 (UTC + 8:00)
System Uptime: 0 days 2:08:19.289
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols

Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`22e15df0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffe07`f40ef080=000000000000000a
8: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffb502e9546a98, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80122d3a559, address which referenced memory

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 765

    Key  : Analysis.Elapsed.mSec
    Value: 1300

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 46

    Key  : Analysis.Init.Elapsed.mSec
    Value: 166908

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 96

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_nt!KiDeferredReadySingleThread

    Key  : Failure.Hash
    Value: {626f59d5-90cc-ab48-85f0-60e170096c96}

BUGCHECK_CODE:  a

BUGCHECK_P1: ffffb502e9546a98

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80122d3a559

FILE_IN_CAB:  111124-7781-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffb50ad3b4b040

READ_ADDRESS: fffff8012371c4a8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffffb502e9546a98 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  fffffe07f40ef1c0 -- (.trap 0xfffffe07f40ef1c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000011 rbx=0000000000000000 rcx=ffffc881b3f54180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80122d3a559 rsp=fffffe07f40ef350 rbp=fffffe07f40ef450
 r8=0000000000000000  r9=0000000000000008 r10=ffffb502e9546a98
r11=0000000000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiDeferredReadySingleThread+0x629:
fffff801`22d3a559 450fb71a        movzx   r11d,word ptr [r10] ds:ffffb502`e9546a98=????
Resetting default scope

STACK_TEXT:  
fffffe07`f40ef078 fffff801`22e2bd29     : 00000000`0000000a ffffb502`e9546a98 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffe07`f40ef080 fffff801`22e27189     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffffe07`f40ef1c0 fffff801`22d3a559     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x489
fffffe07`f40ef350 fffff801`22d30964     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeferredReadySingleThread+0x629
fffffe07`f40ef720 fffff801`22d319fd     : ffffb50a`00000000 00000000`00000001 fffffe07`00000000 00000000`00000002 : nt!KiProcessThreadWaitList+0x134
fffffe07`f40ef7a0 fffff801`22d32c19     : 00000000`00000008 fffffe07`f40ef9d0 ffffc881`b3f54180 fffff801`1f7f8b88 : nt!KiProcessExpiredTimerList+0x35d
fffffe07`f40ef8d0 fffff801`22e1adfe     : 00000000`00000000 ffffc881`b3f54180 ffffb50a`d3b4b040 ffffb50a`e23c9480 : nt!KiRetireDpcList+0xaf9
fffffe07`f40efb80 00000000`00000000     : fffffe07`f40f0000 fffffe07`f40e9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME:  nt!KiDeferredReadySingleThread+629

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.3880

STACK_COMMAND:  .process /r /p 0xfffff80123748f40; .thread 0xffffb50ad3b4b040 ; kb

BUCKET_ID_FUNC_OFFSET:  629

FAILURE_BUCKET_ID:  AV_nt!KiDeferredReadySingleThread

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {626f59d5-90cc-ab48-85f0-60e170096c96}

Followup:     MachineOwner
---------
Windows 商业版 | 面向 IT 专业人士的 Windows 客户端 | 性能 | 应用程序技术和兼容性

锁定的问题。 此问题已从 Microsoft 支持社区迁移。 你可投票决定它是否有用,但不能添加评论或回复,也不能关注问题。

0 个注释 无注释
{count} 票
问题作者接受的答案
  1. 匿名
    2024-11-13T23:04:27+00:00

    您好,

    IRQL_NOT_LESS_OR_EQUAL 错误通常发生在系统进程或设备驱动程序尝试访问没有适当权限的内存地址时。

    您可以采取以下一些步骤来排除故障并解决此错误:

    验证并更新驱动程序:使用Driver Verifier工具检查驱动程序是否正常,并确保所有设备驱动程序都是最新的。您可以通过设备管理器右键单击每个设备并选择“更新驱动程序”来执行此操作。

    运行系统文件检查器 (SFC) 和 DISM:

    以管理员身份打开命令提示符。

    逐个运行以下命令:

    DISM /Online /Cleanup-Image /CheckHealth

    DISM /Online /Cleanup-Image /ScanHealth

    DISM /Online /Cleanup-Image /RestoreHealth

    sfc /scannow

    这些命令将检查并修复任何损坏的系统文件。

    检查 Windows 更新:确保您的系统已更新到最新的 Windows 更新,因为这些更新通常包含已知问题的修复。

    Bug Check 0xA IRQL_NOT_LESS_OR_EQUAL - Windows drivers | Microsoft Learn

    此致

    Wesley Li

    0 个注释 无注释

0 个其他答案

排序依据: 非常有帮助