回复：电脑蓝屏分析开贴，有回复必回

救救孩子

楼主大大，帮忙看下，偶尔开机才有，开机进去之后都不会蓝屏

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\XWCDFB-29\Desktop\Minidump(2)\Minidump\111023-9500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707
Machine Name:
Kernel base = 0xfffff800`0425f000 PsLoadedModuleList = 0xfffff800`04498c90
Debug session time: Fri Nov 10 16:10:07.181 2023 (UTC + 8:00)
System Uptime: 0 days 0:53:08.055
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: fffffa86c1c04e00, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff800042d2f60, address which referenced memory
Debugging Details:
------------------
GetUlongPtrFromAddress: unable to read from fffff800044fc300
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707
SYSTEM_MANUFACTURER: To be filled by O.E.M.
SYSTEM_PRODUCT_NAME: To be filled by O.E.M.
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: To be filled by O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 4.6.5
BIOS_DATE: 08/16/2022
BASEBOARD_MANUFACTURER: INTEL Corporation
BASEBOARD_PRODUCT: ChiefRiver
BASEBOARD_VERSION: To be filled by O.E.M.
DUMP_TYPE: 2
BUGCHECK_P1: fffffa86c1c04e00
BUGCHECK_P2: 2
BUGCHECK_P3: 1
BUGCHECK_P4: fffff800042d2f60
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800044fc100
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800044fc2f0
GetUlongPtrFromAddress: unable to read from fffff800044fc4a8
GetPointerFromAddress: unable to read from fffff800044fc0d8
fffffa86c1c04e00 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiReplenishPageSlist+c0
fffff800`042d2f60 f00fba6b1000 lock bts dword ptr [rbx+10h],0
CPU_COUNT: 4
CPU_MHZ: 9c0
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3a
CPU_STEPPING: 9
CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 17'00000000 (cache) 17'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: XKÕ(MemTest64
ANALYSIS_SESSION_HOST: DESKTOP-D8KMGFE
ANALYSIS_SESSION_TIME: 11-15-2023 10:21:05.0539
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
TRAP_FRAME: fffff880076ee7f0 -- (.trap 0xfffff880076ee7f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=000000003d441000
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800043f5545 rsp=fffff880076ee980 rbp=fffff880076eeb60
r8=fffff680001ea208 r9=000000003f80f000 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!NtLockVirtualMemory+0x305:
fffff800`043f5545 8b01 mov eax,dword ptr [rcx] ds:00000000`3d441000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800043012e9 to fffff800042f2ea0
STACK_TEXT:
fffff880`076ee248 fffff800`043012e9 : 00000000`0000000a fffffa86`c1c04e00 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`076ee250 fffff800`042ff0ce : 00000000`00000001 fffffa86`c1c04e00 fffff6fb`7dc00000 fffffa86`c1c04df0 : nt!KiBugCheckDispatch+0x69
fffff880`076ee390 fffff800`042d2f60 : fffff6fb`7dbedf70 fffff800`042d22f6 fffff880`076ee540 fffff800`04443180 : nt!KiPageFault+0x44e
fffff880`076ee520 fffff800`042d2e56 : fffffa80`065d0848 fffffa80`025be1f0 00000000`00000035 00000000`00000035 : nt!MiReplenishPageSlist+0xc0
fffff880`076ee590 fffff800`043ce020 : ffffffff`ffffffff 00000000`00000002 00000000`00000000 2aaaaaaa`aaaaaaab : nt!MiRemoveAnyPage+0x7d6
fffff880`076ee6a0 fffff800`042fefdc : 00000000`00000000 00000000`3d441000 00000000`00000000 ffffffff`ffffffff : nt!MmAccessFault+0x3990
fffff880`076ee7f0 fffff800`043f5545 : ffffffff`ffffffff fffff880`076eeb60 00000000`00000000 00000000`00000002 : nt!KiPageFault+0x35c
fffff880`076ee980 fffff800`04300f53 : fffffa80`09497b50 00000000`0210f590 00000000`0210f598 00000000`00000000 : nt!NtLockVirtualMemory+0x305
fffff880`076eeae0 00000000`7784a60a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0210f558 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7784a60a
THREAD_SHA1_HASH_MOD_FUNC: 053392fa361cd8cc2a4d5964cba88d33012f37d6
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6a2dc5043cd947f54ff48b8ca0c570c3700c7528
THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe
FOLLOWUP_IP:
nt!MiReplenishPageSlist+c0
fffff800`042d2f60 f00fba6b1000 lock bts dword ptr [rbx+10h],0
FAULT_INSTR_CODE: 6bba0ff0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiReplenishPageSlist+c0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5e0ead5e
IMAGE_VERSION: 6.1.7601.24545
STACK_COMMAND: .thread ; .cxr ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiReplenishPageSlist+c0
BUCKET_ID: X64_0xA_nt!MiReplenishPageSlist+c0
PRIMARY_PROBLEM_CLASS: X64_0xA_nt!MiReplenishPageSlist+c0
TARGET_TIME: 2023-11-10T08:10:07.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2020-01-03 10:56:30
BUILDDATESTAMP_STR: 200102-1707
BUILDLAB_STR: win7sp1_ldr_escrow
BUILDOSVER_STR: 6.1.7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707
ANALYSIS_SESSION_ELAPSED_TIME: 830
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xa_nt!mireplenishpageslist+c0
FAILURE_ID_HASH: {bfd4b47d-f7c1-0239-94a3-b05674fed1ca}
Followup: MachineOwner
---------

链接：https://pan.baidu.com/s/1dDqkd19WiuAYd_ZW_OADNw?pwd=k6xr
提取码：k6xr
麻烦帮忙看下

平常看的DUMP较多，还要做很多测试类报告，今天就恢复一个贴友的蓝屏故障，因为有完成的DUMP文件，就比较能直观的分析了，代码是SYSTEM_THREAD_EXCEPTION_NOT_HANDLED ，这种属于进程终止类故障，如下图：

把吧友的分析图片全放出来看下，如图：




我们先看图一，展示了大概的蓝屏类型，前面说了，属于进程崩溃类型 。
图二的话展示了蓝屏的终止点，我们一般看最后一个终止点。
图三输出为栈文件，里面频繁显示系统的NDIS组件异常，询问之后得知台式主机外接了一个USB的无线网卡，网卡为杂牌。
图四，输出关键原因，定位为无线网卡射频异常。
结果，很明显就是这个杂牌的无线网卡有问题，要么不适用这个win11系统，要么是质量问题，优先建议更换为intel PCI无线网卡，不会发生类似情况。

私信发不了联系，直接TB搜店铺大米饭的phy发DUMP 给我客服就行了。平常确实比较忙一点，文件全的都能看一看，尽量用windbg给我截图，如果需要进一步需要文件请直接联系我就行了，我看到就会提取DUMP文件分析了。

无论是因为软件系统问题蓝屏，还是硬件系统蓝屏，软件问题的定位是百分之百的概率，硬件系统定位有时候需要借助辅助工具定位，必要的时候还要线下工具测试，但是分析过文件的基本上能知道问题所在，不会盲目胡乱操作。出现蓝屏后，一定要引起重视，视而不见，多次之后，可能出现损坏硬件的情况。蓝屏其实就是计算机为了保护电脑而发出的警告，提示你计算机现在已经开始变得很危险了，必须赶紧解决了，跟你汽车仪表盘上报故障灯一样的效果。

nt文件系统驱动程序，这个怎么解决啊