取消
显示结果 
搜索替代 
您的意思是: 

最新主题

按照方法一后,还是会时不时的蓝屏 目前系统是win10,升级不到win11所以没有试方法二
经过一晚上的测试,好像都是正常的
电脑开机以后会时不时的蓝屏 ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : false ... 查看更多...
电脑开机以后会时不时的蓝屏 ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : false AllowNugetExeUpdate : false AllowNugetMSCredentialProviderInstall : false AllowParallelInitializationOfLocalRepositories : true -- 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.031 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36 Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\HP\Desktop\080923-9953-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 (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xfffff800`2b000000 PsLoadedModuleList = 0xfffff800`2bc2a350 Debug session time: Wed Aug 9 07:41:51.922 2023 (UTC + 8:00) System Uptime: 0 days 0:01:18.682 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 -vnt!KeBugCheckEx: fffff800`2b3fc030 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffab00`a6d25390=0000000000000124 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details. Arguments: Arg1: 0000000000000010, Device Driver Error Arg2: ffffd68b16a9d028, Address of the nt!_WHEA_ERROR_RECORD structure. Arg3: ffffd68ae558192c Arg4: ffffd68ae55c51a0 Debugging Details: ------------------ *** WARNING: Check Image - Checksum mismatch - Dump: 0xba17e, File: 0xb5f2f - C:\ProgramData\Dbg\sym\storport.sys\19BAC484b5000\storport.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3327 Key : Analysis.Elapsed.mSec Value: 8604 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 405 Key : Analysis.Init.Elapsed.mSec Value: 18318 Key : Analysis.Memory.CommitPeak.Mb Value: 88 Key : Bugcheck.Code.LegacyAPI Value: 0x124 Key : Dump.Attributes.AsUlong Value: 8 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys Key : Failure.Hash Value: {37af9407-4a3e-0b08-acdd-dadffdc34c3c} BUGCHECK_CODE: 124 BUGCHECK_P1: 10 BUGCHECK_P2: ffffd68b16a9d028 BUGCHECK_P3: ffffd68ae558192c BUGCHECK_P4: ffffd68ae55c51a0 FILE_IN_CAB: 080923-9953-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffab00`a6d25388 fffff800`2b5b9a1c : 00000000`00000124 00000000`00000010 ffffd68b`16a9d028 ffffd68a`e558192c : nt!KeBugCheckEx ffffab00`a6d25390 fffff800`2b5ba579 : ffffd68b`1261da10 ffffd68b`1261da10 ffffd68a`e5581900 ffffd68b`0c83d128 : nt!WheaReportHwError+0x3ec ffffab00`a6d25470 fffff800`2b5ba695 : 00000000`00000000 00000000`00000062 ffffd68b`1261da10 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9 ffffab00`a6d254a0 fffff800`307f3831 : 00000000`00000000 ffffab00`a6d256c0 ffffd68a`e55c51a0 ffffd68a`e55ca0ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5 ffffab00`a6d25500 fffff800`307ecc10 : 00000000`00000000 ffffd68a`e55c51a0 ffffd68a`e56cb1a0 00000000`00000000 : storport!StorpWheaReportError+0x9d ffffab00`a6d25590 fffff800`307bf0bc : fffff800`30819000 00000000`00000062 00000000`00000000 ffffab00`a6d25930 : storport!StorpMarkDeviceFailed+0x358 ffffab00`a6d25820 fffff800`3078b57d : 00000000`00000000 ffffd68a`e55ca020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x91c ffffab00`a6d258f0 fffff800`3078e78e : ffffd68a`c1000002 00000000`00000000 ffffd68a`e55ca020 00000000`00000003 : stornvme!ControllerReset+0x1a1 ffffab00`a6d25970 fffff800`3078d6ef : ffffd68a`e55ca020 ffffd68a`e55c5050 ffffd68b`1518a390 80000000`00002000 : stornvme!NVMeControllerReset+0x10a ffffab00`a6d259a0 fffff800`307ea306 : ffffd68b`1518a390 ffffd68a`e55c5050 ffffd68a`e5624080 ffffd68a`e2f02a60 : stornvme!NVMeControllerAsyncResetWorker+0x3f ffffab00`a6d259d0 fffff800`2b243f85 : ffffd68b`16446130 ffffd68b`16446130 ffffd68a`e55c5050 fffff800`4ff95440 : storport!StorPortWorkItemRoutine+0x46 ffffab00`a6d25a00 fffff800`2b28e5c5 : ffffd68a`e568c080 ffffd68a`e568c080 fffff800`2b243e50 00000000`00000000 : nt!IopProcessWorkItem+0x135 ffffab00`a6d25a70 fffff800`2b3268f5 : ffffd68a`e568c080 00000000`00000080 ffffd68a`e2ec2040 000fa4ef`bd9bbfff : nt!ExpWorkerThread+0x105 ffffab00`a6d25b10 fffff800`2b404c68 : fffff800`27bda180 ffffd68a`e568c080 fffff800`2b3268a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffffab00`a6d25b60 00000000`00000000 : ffffab00`a6d26000 ffffab00`a6d1f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel.sys STACK_COMMAND: .cxr; .ecxr ; kb FAILURE_BUCKET_ID: 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {37af9407-4a3e-0b08-acdd-dadffdc34c3c} Followup: MachineOwner --------- 4: kd> lmvm GenuineIntelBrowse full module liststart end module name
† 惠普支持社区是一个客户交流平台,便于客户找到有效的解决方法,快速解决问题,充分利用惠普产品。请在发帖之前,阅读社区的使用条款注册须知。