0x0A (IRQL_NOT_LESS_OR_EQUAL)


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


Loading Dump File [E:\A28\dump\39174_82RD00505_\OSdump\memory.dmp]
Kernel Bitmap Dump File: Full address space is available

Dump completed successfully, progress percentage: 100


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 22000 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff803`3e000000 PsLoadedModuleList = 0xfffff803`3ec29bc0
Debug session time: Fri Apr 22 10:07:27.813 2022 (UTC + 8:00)
System Uptime: 0 days 0:09:54.634
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............................
Loading User Symbols
................................................................
..................
Loading unloaded module list
...................................................
For analysis of this file, run !analyze -v
0: 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: ffffa48180180240, 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: fffff8033e329ab3, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4312

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on LAPTOP-3L24QV3P

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 4401

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

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

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE:  a

BUGCHECK_P1: ffffa48180180240

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8033e329ab3

READ_ADDRESS:  ffffa48180180240 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff38df761f4c0 -- (.trap 0xfffff38df761f4c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa48000000000 rbx=0000000000000000 rcx=ffffbf0000000028
rdx=fffff38df761fa20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8033e329ab3 rsp=fffff38df761f650 rbp=fffff38df761f840
 r8=0000007ffffffff8  r9=000000ffffffffff r10=ffffbf0000000000
r11=ffffbf0000000018 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!MiResolveProtoPteFault+0xe3:
fffff803`3e329ab3 488b07          mov     rax,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

STACK_TEXT:  
fffff38d`f761f378 fffff803`3e428da9     : 00000000`0000000a ffffa481`80180240 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff38d`f761f380 fffff803`3e424f00     : 00000000`00000000 ffffa805`a533c1c0 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff38d`f761f4c0 fffff803`3e329ab3     : 00000000`79517350 fffff38d`f761f678 00000000`00000000 0000009a`397ff7dc : nt!KiPageFault+0x440
fffff38d`f761f650 fffff803`3e3292e3     : fffff38d`f761f7a0 00000000`00000000 fffff38d`f761f780 ffffa4d2`5ffe90b0 : nt!MiResolveProtoPteFault+0xe3
fffff38d`f761f740 fffff803`3e3278e2     : 00000000`00000000 00000000`00000100 00000000`c0000016 00000000`00000000 : nt!MiDispatchFault+0x1b3
fffff38d`f761f880 fffff803`3e424df5     : ffffa805`a533c080 0000009a`397ff7a0 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x152
fffff38d`f761fa20 00007ffa`42c2e910     : 00007ffa`446d6132 0000028d`28b43000 00000000`00000000 0000009a`397ff4e4 : nt!KiPageFault+0x335
0000009a`397ff2a8 00007ffa`446d6132     : 0000028d`28b43000 00000000`00000000 0000009a`397ff4e4 00000ff6`fb408c17 : combase!ThreadInvoke [onecore\com\combase\dcomrem\channelb.cxx @ 7295] 
0000009a`397ff2b0 00007ffa`44692fff     : 0000009a`397ff410 00007ffa`42c222b5 0000009a`397ff4e4 0000028d`28aa98a0 : RPCRT4!DispatchToStubInCNoAvrf+0x22
0000009a`397ff300 00007ffa`44692c08     : 0000028d`28aaf9c0 00000000`00000000 00000000`00000001 00000001`00000003 : RPCRT4!RPC_INTERFACE::DispatchToStubWorker+0x1af
0000009a`397ff3e0 00007ffa`446a20f5     : 00000000`00000000 00007ffa`44bca8c7 0000028d`270511c0 00000000`00000000 : RPCRT4!RPC_INTERFACE::DispatchToStubWithObject+0x188
0000009a`397ff480 00007ffa`446a1747     : 00000000`0006076d 00000000`00000002 00000000`00000000 0000028d`28a8b6a0 : RPCRT4!LRPC_SCALL::DispatchRequest+0x175
0000009a`397ff550 00007ffa`446a0dcb     : 00000000`00000000 0000028d`28ab6560 00000000`00000000 00000000`00000000 : RPCRT4!LRPC_SCALL::HandleRequest+0x837
0000009a`397ff650 00007ffa`446a0aa1     : 00000000`00000000 0000028d`28ac9c40 0000028d`26f70000 00000000`00000000 : RPCRT4!LRPC_SASSOCIATION::HandleRequest+0x24b
0000009a`397ff6d0 00007ffa`446a06d7     : 0000028d`2703a5d0 0000009a`397ff870 00000000`00000001 0000028d`28ab6560 : RPCRT4!LRPC_ADDRESS::HandleRequest+0x181
0000009a`397ff770 00007ffa`446a6cb9     : 00000000`00000000 0000028d`28a8b6a0 0000028d`2703a6d8 0000009a`397ffb28 : RPCRT4!LRPC_ADDRESS::ProcessIO+0x897
0000009a`397ff8b0 00007ffa`44bc20b0     : 00000000`00000000 00000000`00000000 0000009a`397ffb28 0000028d`270e6c68 : RPCRT4!LrpcIoComplete+0xc9
0000009a`397ff940 00007ffa`44bb6d98     : 00000000`00000000 0000028d`27002500 00000000`00000000 0000028d`28a89280 : ntdll!TppAlpcpExecuteCallback+0x280
0000009a`397ff9c0 00007ffa`43c554e0     : 00000050`00000020 00000000`00000000 00000000`00000000 80000000`00000800 : ntdll!TppWorkerThread+0x448
0000009a`397ffcb0 00007ffa`44ba485b     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x10
0000009a`397ffce0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2b


SYMBOL_NAME:  nt!MiResolveProtoPteFault+e3

MODULE_NAME: nt

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  e3

FAILURE_BUCKET_ID:  AV_nt!MiResolveProtoPteFault

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {2f2238e9-4751-e3c3-543c-b0cdf930b219}

Followup:     MachineOwner
---------

0: kd> dd ffffa48180180240  //查看引用内存内容
ffffa481`80180240  ???????? ???????? ???????? ????????
ffffa481`80180250  ???????? ???????? ???????? ????????
ffffa481`80180260  ???????? ???????? ???????? ????????
ffffa481`80180270  ???????? ???????? ???????? ????????
ffffa481`80180280  ???????? ???????? ???????? ????????
ffffa481`80180290  ???????? ???????? ???????? ????????
ffffa481`801802a0  ???????? ???????? ???????? ????????
ffffa481`801802b0  ???????? ???????? ???????? ????????
0: kd> !pte ffffa48180180240 //查看页表 未分配
                                           VA 0000030030048000
PXE at FFFFA4D269349030    PPE at FFFFA4D269206000    PDE at FFFFA4D240C00C00    PTE at FFFFA48180180240
contains 0000000000000000
contains 0000000000000000
not valid

0: kd> !pte ffffa48180180240
                                           VA 0000030030048000
PXE at FFFFA4D269349030    PPE at FFFFA4D269206000    PDE at FFFFA4D240C00C00    PTE at FFFFA48180180240
contains 0000000000000000
contains 0000000000000000
not valid

0: kd> u fffff8033e329ab3-0x20 L0x20 //反汇编 parameter4  fffff8033e329ab3不是内存起始地址,故判断可能为CPU问题或者内存问题,CPU跑飞导致
nt!MiResolveProtoPteFault+0xc3:
fffff803`3e329a93 ff              ???
fffff803`3e329a94 ff49bd          dec     dword ptr [rcx-43h]
fffff803`3e329a97 ff              ???
fffff803`3e329a98 ff              ???
fffff803`3e329a99 ff              ???
fffff803`3e329a9a ff              ???
fffff803`3e329a9b ff              ???
fffff803`3e329a9c ff              ???
fffff803`3e329a9d ff              ???
fffff803`3e329a9e 7f49            jg      nt!MiResolveProtoPteFault+0x119 (fffff803`3e329ae9)
fffff803`3e329aa0 be00000000      mov     esi,0
fffff803`3e329aa5 0000            add     byte ptr [rax],al
fffff803`3e329aa7 400048b9        add     byte ptr [rax-47h],cl
fffff803`3e329aab 2800            sub     byte ptr [rax],al
fffff803`3e329aad 0000            add     byte ptr [rax],al
fffff803`3e329aaf 00bfffff488b    add     byte ptr [rdi-74B70001h],bh
fffff803`3e329ab5 07              ???
fffff803`3e329ab6 4c8bc0          mov     r8,rax
fffff803`3e329ab9 4183e001        and     r8d,1
fffff803`3e329abd 4d85c0          test    r8,r8
fffff803`3e329ac0 0f845f0b0000    je      nt!MiResolveProtoPteFault+0xc55 (fffff803`3e32a625)
fffff803`3e329ac6 480fbae009      bt      rax,9
fffff803`3e329acb 0f82540b0000    jb      nt!MiResolveProtoPteFault+0xc55 (fffff803`3e32a625)
fffff803`3e329ad1 488bd8          mov     rbx,rax
fffff803`3e329ad4 48c1eb0c        shr     rbx,0Ch
fffff803`3e329ad8 4923d9          and     rbx,r9
fffff803`3e329adb 483b1d9e6d9200  cmp     rbx,qword ptr [nt!MiState+0x1800 (fffff803`3ec50880)]
fffff803`3e329ae2 77d9            ja      nt!MiResolveProtoPteFault+0xed (fffff803`3e329abd)
fffff803`3e329ae4 4c8d3c5b        lea     r15,[rbx+rbx*2]
fffff803`3e329ae8 49c1e704        shl     r15,4
fffff803`3e329aec 4c897c2450      mov     qword ptr [rsp+50h],r15
fffff803`3e329af1 488bc9          mov     rcx,rcx
0: kd> dd fffff8033e329ab3
fffff803`3e329ab3  4c078b48 8341c08b 854d01e0 5f840fc0
fffff803`3e329ac3  4800000b 09e0ba0f 0b54820f 8b480000
fffff803`3e329ad3  ebc148d8 d923490c 9e1d3b48 7700926d
fffff803`3e329ae3  3c8d4cd9 e7c1495b 7c894c04 8b485024
fffff803`3e329af3  34854dc9 28b9480f 00000000 74ffffbf
fffff803`3e329b03  c28b49b9 07048d4d 0824b489 4c000001
fffff803`3e329b13  30244489 f0c38b49 2cba0f49 8d4d3f07
fffff803`3e329b23  820f0734 00000ab5 a8078b48 63840f01
0: kd> dqs fffff8033e329ab3
fffff803`3e329ab3  8341c08b`4c078b48
fffff803`3e329abb  5f840fc0`854d01e0
fffff803`3e329ac3  09e0ba0f`4800000b
fffff803`3e329acb  8b480000`0b54820f
fffff803`3e329ad3  d923490c`ebc148d8
fffff803`3e329adb  7700926d`9e1d3b48
fffff803`3e329ae3  e7c1495b`3c8d4cd9
fffff803`3e329aeb  8b485024`7c894c04
fffff803`3e329af3  28b9480f`34854dc9
fffff803`3e329afb  74ffffbf`00000000
fffff803`3e329b03  07048d4d`c28b49b9
fffff803`3e329b0b  4c000001`0824b489
fffff803`3e329b13  f0c38b49`30244489
fffff803`3e329b1b  8d4d3f07`2cba0f49
fffff803`3e329b23  00000ab5`820f0734
fffff803`3e329b2b  63840f01`a8078b48
 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
DRIVER_IRQL_NOT_LESS_OR_EQUAL是一个Windows操作系统的蓝屏错误代码,通常表示驱动程序在访问无效的内存地址或者以错误的IRQL(中断请求级别)访问了内核模式下的资源。这个错误通常与驱动程序的问题有关。 当系统发生DRIVER_IRQL_NOT_LESS_OR_EQUAL错误时,可能会导致系统崩溃并重新启动。为了解决这个问题,可以尝试以下几个步骤: 1. 更新驱动程序:检查并确保所有硬件设备的驱动程序都是最新版本。可以通过访问硬件制造商的官方网站来获取最新的驱动程序。 2. 检查硬件冲突:某些硬件设备可能会与其他设备或驱动程序发生冲突,导致DRIVER_IRQL_NOT_LESS_OR_EQUAL错误。可以尝试禁用或卸载最近安装的硬件设备,然后重新启动系统,看看问题是否解决。 3. 检查内存问题:使用Windows自带的内存诊断工具(Windows Memory Diagnostic)来检查系统内存是否存在问题。如果发现有错误,可能需要更换或修复损坏的内存模块。 4. 执行系统文件检查:运行命令提示符(以管理员身份运行),输入" sfc /scannow"命令来执行系统文件检查。这将扫描并修复系统文件中的任何损坏或错误。 5. 更新操作系统:确保操作系统是最新版本,并安装所有可用的更新补丁程序。 如果以上方法无法解决问题,建议联系技术支持或专业人士进行进一步的故障排除和修复。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值