WARNING: Unable to verify timestamp for rt640x64.sys

LU LIU 20 信誉分
2024-10-28T04:02:07.3533333+00:00

我的机器莫名其妙最近总蓝屏,求助各位大神帮忙看下具体原因。以下是分析情况:

************* Preparing the environment for Debugger Extensions Gallery repositories **************

ExtensionRepository : Implicit

UseExperimentalFeatureForNugetShare : true

AllowNugetExeUpdate : true

NonInteractiveNuget : true

AllowNugetMSCredentialProviderInstall : true

AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : false

-- Configuring repositories

  ----> Repository : LocalInstalled, Enabled: true

  ----> Repository : UserExtensions, Enabled: true

Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.047 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.312 seconds

----> Repository : UserExtensions, Enabled: true, Packages count: 0

----> Repository : LocalInstalled, Enabled: true, Packages count: 29

Microsoft (R) Windows Debugger Version 10.0.26100.1742 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\102724-28078-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 20348 MP (12 procs) Free x64

Product: Server, suite: TerminalServer DataCenter SingleUserTS

Edition build lab: 20348.859.amd64fre.fe_release_svc_prod2.220707-1832

Kernel base = 0xfffff80510400000 PsLoadedModuleList = 0xfffff80511033990

Debug session time: Sun Oct 27 03:59:22.737 2024 (UTC + 8:00)

System Uptime: 1 days 19:13:57.607

Loading Kernel Symbols

...............................................................

................................................................

..........................................

Loading User Symbols

Loading unloaded module list

.............

For analysis of this file, run !analyze -v

4: 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: fffff8051516d6cd, The address that the exception occurred at

Arg3: 0000000000000000, Parameter 0 of the exception

Arg4: fffff805106abfc0, Parameter 1 of the exception

Debugging Details:


*** WARNING: Unable to verify timestamp for rt640x64.sys




*** 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 ***






*** 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: 12718

Key  : Analysis.Elapsed.mSec

Value: 49251

Key  : Analysis.IO.Other.Mb

Value: 24

Key  : Analysis.IO.Read.Mb

Value: 19

Key  : Analysis.IO.Write.Mb

Value: 33

Key  : Analysis.Init.CPU.mSec

Value: 3890

Key  : Analysis.Init.Elapsed.mSec

Value: 46085

Key  : Analysis.Memory.CommitPeak.Mb

Value: 118

Key  : Bugcheck.Code.KiBugCheckData

Value: 0x1e

Key  : Bugcheck.Code.LegacyAPI

Value: 0x1e

Key  : Failure.Bucket

Value: 0x1E_C000001D_BAD_IP_rt640x64!unknown_function

Key  : Failure.Hash

Value: {ed4779dd-e6df-3cbc-a6d1-f91749c0bf90}

Key  : WER.OS.Branch

Value: fe_release_svc_prod2

Key  : WER.OS.Version

Value: 10.0.20348.859

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff8051516d6cd

BUGCHECK_P3: 0

BUGCHECK_P4: fffff805106abfc0

FILE_IN_CAB: 102724-28078-01.dmp

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: fffff805106abfc0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

FAILED_INSTRUCTION_ADDRESS:

Wdf01000!imp_WdfTimerStart+3d [minkernel\wdf\framework\shared\core\fxtimerapi.cpp @ 242]

fffff805`1516d6cd 48 ???

STACK_TEXT:

ffff97015a9f1108 fffff80510940066 : 000000000000001e ffffffffc000001d fffff8051516d6cd 0000000000000000 : nt!KeBugCheckEx

ffff97015a9f1110 fffff8051082b3bf : 0000000000000000 0000000000000000 0000000000000000 ffff97015a9f16f0 : nt!HvlpVtlCallExceptionHandler+0x22

ffff97015a9f1150 fffff8051063ae41 : ffff97015a9f16f0 fffff80510824cae 0000000000000000 0000000000000000 : nt!RtlpExecuteHandlerForException+0xf

ffff97015a9f1180 fffff8051063f444 : fffff0871025ede0 ffff97015a9f1e00 fffff0871025ede0 00001b3c00001b3b : nt!RtlDispatchException+0x301

ffff97015a9f18d0 fffff80510820ef2 : 00001cee00001ced 00001cf000001cef 00001cf200001cf1 00001cf400001cf3 : nt!KiDispatchException+0x304

ffff97015a9f1fb0 fffff80510820ec0 : fffff80510835847 0000000000000000 0000000000000000 0000000000000000 : nt!KxExceptionDispatchOnExceptionStack+0x12

fffff0871025ebf8 fffff80510835847 : 0000000000000000 0000000000000000 0000000000000000 fffff0871025ee24 : nt!KiExceptionDispatchOnExceptionStackContinue

fffff0871025ec00 fffff8051082edda : 0000000000000000 fffff80510661020 000008a5ce466067 ffff59257eb1284c : nt!KiExceptionDispatch+0x107

fffff0871025ede0 fffff8051516d6cd : ffff830b1f4789a0 ffff830b1f4d3ca0 ffff830b1f63a000 ffff830b1d037401 : nt!KiInvalidOpcodeFault+0x31a

fffff0871025ef70 fffff80537030da0 : 0000000000000000 ffff830b1d037370 0000000000000000 0000000000000000 : Wdf01000!imp_WdfTimerStart+0x3d [minkernel\wdf\framework\shared\core\fxtimerapi.cpp @ 242]

fffff0871025efb0 0000000000000000 : ffff830b1d037370 0000000000000000 0000000000000000 0000000000000000 : rt640x64+0x30da0

SYMBOL_NAME: rt640x64+30da0

MODULE_NAME: rt640x64

IMAGE_NAME: rt640x64.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 30da0

FAILURE_BUCKET_ID: 0x1E_C000001D_BAD_IP_rt640x64!unknown_function

OS_VERSION: 10.0.20348.859

BUILDLAB_STR: fe_release_svc_prod2

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ed4779dd-e6df-3cbc-a6d1-f91749c0bf90}

Followup: MachineOwner


Windows 商业版 | 面向 IT 专业人士的 Windows 客户端 | 用户体验 | 其他
0 个注释 无注释
{count} 票

接受的答案
  1. Wesley Li 11,285 信誉分
    2024-10-28T08:06:13.42+00:00

    您好,

    从分析情况来看是系统模块 rt640x64 出现问题,而 rt640x64.sys 文件与 Realtek RTL8136 系列以太网驱动程序相关。您可以尝试更新 Realtek 驱动程序或者运行系统文件检查 (SFC) 扫描并修复系统以解决此问题。

    1 个人认为此答案很有帮助。

0 个其他答案

排序依据: 非常有帮助

你的答案

问题作者可以将答案标记为“接受的答案”,这有助于用户了解已解决作者问题的答案。