IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe問題

匿名
2020-03-13T18:21:15+00:00

以下是從dump檔擷取下來的 請問一下這個藍屏是什麼問題?不久以前還有發生KERNEL_MODE_HEAP_CORRUPTION問題麻煩幫我分析一下! 感謝QAQMicrosoft (R) Windows Debugger Version 10.0.19528.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\031420-12046-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 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`81400000 PsLoadedModuleList = 0xfffff804`81848190
Debug session time: Sat Mar 14 00:40:52.032 2020 (UTC + 8:00)
System Uptime: 4 days 22:56:20.226
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`815c1510 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff209`dee98580=000000000000000a
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'

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

Loading Dump File [C:\Windows\Minidump\031420-12046-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 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`81400000 PsLoadedModuleList = 0xfffff804`81848190
Debug session time: Sat Mar 14 00:40:52.032 2020 (UTC + 8:00)
System Uptime: 4 days 22:56:20.226
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`815c1510 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff209`dee98580=000000000000000a
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: 000003e4ef4e62b9, 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: fffff8048143dceb, address which referenced memory

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-A9FP5RL

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 2

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1

    Key  : Dump.Attributes.RequiredDumpfileSize
    Value: 0xC0258AF8

ADDITIONAL_XML: 1

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

BUGCHECK_CODE:  a

BUGCHECK_P1: 3e4ef4e62b9

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8048143dceb

READ_ADDRESS: fffff804819733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8048182a3d8: Unable to get Flags value from nt!KdVersionBlock
fffff8048182a3d8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 000003e4ef4e62b9 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  fffff209dee986c0 -- (.trap 0xfffff209dee986c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000008c rbx=0000000000000000 rcx=fffff209dee98908
rdx=fffff8047ee5d180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8048143dceb rsp=fffff209dee98850 rbp=000003e4ef4e62b9
 r8=0000000000000000  r9=fffff8047ee60800 r10=fffff8047ee5d180
r11=fffff80481400000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KiInsertTimerTable+0x25b:
fffff804`8143dceb c9              leave
Resetting default scope

MISALIGNED_IP: 
nt!KiInsertTimerTable+25b
fffff804`8143dceb c9              leave

STACK_TEXT:  
fffff209`dee98578 fffff804`815d33e9 : 00000000`0000000a 000003e4`ef4e62b9 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff209`dee98580 fffff804`815cf72b : ffffcb01`6a1d8340 ffffdf8f`92fc4080 ffffdf8f`92fc4080 fffff804`815c8a24 : nt!KiBugCheckDispatch+0x69
fffff209`dee986c0 fffff804`8143dceb : 00000000`00000102 fffff804`8143c7e2 ffffcb01`69b94180 00000000`00000000 : nt!KiPageFault+0x46b
fffff209`dee98850 00000000`00000001 : fffff804`7ee5d180 00000000`00000000 00000000`00000000 00000000`00000002 : nt!KiInsertTimerTable+0x25b
fffff209`dee988d0 fffff804`7ee5d180 : 00000000`00000000 00000000`00000000 00000000`00000002 fffff804`7ee5d180 : 0x1
fffff209`dee988d8 00000000`00000000 : 00000000`00000000 00000000`00000002 fffff804`7ee5d180 fffff804`8143b6f7 : 0xfffff804`7ee5d180

SYMBOL_NAME:  nt!KiInsertTimerTable+25b

IMAGE_NAME:  hardware

IMAGE_VERSION:  10.0.18362.657

STACK_COMMAND:  .thread ; .cxr ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {201b0e5d-db2a-63d2-77be-8ce8ff234750}

Followup:     MachineOwner
---------
Windows for home | Windows 10 | 裝置和驅動程式

鎖定的問題。 此問題已從 Microsoft 支援服務社群移轉。 您可以對其是否有幫助進行投票，但無法對問題新增註解或回覆，或進行追蹤。

0 則留言
由問題作者接受的回答
TaoLi 120.6K 信譽點數 獨立顧問
2020-03-18T02:55:12+00:00

謝謝回復，

根據此次的藍屏檔來看，這邊確認是您設備中的nvlddmkm.sys運行錯誤導致的

nvlddmkm.sys是您設備中的顯卡驅動，建議嘗試以下方法重新安裝驅動：

HTTPs://www.geforce.cn/drivers

此回答有幫助嗎？

有 2 人認為此回答有所幫助。
0 則留言

10 個其他答案

排序依據： 最實用
最實用 最新 最舊
  1. 匿名
    2020-03-17T12:11:16+00:00

    您好！

    我們了解到您關於Windows操作系統出現藍屏的問題，

    我們需要您提供您的dump文件來為您分析您系統藍屏的原因，

    建議你嘗試以下方案進行操作：

    打開控制臺>>系統>>進堦系統設定>>進階>>啓動及修復>>設定，

    寫入偵錯咨詢>>选择“小記憶體傾印（256KB）”，傾印檔案選擇默認，確定。

    完成後重新啟動您的電腦，使設定生效；再次出現這個問題，前往檔案C:\Windows\Minidump提取即可。

    我們將通過私人訊息聯繫您，請注意查收。

    感謝!!已私訊回覆您 再麻煩您幫忙了

    此回答有幫助嗎？

    0 則留言
  2. 匿名
    2020-03-16T08:48:56+00:00

    您好！

    我們了解到您關於Windows操作系統出現藍屏的問題，

    我們需要您提供您的dump文件來為您分析您系統藍屏的原因，

    建議你嘗試以下方案進行操作：

    打開控制臺>>系統>>進堦系統設定>>進階>>啓動及修復>>設定，

    寫入偵錯咨詢>>选择“小記憶體傾印（256KB）”，傾印檔案選擇默認，確定。

    完成後重新啟動您的電腦，使設定生效；再次出現這個問題，前往檔案C:\Windows\Minidump提取即可。

    我們將通過私人訊息聯繫您，請注意查收。

    此回答有幫助嗎？

    0 則留言
  3. 匿名
    2020-03-14T06:44:41+00:00

    IRQL_NOT_LESS_OR_EQUAL

    代表驅動程式問題。

    大多數是顯卡驅動程式，實際要看完整的記憶體傾印。

    此回答有幫助嗎？

    0 則留言
  4. TaoLi 120.6K 信譽點數 獨立顧問
    2020-03-14T02:52:18+00:00

    您好，

    您提供的信息比較有限，這邊無法定位到藍屏位置所在，建議您將藍屏檔上傳至國內的任意網盤。

    此回答有幫助嗎？

    0 則留言