大佬们，win10拯救者笔记本蓝屏怎么解决

Maomaozhen 2023-06-11 19:31:21

蓝屏文件代码：

Loading Dump File [C:\WINDOWS\Minidump\061123-19859-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 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`2de00000 PsLoadedModuleList = 0xfffff800`2ea29b20
Debug session time: Sun Jun 11 19:00:18.407 2023 (UTC + 8:00)
System Uptime: 0 days 8:42:28.149
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!CmpDoParseKey+0x62d:
fffff800`2e4e6f6d 84c0 test al,al
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffce00a8f51e50
Arg3: 00000000d116af10
Arg4: fffff8002e4e6f6d

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1780

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 4650

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

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

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

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x1000007f

Key : Bugcheck.Code.Register
Value: 0x7f

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

FILE_IN_CAB: 061123-19859-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BUGCHECK_CODE: 7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffce00a8f51e50

BUGCHECK_P3: d116af10

BUGCHECK_P4: fffff8002e4e6f6d

BAD_STACK_POINTER: 00000000d116af10

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: RuntimeBroker.

STACK_TEXT:
00000000`d116af10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpDoParseKey+0x62d

SYMBOL_NAME: nt!CmpDoParseKey+62d

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22000.1936

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 62d

FAILURE_BUCKET_ID: 0x7f_8_STACKPTR_ERROR_nt!CmpDoParseKey

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {14b9b198-e1f2-e3e4-e5d6-6e9ed5120b89}

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

6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************