关于360的 360Hvm64.sys 驱动导致 远光84 游戏电脑蓝屏的dmg报告
本帖最后由 360电脑专家003 于 2025-8-14 15:55 编辑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.031 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 45Microsoft (R) Windows Debugger Version 10.0.27871.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv* Executable search path is:Windows 10 Kernel Version 26100 MP (20 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0xfffff807`bb600000 PsLoadedModuleList = 0xfffff807`bc4f4870 Debug session time: Wed Aug 13 22:01:08.139 2025 (UTC + 8:00) System Uptime: 2 days 22:25:39.515 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`00286018).Type ".hh dbgerr001" for details Loading unloaded module list .................................................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff807`bbab85d0 48894c2408 mov qword ptr ,rcx ss:0018:ffffd100`362e6ce0=0000000000000133 6: 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.............................................................. ................................................................ ................................................................ .............................................................. Loading User Symbols PEB is paged out (Peb.Ldr = 00000000`00286018).Type ".hh dbgerr001" for details Loading unloaded module list .................................................. ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. Arg2: 0000000000001e00, The watchdog period (in ticks). Arg3: fffff807bc5c33a0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeout Arg4: 0000000000000000Debugging Details: ------------------*** WARNING: Unable to verify timestamp for 360Hvm64.sys ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information.Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information.Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: TickPeriods *** *** *** *************************************************************************KEY_VALUES_STRING: 1 Key: Analysis.CPU.mSec Value: 1390 Key: Analysis.Elapsed.mSec Value: 41170 Key: Analysis.IO.Other.Mb Value: 4 Key: Analysis.IO.Read.Mb Value: 1 Key: Analysis.IO.Write.Mb Value: 24 Key: Analysis.Init.CPU.mSec Value: 1718 Key: Analysis.Init.Elapsed.mSec Value: 575886 Key: Analysis.Memory.CommitPeak.Mb Value: 110 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: 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: 0x133_ISR_360Hvm64!unknown_function Key: Failure.Hash Value: {9006ed43-9cd3-628f-18ab-f4969336ae4b} Key: Stack.Pointer Value: ISR BUGCHECK_CODE:133BUGCHECK_P1: 1BUGCHECK_P2: 1e00BUGCHECK_P3: fffff807bc5c33a0BUGCHECK_P4: 0FILE_IN_CAB:081325-12109-01.dmpDUMP_FILE_ATTRIBUTES: 0x21008 Kernel Generated Triage DumpFAULTING_THREAD:ffffe2844315b080DPC_TIMEOUT_TYPE:DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDEDBLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT:1PROCESS_NAME:SolarlandClienSTACK_TEXT: ffffd100`362e6cd8 fffff807`bb975129 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`bc5c33a0 : nt!KeBugCheckEx ffffd100`362e6ce0 fffff807`bb967b61 : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00f798e0 : nt!KeAccumulateTicks+0x589 ffffd100`362e6d50 fffff807`bb86ebfb : 0000024e`5153eef0 00000000`00000000 fffff807`bc58dd00 ffffe283`f5762380 : nt!KiUpdateRunTime+0xc9 ffffd100`362e6dd0 fffff807`bb8702ad : ffffe283`f5762380 00000000`00000000 ffffe283`f5762430 fffff807`bc58dda0 : nt!KeClockInterruptNotify+0x96b ffffd100`362e6f50 fffff807`bbc7be9e : 00000000`d21be102 ffffe283`f5762380 ffffcf09`6171f260 0000024e`5c70b950 : nt!KiCallInterruptServiceRoutine+0x2ed ffffd100`362e6fb0 fffff807`bbc7c6ac : 0000024e`5c70a5c2 ffffcf09`6171f2e0 0000024e`5c70a5c5 000325c0`2a8bd979 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e ffffcf09`6171f260 fffff807`bb87deb5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c ffffcf09`6171f3f0 fffff807`bb87dde4 : fffff807`bc438680 ffffe284`1eece110 00000000`00000001 00000000`00000001 : nt!ExpAcquireSpinLockExclusive+0x45 ffffcf09`6171f420 fffff807`bba0d4bf : 00000000`00000000 ffffe284`216850c0 ffffe284`1eece200 ffffe284`216850c0 : nt!MiLockWorkingSetExclusive+0x54 ffffcf09`6171f450 fffff807`bbf89893 : ffffe284`1bfd9890 00000000`00000000 00000000`00000001 ffffe284`216850c0 : nt!MiGetVadWakeList+0x3f ffffcf09`6171f480 fffff807`bbf89786 : ffffe284`1bfd9890 ffffcf09`6171f530 00000000`0000000b 00000000`0000000b : nt!MiReleaseVadEventBlocks+0x43 ffffcf09`6171f4c0 fffff807`bba0cecb : ffffe284`1bfd9890 ffffe284`216850c0 ffffe284`1eece210 ffffe284`216850c0 : nt!MiRemoveVadCharges+0x112 ffffcf09`6171f550 fffff807`bbebd4fd : 00000000`00000000 ffffcf09`6171f610 ffffe284`1bfd9890 00000000`00000000 : nt!MiFinishVadDeletion+0x183 ffffcf09`6171f5a0 fffff807`bba71d1c : 00000002`7ca10000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeleteVad+0x2d9 ffffcf09`6171f650 fffff807`bbf607b4 : ffffe284`00000000 00000000`00000000 00000000`0027ca10 fffff807`bb84df97 : nt!MiFreeVadRange+0xc8 ffffcf09`6171f6b0 fffff807`bbf60367 : ffffe284`216850c0 ffffcf09`6171f800 00000002`00008000 00000000`00000000 : nt!MiFreeVirtualMemory+0x25c ffffcf09`6171f740 fffff807`bbf6018d : 00000000`00000000 00000000`0000001e ffffae07`f94b0000 00000000`341ffb60 : nt!MmFreeVirtualMemory+0x1a7 ffffcf09`6171f860 fffff807`6286eba2 : 00000000`00000000 00000000`00000056 ffffcf09`6171f8f0 00000000`00601802 : nt!NtFreeVirtualMemory+0x8d ffffcf09`6171f8c0 00000000`00000000 : 00000000`00000056 ffffcf09`6171f8f0 00000000`00601802 ffffcf09`6171f910 : 360Hvm64+0x1eba2 SYMBOL_NAME:360Hvm64+1eba2MODULE_NAME: 360Hvm64IMAGE_NAME:360Hvm64.sysSTACK_COMMAND: .process /r /p 0xffffe284216850c0; .thread 0xffffe2844315b080 ; kbBUCKET_ID_FUNC_OFFSET:1eba2FAILURE_BUCKET_ID:0x133_ISR_360Hvm64!unknown_functionOSPLATFORM_TYPE:x64OSNAME:Windows 10FAILURE_ID_HASH:{9006ed43-9cd3-628f-18ab-f4969336ae4b}Followup: MachineOwner --------- 您好，您蓝屏dump应该还在附件内，没有上传成功，您重新上传一下 附件在这里
页:
[1]