蓝屏档解读如下,机器是AMD的 Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Evanliu\Desktop\14JK\961 s4\011423-9875-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 = 0xfffff804`70a00000 PsLoadedModuleList = 0xfffff804`71613450 Debug session time: Fri Jan 13 17:41:22.574 2023 (UTC 8:00) System Uptime: 0 days 0:49:23.291 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........... Loading User Symbols Loading unloaded module list ............................................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff804`70e1d050 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:fffffb02`86c5f770=000000000000009f 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time Arg2: ffffe68fdd3dd780, Physical Device Object of the stack Arg3: fffffb0286c5f7b8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffe68fe066c010, The blocked IRP Debugging Details: ------------------ Implicit thread is now ffffe68f`e0768040 KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 703 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 55044 Key : Analysis.IO.Other.Mb Value: 12 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 32 Key : Analysis.Init.CPU.mSec Value: 171 Key : Analysis.Init.Elapsed.mSec Value: 81997 Key : Analysis.Memory.CommitPeak.Mb Value: 114 Key : Bugcheck.Code.DumpHeader Value: 0x9f Key : Bugcheck.Code.Register Value: 0x9f 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: 011423-9875-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b BUGCHECK_CODE: 9f BUGCHECK_P1: 3 BUGCHECK_P2: ffffe68fdd3dd780 BUGCHECK_P3: fffffb0286c5f7b8 BUGCHECK_P4: ffffe68fe066c010 DRVPOWERSTATE_SUBCODE: 3 FAULTING_THREAD: ffffe68fe0768040 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffffb02`8a147080 fffff804`70c8d7a5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapContext 0x76 fffffb02`8a1471c0 fffff804`70c8ebc7 : 00000000`00000008 00000000`00000000 ffffe68f`09b409e8 00000000`00000000 : nt!KiSwapThread 0xa65 fffffb02`8a147310 fffff804`70c90eb6 : 00000000`00000000 00000000`00000001 ffffe68f`00000000 00000000`00000000 : nt!KiCommitThreadWait 0x137 fffffb02`8a1473c0 fffff804`75dba081 : 00000003`5459407e 00000000`00000103 00000000`fd010101 ffffe68f`e06211a0 : nt!KeWaitForSingleObject 0x256 fffffb02`8a147760 fffff804`75cb8e2d : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : ndis!ndisWaitForKernelObject 0x21 fffffb02`8a1477a0 fffff804`75d31dc0 : ffffe68f`e0621100 00000000`00000000 00000003`5459407e ffffe68f`e06211a0 : ndis!ndisQuerySetMiniportEx 0x1bd fffffb02`8a147830 fffff804`75cfe4e4 : ffffe68f`e066a280 ffffe68f`e066a280 ffffe68f`e066c010 ffffe68f`e06211a0 : ndis!ndisQuerySetMiniportDeviceState 0x140 fffffb02`8a1479e0 fffff804`75cc5d67 : 00000000`00000000 ffffe68f`e06211a0 ffffe68f`e066c518 ffffe68f`e066c518 : ndis!ndisSetDevicePower 0x382dc fffffb02`8a147a50 fffff804`75cc5c0e : ffffe68f`e066c010 ffffe68f`e04f5e10 ffffe68f`e066c518 ffffe68f`e06211a0 : ndis!ndisSetPower 0x9f fffffb02`8a147ab0 fffff804`70dcad31 : ffffe68f`e0768040 fffffb02`8a147b90 ffffe68f`e03c0a00 ffffe68f`e0621050 : ndis!ndisPowerDispatch 0x11e fffffb02`8a147b10 fffff804`70cc31e7 : ffffffff`fa0a1f00 fffff804`70dcaad0 ffffe68f`e8d48350 00000000`0000008c : nt!PopIrpWorker 0x261 fffffb02`8a147bb0 fffff804`70e21174 : ffffb280`a7957180 ffffe68f`e0768040 fffff804`70cc3190 00000000`00000246 : nt!PspSystemThreadStartup 0x57 fffffb02`8a147c00 00000000`00000000 : fffffb02`8a148000 fffffb02`8a141000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread 0x34 SYMBOL_NAME: ndis!ndisWaitForKernelObject 21 MODULE_NAME: ndis IMAGE_NAME: ndis.sys IMAGE_VERSION: 10.0.22621.900 STACK_COMMAND: .process /r /p 0xffffe68fd4ac3040; .thread 0xffffe68fe0768040 ; kb BUCKET_ID_FUNC_OFFSET: 21 FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_ndis!ndisWaitForKernelObject OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {72c8f05e-7820-a1d9-f367-64bcbf47c096} Followup: MachineOwner --------- 2: kd> lmvm ndis Browse full module list start end module name fffff804`75cb0000 fffff804`75e3e000 ndis # (pdb symbols) C:\ProgramData\Dbg\sym\ndis.pdb\D840164B1C63ABF9943E6A6CAB78575B1\ndis.pdb Loaded symbol image file: ndis.sys Mapped memory image file: C:\ProgramData\Dbg\sym\ndis.sys\FA02E33918e000\ndis.sys Image path: \SystemRoot\system32\drivers\ndis.sys Image name: ndis.sys Browse all global symbols functions data Image was built with /Brepro flag. Timestamp: FA02E339 (This is a reproducible build file hash, not a timestamp) CheckSum: 0019212F ImageSize: 0018E000 File version: 10.0.22621.900 Product version: 10.0.22621.900 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.6 Driver File date: 00000000.00000000 Translations: 0409.04b0 Information from resource tables: CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: NDIS.SYS OriginalFilename: NDIS.SYS ProductVersion: 10.0.22621.900 FileVersion: 10.0.22621.900 (WinBuild.160101.0800) FileDescription: Network Driver Interface Specification (NDIS) LegalCopyright: © Microsoft Corporation. All rights reserved.

您好,欢迎询问本站感谢您的反馈,根据您提供得信息,您遇到的蓝屏报错是DRIVER_POWER_STATE_FAILURE这个报错信息通常是在启动某个硬件出现问题时出现。另外从报错日志中发现出错的模块是ndis.sys。这个模块是网络设备的驱动模块。这个报错指向了您的网络设备。结合这两个特征,您的问题可能出在网卡和主板上,您可以通过到主板厂商的官网,更新您的主板驱动和网卡驱动,如果您有安装虚拟网卡类的设备的话,可以暂时移除,看看是否能缓解您的问题。


您电脑的型号是什么呢??可以到您电脑制造商的官网,下载所有最新版本的驱动更新一下。(蓝牙 芯片组 网卡 声卡 显卡 BIOS)(建议不要使用第三方软件更新驱动)如果您不了解您电脑的型号,您可按查找》输入“系统信息”(SystemInformation)》在主页的SystemSummary(系统摘要)下,截图或拍张照片上传上来吗??(以方便我帮您查找您电脑制造商的最新驱动下载链接,然后发那链接给您。)


点赞(95) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部