以下为蓝屏日志，请求帮助分析 ———————————————————————————————————————————————————————————————————————————————————————————— Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\lipen\Desktop\081422-6890-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 19041 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff804`6c600000 PsLoadedModuleList = 0xfffff804`6d22a250 Debug session time: Sun Aug 14 17:11:49.771 2022 (UTC 8:00) System Uptime: 0 days 0:17:21.513 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!KeBugCheckEx: fffff804`6c9f88c0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffb108`0ba1f7e0=000000000000010d 7: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WDF_VIOLATION (10d) The Kernel-Mode Driver Framework was notified that Windows detected an error in a framework-based driver. In general, the dump file will yield additional information about the driver that caused this BugCheck. Arguments: Arg1: 000000000000000d, A power IRP was received for the device but the IRP was not requested by the device (the power policy owner). Possibly there are multiple power policy owners. Only one driver in the stack can be the power policy owner. A KMDF driver can change power policy ownership by calling the DDI WdfDeviceInitSetPowerPolicyOwnership. Arg2: ffffd20538d03280, Device object pointer. Arg3: ffffd205420d67e0, Power IRP. Arg4: ffffd2053913bd60, Reserved. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2031 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2037 Key : Analysis.Init.CPU.mSec Value: 421 Key : Analysis.Init.Elapsed.mSec Value: 83431 Key : Analysis.Memory.CommitPeak.Mb Value: 105 Key : Bugcheck.Code.DumpHeader Value: 0x10d Key : Bugcheck.Code.Register Value: 0x10d Key : Dump.Attributes.AsUlong Value: 8 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 FILE_IN_CAB: 081422-6890-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 10d BUGCHECK_P1: d BUGCHECK_P2: ffffd20538d03280 BUGCHECK_P3: ffffd205420d67e0 BUGCHECK_P4: ffffd2053913bd60 DEVICE_OBJECT: ffffd20538d03280 IRP_ADDRESS: ffffd205420d67e0 DRIVER_OBJECT: ffffd20539140dd0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffb108`0ba1f7d8 fffff804`715f8920 : 00000000`0000010d 00000000`0000000d ffffd205`38d03280 ffffd205`420d67e0 : nt!KeBugCheckEx ffffb108`0ba1f7e0 fffff804`715c1842 : ffffd205`392db8b0 00000000`00000016 ffffd205`392f2c00 ffffb108`0ba1f910 : Wdf01000!FxVerifierBugCheckWorker 0x24 [minkernel\wdf\framework\shared\object\fxverifierbugcheck.cpp @ 68] ffffb108`0ba1f820 fffff804`715b10b5 : ffffd205`392db8b0 ffffb108`0ba1f8e8 00000000`00000004 00000000`00000000 : Wdf01000!FxPkgFdo::DispatchDeviceSetPower 0x10782 [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 324] ffffb108`0ba1f870 fffff804`715acc60 : ffffd205`392db8b0 ffffd205`392f2c00 00000000`00000001 00000000`00000000 : Wdf01000!FxPkgFdo::_DispatchSetPower 0x25 [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 120] ffffb108`0ba1f8a0 fffff804`715aa867 : ffffd205`420d67e0 00000000`00000000 ffffd205`420d67e0 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch 0xb0 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 765] ffffb108`0ba1f910 fffff804`6c99666f : 00000000`00000000 00000000`00000000 ffffb108`0ba5ff00 ffffd205`420d67e0 : Wdf01000!FxDevice::DispatchWithLock 0x157 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447] ffffb108`0ba1f970 fffff804`6c8abadd : 00000000`00000000 00000000`00000000 ffffd205`391c01a0 ffffd205`420d67e0 : nt!IopPoHandleIrp 0x3b ffffb108`0ba1f9a0 fffff804`6c9988f9 : ffffb108`0ba5ff00 00000000`00000002 ffffb108`0ba1fa20 ffffb108`0ba1faf0 : nt!IofCallDriver 0x6d ffffb108`0ba1f9e0 fffff804`a4c94ae3 : 00000000`00000000 fffff804`a4c98ef0 00000000`00000000 ffffd205`391ca44c : nt!IoCallDriver 0x9 ffffb108`0ba1fa10 00000000`00000000 : fffff804`a4c98ef0 00000000`00000000 ffffd205`391ca44c ffffd205`420d67e0 : libusb0 0x4ae3 SYMBOL_NAME: libusb0 4ae3 MODULE_NAME: libusb0 IMAGE_NAME: libusb0.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 4ae3 FAILURE_BUCKET_ID: 0x10D_d_libusb0!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {1031989d-5ebe-078d-fd42-fbdbd1710e3c} Followup: MachineOwner ---------
欢迎咨询本站！。请问是否插入了某些usb设备后出现的异常？或者正在运行某些需要访问usb设备的程序？建议拔掉usb上的键盘鼠标以外的设备，然后执行一下干净启动，排除其他干扰：https://support.microsoft.com/zh-cn/help/929135.先卸载设备中全部的第三方反病毒软件与系统优化软件(例如360、联想电脑管家、360桌面、腾讯电脑管家、腾讯桌面、鲁大师，代理，加速器，虚拟机等)。然后鼠标右键单击开始菜单→运行（RUN）→输入：msconfig（按下Enter键）点击上面的“服务”勾选下面的“隐藏所有Microsoft服务”（请务必勾选）点击“全部禁用”。然后鼠标右键单击开始菜单→任务管理器，（点击底部“详细信息”），点击顶部”启动”，鼠标右键单击“状态”显示为“已启动”的项，选择“禁用”。（禁用所有启动项。）然后鼠标右键单击开始按钮（图标的按钮）→"WindowsPowerShell(I)（管理员)(A）”→输入：（WIndows11中可能显示Windows终端（管理员））sfc/SCANNOW（按下Enter键）Dism/Online/Cleanup-Image/ScanHealth（按下Enter键）Dism/Online/Cleanup-Image/CheckHealth（按下Enter键）DISM/Online/Cleanup-image/RestoreHealth（按下Enter键）完成后重启电脑，再次输入：sfc/SCANNOW（按下Enter键）看下是否恢复正常。
