0x0000008E watchdog.exe 问题

最新推荐文章于 2021-12-14 23:40:55 发布
最新推荐文章于 2021-12-14 23:40:55 发布
阅读量1.1k 收藏
点赞数
CC 4.0 BY-SA版权
分类专栏： 笔记本 文章标签： dell ie
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/qingfengke78/article/details/6767189
作者遇到新安装IE8浏览器后电脑频繁死机并出现蓝屏的问题，通过安装驱动人生确认显卡驱动为最新版本，但观看优酷视频时仍出现蓝屏现象。在重新下载并安装官方显卡驱动后，问题得以解决。作者正在继续观察以确保问题完全解决。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

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

 

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

观察中

 

龙芯3A5000在银河麒麟上的“watchdog: BUG: soft lockup ”问题
qq_15895713的博客
11-28 847
龙芯3A5000. 麒麟kylin softlockup
android 开机启动流程分析（03）init启动中关键进程 uevent & watchdog
wangdsh的博客
05-22 1967
系列文章解读&说明： Android开机启动流程的分析主要分为以下部分： android 开机启动流程分析（01） init之前启动说明 android 开机启动流程分析（02）init的启动流程分析 android 开机启动流程分析（03）init启动中关键进程 uevent & watchdog android 开机启动流程分析（04）init启动中关键服务-属性服务...
Android WatchDog（1）- 启动流程（Android 12）
weixin_41678668的博客
12-14 2173
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 //
winload.exe
08-10
win7、win8、win10，在C盘找到widows/system32/system32\winload.efi，
Win7纯净版系统Windows未能启动,文件Winload.exe的解决方法
能看代码的CrackLibby
09-19 3万+
http://www.xitonghe.com/jiaocheng/windows7-1649.html 在win7纯净版系统安装后或使用过程中我们可能会遇上开机故障，而Windows 未能启动 就是一个很常见的故障，通常下面会标注出现问题的文件：文件:\windows\system32\winload.exe 错误0xc000000f 等信息，这又该如何解决
安装系统出现Winload.exe错误0xc000000e解决方法
热门推荐
xcntime的专栏
12-05 12万+
有的用户在安装Win7/Win8/Win10操作系统后，重启时出现Windows 启动管理器错误，无法加载所选项，因为应用程序丢失或损坏的的故障，错误代码：0xc000000e，这是由于引导文件没有正确设置导致加载失败引起的，下面我们来看看怎么解决这个问题，同样下面的方法也适用于一些 使用windows系统后出现这样状况的朋友。 所需工具：U盘启动盘（如老毛桃，电脑店，大白菜等）；
************* 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），需要专业级的解决方案。这个错误属于硬件相关的严重系统崩溃，通常意味着处理器线程响应超时，可能涉及硬件故障、驱动不兼容或系统设置问题。 用户...
Backtrace: 0x42021A86:0x3FCA2340 0x42021EE4:0x3FCA2360 0x403776CD:0x3FCA2390 0x4037FEFB:0x3FCAE9D0 0x42004BE2:0x3FCAE9F0 0x40384641:0x3FCAEA10 0x40385C56:0x3FCAEA30 --- 0x42021a86: task_wdt_timeout_handling at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:489 (discriminator 3) 0x42021ee4: task_wdt_isr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:565 0x403776cd: _xt_lowint1 at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/xtensa_vectors.S:1240 0x4037fefb: xt_utils_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/xtensa/include/xt_utils.h:81 (inlined by) esp_cpu_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_hw_support/cpu.c:111 0x42004be2: esp_vApplicationIdleHook at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/freertos_hooks.c:59 0x40384641: prvIdleTask at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:4439 (discriminator 1) 0x40385c56: vPortTaskWrapper at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:162 free_heap_size = 114267 | run time : 250 | mesh rssi: 0 free_heap_size = 114267 | run time : 251 | mesh rssi: 0 free_heap_size = 114267 | run time : 252 | mesh rssi: 0 free_heap_size = 114267 | run time : 253 | mesh rssi: 0 free_heap_size = 114267 | run time : 254 | mesh rssi: 0 free_heap_size = 114267 | run time : 255 | mesh rssi: 0 free_heap_size = 114267 | run time : 256 | mesh rssi: 0 ESP-ROM:esp32s3-20210327 Build:Mar 27 2021 rst:0x1 (POWERON),boot:0x27 (UART0_BOOT) wait uart0 download PS D:\CxhData\test\2\24_0222_RGBMatrix\LedRGBMatrix\LedRGBMatrix_Single> PS D:\CxhData\test\2\24_0222_RGBMatrix\LedRGBMatrix\LedRGBMatrix_Single> PS D:\CxhData\test\2\24_0222_RGBMatrix\LedRGBMatrix\LedRGBMatrix_Single> PS D:\CxhData\test\2\24_0222_RGBMatrix\LedRGBMatrix\LedRGBMatrix_Single> $env:IDF_PATH = 'D:\CxhData\EspData\esp\v5.1.5\esp-idf'; PS D:\CxhData\test\2\24_0222_RGBMatrix\LedRGBMatrix\LedRGBMatrix_Single> & 'd:\CxhData\EspData\.espressif\python_env\idf5.1_py3.11_env\Scripts\python.exe' 'D:\CxhData\EspData\esp\v5.1.5\esp-idf\tools\idf_monitor.py' -p COM15 -b 115200 --toolchain-prefix xtensa-esp32s3-elf- --make '''d:\CxhData\EspData\.espressif\python_env\idf5.1_py3.11_env\Scripts\python.exe'' ''D:\CxhData\EspData\esp\v5.1.5\esp-idf\tools\idf.py''' --target esp32s3 'd:\CxhData\test\2\24_0222_RGBMatrix\LedRGBMatrix\LedRGBMatrix_Single\build\RGBMatrix.elf' --- Warning: GDB cannot open serial ports accessed as COMx --- Using \\.\COM15 instead... --- esp-idf-monitor 1.5.0 on \\.\COM15 115200 --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H free_heap_size = 114271 | run time : 19 | mesh rssi: 0 free_heap_size = 114271 | run time : 20 | mesh rssi: 0 free_heap_size = 114271 | run time : 21 | mesh rssi: 0 free_heap_size = 114271 | run time : 22 | mesh rssi: 0 free_heap_size = 114271 | run time : 23 | mesh rssi: 0 free_heap_size = 114271 | run time : 24 | mesh rssi: 0 E (34734) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time: E (34734) task_wdt: - main (CPU 0) E (34734) task_wdt: Tasks currently running: E (34734) task_wdt: CPU 0: IDLE0 E (34734) task_wdt: CPU 1: IDLE1 E (34734) task_wdt: Print CPU 0 (current core) backtrace Backtrace: 0x42021A5A:0x3FCA2340 0x42021EB8:0x3FCA2360 0x403776CD:0x3FCA2390 0x4037FEFB:0x3FCAE9D0 0x42004C32:0x3FCAE9F0 0x40384641:0x3FCAEA10 0x40385C56:0x3FCAEA30 --- 0x42021a5a: task_wdt_timeout_handling at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:489 (discriminator 3) 0x42021eb8: task_wdt_isr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:565 0x403776cd: _xt_lowint1 at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/xtensa_vectors.S:1240 0x4037fefb: xt_utils_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/xtensa/include/xt_utils.h:81 (inlined by) esp_cpu_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_hw_support/cpu.c:111 0x42004c32: esp_vApplicationIdleHook at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/freertos_hooks.c:59 0x40384641: prvIdleTask at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:4439 (discriminator 1) 0x40385c56: vPortTaskWrapper at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:162 free_heap_size = 114271 | run time : 25 | mesh rssi: 0 free_heap_size = 114271 | run time : 26 | mesh rssi: 0 free_heap_size = 114271 | run time : 27 | mesh rssi: 0 free_heap_size = 114271 | run time : 28 | mesh rssi: 0 free_heap_size = 114271 | run time : 29 | mesh rssi: 0 free_heap_size = 114271 | run time : 30 | mesh rssi: 0 free_heap_size = 114271 | run time : 31 | mesh rssi: 0 free_heap_size = 114271 | run time : 32 | mesh rssi: 0 free_heap_size = 114271 | run time : 33 | mesh rssi: 0 free_heap_size = 114271 | run time : 34 | mesh rssi: 0 free_heap_size = 114271 | run time : 35 | mesh rssi: 0 free_heap_size = 114271 | run time : 36 | mesh rssi: 0 free_heap_size = 114271 | run time : 37 | mesh rssi: 0 E (39734) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time: E (39734) task_wdt: - main (CPU 0) E (39734) task_wdt: Tasks currently running: E (39734) task_wdt: CPU 0: IDLE0 E (39734) task_wdt: CPU 1: IDLE1 E (39734) task_wdt: Print CPU 0 (current core) backtrace Backtrace: 0x42021A5A:0x3FCA2340 0x42021EB8:0x3FCA2360 0x403776CD:0x3FCA2390 0x4037FEFB:0x3FCAE9D0 0x42004C32:0x3FCAE9F0 0x40384641:0x3FCAEA10 0x40385C56:0x3FCAEA30 --- 0x42021a5a: task_wdt_timeout_handling at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:489 (discriminator 3) 0x42021eb8: task_wdt_isr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:565 0x403776cd: _xt_lowint1 at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/xtensa_vectors.S:1240 0x4037fefb: xt_utils_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/xtensa/include/xt_utils.h:81 (inlined by) esp_cpu_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_hw_support/cpu.c:111 0x42004c32: esp_vApplicationIdleHook at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/freertos_hooks.c:59 0x40384641: prvIdleTask at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:4439 (discriminator 1) 0x40385c56: vPortTaskWrapper at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:162 free_heap_size = 114271 | run time : 38 | mesh rssi: 0 free_heap_size = 114271 | run time : 39 | mesh rssi: 0 free_heap_size = 114271 | run time : 40 | mesh rssi: 0 free_heap_size = 114271 | run time : 41 | mesh rssi: 0 free_heap_size = 114271 | run time : 42 | mesh rssi: 0 free_heap_size = 114271 | run time : 43 | mesh rssi: 0 free_heap_size = 114271 | run time : 44 | mesh rssi: 0 free_heap_size = 114271 | run time : 45 | mesh rssi: 0 free_heap_size = 114271 | run time : 46 | mesh rssi: 0 free_heap_size = 114271 | run time : 47 | mesh rssi: 0 free_heap_size = 114271 | run time : 48 | mesh rssi: 0 free_heap_size = 114271 | run time : 49 | mesh rssi: 0 E (44734) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time: E (44734) task_wdt: - main (CPU 0) E (44734) task_wdt: Tasks currently running: E (44734) task_wdt: CPU 0: IDLE0 E (44734) task_wdt: CPU 1: IDLE1 E (44734) task_wdt: Print CPU 0 (current core) backtrace Backtrace: 0x42021A5A:0x3FCA2340 0x42021EB8:0x3FCA2360 0x403776CD:0x3FCA2390 0x4037FEFB:0x3FCAE9D0 0x42004C32:0x3FCAE9F0 0x40384641:0x3FCAEA10 0x40385C56:0x3FCAEA30 --- 0x42021a5a: task_wdt_timeout_handling at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:489 (discriminator 3) 0x42021eb8: task_wdt_isr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:565 0x403776cd: _xt_lowint1 at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/xtensa_vectors.S:1240 0x4037fefb: xt_utils_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/xtensa/include/xt_utils.h:81 (inlined by) esp_cpu_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_hw_support/cpu.c:111 0x42004c32: esp_vApplicationIdleHook at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/freertos_hooks.c:59 0x40384641: prvIdleTask at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:4439 (discriminator 1) 0x40385c56: vPortTaskWrapper at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:162 free_heap_size = 114271 | run time : 50 | mesh rssi: 0 free_heap_size = 114271 | run time : 51 | mesh rssi: 0 free_heap_size = 114271 | run time : 52 | mesh rssi: 0 free_heap_size = 114271 | run time : 53 | mesh rssi: 0 free_heap_size = 114271 | run time : 54 | mesh rssi: 0 free_heap_size = 114271 | run time : 55 | mesh rssi: 0 free_heap_size = 114271 | run time : 56 | mesh rssi: 0 free_heap_size = 114271 | run time : 57 | mesh rssi: 0 free_heap_size = 114271 | run time : 58 | mesh rssi: 0 free_heap_size = 114271 | run time : 59 | mesh rssi: 0 free_heap_size = 114271 | run time : 60 | mesh rssi: 0 free_heap_size = 114271 | run time : 61 | mesh rssi: 0 free_heap_size = 114271 | run time : 62 | mesh rssi: 0 E (49734) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time: E (49734) task_wdt: - main (CPU 0) E (49734) task_wdt: Tasks currently running: E (49734) task_wdt: CPU 0: IDLE0 E (49734) task_wdt: CPU 1: IDLE1 E (49734) task_wdt: Print CPU 0 (current core) backtrace Backtrace: 0x42021A5A:0x3FCA2340 0x42021EB8:0x3FCA2360 0x403776CD:0x3FCA2390 0x4037FEFB:0x3FCAE9D0 0x42004C32:0x3FCAE9F0 0x40384641:0x3FCAEA10 0x40385C56:0x3FCAEA30 --- 0x42021a5a: task_wdt_timeout_handling at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:489 (discriminator 3) 0x42021eb8: task_wdt_isr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:565 0x403776cd: _xt_lowint1 at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/xtensa_vectors.S:1240 0x4037fefb: xt_utils_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/xtensa/include/xt_utils.h:81 (inlined by) esp_cpu_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_hw_support/cpu.c:111 0x42004c32: esp_vApplicationIdleHook at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/freertos_hooks.c:59 0x40384641: prvIdleTask at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:4439 (discriminator 1) 0x40385c56: vPortTaskWrapper at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:162 free_heap_size = 114271 | run time : 63 | mesh rssi: 0 free_heap_size = 114271 | run time : 64 | mesh rssi: 0 free_heap_size = 114271 | run time : 65 | mesh rssi: 0 free_heap_size = 114271 | run time : 66 | mesh rssi: 0 free_heap_size = 114271 | run time : 67 | mesh rssi: 0 free_heap_size = 114271 | run time : 68 | mesh rssi: 0 free_heap_size = 114271 | run time : 69 | mesh rssi: 0 free_heap_size = 114271 | run time : 70 | mesh rssi: 0 free_heap_size = 114271 | run time : 71 | mesh rssi: 0 free_heap_size = 114271 | run time : 72 | mesh rssi: 0 free_heap_size = 114271 | run time : 73 | mesh rssi: 0 free_heap_size = 114271 | run time : 74 | mesh rssi: 0 E (54734) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time: E (54734) task_wdt: - main (CPU 0) E (54734) task_wdt: Tasks currently running: E (54734) task_wdt: CPU 0: IDLE0 E (54734) task_wdt: CPU 1: IDLE1 E (54734) task_wdt: Print CPU 0 (current core) backtrace Backtrace: 0x42021A5A:0x3FCA2340 0x42021EB8:0x3FCA2360 0x403776CD:0x3FCA2390 0x4037FEFB:0x3FCAE9D0 0x42004C32:0x3FCAE9F0 0x40384641:0x3FCAEA10 0x40385C56:0x3FCAEA30 --- 0x42021a5a: task_wdt_timeout_handling at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:489 (discriminator 3) 0x42021eb8: task_wdt_isr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:565 0x403776cd: _xt_lowint1 at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/xtensa_vectors.S:1240 0x4037fefb: xt_utils_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/xtensa/include/xt_utils.h:81 (inlined by) esp_cpu_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_hw_support/cpu.c:111 0x42004c32: esp_vApplicationIdleHook at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/freertos_hooks.c:59 0x40384641: prvIdleTask at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:4439 (discriminator 1) 0x40385c56: vPortTaskWrapper at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:162 free_heap_size = 114271 | run time : 75 | mesh rssi: 0 free_heap_size = 114271 | run time : 76 | mesh rssi: 0 free_heap_size = 114271 | run time : 77 | mesh rssi: 0 free_heap_size = 114271 | run time : 78 | mesh rssi: 0 free_heap_size = 114271 | run time : 79 | mesh rssi: 0 free_heap_size = 114271 | run time : 80 | mesh rssi: 0 free_heap_size = 114271 | run time : 81 | mesh rssi: 0 free_heap_size = 114271 | run time : 82 | mesh rssi: 0 free_heap_size = 114271 | run time : 83 | mesh rssi: 0 free_heap_size = 114271 | run time : 84 | mesh rssi: 0 free_heap_size = 114271 | run time : 85 | mesh rssi: 0 free_heap_size = 114271 | run time : 86 | mesh rssi: 0 free_heap_size = 114271 | run time : 87 | mesh rssi: 0 E (59734) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time: E (59734) task_wdt: - main (CPU 0) E (59734) task_wdt: Tasks currently running: E (59734) task_wdt: CPU 0: IDLE0 E (59734) task_wdt: CPU 1: IDLE1 E (59734) task_wdt: Print CPU 0 (current core) backtrace Backtrace: 0x42021A5A:0x3FCA2340 0x42021EB8:0x3FCA2360 0x403776CD:0x3FCA2390 0x4037FEFB:0x3FCAE9D0 0x42004C32:0x3FCAE9F0 0x40384641:0x3FCAEA10 0x40385C56:0x3FCAEA30 --- 0x42021a5a: task_wdt_timeout_handling at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:489 (discriminator 3) 0x42021eb8: task_wdt_isr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:565 0x403776cd: _xt_lowint1 at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/xtensa_vectors.S:1240 0x4037fefb: xt_utils_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/xtensa/include/xt_utils.h:81 (inlined by) esp_cpu_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_hw_support/cpu.c:111 0x42004c32: esp_vApplicationIdleHook at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/freertos_hooks.c:59 0x40384641: prvIdleTask at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:4439 (discriminator 1) 0x40385c56: vPortTaskWrapper at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:162 free_heap_size = 114271 | run time : 88 | mesh rssi: 0 free_heap_size = 114271 | run time : 89 | mesh rssi: 0 free_heap_size = 114271 | run time : 90 | mesh rssi: 0 free_heap_size = 114271 | run time : 91 | mesh rssi: 0 free_heap_size = 114271 | run time : 92 | mesh rssi: 0 free_heap_size = 114271 | run time : 93 | mesh rssi: 0 free_heap_size = 114271 | run time : 94 | mesh rssi: 0 free_heap_size = 114271 | run time : 95 | mesh rssi: 0 free_heap_size = 114271 | run time : 96 | mesh rssi: 0 free_heap_size = 114271 | run time : 97 | mesh rssi: 0 free_heap_size = 114271 | run time : 98 | mesh rssi: 0 free_heap_size = 114271 | run time : 99 | mesh rssi: 0 E (64734) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time: E (64734) task_wdt: - main (CPU 0) E (64734) task_wdt: Tasks currently running: E (64734) task_wdt: CPU 0: IDLE0 E (64734) task_wdt: CPU 1: IDLE1 E (64734) task_wdt: Print CPU 0 (current core) backtrace Backtrace: 0x42021A5A:0x3FCA2340 0x42021EB8:0x3FCA2360 0x403776CD:0x3FCA2390 0x4037FEFB:0x3FCAE9D0 0x42004C32:0x3FCAE9F0 0x40384641:0x3FCAEA10 0x40385C56:0x3FCAEA30 --- 0x42021a5a: task_wdt_timeout_handling at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:489 (discriminator 3) 0x42021eb8: task_wdt_isr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/task_wdt/task_wdt.c:565 0x403776cd: _xt_lowint1 at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/xtensa_vectors.S:1240 0x4037fefb: xt_utils_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/xtensa/include/xt_utils.h:81 (inlined by) esp_cpu_wait_for_intr at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_hw_support/cpu.c:111 0x42004c32: esp_vApplicationIdleHook at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/esp_system/freertos_hooks.c:59 0x40384641: prvIdleTask at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:4439 (discriminator 1) 0x40385c56: vPortTaskWrapper at D:/CxhData/EspData/esp/v5.1.5/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:162 free_heap_size = 114271 | run time : 100 | mesh rssi: 0 free_heap_size = 114271 | run time : 101 | mesh rssi: 0 free_heap_size = 114271 | run time : 102 | mesh rssi: 0 free_heap_size = 114271 | run time : 103 | mesh rssi: 0 free_heap_size = 114271 | run time : 104 | mesh rssi: 0 free_heap_size = 114271 | run time : 105 | mesh rssi: 0 free_heap_size = 114271 | run time : 106 | mesh rssi: 0
07-08
E (34734) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time: E (34734) task_wdt: - main (CPU 0) ``` 主任务（main task）未在规定时间内"喂狗"，导致...
************* 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.046 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:\Users\鱼噢\Desktop\112623-13812-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 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff800`62800000 PsLoadedModuleList = 0xfffff800`6342a6d0 Debug session time: Sun Nov 26 14:05:43.333 2023 (UTC + 8:00) System Uptime: 1 days 3:54:13.677 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................................................ Loading User Symbols Loading unloaded module list .................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff800`62bfd730 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffcc83`ee82f790=0000000000000119 8: kd> !analyze -v Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................................................ Loading User Symbols Loading unloaded module list .................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_SCHEDULER_INTERNAL_ERROR (119) The video scheduler has detected that fatal violation has occurred. This resulted in a condition that video scheduler can no longer progress. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 0000000000000002, The driver failed upon the submission of a command. Arg2: ffffffffc000000d Arg3: ffffcc83ee82f860 Arg4: ffffb70a623aabb0 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2093 Key : Analysis.Elapsed.mSec Value: 65924 Key : Analysis.IO.Other.Mb Value: 20 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 28 Key : Analysis.Init.CPU.mSec Value: 937 Key : Analysis.Init.Elapsed.mSec Value: 66871 Key : Analysis.Memory.CommitPeak.Mb Value: 112 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: 0x119 Key : Bugcheck.Code.TargetModel Value: 0x119 Key : Failure.Bucket Value: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue Key : Failure.Hash Value: {9a11bf9c-270e-962e-7a82-3efdab93c10e} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 119 BUGCHECK_P1: 2 BUGCHECK_P2: ffffffffc000000d BUGCHECK_P3: ffffcc83ee82f860 BUGCHECK_P4: ffffb70a623aabb0 FILE_IN_CAB: 112623-13812-01.dmp FAULTING_THREAD: ffffb70a62340380 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffcc83`ee82f788 fffff800`7d373ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffcc83`ee82f860 : nt!KeBugCheckEx ffffcc83`ee82f790 fffff800`7c5f9989 : ffffb70a`623a7000 00000000`c000000d ffffcc83`ee82f899 00000000`00000002 : watchdog!WdLogEvent5_WdCriticalError+0xe0 ffffcc83`ee82f7d0 fffff800`7c6751ad : ffffb70a`00000000 ffffb70a`623aabb0 ffffb70a`62335000 ffffb70a`62481010 : dxgmms2!VidSchiSendToExecutionQueue+0xa99 ffffcc83`ee82f900 fffff800`7c67deda : ffffb70a`62481010 ffffb70a`62335000 00000000`00000000 ffffb70a`623cc620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed ffffcc83`ee82fa80 fffff800`7c67dd4a : ffffb70a`62335400 fffff800`7c67dc80 ffffb70a`62335000 ffffe201`bfa47100 : dxgmms2!VidSchiRun_PriorityTable+0x17a ffffcc83`ee82fad0 fffff800`62b078e5 : ffffb70a`62340380 fffff800`00000001 ffffb70a`62335000 000fa4ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca ffffcc83`ee82fb10 fffff800`62c06368 : ffffe201`bfa47180 ffffb70a`62340380 fffff800`62b07890 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffffcc83`ee82fb60 00000000`00000000 : ffffcc83`ee830000 ffffcc83`ee829000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+a99 MODULE_NAME: dxgmms2 IMAGE_NAME: dxgmms2.sys IMAGE_VERSION: 10.0.19041.3745 STACK_COMMAND: .process /r /p 0xffffb70a3c8b2140; .thread 0xffffb70a62340380 ; kb BUCKET_ID_FUNC_OFFSET: a99 FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e} Followup: MachineOwner ---------
07-26
- 找到导致问题的应用程序（如游戏或视频软件）的可执行文件（.exe）。 - 右键单击该文件 > 选择“属性” > 切换到“兼容性”选项卡。 - 勾选“禁用全屏优化” > 点击“应用”并确定。 - 重启应用程序测试。如果...
ffff8480`00c07328 fffff806`4e2892d6 : 00000000`00000050 fffff806`c18e143b 00000000`00000010 ffff8480`00c07550 : nt!KeBugCheckEx ffff8480`00c07330 fffff806`4e02375c : 00000000`00000000 00000000`00000010 00000000`00000000 fffff806`c18e143b : nt!MiSystemFault+0x202506 ffff8480`00c07430 fffff806`4e225b7e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`64886af7 : nt!MmAccessFault+0x29c ffff8480`00c07550 fffff806`c18e143b : 00000000`00000000 000000ae`7beff5c0 00000000`00000008 fffff806`64885360 : nt!KiPageFault+0x37e ffff8480`00c076e0 00000000`00000000 : 000000ae`7beff5c0 00000000`00000008 fffff806`64885360 ffff880f`be437290 : 0xfffff806`c18e143b 这个是什么指向
04-23
KiPageFault+0x37e ``` *核心线索*： 1. `nt!MiSystemFault` 和 `nt!MmAccessFault` 的组合表明**内存访问异常**（常见于无效地址访问或内存页保护错误） 2. 最终调用链指向第三方模块地址 `fffff806`c18e143b`（非...
windows常见开机报错码以及解决方法
爱美食的Geek
05-19 5168
很多朋友碰到蓝屏或者是经常听说蓝屏，大家首先想到的都是重装系统，其实不然。　　 windows 系统最人性化的地方就是有个日志，你所有出现的蓝屏和错误都会记录在里面：包括什么时间出现的;错误代码是什么;记录的很详细的。 大家不妨打开看看再做判断,，不要盲目装系统!下面总结的一些比较有把握的蓝屏代码和解决方案，希望对大家有所帮助　　 1.0x0000000A　　 此问题百分之八十是驱动冲突, ...
三条命令搞定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:为系统分区盘符 运行以下三条命令:
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 执行即可。 方法二： 在控制面板中点击【程序和功能】，大图标的查看方式下； 然后将无法正常运行的程序找到后单击右键，选择 卸载将其卸载；卸载后重新下载安装即可解决问题...
0xc000000e错误解决办法（补充）
wwwtwdd123的博客
03-25 2万+
我的电脑是多系统，两个WIN7+Win10+MAC系统，用的clover引导。双硬盘，其中一个win7在另一个硬盘上。不知何时，就是这个win7系统一直启动不了，开机提示0xc000000e错误。网上搜了一堆，都是用bcdedit命令修复，无果，又不想重装系统。今天偶然发现该硬盘上的win7处于逻辑分区。于是改成主分区，居然解决问题了！所以注意了，用clover引导或者UEFI装机，需要注意安装盘
Siki_Unity_2-1_API常用方法和类详细讲解(上)
weixin_30279671的博客
02-22 419
Unity 2-1 API常用方法和类详细讲解(上) 任务1&2：课程前言、学习方法 && 开发环境、查API文档 API: Application Programming Interface 应用程序编程接口 查看Unity文档和API手册： help->Unity Manual/ Scripting Reference 任务3&4：事件函数 &a...
Win10数字签名错误/winload.exe 错误解决办法
小飞飞的专栏
12-23 4万+
装win10或者升级win10的时候总会出现数字签名错误和找不到winload.exe，我觉得这2个错误是差不多的，接下来看我的解决过程吧！
中文疾病诊断数据集（百万条），可用于中国人疾病分析、疾病诊断
08-19
资源下载链接为： https://pan.quark.cn/s/056be54e94fa 中文疾病诊断数据集（百万条），可用于中国人疾病分析、疾病诊断。（最新、最全版本！打开链接下载即可用！）
【计算机视觉】基于立体视觉的3D目标检测框架优化：联合2D边界框与实例深度估计的高效多类别检测系统设计（含详细代码及解释）
最新发布
08-19
内容概要：这篇论文提出了一种基于立体视觉的3D目标检测框架，核心创新包括直接实例深度估计方法、自适应空间特征聚合模块。该框架仅用左图像生成联合2D边界框并预测3D框中心深度，通过减弱背景点影响并整合重要实例特征，提高了3D检测的精度和效率。相比现有方法，该框架在KITTI基准测试上表现出色，实现了更高的检测精度（68.7% AP）和更快的推理速度（8.5 FPS）。论文还详细介绍了框架的核心模块实现，如实例深度估计网络、自适应空间特征聚合模块以及完整的立体3D检测框架，并通过实验验证了各模块的有效性。 适合人群：从事计算机视觉、自动驾驶或机器人领域的研究人员和技术开发者，尤其是对3D目标检测、立体视觉感兴趣的从业者。 使用场景及目标：①提高3D目标检测精度和效率；②研究立体视觉在3D检测中的应用；③探索深度估计和特征聚合的新方法；④应用于自动驾驶、机器人导航等实际场景。 其他说明：论文不仅提供了理论分析，还给出了详细的代码实现，便于读者理解和复现。该框架在KITTI数据集上进行了充分验证，证明了其在多类别3D检测任务中的优越性能。此外，论文还讨论了现有方法的局限性，并提出了针对性的解决方案。
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值