0x0000008E watchdog.exe 问题

最新推荐文章于 2020-06-26 11:14:12 发布
原创 最新推荐文章于 2020-06-26 11:14:12 发布 · 1.2k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#dell #ie

作者遇到新安装IE8浏览器后电脑频繁死机并出现蓝屏的问题，通过安装驱动人生确认显卡驱动为最新版本，但观看优酷视频时仍出现蓝屏现象。在重新下载并安装官方显卡驱动后，问题得以解决。作者正在继续观察以确保问题完全解决。

 新装IE8 ，浏览几个网页死机，出现如下提示：

 

我也安装了驱动人生，它提示我已经安装最新的显卡驱动，但是一看优酷，电脑就像上面这样蓝屏，到DELL官方网站重新下载一下显卡驱动，重新安装，重启。看了几部视频， 没有发生蓝屏现象。

观察中

 

Android WatchDog（1）- 启动流程（Android 12）
weixin_41678668的博客
12-14 2224
SystemServer启动时会启动WatchDog并进行初始化，如下： private void startBootstrapServices(@NonNull TimingsTraceAndSlog t) { t.traceBegin("startBootstrapServices"); // Start the watchdog as early as possible so we can crash the system server //
龙芯3A5000在银河麒麟上的“watchdog: BUG: soft lockup ”问题
qq_15895713的博客
11-28 947
龙芯3A5000. 麒麟kylin softlockup
android 开机启动流程分析（03）init启动中关键进程 uevent & watchdog
wangdsh的博客
05-22 2088
系列文章解读&说明： Android开机启动流程的分析主要分为以下部分： android 开机启动流程分析（01） init之前启动说明 android 开机启动流程分析（02）init的启动流程分析 android 开机启动流程分析（03）init启动中关键进程 uevent & watchdog android 开机启动流程分析（04）init启动中关键服务-属性服务...
winload.exe
08-10
win7、win8、win10，在C盘找到widows/system32/system32\winload.efi，
Win10数字签名错误/winload.exe 错误解决办法
小飞飞的专栏
12-23 4万+
装win10或者升级win10的时候总会出现数字签名错误和找不到winload.exe，我觉得这2个错误是差不多的，接下来看我的解决过程吧！
Win7纯净版系统Windows未能启动,文件Winload.exe的解决方法
能看代码的CrackLibby
09-19 3万+
http://www.xitonghe.com/jiaocheng/windows7-1649.html 在win7纯净版系统安装后或使用过程中我们可能会遇上开机故障，而Windows 未能启动 就是一个很常见的故障，通常下面会标注出现问题的文件：文件:\windows\system32\winload.exe 错误0xc000000f 等信息，这又该如何解决
************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.000 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 44 Microsoft (R) Windows Debugger Version 10.0.27829.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\071525-14000-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 26100 MP (32 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xfffff803`85000000 PsLoadedModuleList = 0xfffff803`85ef4420 Debug session time: Tue Jul 15 17:28:19.638 2025 (UTC + 8:00) System Uptime: 0 days 0:17:31.281 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................................ Loading User Symbols Loading unloaded module list ............................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803`85487cc0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc881`cabadb10=0000000000000101 8: kd> !analyze -v Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................................ Loading User Symbols Loading unloaded module list ............................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000006, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: ffffc881ca7a4180, The PRCB address of the hung processor. Arg4: 0000000000000002, The index of the hung processor. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1796 Key : Analysis.Elapsed.mSec Value: 10236 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 23 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 359 Key : Analysis.Init.Elapsed.mSec Value: 11295 Key : Analysis.Memory.CommitPeak.Mb Value: 103 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: 0x101 Key : Bugcheck.Code.TargetModel Value: 0x101 Key : Dump.Attributes.AsUlong Value: 0x21008 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: CLOCK_WATCHDOG_TIMEOUT_nt!KeAccumulateTicks Key : Failure.Hash Value: {f9e2f3e5-5717-d66f-239c-7b2e10a43f9e} Key : Stack.Pointer Value: ISR BUGCHECK_CODE: 101 BUGCHECK_P1: 6 BUGCHECK_P2: 0 BUGCHECK_P3: ffffc881ca7a4180 BUGCHECK_P4: 2 FILE_IN_CAB: 071525-14000-01.dmp DUMP_FILE_ATTRIBUTES: 0x21008 Kernel Generated Triage Dump FAULTING_THREAD: ffff9a8ea34b5040 FAULTING_PROCESSOR: 2 PROCESS_NAME: System BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 STACK_TEXT: ffffc881`cabadb08 fffff803`852d6b0f : 00000000`00000101 00000000`00000006 00000000`00000000 ffffc881`ca7a4180 : nt!KeBugCheckEx ffffc881`cabadb10 fffff803`852f3e48 : 00000000`00000000 ffffc881`cab9a700 ffffc881`cab91180 ffffc881`cab91180 : nt!KeAccumulateTicks+0x6bf ffffc881`cabadb80 fffff803`852f3a39 : 00000000`00000020 00000000`00000000 00000002`729cec98 fffff780`00000350 : nt!KiUpdateRunTime+0xa8 ffffc881`cabadbe0 fffff803`852f2eff : 00000000`00000000 00000000`00000000 00000000`0000000f ffffc881`cab9a860 : nt!KiUpdateTime+0x469 ffffc881`cabade40 fffff803`852f214f : fffff803`85f8da48 ffff9a8e`77798c40 00000000`00000000 ffffc881`cab91180 : nt!KeClockInterruptNotify+0x18f ffffc881`cabadf50 fffff803`8565d6ae : 00000269`20bd783f ffff9a8e`77798c40 00000002`72e3330e 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x2df ffffc881`cabadfb0 fffff803`8565debc : 00000002`72e31f6a ffff8485`843b6c20 00000002`72e31f74 00000262`f85b278e : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e ffff8485`843b6ba0 fffff803`852491c2 : 00000000`00000002 00000000`00000001 ffffc881`cab91180 00000000`00000001 : nt!KiInterruptDispatchNoLockNoEtw+0x3c ffff8485`843b6d30 fffff803`85248e95 : ffff9a8e`77824180 ffff8485`843b6e60 ffff9a8e`77824190 fffff803`00000000 : nt!KiIpiWaitForRequestBarrier+0x32 ffff8485`843b6d60 fffff803`8528dd39 : 00000000`00001000 00000000`00000000 00000000`00000001 ffffaaed`40f2a1c0 : nt!MiFlushTbList+0x885 ffff8485`843b6f70 fffff803`8528d51b : ffffda81`e5438000 00000000`ea932801 0000001c`00000000 00000000`00000004 : nt!MmSetAddressRangeModifiedEx+0x4a9 ffff8485`843b7010 fffff803`85288773 : ffff9a8e`812135c0 00000000`00000000 ffff8485`843b7200 ffff8485`843b7300 : nt!CcFlushCacheOneRange+0x1ab ffff8485`843b7100 fffff803`85288ab4 : 00000000`00000000 ffff9a8e`8109a818 00000000`00000000 ffff9a8e`8109a6e0 : nt!CcWriteBehindAsync+0x127 ffff8485`843b7270 fffff803`852882d7 : ffff9a8e`8109a79c 00000000`00000000 ffff9a8e`8109a818 ffff9a8e`778a5720 : nt!CcAsyncLazywriteWorker+0x1e4 ffff8485`843b7360 fffff803`8527f6e9 : ffff9a8e`a34b5040 ffff8485`843b74c0 fffff803`85288260 ffff9a8e`81213bb0 : nt!CcAsyncLazywriteWorkerThread+0x77 ffff8485`843b73c0 fffff803`8541d24a : ffff9a8e`a34b5040 ffff9a8e`a34b5040 fffff803`8527f540 ffff9a8e`7773fb20 : nt!ExpWorkerThread+0x1a9 ffff8485`843b7570 fffff803`8565c664 : ffffc881`caa59180 ffff9a8e`a34b5040 fffff803`8541d1f0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a ffff8485`843b75c0 00000000`00000000 : ffff8485`843b8000 ffff8485`843b1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: nt!KeAccumulateTicks+6bf MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.26100.1 STACK_COMMAND: .process /r /p 0xffff9a8e776ee040; .thread 0xffff9a8ea34b5040 ; kb BUCKET_ID_FUNC_OFFSET: 6bf FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_nt!KeAccumulateTicks OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f9e2f3e5-5717-d66f-239c-7b2e10a43f9e} Followup: MachineOwner --------- 这个问题怎么解决
07-16
嗯，用户遇到了Windows蓝屏错误CLOCK_WATCHDOG_TIMEOUT（0x101），需要专业级的解决方案。这个错误属于硬件相关的严重系统崩溃，通常意味着处理器线程响应超时，可能涉及硬件故障、驱动不兼容或系统设置问题。 用户...
如果Windbg分析出了: ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.172 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 45 Microsoft (R) Windows Debugger Version 10.0.27871.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\090225-9687-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 22621 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xfffff803`42a00000 PsLoadedModuleList = 0xfffff803`436135f0 Debug session time: Tue Sep 2 18:20:51.790 2025 (UTC + 8:00) System Uptime: 0 days 18:36:53.009 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 PEB is paged out (Peb.Ldr = 00000000`009a4018). Type ".hh dbgerr001" for details Loading unloaded module list ................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803`42e1dfe0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff803`477649f0=0000000000000133 0: 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. -- User interrupt ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace. Arg2: 0000000000000501, The DPC time count (in ticks). Arg3: 0000000000000500, The DPC time allotment (in ticks). Arg4: fffff8034371d340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding this single DPC timeout Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1312 Key : Analysis.Elapsed.mSec Value: 2811 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 31 Key : Analysis.Init.CPU.mSec Value: 1312 Key : Analysis.Init.Elapsed.mSec Value: 210095 Key : Analysis.Memory.CommitPeak.Mb Value: 100 Key : Analysis.Version.DbgEng Value: 10.0.27871.1001 Key : Analysis.Version.Description Value: 10.2505.01.02 amd64fre Key : Analysis.Version.Ext Value: 1.2505.1.2 Key : Bugcheck.Code.LegacyAPI Value: 0x133 Key : Bugcheck.Code.TargetModel Value: 0x133 Key : Dump.Attributes.AsUlong Value: 0x1808 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: 0x133_DPC_nt!KeAccumulateTicks Key : Failure.Hash Value: {88dc98ce-f842-4daa-98d0-858621db6b0f} Key : Hypervisor.Enlightenments.ValueHex Value: 0x1417cf94 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: 0 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: 4722927 Key : Hypervisor.Flags.ValueHex Value: 0x4810ef 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 Key : Stack.Pointer Value: ISR BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff8034371d340 FILE_IN_CAB: 090225-9687-01.dmp DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump FAULTING_THREAD: ffffc90e0a554080 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: wpscloudsvr.ex STACK_TEXT: fffff803`477649e8 fffff803`42cc7dc5 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx fffff803`477649f0 fffff803`42cc7491 : 0000097d`ec0ff7a3 00000000`00417140 00000000`0041713f 00000000`00000000 : nt!KeAccumulateTicks+0x3d5 fffff803`47764a50 fffff803`42cc3bbf : 00000000`00000004 00000000`00001388 00000000`00417100 00000000`002701b7 : nt!KiUpdateRunTime+0xd1 fffff803`47764c00 fffff803`42cc47a8 : 00000000`00000000 ffffd981`2797be00 fffff803`3e467180 00000000`00000000 : nt!KiUpdateTime+0x63f fffff803`47764ea0 fffff803`42cc406a : fffff803`43660350 ffffd981`2797be70 ffffd981`2797be70 00000000`00000002 : nt!KeClockInterruptNotify+0x228 fffff803`47764f40 fffff803`42d2438c : 0000009c`08132ad1 fffff803`4370d830 fffff803`4370d8e0 fffff803`42e1ff8b : nt!HalpTimerClockInterrupt+0x10a fffff803`47764f70 fffff803`42e201ea : fffff803`4775cbd0 fffff803`4370d830 fffff803`4775cdf0 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c fffff803`47764fb0 fffff803`42e20ab7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff803`4775cb50 fffff803`42c3aee7 : fffff803`3e467180 fffff803`4775cdd0 00000000`00000001 fffff803`4775cdd0 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff803`4775cce0 fffff803`42c3ceed : fffff803`4374c040 00000000`00000000 fffff803`4374c040 00000000`00000000 : nt!KiDeferredReadySingleThread+0xc37 fffff803`4775d0b0 fffff803`42c3c6ab : fffff803`4629e900 fffff803`00000000 00000000`00000000 ffffffff`ffffffff : nt!KiExitDispatcher+0x19d fffff803`4775d460 fffff803`462777e0 : 00000000`00000001 fffff803`4775d5f0 ffffc90d`f29cd328 fffff803`462a03d0 : nt!KeSetEvent+0xeb fffff803`4775d4f0 00000000`00000001 : fffff803`4775d5f0 ffffc90d`f29cd328 fffff803`462a03d0 ffffc90e`105cc050 : 0xfffff803`462777e0 fffff803`4775d4f8 fffff803`4775d5f0 : ffffc90d`f29cd328 fffff803`462a03d0 ffffc90e`105cc050 fffff803`4628143d : 0x1 fffff803`4775d500 ffffc90d`f29cd328 : fffff803`462a03d0 ffffc90e`105cc050 fffff803`4628143d fffff803`42dc7c90 : 0xfffff803`4775d5f0 fffff803`4775d508 fffff803`462a03d0 : ffffc90e`105cc050 fffff803`4628143d fffff803`42dc7c90 fffff803`42cc31a8 : 0xffffc90d`f29cd328 fffff803`4775d510 ffffc90e`105cc050 : fffff803`4628143d fffff803`42dc7c90 fffff803`42cc31a8 00000000`00000000 : 0xfffff803`462a03d0 fffff803`4775d518 fffff803`4628143d : fffff803`42dc7c90 fffff803`42cc31a8 00000000`00000000 ffffc90e`105cc050 : 0xffffc90e`105cc050 fffff803`4775d520 fffff803`42dc7c8f : fffff803`42cc31a8 00000000`00000000 ffffc90e`105cc050 ffffc90d`f29e1dc0 : 0xfffff803`4628143d fffff803`4775d528 fffff803`42cc31a8 : 00000000`00000000 ffffc90e`105cc050 ffffc90d`f29e1dc0 00000000`00000000 : nt!HalpHvTimerArm+0x8f fffff803`4775d530 fffff803`42c529b7 : ffffffff`ffffff81 fffff803`4775d5f0 00000000`00000000 00000000`00000000 : nt!KeQueryPerformanceCounter+0x58 fffff803`4775d570 fffff803`46233519 : ffffc90d`f1a11068 00000000`00000002 00000000`00000002 fffff803`462350a3 : nt!KeCancelTimer+0x37 fffff803`4775d5a0 ffffc90d`f1a11068 : 00000000`00000002 00000000`00000002 fffff803`462350a3 00000007`00000000 : 0xfffff803`46233519 fffff803`4775d5a8 00000000`00000002 : 00000000`00000002 fffff803`462350a3 00000007`00000000 00000001`00000002 : 0xffffc90d`f1a11068 fffff803`4775d5b0 00000000`00000002 : fffff803`462350a3 00000007`00000000 00000001`00000002 fffff803`4775d5cc : 0x2 fffff803`4775d5b8 fffff803`462350a3 : 00000007`00000000 00000001`00000002 fffff803`4775d5cc 00000000`00000018 : 0x2 fffff803`4775d5c0 00000007`00000000 : 00000001`00000002 fffff803`4775d5cc 00000000`00000018 fffff803`4775d5e0 : 0xfffff803`462350a3 fffff803`4775d5c8 00000001`00000002 : fffff803`4775d5cc 00000000`00000018 fffff803`4775d5e0 fffff803`4775d5e0 : 0x00000007`00000000 fffff803`4775d5d0 fffff803`4775d5cc : 00000000`00000018 fffff803`4775d5e0 fffff803`4775d5e0 00000000`00000010 : 0x00000001`00000002 fffff803`4775d5d8 00000000`00000018 : fffff803`4775d5e0 fffff803`4775d5e0 00000000`00000010 00000000`00000000 : 0xfffff803`4775d5cc fffff803`4775d5e0 fffff803`4775d5e0 : fffff803`4775d5e0 00000000`00000010 00000000`00000000 00000000`00000000 : 0x18 fffff803`4775d5e8 fffff803`4775d5e0 : 00000000`00000010 00000000`00000000 00000000`00000000 00000000`0000000a : 0xfffff803`4775d5e0 fffff803`4775d5f0 00000000`00000010 : 00000000`00000000 00000000`00000000 00000000`0000000a ffffc90d`f1a11068 : 0xfffff803`4775d5e0 fffff803`4775d5f8 00000000`00000000 : 00000000`00000000 00000000`0000000a ffffc90d`f1a11068 ffffc90d`f1a11002 : 0x10 SYMBOL_NAME: nt!KeAccumulateTicks+3d5 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.5766 STACK_COMMAND: .process /r /p 0xffffc90e0ee450c0; .thread 0xffffc90e0a554080 ; kb BUCKET_ID_FUNC_OFFSET: 3d5 FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f} Followup: MachineOwner ---------
09-03
或者，直接重命名wpscloudsvr.exe文件（如改为wpscloudsvr.exe.bak）使其无法运行： - 定位到文件所在目录（通过任务管理器右键进程→打开文件所在位置）。 - 重命名该文件。 4. 重启电脑进入正常模式，检查蓝屏...
************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 46 Microsoft (R) Windows Debugger Version 10.0.29457.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\WH\Desktop\dmp\dmp\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff805`44200000 PsLoadedModuleList = 0xfffff805`44e2a270 Debug session time: Wed Oct 29 10:16:13.901 2025 (UTC + 8:00) System Uptime: 18 days 9:28:44.128 Loading Kernel Symbols ............................................................... ................................................................ ....................................................... Loading User Symbols Loading unloaded module list ............ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff805`445f71b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9100`e4cf9e90=00000000000001db 7: kd> !analyze -v Loading Kernel Symbols ............................................................... ................................................................ ....................................................... Loading User Symbols Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IPI_WATCHDOG_TIMEOUT (1db) A processor has been stuck in an IPI loop for more than the allowed time. Arguments: Arg1: 0000000000989680, indicates QPC frequency Arg2: 00000e7521e7d4d9, indicates the current QPC Arg3: 00000e746f1776d8, indicates the baseline QPC Arg4: 0000000000000000 Debugging Details: ------------------ Unable to load image \SystemRoot\System32\drivers\intelppm.sys, Win32 error 0n2 KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1250 Key : Analysis.Elapsed.mSec Value: 89737 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 20 Key : Analysis.Init.CPU.mSec Value: 484 Key : Analysis.Init.Elapsed.mSec Value: 228057 Key : Analysis.Memory.CommitPeak.Mb Value: 104 Key : Analysis.Version.DbgEng Value: 10.0.29457.1000 Key : Analysis.Version.Description Value: 10.2506.23.01 amd64fre Key : Analysis.Version.Ext Value: 1.2506.23.1 Key : Bugcheck.Code.KiBugCheckData Value: 0x1db Key : Bugcheck.Code.LegacyAPI Value: 0x1db Key : Bugcheck.Code.TargetModel Value: 0x1db Key : Failure.Bucket Value: 0x1DB_intelppm!C1Halt Key : Failure.Hash Value: {cacd6e12-d84e-f577-5f18-465580472b7e} Key : Hypervisor.Enlightenments.Value Value: 0 Key : Hypervisor.Enlightenments.ValueHex Value: 0x0 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 0 Key : Hypervisor.Flags.ApicEnlightened Value: 0 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 0 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 0 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 0 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 0 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: 0 Key : Hypervisor.Flags.Phase0InitDone Value: 0 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 0 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 131072 Key : Hypervisor.Flags.ValueHex Value: 0x20000 Key : Hypervisor.Flags.VpAssistPage Value: 0 Key : Hypervisor.Flags.VsmAvailable Value: 0 Key : Hypervisor.RootFlags.AccessStats Value: 0 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 0 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 0 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 0 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 0 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 0 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 0 Key : Hypervisor.RootFlags.MceEnlightened Value: 0 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 0 Key : Hypervisor.RootFlags.Value Value: 0 Key : Hypervisor.RootFlags.ValueHex Value: 0x0 Key : SecureKernel.HalpHvciEnabled Value: 0 Key : Stack.Pointer Value: ISR Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 Key : WER.System.BIOSRevision Value: 5.13.0.0 BUGCHECK_CODE: 1db BUGCHECK_P1: 989680 BUGCHECK_P2: e7521e7d4d9 BUGCHECK_P3: e746f1776d8 BUGCHECK_P4: 0 FILE_IN_CAB: MEMORY.DMP FAULTING_THREAD: ffff9100e4d4b340 PROCESS_NAME: System STACK_TEXT: ffff9100`e4cf9e88 fffff805`446a0489 : 00000000`000001db 00000000`00989680 00000e75`21e7d4d9 00000e74`6f1776d8 : nt!KeBugCheckEx ffff9100`e4cf9e90 fffff805`44526247 : 00000000`00000000 00000000`00000005 00000000`00000000 00000000`00989680 : nt!KiIpiGenericCallTarget+0xfe259 ffff9100`e4cf9ed0 fffff805`445fdea0 : 00000000`00000000 ffffcc0f`10c8f470 00000000`00000000 e983ca8b`00000125 : nt!KiIpiProcessRequests+0x297 ffff9100`e4cf9fb0 fffff805`445fdbb7 : 00000000`00000000 bd1ea1b3`8560aaf8 07c1db9d`37a83ff5 8719716f`96dac933 : nt!KiIpiInterruptSubDispatch+0x90 ffffcc0f`10c8f3f0 fffff805`489244a2 : fffff805`4892dcaa 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIpiInterrupt+0x307 ffffcc0f`10c8f588 fffff805`4892dcaa : 00000000`00000000 00000000`00000000 00000000`00000000 0000000c`00000000 : intelppm!C1Halt+0x2 ffffcc0f`10c8f590 fffff805`48921424 : 00000000`00000000 00120605`d22f8b16 00000000`00000000 00000000`00000002 : intelppm!C1Idle+0x1a ffffcc0f`10c8f5c0 fffff805`44418346 : 00000000`00093590 00000000`00000086 00000000`00000000 00000000`00000000 : intelppm!AcpiCStateIdleExecute+0x24 ffffcc0f`10c8f5f0 fffff805`44417104 : 00000000`00000000 00001f80`00000200 00000000`00000000 ffffcc0f`10c8fbc0 : nt!PpmIdleExecuteTransition+0x10c6 ffffcc0f`10c8f9f0 fffff805`445facd4 : ffffffff`00000000 ffff9100`e4d4b340 ffffd505`e59b6080 00000000`000005ef : nt!PoIdle+0x374 ffffcc0f`10c8fb60 00000000`00000000 : ffffcc0f`10c90000 ffffcc0f`10c89000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54 SYMBOL_NAME: intelppm!C1Halt+2 MODULE_NAME: intelppm IMAGE_NAME: intelppm.sys STACK_COMMAND: .process /r /p 0xfffff80544f24a00; .thread 0xffff9100e4d4b340 ; kb BUCKET_ID_FUNC_OFFSET: 2 FAILURE_BUCKET_ID: 0x1DB_intelppm!C1Halt OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {cacd6e12-d84e-f577-5f18-465580472b7e} Followup: MachineOwner ---------分析蓝屏原因
10-31
- **内存测试**：运行`mdsched.exe`进行内存诊断，排除多通道内存兼容性问题[^1]。 - **CPU温度监控**：使用工具（如HWMonitor）检查CPU温度，过高温度（>95℃）会导致降频或死锁。 - **电源检查**：更换电源或使用...
PS E:\work\ESP32S3\project\11_lvgl_9> $env:IDF_PATH = 'E:/Espressif/frameworks/esp-idf-v5.5/'; PS E:\work\ESP32S3\project\11_lvgl_9> & 'E:\Espressif\python_env\idf5.5_py3.11_env\Scripts\python.exe' 'E:\Espressif\frameworks\esp-idf-v5.5\tools\idf_monitor.py' -p COM3 -b 115200 --toolchain-prefix xtensa-esp32s3-elf- --make '''E:\Espressif\python_env\idf5.5_py3.11_env\Scripts\python.exe'' ''E:\Espressif\frameworks\esp-idf-v5.5\tools\idf.py''' --target esp32s3 'e:\work\ESP32S3\project\11_lvgl_9\build\app-template.elf' --- Warning: GDB cannot open serial ports accessed as COMx --- Using \\.\COM3 instead... --- esp-idf-monitor 1.7.0 on \\.\COM3 115200 --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ESP-ROM:esp32s3-20210327 Build:Mar 27 2021 rst:0x1 (POWERON),boot:0x2b (SPI_FAST_FLASH_BOOT) SPIWP:0xee mode:DIO, clock div:1 load:0x3fce2820,len:0x159c load:0x403c8700,len:0xd24 load:0x403cb700,len:0x2f48 entry 0x403c8924 I (24) boot: ESP-IDF v5.5 2nd stage bootloader I (25) boot: compile time Sep 30 2025 15:31:56 I (25) boot: Multicore bootloader I (25) boot: chip revision: v0.2 I (28) boot: efuse block revision: v1.3 I (31) boot.esp32s3: Boot SPI Speed : 80MHz I (35) boot.esp32s3: SPI Mode : DIO I (39) boot.esp32s3: SPI Flash Size : 2MB I (43) boot: Enabling RNG early entropy source... I (47) boot: Partition Table: I (50) boot: ## Label Usage Type ST Offset Length I (56) boot: 0 nvs WiFi data 01 02 00009000 00006000 I (62) boot: 1 phy_init RF data 01 01 0000f000 00001000 I (69) boot: 2 factory factory app 00 00 00010000 00100000 I (76) boot: End of partition table I (79) esp_image: segment 0: paddr=00010020 vaddr=3c050020 size=111f0h ( 70128) map I (99) esp_image: segment 1: paddr=00021218 vaddr=3fc95000 size=02cech ( 11500) load I (101) esp_image: segment 2: paddr=00023f0c vaddr=40374000 size=0c10ch ( 49420) load I (113) esp_image: segment 3: paddr=00030020 vaddr=42000020 size=45e94h (286356) map I (164) esp_image: segment 4: paddr=00075ebc vaddr=4038010c size=04df4h ( 19956) load I (169) esp_image: segment 5: paddr=0007acb8 vaddr=600fe000 size=00020h ( 32) load I (176) boot: Loaded app from partition at offset 0x10000 I (176) boot: Disabling RNG early entropy source... I (189) cpu_start: Multicore app I (199) cpu_start: Pro cpu start user code I (199) cpu_start: cpu freq: 160000000 Hz I (199) app_init: Application information: I (199) app_init: Project name: app-template I (203) app_init: App version: 1 I (206) app_init: Compile time: Sep 30 2025 14:52:18 I (211) app_init: ELF file SHA256: 956f6deb6... I (216) app_init: ESP-IDF: v5.5 I (219) efuse_init: Min chip rev: v0.0 I (223) efuse_init: Max chip rev: v0.99 I (227) efuse_init: Chip rev: v0.2 I (231) heap_init: Initializing. RAM available for dynamic allocation: I (237) heap_init: At 3FCA87F0 len 00040F20 (259 KiB): RAM I (243) heap_init: At 3FCE9710 len 00005724 (21 KiB): RAM I (248) heap_init: At 3FCF0000 len 00008000 (32 KiB): DRAM I (253) heap_init: At 600FE020 len 00001FC8 (7 KiB): RTCRAM I (259) spi_flash: detected chip: winbond I (262) spi_flash: flash io: dio W (265) spi_flash: Detected size(16384k) larger than the size in the binary image header(2048k). Using the size in the binary image header. I (277) sleep_gpio: Configure to isolate all GPIO pins in sleep state I (284) sleep_gpio: Enable automatic switching of GPIO sleep configuration I (290) main_task: Started on CPU0 I (310) main_task: Calling app_main() bus initialize successes! device config success E (5710) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time: E (5710) task_wdt: - IDLE0 (CPU 0) E (5710) task_wdt: Tasks currently running: E (5710) task_wdt: CPU 0: main E (5710) task_wdt: CPU 1: IDLE1 E (5710) task_wdt: Print CPU 0 (current core) backtrace Backtrace: 0x42032CBA:0x3FC962D0 0x420330D0:0x3FC962F0 0x403772C1:0x3FC96320 0x4200F204:0x3FCAC1B0 0x420307BE:0x3FCAC1F0 0x4200999D:0x3FCAC210 0x42044FBC:0x3FCAC250 0x4037BB81:0x3FCAC280 --- 0x42032cba: task_wdt_timeout_handling at E:/Espressif/frameworks/esp-idf-v5.5/components/esp_system/task_wdt/task_wdt.c:436 --- 0x420330d0: task_wdt_isr at E:/Espressif/frameworks/esp-idf-v5.5/components/esp_system/task_wdt/task_wdt.c:509 --- 0x403772c1: _xt_lowint1 at E:/Espressif/frameworks/esp-idf-v5.5/components/xtensa/xtensa_vectors.S:1240 --- 0x4200f204: lv_display_set_buffers at E:/work/ESP32S3/project/11_lvgl_9/components/lvgl/src/display/lv_display.c:400 --- 0x420307be: lv_port_disp_init at E:/work/ESP32S3/project/11_lvgl_9/components/porting/lv_port_disp_template.c:72 --- 0x4200999d: app_main at E:/work/ESP32S3/project/11_lvgl_9/main/main.c:48 --- 0x42044fbc: main_task at E:/Espressif/frameworks/esp-idf-v5.5/components/freertos/app_startup.c:208 --- 0x4037bb81: vPortTaskWrapper at E:/Espressif/frameworks/esp-idf-v5.5/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:139 E (10710) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time: E (10710) task_wdt: - IDLE0 (CPU 0) E (10710) task_wdt: Tasks currently running: E (10710) task_wdt: CPU 0: main E (10710) task_wdt: CPU 1: IDLE1 E (10710) task_wdt: Print CPU 0 (current core) backtrace Backtrace: 0x42032CBA:0x3FC962D0 0x420330D0:0x3FC962F0 0x403772C1:0x3FC96320 0x4200F204:0x3FCAC1B0 0x420307BE:0x3FCAC1F0 0x4200999D:0x3FCAC210 0x42044FBC:0x3FCAC250 0x4037BB81:0x3FCAC280 --- 0x42032cba: task_wdt_timeout_handling at E:/Espressif/frameworks/esp-idf-v5.5/components/esp_system/task_wdt/task_wdt.c:436 --- 0x420330d0: task_wdt_isr at E:/Espressif/frameworks/esp-idf-v5.5/components/esp_system/task_wdt/task_wdt.c:509 --- 0x403772c1: _xt_lowint1 at E:/Espressif/frameworks/esp-idf-v5.5/components/xtensa/xtensa_vectors.S:1240 --- 0x4200f204: lv_display_set_buffers at E:/work/ESP32S3/project/11_lvgl_9/components/lvgl/src/display/lv_display.c:400 --- 0x420307be: lv_port_disp_init at E:/work/ESP32S3/project/11_lvgl_9/components/porting/lv_port_disp_template.c:72 --- 0x4200999d: app_main at E:/work/ESP32S3/project/11_lvgl_9/main/main.c:48 --- 0x42044fbc: main_task at E:/Espressif/frameworks/esp-idf-v5.5/components/freertos/app_startup.c:208 --- 0x4037bb81: vPortTaskWrapper at E:/Espressif/frameworks/esp-idf-v5.5/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:139 E (15710) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time: E (15710) task_wdt: - IDLE0 (CPU 0) E (15710) task_wdt: Tasks currently running: E (15710) task_wdt: CPU 0: main E (15710) task_wdt: CPU 1: IDLE1 E (15710) task_wdt: Print CPU 0 (current core) backtrace Backtrace: 0x42032CBA:0x3FC962D0 0x420330D0:0x3FC962F0 0x403772C1:0x3FC96320 0x4200F204:0x3FCAC1B0 0x420307BE:0x3FCAC1F0 0x4200999D:0x3FCAC210 0x42044FBC:0x3FCAC250 0x4037BB81:0x3FCAC280 --- 0x42032cba: task_wdt_timeout_handling at E:/Espressif/frameworks/esp-idf-v5.5/components/esp_system/task_wdt/task_wdt.c:436 --- 0x420330d0: task_wdt_isr at E:/Espressif/frameworks/esp-idf-v5.5/components/esp_system/task_wdt/task_wdt.c:509 --- 0x403772c1: _xt_lowint1 at E:/Espressif/frameworks/esp-idf-v5.5/components/xtensa/xtensa_vectors.S:1240 --- 0x4200f204: lv_display_set_buffers at E:/work/ESP32S3/project/11_lvgl_9/components/lvgl/src/display/lv_display.c:400 --- 0x420307be: lv_port_disp_init at E:/work/ESP32S3/project/11_lvgl_9/components/porting/lv_port_disp_template.c:72 --- 0x4200999d: app_main at E:/work/ESP32S3/project/11_lvgl_9/main/main.c:48 --- 0x42044fbc: main_task at E:/Espressif/frameworks/esp-idf-v5.5/components/freertos/app_startup.c:208 --- 0x4037bb81: vPortTaskWrapper at E:/Espressif/frameworks/esp-idf-v5.5/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:139 E (20710) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time: E (20710) task_wdt: - IDLE0 (CPU 0) E (20710) task_wdt: Tasks currently running: E (20710) task_wdt: CPU 0: main E (20710) task_wdt: CPU 1: IDLE1 E (20710) task_wdt: Print CPU 0 (current core) backtrace 烧录后板载只显示黄色屏幕，什么原因，是因为缓冲区大小不等于全屏幕的时候，怎么解决
10-01
我们正在解决ESP32S3使用ESP-IDF v5.5和LVGL 9烧录后屏幕只显示黄色的问题，用户怀疑是缓冲区大小不等于全屏幕导致。 根据引用[1]的内容，我们了解到esp32-camera组件用于图像传感器驱动，但当前问题与显示有关，而...
python程序设计第四章字符串 题库及选解
zimuzi2019的博客
06-26 5万+
*由于学校考试不要求,这里去掉了涉及正则表达式的题目 填空 1、 表达式 ‘abc’ in (‘abcdefg’) 的值为 True 2、 表达式 ‘abc’ in [‘abcdefg’] 的值为() (False) 3、 表达式 ‘\x41’ == ‘A’ 的值为 True \x表示十六进制 4、 Python语句’’.join(list(‘hello world!’))执行的结果是 'hello world!' str.join(sequence)方法接收一个要连接的元素序列,以指
损坏的镜像错误
09-16 1万+
解决方法一： 1、在搜索框中输入 cmd ，选择【以管理员身份运行】； 复制代码 for %1 in (%windir%\system32\*.dll) do regsvr32.exe /s %1 执行即可。 方法二： 在控制面板中点击【程序和功能】，大图标的查看方式下； 然后将无法正常运行的程序找到后单击右键，选择 卸载将其卸载；卸载后重新下载安装即可解决问题...
三条命令搞定Winload.exe出现0xc000000e错误
zhacker的专栏
06-25 1万+
三条命令搞定Winload.exe出现0xc000000e错误File: /Windows/system32/winload.exe Status: 0xc000000e解决办法是: 使用WinPE盘启动,然后切换到新硬盘系统分区的:windows/system32目录下 切换目录命令为: Code: cd c:/windows/system32 C:为系统分区盘符 运行以下三条命令:
安装系统出现Winload.exe错误0xc000000e解决方法
热门推荐
xcntime的专栏
12-05 12万+
有的用户在安装Win7/Win8/Win10操作系统后，重启时出现Windows 启动管理器错误，无法加载所选项，因为应用程序丢失或损坏的的故障，错误代码：0xc000000e，这是由于引导文件没有正确设置导致加载失败引起的，下面我们来看看怎么解决这个问题，同样下面的方法也适用于一些 使用windows系统后出现这样状况的朋友。 所需工具：U盘启动盘（如老毛桃，电脑店，大白菜等）；
windows常见开机报错码以及解决方法
爱美食的Geek
05-19 5305
很多朋友碰到蓝屏或者是经常听说蓝屏，大家首先想到的都是重装系统，其实不然。　　 windows 系统最人性化的地方就是有个日志，你所有出现的蓝屏和错误都会记录在里面：包括什么时间出现的;错误代码是什么;记录的很详细的。 大家不妨打开看看再做判断,，不要盲目装系统!下面总结的一些比较有把握的蓝屏代码和解决方案，希望对大家有所帮助　　 1.0x0000000A　　 此问题百分之八十是驱动冲突, ...
Siki_Unity_2-1_API常用方法和类详细讲解(上)
weixin_30279671的博客
02-22 442
Unity 2-1 API常用方法和类详细讲解(上) 任务1&2：课程前言、学习方法 && 开发环境、查API文档 API: Application Programming Interface 应用程序编程接口 查看Unity文档和API手册： help->Unity Manual/ Scripting Reference 任务3&4：事件函数 &a...
0xc000000e错误解决办法（补充）
wwwtwdd123的博客
03-25 2万+
我的电脑是多系统，两个WIN7+Win10+MAC系统，用的clover引导。双硬盘，其中一个win7在另一个硬盘上。不知何时，就是这个win7系统一直启动不了，开机提示0xc000000e错误。网上搜了一堆，都是用bcdedit命令修复，无果，又不想重装系统。今天偶然发现该硬盘上的win7处于逻辑分区。于是改成主分区，居然解决问题了！所以注意了，用clover引导或者UEFI装机，需要注意安装盘
HANA ODBC驱动64位windows安装包
最新发布
12-24
HANA ODBC驱动64位windows安装包
评论 1
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值