遇到个很奇怪的事情,电脑开机自启项太多和1秒内打开4/5个软件会掉驱动
本帖最后由 ahrenschan 于 2025-7-21 13:51 编辑但是3dmark和甜甜圈和打游戏却又没有问题.驱动是最新和3个月前的都有这个问题
minidump分析结果上是VIDEO_TDR_FAILURE (116) 电脑格式化重装好几次了,并且显卡和内存放在老电脑上就没这个事情,问了下ai,ai说可能是电源和我的hdmi和dp线有问题.大家有没有遇到过类似的情况?下面是minidump分析信息
nt!KeBugCheckEx:
fffff806`a35005d0 48894c2408 mov qword ptr ,rcx ss:0018:ffffc783`de6d7220=0000000000000116
8: kd> !analyze -v
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
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffb603deb31010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80681f86af0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
KEY_VALUES_STRING: 1
Key: Analysis.CPU.mSec
Value: 1625
Key: Analysis.Elapsed.mSec
Value: 10202
Key: Analysis.IO.Other.Mb
Value: 0
Key: Analysis.IO.Read.Mb
Value: 1
Key: Analysis.IO.Write.Mb
Value: 0
Key: Analysis.Init.CPU.mSec
Value: 515
Key: Analysis.Init.Elapsed.mSec
Value: 15259
Key: Analysis.Memory.CommitPeak.Mb
Value: 114
Key: Analysis.Version.DbgEng
Value: 10.0.27829.1001
Key: Analysis.Version.Description
Value: 10.2503.24.01 amd64fre
Key: Analysis.Version.Ext
Value: 1.2503.24.1
Key: Bugcheck.Code.LegacyAPI
Value: 0x116
Key: Bugcheck.Code.TargetModel
Value: 0x116
Key: Dump.Attributes.AsUlong
Value: 0x21808
Key: Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key: Dump.Attributes.ErrorCode
Value: 0x0
Key: Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key: Dump.Attributes.LastLine
Value: Dump completed successfully.
Key: Dump.Attributes.ProgressPercentage
Value: 0
Key: Failure.Bucket
Value: 0x116_IMAGE_nvlddmkm.sys
Key: Failure.Exception.IP.Address
Value: 0xfffff80681f86af0
Key: Failure.Exception.IP.Module
Value: nvlddmkm
Key: Failure.Exception.IP.Offset
Value: 0x1986af0
Key: Failure.Hash
Value: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Key: Hypervisor.Enlightenments.ValueHex
Value: 0x7497cf94
Key: Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key: Hypervisor.Flags.ApicEnlightened
Value: 1
Key: Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key: Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key: Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key: Hypervisor.Flags.CpuManager
Value: 1
Key: Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key: Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key: Hypervisor.Flags.Epf
Value: 0
Key: Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key: Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key: Hypervisor.Flags.MaxBankNumber
Value: 0
Key: Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key: Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key: Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key: Hypervisor.Flags.Phase0InitDone
Value: 1
Key: Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key: Hypervisor.Flags.RootScheduler
Value: 0
Key: Hypervisor.Flags.SynicAvailable
Value: 1
Key: Hypervisor.Flags.UseQpcBias
Value: 0
Key: Hypervisor.Flags.Value
Value: 38408431
Key: Hypervisor.Flags.ValueHex
Value: 0x24a10ef
Key: Hypervisor.Flags.VpAssistPage
Value: 1
Key: Hypervisor.Flags.VsmAvailable
Value: 1
Key: Hypervisor.RootFlags.AccessStats
Value: 1
Key: Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key: Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key: Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key: Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key: Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key: Hypervisor.RootFlags.IsHyperV
Value: 1
Key: Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key: Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key: Hypervisor.RootFlags.MceEnlightened
Value: 1
Key: Hypervisor.RootFlags.Nested
Value: 0
Key: Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key: Hypervisor.RootFlags.Value
Value: 1015
Key: Hypervisor.RootFlags.ValueHex
Value: 0x3f7
BUGCHECK_CODE:116
BUGCHECK_P1: ffffb603deb31010
BUGCHECK_P2: fffff80681f86af0
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
FILE_IN_CAB:071925-10390-01.dmp
TAG_NOT_DEFINED_202b:*** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump
FAULTING_THREAD:ffffb603d0c47040
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffb603deb31010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 0000000000000004
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT:1
PROCESS_NAME:System
STACK_TEXT:
ffffc783`de6d7218 fffff806`3509375d : 00000000`00000116 ffffb603`deb31010 fffff806`81f86af0 ffffffff`c000009a : nt!KeBugCheckEx
ffffc783`de6d7220 fffff806`35307be6 : fffff806`81f86af0 ffffb603`cb457050 00000000`00000004 ffffb603`deb31010 : dxgkrnl!TdrBugcheckOnTimeout+0x101
ffffc783`de6d7260 fffff806`350a24be : 00000000`00000000 00000000`00002000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x232
ffffc783`de6d7290 fffff806`350d9375 : ffffb603`00000100 00000000`00000000 ffffc783`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x59a
ffffc783`de6d7320 fffff806`350d94d2 : ffffb603`b8587f98 00000000`00000000 00000000`0042dc00 fffff806`a3fcfbc0 : dxgkrnl!TdrResetFromTimeout+0x15
ffffc783`de6d7350 fffff806`a323072c : ffffb603`d0c47040 ffffb603`b8702ae0 fffff806`a3a52400 ffffb603`b8702ae0 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
ffffc783`de6d7390 fffff806`a349e2da : ffffb603`d0c47040 ffffb603`d0c47040 fffff806`a3230140 ffffb603`b8702ae0 : nt!ExpWorkerThread+0x5ec
ffffc783`de6d7570 fffff806`a36a67e4 : ffffca00`94187180 ffffb603`d0c47040 fffff806`a349e280 1de90007`51b2e900 : nt!PspSystemThreadStartup+0x5a
ffffc783`de6d75c0 00000000`00000000 : ffffc783`de6d8000 ffffc783`de6d1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME:nvlddmkm+1986af0
MODULE_NAME: nvlddmkm
IMAGE_NAME:nvlddmkm.sys
STACK_COMMAND: .process /r /p 0xffffb603b85a5040; .thread 0xffffb603d0c47040 ; kb
FAILURE_BUCKET_ID:0x116_IMAGE_nvlddmkm.sys
OSPLATFORM_TYPE:x64
OSNAME:Windows 10
FAILURE_ID_HASH:{c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
--------- 找个盘装最新版本win11，在硬件不变的情况下对比一下还会不会出现这个蓝屏 PPXG 发表于 2025-7-21 14:05
找个盘装最新版本win11，在硬件不变的情况下对比一下还会不会出现这个蓝屏 ...
我每次重装系统都是格式化c盘重装的,倒是没有搞过换个ssd这种方法,主要我硬件(显卡/内存/ssd)平移到老电脑上就没事,不会出这种情况.ai说他觉得是电源的锅,这周借一下同事的电源和ssd试试看去 本帖最后由 ahrenschan 于 2025-7-21 15:19 编辑
PPXG 发表于 2025-7-21 14:05
找个盘装最新版本win11，在硬件不变的情况下对比一下还会不会出现这个蓝屏 ...
忘记说了,我新电脑使用蓝牙耳机(在我的笔记本/我妹笔记本/老电脑上测试都没有电音)和别人开会议时还会有电音,听说都有电音(频率不高).我冲浪时咨询网友说有可能是电源干扰导致的. 感觉是本身不稳定导致的，在某些场景就触发不稳定了。 PPXG 发表于 2025-7-21 14:05
找个盘装最新版本win11，在硬件不变的情况下对比一下还会不会出现这个蓝屏 ...
最后发现是显卡吊装导致的,太沉了把主板压的受不了了,卧式放法就没事.把锅从内存,主板,电源甩了一圈发现是这个原因... panzerlied 发表于 2025-7-21 16:38
感觉是本身不稳定导致的，在某些场景就触发不稳定了。
最后发现是显卡吊装导致的,太沉了把主板压的受不了了,卧式放法就没事.把锅从内存,主板,电源甩了一圈发现是这个原因...
页:
[1]