目前已讓win11跳過更新AMD驅動,但您給的連結無法使用
以下為最後遇到的代碼
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010923-11000-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 Personal
Machine Name:
Kernel base = 0xfffff802`60200000 PsLoadedModuleList = 0xfffff802`60e12fc0
Debug session time: Mon Jan 9 12:01:34.332 2023 (UTC + 8:00)
System Uptime: 0 days 0:00:29.155
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`60628700 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa887`fd6a6520=000000000000001e
14: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80262eea391, The address that the exception occurred at
Arg3: ffffc082f36d26a0, Parameter 0 of the exception
Arg4: fffff802604e1df0, Parameter 1 of the exception
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3421
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 11067
Key : Analysis.IO.Other.Mb
Value: 4
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 7
Key : Analysis.Init.CPU.mSec
Value: 249
Key : Analysis.Init.Elapsed.mSec
Value: 37679
Key : Analysis.Memory.CommitPeak.Mb
Value: 106
Key : Bugcheck.Code.DumpHeader
Value: 0x1e
Key : Bugcheck.Code.Register
Value: 0x1e
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: 010923-11000-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc000001d
BUGCHECK_P2: fffff80262eea391
BUGCHECK_P3: ffffc082f36d26a0
BUGCHECK_P4: fffff802604e1df0
EXCEPTION_PARAMETER1: ffffc082f36d26a0
EXCEPTION_PARAMETER2: fffff802604e1df0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: SearchIndexer.
TRAP_FRAME: ffffa887fd6a73d9 -- (.trap 0xffffa887fd6a73d9)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=f0ffffa887fd6a74 rbp=a0ffff80050e4da1
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
00000000`00000000 ?? ???
Resetting default scope
IP_IN_FREE_BLOCK: 0
FAILED_INSTRUCTION_ADDRESS:
Ntfs!NtfsUpdateFileTimestampsFromNonpagedFcb+31
fffff802`62eea391 f0a807 lock test al,7
STACK_TEXT:
ffffa887`fd6a6518 fffff802`6041055b : 00000000`0000001e ffffffff`c000001d fffff802`62eea391 ffffc082`f36d26a0 : nt!KeBugCheckEx
ffffa887`fd6a6520 fffff802`6063defc : ffff8005`00000000 00000000`00000002 ffffa887`fd6a73d9 00000000`00000000 : nt!KiDispatchException+0x7eb
ffffa887`fd6a6c00 fffff802`6063742d : fffff802`60200000 ffff8005`1a5d09b0 ffff8005`06402140 00000000`00000000 : nt!KiExceptionDispatch+0x13c
ffffa887`fd6a6de0 fffff802`62eea391 : ffff8005`1b6c45a0 00000000`00000000 ffff8005`00000000 fffff802`62eea2dd : nt!KiInvalidOpcodeFault+0x32d
ffffa887`fd6a6f70 ffff8005`1b6c45a0 : 00000000`00000000 ffff8005`00000000 fffff802`62eea2dd ffffa887`fd6a74d0 : Ntfs!NtfsUpdateFileTimestampsFromNonpagedFcb+0x31
ffffa887`fd6a6f78 00000000`00000000 : ffff8005`00000000 fffff802`62eea2dd ffffa887`fd6a74d0 00300033`00490024 : 0xffff8005`1b6c45a0
SYMBOL_NAME: Ntfs!NtfsUpdateFileTimestampsFromNonpagedFcb+31
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
IMAGE_VERSION: 10.0.22621.1028
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 31
FAILURE_BUCKET_ID: 0x1E_C000001D_BAD_IP_Ntfs!NtfsUpdateFileTimestampsFromNonpagedFcb
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {d80fde7b-0aa2-9cb4-fcd7-8888b5bec444}
Followup: MachineOwner
---------