環境：

Win10 專業版

DELL7080

問題描述：

WIN10開機突然，過一會就自動重啟藍屏DRIVER_IRQL_NOT_LESS_OR_EQUAL
事件日志

解決方案：

1.找到MEMORY.DMP文件內容，分析一下

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [E:\MEMORY\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`27a00000 PsLoadedModuleList = 0xfffff803`2862a250
Debug session time: Fri Jul 12 09:00:07.774 2024 (UTC + 8:00)
System Uptime: 0 days 0:05:14.661
Loading Kernel Symbols
...............................................................
..........................Page 46a880 not present in the dump file. Type ".hh dbgerr004" for details
......................................
................................................................
........
Loading User SymbolsLoading unloaded module list
........
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000060, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8033e0d8304, address which referenced memoryDebugging Details:
------------------KEY_VALUES_STRING: 1PROCESSES_ANALYSIS: 1SERVICE_ANALYSIS: 1STACKHASH_ANALYSIS: 1TIMELINE_ANALYSIS: 1DUMP_CLASS: 1DUMP_QUALIFIER: 401BUILD_VERSION_STRING:  19041.1.amd64fre.vb_release.191206-1406SYSTEM_MANUFACTURER:  Dell Inc.SYSTEM_PRODUCT_NAME:  OptiPlex 7080SYSTEM_SKU:  09A4BIOS_VENDOR:  Dell Inc.BIOS_VERSION:  1.6.0BIOS_DATE:  09/29/2021BASEBOARD_MANUFACTURER:  Dell Inc.BASEBOARD_PRODUCT:  0J37VMBASEBOARD_VERSION:  A01DUMP_TYPE:  1BUGCHECK_P1: 60BUGCHECK_P2: 2BUGCHECK_P3: 0BUGCHECK_P4: fffff8033e0d8304READ_ADDRESS:  0000000000000060 CURRENT_IRQL:  2FAULTING_IP: 
rtwlanu+48304
fffff803`3e0d8304 488b5260        mov     rdx,qword ptr [rdx+60h]CPU_COUNT: 10CPU_MHZ: b58CPU_VENDOR:  GenuineIntelCPU_FAMILY: 6CPU_MODEL: a5CPU_STEPPING: 5CPU_MICROCODE: 6,a5,5,0 (F,M,S,R)  SIG: EC'00000000 (cache) EC'00000000 (init)BLACKBOXBSD: 1 (!blackboxbsd)BLACKBOXNTFS: 1 (!blackboxntfs)BLACKBOXPNP: 1 (!blackboxpnp)BLACKBOXWINLOGON: 1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  SystemANALYSIS_SESSION_HOST:  ST-LANALYSIS_SESSION_TIME:  07-12-2024 09:41:32.0623ANALYSIS_VERSION: 10.0.18362.1 amd64freTRAP_FRAME:  fffff8032695a980 -- (.trap 0xfffff8032695a980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9f87137ad000 rbx=0000000000000000 rcx=ffff9f8715000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8033e0d8304 rsp=fffff8032695ab10 rbp=0000000000000000r8=ffff9f8715000000  r9=0000000000000000 r10=fffff803266a0ac0
r11=6924020181af0100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
rtwlanu+0x48304:
fffff803`3e0d8304 488b5260        mov     rdx,qword ptr [rdx+60h] ds:00000000`00000060=????????????????
Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff80327def929 to fffff80327ddda20STACK_TEXT:  
fffff803`2695a838 fffff803`27def929 : 00000000`0000000a 00000000`00000060 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff803`2695a840 fffff803`27debc29 : 00000000`00000000 00000000`00000001 ffff9f87`1382f1b0 ffff9f87`1382f1b0 : nt!KiBugCheckDispatch+0x69
fffff803`2695a980 fffff803`3e0d8304 : 00000000`00000000 00000000`00000000 00000000`c0000001 ffff9f87`15000000 : nt!KiPageFault+0x469
fffff803`2695ab10 fffff803`3e0d07f0 : ffff9f87`1501bc58 ffff9f87`1501bc58 00000000`00000000 00000000`00000000 : rtwlanu+0x48304
fffff803`2695ab40 fffff803`3e0d08a8 : 00000000`00000000 ffff9f87`1501bc58 00000000`00000000 ffff9f87`15000000 : rtwlanu+0x407f0
fffff803`2695abb0 fffff803`3e179b3a : ffff9f87`15000000 fffff803`2695ad00 fffff803`3e64d000 ffff9f87`1501bc58 : rtwlanu+0x408a8
fffff803`2695ac00 fffff803`3e179250 : ffff9f87`15029958 fffff803`3e505585 ffff9f87`1501bc58 ffff9f87`15000000 : rtwlanu+0xe9b3a
fffff803`2695af00 fffff803`3e35761a : ffff9f87`15000000 ffff9f87`14150002 ffff9f87`19acf0e6 ffff9f87`15000000 : rtwlanu+0xe9250
fffff803`2695af40 fffff803`3e357afd : ffff9f87`1501bc58 fffff803`2695afc0 ffff9f87`19acf0e8 fffff803`2c80d291 : rtwlanu+0x2c761a
fffff803`2695af80 fffff803`3e3574b9 : ffff9f87`15000000 ffff9f87`14150000 ffff9f87`14a8d980 00000000`0000008e : rtwlanu+0x2c7afd
fffff803`2695aff0 fffff803`3e356fd2 : ffff9f87`15000000 00000000`00000002 ffff9f87`13542ca0 ffff9f87`14a8d980 : rtwlanu+0x2c74b9
fffff803`2695b030 fffff803`3e0d6b27 : ffff9f87`1378e600 00000000`00000000 00000000`00000000 ffff9f87`137bd280 : rtwlanu+0x2c6fd2
fffff803`2695b080 fffff803`2c7a9249 : ffff9f87`1355d1a0 fffff803`00000000 00006078`d9270f00 ffff9f87`1378e630 : rtwlanu+0x46b27
fffff803`2695b110 fffff803`2c7ac7a4 : 00006078`ecaa2e58 ffff9f87`1355d1a0 ffff9f87`1355d1a0 00000000`00000000 : Wdf01000!FxRequestBase::CompleteSubmitted+0xe9 [minkernel\wdf\framework\shared\core\fxrequestbase.cpp @ 530] 
fffff803`2695b1a0 fffff803`27d45d46 : ffff9f87`13866050 ffff9f87`1efc7002 ffff9f87`1efc7060 00000000`00000000 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0xe4 [minkernel\wdf\framework\shared\targets\general\fxiotarget.cpp @ 2448] 
fffff803`2695b210 fffff803`27c3c7ce : ffff9f87`1efc7060 fffff803`2695b2c9 00000000`00000000 ffff9f87`1efc7493 : nt!IopUnloadSafeCompletion+0x56
fffff803`2695b240 fffff803`27c3c697 : 00000000`00000001 00000000`00000000 ffff9f87`137cc810 00000000`00000002 : nt!IopfCompleteRequest+0x11e
fffff803`2695b330 fffff803`2c7a811a : 00000000`00000000 ffff9f87`13033d30 ffff9f87`1efc7060 fffff803`2695b410 : nt!IofCompleteRequest+0x17
fffff803`2695b360 fffff803`2c7a5bbf : ffff9f87`24ad9b02 fffff803`27d20424 ffff9f87`1efc7060 00000000`00000000 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869] 
fffff803`2695b3f0 fffff803`2e980eed : 00000000`ffffff02 ffff9f87`24ad9a30 ffff9f87`137ccbf0 ffff9f87`137ccbf0 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436] 
fffff803`2695b450 fffff803`2e980db1 : ffff9f87`24ad9bd0 00000000`000000e6 ffff9f87`24ad9c60 fffff803`2695b668 : USBXHCI!Bulk_Transfer_CompleteCancelable+0xc9
fffff803`2695b4b0 fffff803`2e980ba0 : 00000000`00000004 fffff803`2695b620 00000000`00000000 ffff9f87`137e5090 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x1fd
fffff803`2695b560 fffff803`2e9788c1 : 00000000`00000004 fffff803`2695b638 00000000`00000008 fffff803`2695b640 : USBXHCI!Bulk_EP_TransferEventHandler+0x10
fffff803`2695b590 fffff803`2e9783f5 : 00000000`00000780 00006078`ece3a400 ffff9f87`131f12c0 ffff9f87`13714320 : USBXHCI!Endpoint_TransferEventHandler+0xb1
fffff803`2695b5f0 fffff803`2e9780cc : 00000000`00000002 00000000`00000000 00006078`eceb9308 00000000`00000001 : USBXHCI!Interrupter_DeferredWorkProcessor+0x315
fffff803`2695b6f0 fffff803`2c7a38f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
fffff803`2695b720 fffff803`27c3a69e : fffff803`266a0240 00000000`00000000 fffff803`2695ba20 00000000`00000000 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0xa6 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 410] 
fffff803`2695b760 fffff803`27c39984 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffff803`2695b8d0 fffff803`27de158e : 00000000`00000000 fffff803`2669d180 fffff803`28726600 ffff9f87`25f58640 : nt!KiRetireDpcList+0x1f4
fffff803`2695bb60 00000000`00000000 : fffff803`2695c000 fffff803`26955000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9eTHREAD_SHA1_HASH_MOD_FUNC:  735f1254286616ef1fc93f2fd2669b7149224dbbTHREAD_SHA1_HASH_MOD_FUNC_OFFSET:  20a47503875ea33d762e7925974100116e8849ceTHREAD_SHA1_HASH_MOD:  c42ed4c6ff47989179e03a072fb3ecc42c29e9ebFOLLOWUP_IP: 
rtwlanu+48304
fffff803`3e0d8304 488b5260        mov     rdx,qword ptr [rdx+60h]FAULT_INSTR_CODE:  60528b48SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  rtwlanu+48304FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: rtwlanuIMAGE_NAME:  rtwlanu.sysDEBUG_FLR_IMAGE_TIMESTAMP:  6107c19eSTACK_COMMAND:  .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET:  48304FAILURE_BUCKET_ID:  AV_rtwlanu!unknown_functionBUCKET_ID:  AV_rtwlanu!unknown_functionPRIMARY_PROBLEM_CLASS:  AV_rtwlanu!unknown_functionTARGET_TIME:  2024-07-12T01:00:07.000ZOSBUILD:  19041OSSERVICEPACK:  0SERVICEPACK_NUMBER: 0OS_REVISION: 0SUITE_MASK:  272PRODUCT_TYPE:  1OSPLATFORM_TYPE:  x64OSNAME:  Windows 10OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTSOS_LOCALE:  USER_LCID:  0OSBUILD_TIMESTAMP:  unknown_dateBUILDDATESTAMP_STR:  191206-1406BUILDLAB_STR:  vb_releaseBUILDOSVER_STR:  10.0.19041.1.amd64fre.vb_release.191206-1406ANALYSIS_SESSION_ELAPSED_TIME:  b1edANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:av_rtwlanu!unknown_functionFAILURE_ID_HASH:  {ba94ae44-1665-76da-0bc4-d0359d32d7d0}Followup:     MachineOwner
---------0: kd> 
0: kd> 
0: kd> 
0: kd> 
0: kd> 
0: kd> 

2.根據您提供的藍屏轉儲（crash dump）文件分析結果，這次操作系統崩潰（藍屏）是由 DRIVER_IRQL_NOT_LESS_OR_EQUAL 錯誤引起的。這個錯誤表明在過高的中斷請求級別（IRQL）下嘗試訪問了一個分頁（或完全無效的）地址。這種情況通常是由于驅動程序使用了不當的地址。

這里是一些關鍵信息的解讀：

錯誤代碼：DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
錯誤參數：Arg1：0000000000000060，嘗試訪問的內存地址。Arg2：0000000000000002，IRQL 級別。Arg3：0000000000000000，操作類型（0 表示讀操作，1 表示寫操作）。Arg4：fffff8033e0d8304，引用內存的地址。
故障指令地址：rtwlanu+48304，這表明錯誤發生在 rtwlanu.sys 驅動的某個位置。
當前中斷級別：2，表示當前操作在較高的 IRQL 下發生。
訪問的地址：0000000000000060，這通常不是一個有效的地址。

3.rtwlanu.sys 是什么？

rtwlanu.sys 是一個與無線網絡適配器相關的系統文件，通常是 Realtek 無線網卡驅動程序的一部分。這個文件作為驅動程序在 Windows 操作系統中運行，負責管理無線網絡連接和通信。
為什么 rtwlanu.sys 很重要：

硬件兼容性：它確保您的 Realtek 無線網卡與操作系統兼容，并能夠正常工作。
網絡連接：驅動程序管理無線網絡的連接和斷開，以及數據的發送和接收。
性能優化：它可能包含對無線網卡性能的優化，以確保網絡速度和穩定性。

問題和解決方案：

如果 rtwlanu.sys 文件出現問題，比如文件損壞、版本過舊或者不兼容，可能會導致無線網絡連接問題，甚至系統崩潰（藍屏錯誤）。解決這類問題的一些常見步驟包括：

更新驅動程序：通過設備管理器或硬件制造商的官方網站下載并安裝最新的驅動程序版本。
檢查硬件：確保無線網卡沒有物理損壞，并且正確安裝在計算機上。
系統更新：確保操作系統是最新的，因為 Windows 更新有時會包含對驅動程序的改進和修復。
故障排除：運行硬件故障排除工具，檢查是否有任何沖突或問題。
系統還原：如果問題始于最近的系統更改，您可以嘗試使用系統還原功能回退到之前的狀態。

4.本案例直接更新無線網卡驅動解決