电脑异常蓝屏

sty123456 · ‎2022-12-20

电脑经常性蓝屏，时间不一定，有时候开几个小时也没事，有时候开机几分钟就蓝屏，报的错多种多样，不过基本上报错的程序都是ntkrnlmp.exe或者ntoskrnl.exe，网上查了一下蓝屏代码基本上都说是驱动问题。然后在驱动程序验证中选中如下图npsvctrig.sys和ntoskrnl.exe两个，再任意选一个其他的驱动，重启必蓝屏，报错代码：SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M ，报错驱动：npsvctrig.sys，单选中这两个东西重启不会蓝屏，在别的正常电脑上这样操作不会蓝屏。系统已经重置过了问题依旧。

关于必蓝屏的windbg分析如下

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


Loading Dump File [C:\Windows\Minidump\122022-15906-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Machine Name:
Kernel base = 0xfffff807`72008000 PsLoadedModuleList = 0xfffff807`72c1aff0
Debug session time: Tue Dec 20 21:22:21.138 2022 (UTC + 8:00)
System Uptime: 0 days 0:00:10.235
Loading Kernel Symbols
...............................................................
..........................................
Loading User Symbols
Loading unloaded module list
..
For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff807`72430700 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff509`12004ec0=000000000000007e
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff8077243a728, The address that the exception occurred at
Arg3: fffff50912005f28, Exception Record Address
Arg4: fffff50912005740, Context Record Address

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2077

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 10917

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x1000007e

    Key  : Bugcheck.Code.Register
    Value: 0x7e

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Timestamp
    Value: 2022-05-06T12:50:00Z

    Key  : WER.OS.Version
    Value: 10.0.22621.1


FILE_IN_CAB:  122022-15906-01.dmp

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffff80000003

BUGCHECK_P2: fffff8077243a728

BUGCHECK_P3: fffff50912005f28

BUGCHECK_P4: fffff50912005740

EXCEPTION_RECORD:  fffff50912005f28 -- (.exr 0xfffff50912005f28)ExceptionAddress: fffff8077243a728 (nt!DebugPromptAfterInt3)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000002

CONTEXT:  fffff50912005740 -- (.cxr 0xfffff50912005740)rax=0000000000000002 rbx=00000000000000a0 rcx=fffff807718f4300
rdx=fffff5091200001f rsi=fffff807718fc010 rdi=000000000000002f
rip=fffff8077243a727 rsp=fffff50912006168 rbp=fffff509120062c0
 r8=fffff509120061f0  r9=0000000000000002 r10=fffff8077259d820
r11=0000000000000000 r12=ffff8007875767c4 r13=fffff50912006640
r14=fffff50912006500 r15=ffff80078a9c4b80
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040246
nt!DebugPrompt+0x17:
fffff807`7243a727 cc              int     3
Resetting default scope

BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0x80000003 - {    }

EXCEPTION_CODE_STR:  80000003

EXCEPTION_PARAMETER1:  0000000000000002

EXCEPTION_STR:  0x80000003

STACK_TEXT:  
fffff509`12006168 fffff807`7259d864     : 00000000`000000a0 fffff807`718fc010 00000000`0000002f fffff807`718ec5c7 : nt!DebugPrompt+0x17
fffff509`12006170 fffff807`7192ea48     : 00000000`000000a0 fffff807`718fc010 fffff807`718f42fc 00000000`00000007 : nt!DbgPrompt+0x44
fffff509`120061c0 fffff807`718ec485     : 00000000`00000050 ffff8007`8a9f2cb0 ffff8007`8a9c6ff0 00000000`0000000d : FLTMGR!FltpvPrintErrors+0x16c
fffff509`12006440 fffff807`719353a8     : 00000000`0000000d 00000000`00000000 00000000`00000000 fffff509`120064d0 : FLTMGR!FltpvValidateVerifierState+0x85
fffff509`12006470 fffff807`7190b6db     : ffff8007`8a9fad10 00000000`00000000 00000000`00000000 00000000`00000001 : FLTMGR!FltvInstanceSetup+0x38
fffff509`120064d0 fffff807`7190c420     : 00000000`00000000 ffff8007`8a9f2cb0 ffff8007`875767c4 ffff8007`8a9fad10 : FLTMGR!FltpDoInstanceSetupNotification+0x7b
fffff509`12006540 fffff807`7190ba94     : 00000000`00000000 00000053`00450043 ffff8007`00000001 fffff509`12006640 : FLTMGR!FltpInitInstance+0x490
fffff509`120065e0 fffff807`7190b853     : 00000000`00000000 ffff8007`87576790 ffff8007`875767a0 00000000`00000018 : FLTMGR!FltpCreateInstanceFromName+0x1e0
fffff509`120066c0 fffff807`7191b87d     : 00000000`00000022 ffff8007`875767a0 ffff8007`8606e948 ffffffff`800001a8 : FLTMGR!FltpEnumerateRegistryInstances+0xe3
fffff509`12006750 fffff807`7191b75b     : 00000000`00000000 fffff509`12006839 00000000`00000001 ffffffff`800001b4 : FLTMGR!FltpDoVolumeNotificationForNewFilter+0xa5
fffff509`12006790 fffff803`7124c29d     : 00000000`00000000 00000000`00000001 ffff8007`8a99eff8 00000000`00000000 : FLTMGR!FltStartFiltering+0x2b
fffff509`120067d0 fffff803`7124c030     : ffff8007`881c0000 ffff8007`881c0000 ffff8007`88e42fad ffff8007`8aa40e60 : npsvctrig!DriverEntry+0x21d
fffff509`120068a0 fffff807`727ead2c     : ffff8007`881c0000 00000000`00000000 ffff8007`8aa40e60 fffff807`723412c0 : npsvctrig!GsDriverEntry+0x20
fffff509`120068d0 fffff807`7272fb37     : ffff8007`881c0000 00000000`00000000 00000000`00000000 ffffdd8b`a4288fd0 : nt!PnpCallDriverEntry+0x54
fffff509`12006920 fffff807`72b4fbb3     : ffff8007`88bbafc0 ffff8007`88bbafc0 fffff509`12006b50 00000000`00000000 : nt!IopLoadDriver+0x523
fffff509`12006ae0 fffff807`72b57b82     : fffff807`00000000 ffffdd8b`a5fc2fd0 00000000`00000000 fffff807`6bc4bd00 : nt!IopInitializeSystemDrivers+0x157
fffff509`12006b80 fffff807`728379eb     : fffff807`728379b0 fffff807`72c65a54 fffff807`728379b0 fffff807`6bc4bd00 : nt!IoInitSystem+0x2e
fffff509`12006bb0 fffff807`723109b7     : ffff8007`7bd3e300 fffff807`728379b0 fffff807`6bc4bd00 01010101`01010101 : nt!Phase1Initialization+0x3b
fffff509`12006bf0 fffff807`72435664     : fffff807`6bfb5180 ffff8007`7bd3e300 fffff807`72310960 01010101`01010101 : nt!PspSystemThreadStartup+0x57
fffff509`12006c40 00000000`00000000     : fffff509`12007000 fffff509`12001000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  npsvctrig!DriverEntry+21d

MODULE_NAME: npsvctrig

IMAGE_NAME:  npsvctrig.sys

IMAGE_VERSION:  10.0.22621.898

STACK_COMMAND:  .cxr 0xfffff50912005740 ; kb

BUCKET_ID_FUNC_OFFSET:  21d

FAILURE_BUCKET_ID:  0x7E_80000003_VRFK_npsvctrig!DriverEntry

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5333e2cf-eb68-bea9-e990-1d7da5156b00}

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

还有一个附加问题，就是bios无法通过官网下载的更新程序刷入，打开官网安装包，跑完一个安装包的解压以后，无法启动bios更新程序，不管是自动启动还是手动点击这个更新程序，但是在任务管理器进程中这个更新程序会出现一两分钟，然后自动消失。现在要更新bios只能通过在别的电脑上创建升级U盘，然后进bios固件管理手动升级，不知道和这个经常性的异常蓝屏是否有关。

y2kim · ‎2022-12-21

Windows 10 频繁重启——文件系统筛选器“npsvctrig” - Microsoft Community

HP 电脑 - 蓝屏上显示错误消息 (Windows 10) | HP®客户支持

蓝屏错误疑难解答

https://www.windows.com/stopcode

Bug 检查代码参考 - Windows drivers | Microsoft Learn

欢迎来到社区，我是一名志愿者，私人信息不会被回复。
如果我的回复对您有帮助， 请点击按钮。如果我的回复帮助您解决了问题，别忘了点击，可以帮到其他遇到同样问题的用户。

微信服务 | 惠普官网 (hp.com)

惠普服务中心查询 | HP®客户支持

我长期使用过的机型
DC7600 USDT
Pavilion dv4000
ProBook 6510b
xw4600
z800
z820
EliteBook 2740p
ProBook 6460b
Pavilion DV4
Envy 15
SlateBook x2
ProDesk 600 G3 SFF
t5740 Thin Client
t620 Thin Client
EliteBook 840 G3
ZBook 15 G3
ProBook 440 G8
Omen 25L GT12 AMD

sty123456 · ‎2022-12-21

上述的方法都试过，没用。然后刚刚又蓝屏了。

Loading Dump File [C:\Windows\Minidump\122122-19390-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Machine Name:
Kernel base = 0xfffff806`2d600000 PsLoadedModuleList = 0xfffff806`2e212ff0
Debug session time: Wed Dec 21 12:57:46.680 2022 (UTC + 8:00)
System Uptime: 0 days 1:22:01.508
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff806`2da28700 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffd281`d2d22dd0=000000000000000a
2: 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: 00007fffffff0000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000060, 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: fffff8062da4a96f, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2125

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 11135

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xa

    Key  : Bugcheck.Code.Register
    Value: 0xa

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Timestamp
    Value: 2022-05-06T12:50:00Z

    Key  : WER.OS.Version
    Value: 10.0.22621.1


FILE_IN_CAB:  122122-19390-01.dmp

BUGCHECK_CODE:  a

BUGCHECK_P1: 7fffffff0000

BUGCHECK_P2: ff

BUGCHECK_P3: 60

BUGCHECK_P4: fffff8062da4a96f

READ_ADDRESS: fffff8062e31c468: 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
 00007fffffff0000 

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  lw.exe

TRAP_FRAME:  ffffd281d2d22f10 -- (.trap 0xffffd281d2d22f10)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=00007fffffff0000 rbx=0000000000000000 rcx=00007fffffff0000
rdx=ffffd281d2d23258 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8062da4a96f rsp=ffffd281d2d230a0 rbp=ffffd281d2d236c0
 r8=0000000000000000  r9=0000000000000000 r10=ffffd281d2d231c0
r11=fffff8062e212ff0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na po nc
nt!RtlpxVirtualUnwind+0x23c90f:
fffff806`2da4a96f 0fb600          movzx   eax,byte ptr [rax] ds:00007fff`ffff0000=??
Resetting default scope

STACK_TEXT:  
ffffd281`d2d22dc8 fffff806`2da3dda9     : 00000000`0000000a 00007fff`ffff0000 00000000`000000ff 00000000`00000060 : nt!KeBugCheckEx
ffffd281`d2d22dd0 fffff806`2da39434     : 00000000`00000000 fffff806`2d6b4978 ffffd281`d2d231c0 ffff958a`3c2bc2e8 : nt!KiBugCheckDispatch+0x69
ffffd281`d2d22f10 fffff806`2da4a96f     : fffff806`00000000 fffff806`2da335bd 00000000`00000000 fffff806`2da4b7ea : nt!KiPageFault+0x474
ffffd281`d2d230a0 fffff806`2d80c135     : ffff958a`3bc682b8 ffff958a`3bc68078 00000000`00000000 00000000`00000000 : nt!RtlpxVirtualUnwind+0x23c90f
ffffd281`d2d23160 fffff806`2d810087     : ffffffff`ffffffff ffff958a`3bc68120 ffff958a`3bc68120 ffffd281`d2d23900 : nt!RtlDispatchException+0x215
ffffd281`d2d238d0 fffff806`2da298c2     : 004005b9`0b75c985 48cc0001`32eae880 0fc08545`0975f685 018b4900`00009e85 : nt!KiDispatchException+0x317
ffffd281`d2d23fb0 fffff806`2da29890     : fffff806`2da3def5 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffff958a`3bc67f38 fffff806`2da3def5     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
ffff958a`3bc67f40 fffff806`2da3742d     : 00000000`00000000 00000000`0000ffff ffffd281`d3391180 ffff830b`1ffb70c0 : nt!KiExceptionDispatch+0x135
ffff958a`3bc68120 fffff806`2da335bd     : fffff806`2d948fde 00000048`1e11d000 00000000`00000004 ffffd281`00000000 : nt!KiInvalidOpcodeFault+0x32d
ffff958a`3bc682b8 00000000`00000000     : 00000000`00000000 ffffd281`00000000 00000007`00000000 00000000`00000001 : nt!NtCallEnclave+0x1d


SYMBOL_NAME:  nt!RtlpxVirtualUnwind+23c90f

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1037

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  23c90f

FAILURE_BUCKET_ID:  AV_nt!RtlpxVirtualUnwind

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {90caf8d4-a034-a257-3599-d8f696fd9681}

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

y2kim · ‎2022-12-21

看看这个lw.exe是什么？

欢迎来到社区，我是一名志愿者，私人信息不会被回复。
如果我的回复对您有帮助， 请点击按钮。如果我的回复帮助您解决了问题，别忘了点击，可以帮到其他遇到同样问题的用户。

微信服务 | 惠普官网 (hp.com)

惠普服务中心查询 | HP®客户支持

我长期使用过的机型
DC7600 USDT
Pavilion dv4000
ProBook 6510b
xw4600
z800
z820
EliteBook 2740p
ProBook 6460b
Pavilion DV4
Envy 15
SlateBook x2
ProDesk 600 G3 SFF
t5740 Thin Client
t620 Thin Client
EliteBook 840 G3
ZBook 15 G3
ProBook 440 G8
Omen 25L GT12 AMD